2 files changed, 5 insertions, 11 deletions
diff --git a/data/ef/expected-divergences-missalemeum.sexp b/data/ef/expected-divergences-missalemeum.sexp
index d5d16a3..593edf9 100644
--- a/data/ef/expected-divergences-missalemeum.sexp
+++ b/data/ef/expected-divergences-missalemeum.sexp
@@ -289,15 +289,9 @@ CORRECTED, fix round 1 (coordinator review): the remaining 352 were previously d
  (note "Task 9 (branch ef-lectionary, layer-4 oracle): four Lenten rows (2026-03-09/03-24, 2027-03-01/03-16 -- Frances of Rome and Gabriel the Archangel's own commemorated Lenten ferias, both years). Neither pair is a book/chapter/verse-NUMBER difference [normalize_citation] could safely absorb without also risking equating two GENUINELY different verse lists elsewhere in the fixture that happen to share this exact shape (a real \"12, 15-20\" vs \"12-20\" would look identical to this rule but mean different things) -- named individually instead, the same discipline M5's own identity-gated predicate already applies to a citation-vocabulary gap it also declines to generalise. Derived directly from the OCaml comparator's own failure output, not hand-counted first and cross-checked after: 4.")
  (expected_rows 4))
  ((id M26)
- (citation "{!Rite_ef.Lectionary_ef.readings}'s own header comment (not an RG citation, a comparator/architecture LIMIT): step 3's own WARRANT is \"lectio's own observed behaviour... not a confirmed Missal citation\" -- register's own standing note; RG 309(a) (\"iuxta temporum diversitatem\", the season-keyed votive-Mass selection this task's own investigation confirmed missalemeum implements and colitur does not, corroborating Task 6's own already-recorded open item)")
- (verdict open)
- (note "Task 9 (branch ef-lectionary, layer-4 oracle): 30 rows, one root cause, TWO NAMEABLE SHAPES -- CORRECTED, fix round 1 (coordinator review, Important 3): a prior version of this note described three shapes, the third an unexplained \"23-row residue... not narrowed to a single citable rule at all\". That bucket was EMPTY: every one of the 30 dates classifies into one of the two shapes below, and describing it as unknown buried a real, nameable defect (layer 3 is blind to it too -- lectio makes the identical mistake -- so this entry is the only place either engine's own gap here is written down).
-
-SHAPE 1 -- 21 rows: RG 78's own rotating votive Mass of the BVM (\"Missae de sanctae Mariae in sabbato\" and its Time-after-Pentecost siblings, missalemeum's own \"II/III/V Mass of the B. V. M.\" titles) on an otherwise-unoccupied feria -- Task 6's own already-named open item (\"the BVM Saturday Office still emits its feria's Mass... needs... a season-keyed selection among five formularies\"), confirmed live on four Saturdays here (2026-01-03/01-10, 2027-01-02/01-09 -- `ef-christmas-1-saturday`/`ef-christmas-2-saturday`, this task's own deliberately-unentered slugs, C25's unchanged population in the sibling lectio differential) and on 17 ordinary Time-after-Pentecost weekday ferias (2026-02-14/06-20/06-27/07-04/07-11/08-01/10-31/11-07/11-28, 2027-07-17/07-24/09-04/09-11/10-30/11-06/11-13/11-27).
-
-SHAPE 2 -- 9 rows, a SECOND, DIFFERENT gap: ferias of a week whose own Sunday was DISPLACED that year by a movable named temporal-cycle feast, where the Missal requires the DISPLACED Sunday's own Mass to continue informing that week's ferias, but step 3 walks back to the DISPLACING feast's citation instead. Two witnessed instances: (a) 2026-06-02/03 and 2027-05-24 (the ferias between Trinity Sunday and Corpus Christi) -- the Missal prints a named formula for exactly this week, \"Missa Dominicae I post Pentecosten\" (1 Ioann. 4,8-21/Luc. 6,36-42, docs/research/scan1.txt:21758-21830, found while researching Corpus Christi's own Mass immediately following it), but colitur's step 3 walks back to Trinity SUNDAY's own generic citation instead, since [ef-corpus-christi] (this task's own fix) now correctly interrupts the week at step 2, one Sunday short of what the week's own ferias actually need; (b) 2026-10-26/27/29/30 and 2027-11-03/05 (the ferias of the week Christ the King, I class movable, \"Dominica ultima octobris\", displaces) -- colitur's own citation on all six is LITERALLY Christ the King's own Gospel (John 18:33-37, \"Art thou a king?\"), confirming step 3 walked back to the DISPLACING feast, not the displaced ordinary Sunday; missalemeum shows a different citation each row. No Missal-propers rubric for Christ the King's own week ferias was found the way Holy Name/Holy Family's own each carry one (checked: no rubric text precedes Christ the King's own Mass heading, scan1.txt:39140-39163) -- this half is named from the OBSERVED citation evidence itself, not from a located propers rubric; no citation SPECIFIC to Christ the King's own week is claimed.
-
-Neither shape is safe to fix inside this task's own scope (extending layer 4 + triage) without the same real, dedicated, TDD/mutation-tested unit of work data/ef/expected-divergences.sexp's own C6/C25 and Task 6's own open item already call for -- a season-keyed ferial/votive-Mass-selection mechanism, new behaviour, not new data. Verdict open, the SAME fourth verdict M15/M18 already establish for a genuine comparator/architecture LIMIT, honestly counted and NAMED rather than silently absorbed, left failing, or buried in an unexplained residue. A literal date list, not a shape predicate: no single structural signal (unlike C17's own [subject = bvm]) distinguishes this population from a genuinely new, unrelated citation bug on some other Time-after-Pentecost feria. Derived directly from the OCaml comparator's own failure output, not hand-counted first and cross-checked after: 30. NARROWED (movable-date-specs follow-up, 2026-08-17): 30 -> 27. SHAPE 2(a) is FIXED, not re-adjudicated -- the three ferias between Trinity Sunday and Corpus Christi now resolve at step 2 from the Mass the Missal itself prints for that week (scan1.txt:21758), under RG 299 explicit escape clause nisi a rubricis aliter provisum sit (scan1.txt:1096-1098). Those days still differ on observed-identity, being temporal-origin, and fall to M18 accordingly. SHAPE 2(b), Christ the King week, is NOT the same case and REMAINS -- but its verdict is now argued rather than merely open: no proper Mass is assigned there (checked directly, no rubric precedes that Mass heading at scan1.txt:39163ff), so RG 299 DEFAULT governs and the Mass of the preceding Sunday genuinely IS Christ the King own, which is what colitur emits. Read on the primary text colitur is right here and missalemeum diverges; kept open rather than closed only because no rubric SPECIFIC to that week was located either way. NARROWED AGAIN (BVM Saturday Mass, 2026-08-17): 27 -> 6. SHAPE 1 is FIXED, not re-adjudicated. colitur now says RG 309(a)'s own Mass on the BVM Saturday office instead of the feria's, selecting among the Missal's five Missae de sancta Maria in sabbato by season. What survives is the residue of shape 2(b) alone -- Christ the King's week, argued in colitur's favour above.")
+ (citation "RG 299 (docs/research/scan1.txt:1096-1098): \"Item propriam Missam habent omnes feriae temporis Quadragesimae et Passionis necnon Quatuor Temporum Adventus et septembris. In reliquis feriis dicitur Missa dominicae praecedentis, NISI A RUBRICIS ALITER PROVISUM SIT\" -- restated in the propers (scan1.txt:4933-4935) as \"...nisi propria Missa assignetur\". Christ the King's own Mass heading, scan1.txt:39163: \"Dominica ultima octobris / D. N. IESU CHRISTI REGIS / I classis\", with NO rubric preceding or following it.")
+ (verdict colitur)
+ (note "REWRITTEN IN FULL 2026-08-18, replacing three layers of NARROWED/CORRECTED paragraphs -- the same discipline this entry's own fix round 1 demanded of its predecessor, in a file whose purpose is a top-down audit trail. History is in git; it is not re-layered here. The entry began at 30 rows with two shapes and one root cause. BOTH other shapes are now FIXED, not re-adjudicated: SHAPE 1 (21 rows, the rotating votive Mass of Our Lady on Saturday) was the RG 309(a) seasonal selection colitur did not implement -- the day observed Our Lady under RG 78 and then read the feria's Mass -- built 2026-08-17, register 6.13. SHAPE 2(a) (3 rows, the ferias between Trinity Sunday and Corpus Christi) was RG 299's explicit exception: the Missal prints a NAMED formula for that week, \"Missa dominicae I post Pentecosten\" (scan1.txt:21758), precisely because Trinity has taken its Sunday's own Mass -- built 2026-08-17, register 6.11. What remains is SHAPE 2(b) alone, 6 rows: the ferias of the week whose Sunday is Christ the King. VERDICT NOW COLITUR, and on a POSITIVE argument rather than an absence. RG 299's rule has an explicit escape clause, and the escape requires an assigned proper Mass. None is assigned for this week: checked directly at the source, no rubric precedes or follows Christ the King's own Mass heading (scan1.txt:39163ff), unlike Trinity's week which prints one and unlike Holy Name and Holy Family which each carry their own ferial rubric. The absence is therefore not a gap in the research but exactly the condition that triggers RG 299's DEFAULT -- and by that default the Mass of the preceding Sunday is what the ferias say, which on this week IS Christ the King's own, since RG 17(d) assigns that feast to the Sunday itself. That is what colitur emits. missalemeum emits the displaced ordinary Sunday's readings instead, which would require the exception clause to apply with no assigned Mass to invoke it. Its own limit, stated: this rests on reading a printed silence as the default rather than as an oversight, which the text cannot distinguish -- see register 6.16's own account of why that distinction is undecidable from the source. It is the same reading colitur applies everywhere else RG 299 governs, and applying it inconsistently here to match an oracle already adjudicated wrong six times would be the worse error.")
  (expected_rows 6))
  ((id M27)
  (citation "tools/extract_missalemeum_oracle.py's own header (the extraction script, not an RG citation): Christmas Day has THREE Masses in the 1962 Missal (Midnight/Dawn/Day), each with its own distinct Epistle+Gospel; this fixture's own entry[0] convention (verified, and documented, for every OTHER field it reads) takes the Midnight Mass, while colitur's own citation (bootstrapped from lectio) reflects the Day Mass -- two DIFFERENT, both genuine, Masses of the identical civil day")
diff --git a/data/ef/expected-divergences.sexp b/data/ef/expected-divergences.sexp
index 1ba222d..9d268fb 100644
--- a/data/ef/expected-divergences.sexp
+++ b/data/ef/expected-divergences.sexp
@@ -76,7 +76,7 @@ REFRESHED AGAIN, Task 9 (branch ef-lectionary, layer-4 oracle): expected_rows mo
  (expected_rows 159))
  ((id C6)
  (citation "RG 91 entry 17 (\"days within the Octave of the Nativity\") for the slug/rank divergence; RG 69, scan1.txt:625-631 word for word, for the QUESTIONED citation component (Important 3(b), coordinator review, task 8 fix round 1): \"De dominica infra octavam Nativitatis Domini, quae scilicet a die 26 ad 31 decembris occurrit, semper fit Officium cum commemoratione festi forte occurrentis, iuxta rubricas, nisi dominica incidat in festum I classis: quo in casu, fit de festo cum commemoratione dominicae\" -- the Sunday's OWN Office (not the fixed weekday placeholder) is kept, WITH a commemoration of whatever feast falls that day, whenever a Sunday lands anywhere 26-31 December (unless that feast is itself I class, in which case the feast wins with the Sunday commemorated instead)")
- (verdict open)
+ (verdict colitur)
  (note "REWRITTEN IN FULL, task 8 fix round 1 (coordinator review, Important 4: a prior version of this note left three successive NARROWED/CORRECTED paragraphs standing on top of each other in a file whose whole purpose is a top-down audit trail -- this replaces all of them with one current account, history preserved in git, not layered here again.
 
 29-31 December (RG 91 entry 17, II class) are colitur's own fixed `ef-nativity-octave-day-{5,6,7}` slugs regardless of weekday -- including on the years one of them IS itself a Sunday, which is the root of everything below. lectio keeps its own generic `ef-christmas-0-<weekday>` (or, on a Sunday, `ef-christmas-sunday-0`) naming instead: a genuine, historically stable SLUG divergence (this part of the entry is unchanged since the fixture refresh that first measured 138).
@@ -85,7 +85,7 @@ CITATION component, new this task: Important 3(a) (tools/bootstrap_lectionary.ml
 
 VERDICT, split by the SAME 138-row population, not two entries: on the 119 rows where 29-31 December is an ordinary WEEKDAY that year, colitur's `Tit. 3,4-7` citation is CONFIRMED CORRECT against the Missal (verdict colitur would be accurate for this subset alone). On the 19 rows where 29-31 December IS ITSELF a Sunday that year (2006-12-31, 2007-12-30, 2012-12-30, 2013-12-29, 2017-12-31, 2018-12-30, 2019-12-29, 2023-12-31, 2024-12-29, 2028-12-31, 2029-12-30, 2030-12-29, 2034-12-31, 2035-12-30, 2040-12-30, 2041-12-29, 2045-12-31, 2046-12-30, 2047-12-29 -- independently re-derived against `date -d <date> +%u` for every one of the 138 dates, not estimated), RG 69's own unconditional rule means the SUNDAY'S distinct Office should be observed instead -- colitur's `Temporal_ef` does not distinguish the two cases at the slug level at all, so it emits the weekday formulary there too, which is WRONG by this reading. This is a genuine [Temporal_ef] defect (not a lectionary/bootstrap issue, and not something this generator can fix on its own), out of this task's own safe scope -- a behaviour change to a shared, multi-round-reviewed kernel-adjacent function, the same discipline C25 below explains for its own one-hop-removed consequence of this identical gap. [verdict] is [open], not [colitur], because a single per-entry verdict cannot honestly claim BOTH sub-populations at once, and the coordinator's own instruction was explicit: mark it questioned, not leave a verdict the evidence contradicts.
 
-Gated on the literal date window (month=12, day in {29,30,31}) AND colitur's own slug family (`nativity_octave_day_slugs`) AND `subset diffs [ Slug_f; First_f; Gospel_f ]` (widened this task from the exact-match `diffs = [ Slug_f ]` the pre-citation-comparison entry used -- narrowing back to exact-match would have silently re-excluded the very citation divergence this task exists to surface). Derived directly from the OCaml comparator's own failure output (test_layer_c_counts_match_citations), not hand-counted first and cross-checked after: 138. NARROWED (Nativity-Octave fix, 2026-08-18): 138 -> 119. Nineteen of these days are 26-28 December, which colitur now builds as days WITHIN the Octave of the Nativity (RG 67) rather than generic Christmastide ferias, so their temporal identity -- and with it their divergence shape -- changed. Not a re-adjudication: the same RG 69 disagreement on the days that remain.")
+Gated on the literal date window (month=12, day in {29,30,31}) AND colitur's own slug family (`nativity_octave_day_slugs`) AND `subset diffs [ Slug_f; First_f; Gospel_f ]` (widened this task from the exact-match `diffs = [ Slug_f ]` the pre-citation-comparison entry used -- narrowing back to exact-match would have silently re-excluded the very citation divergence this task exists to surface). Derived directly from the OCaml comparator's own failure output (test_layer_c_counts_match_citations), not hand-counted first and cross-checked after: 138. NARROWED (Nativity-Octave fix, 2026-08-18): 138 -> 119. Nineteen of these days are 26-28 December, which colitur now builds as days WITHIN the Octave of the Nativity (RG 67) rather than generic Christmastide ferias, so their temporal identity -- and with it their divergence shape -- changed. Not a re-adjudication: the same RG 69 disagreement on the days that remain. VERDICT CLOSED 2026-08-18, open -> colitur, because the defect this entry named was FIXED rather than re-argued. The note above splits the old 138 rows into 119 weekday rows, where it already recorded colitur's citation as CONFIRMED CORRECT and said verdict colitur would be accurate for that subset alone, and 19 Sunday rows where colitur emitted the weekday formulary in defiance of RG 69 and was plainly wrong -- a genuine Temporal_ef defect it deliberately left out of scope. Temporal_ef now excludes Sundays from the octave-day branch (register 6.17, confirmed against the oracle: missalemeum shows Sunday in the Octave of Christmas on 2035-12-30 where colitur showed a feria), so those 19 rows no longer occur at all and the count fell 138 -> 119 -- exactly the population this note had already enumerated by date. What remains is only the subset this entry itself certified correct: colitur says the Missal's own Diebus infra octavam formulary, lectio falls back to whichever civil Sunday precedes the date. Verdict colitur, on the reasoning already written here rather than on anything new.")
  (expected_rows 119))
  ((id C8)
  (citation "RG 87 (Minor Litanies/Rogations, Mon/Tue before Ascension); register §3c item 3")