colitur.git/test, branch v0.4.0

fix(ef): the Assumption and St Lawrence vigils are violet (RG 128)

2026-08-18T09:36:33Z

RG 128, transcribed in the rules register since 2026-08-11, gives violet to "vigils of II and III class outside Paschaltide". The Vigil of the Assumption (14 August, II class) carried White and the Vigil of St Lawrence (9 August, III class) carried Red. Both are outside Paschaltide, so both are violet. The Ascension's vigil is untouched: it is the one II-class vigil inside Paschaltide and was already correctly white. The rule had been sitting in the register, disagreeing with the shipped data, since before the data was bootstrapped. It was invisible because colitur, lectio and missalemeum all carried the same two wrong colours -- colitur was bootstrapped from lectio, lectio's ini is generated from missalemeum, and missalemeum uses Divinum Officium's data files. Three sources agreeing is one source counted three times, and the differential and the oracle both went green on the shared error. It surfaced only against witnesses outside that tree: a published 1962 Ordo flagged the Assumption's, and O'Connell, The Celebration of Mass 4th ed. (1964), section 4(c) and footnote 169, gave the general rule and with it St Lawrence's, which the Ordo omits entirely. Two golden pins added, in years where each vigil is actually observed rather than impeded. The divergence this creates against every DO-lineage source is cited in both allow-lists: C37 (lectio, 77 rows -- 92 possible minus 15 where the vigil falls on a Sunday) and M29 (missalemeum, 3 rows in 2026-2027 and 2 in each of 2035 and 2038). Both gated on the exact slugs or dates and on colour alone, so any other divergence on those days would still surface. Also recorded, no code change: rose on Gaudete and Laetare stays. RG 131 is permissive ("adhiberi possunt") and the Ordo prints violet, so the colour field carries a permission rather than a requirement on those two Sundays a year -- a decided position now, not an unexamined one.

fix(ef): Good Friday is black, not violet (RG 128(b), RG 132)

2026-08-18T09:26:04Z

RG 128(b)'s own exception list, transcribed in the rules register and primary-source-verified since Task 16, excepts "Actione liturgica feria VI in Passione et Morte Domini usque ad Communionem exclusive" from the violet that otherwise runs from Septuagesima to the Easter Vigil. RG 132 assigns black there. The register recorded this as an acknowledged gap rather than a disputed reading -- the code comment beside the Holy Thursday exception says so in as many words -- and it is closed here. Found by two witnesses outside the Divinum Officium lineage that colitur, lectio and missalemeum all share: O'Connell, The Celebration of Mass, 4th ed. (1964), revised throughout to the Codex Rubricarum (1960) and the 1962 Missal, and a published 1962 Ordo. Both say black. So does missalemeum's own colour set, which orders the day "bv". The rubric is per-action ("usque ad Communionem exclusive") and the model emits one colour per day; black is the day's principal one, the same acknowledged limit RG 126's Palm Sunday blessing already carries. Blast radius: one day per year, colour only, across the whole 1583-9999 domain. Two golden pins re-pinned. Good Friday's 46 differential rows leave C23 for a new C36 gated on the exact triple [First_f; Gospel_f; Colour_f], so C23's own exact-pair gate still means what its note says for its remaining four days: 184 + 46 = 230, no residue, both counts from the comparator rather than hand-counted.

fix(ef): days within the Octave of the Nativity, and RG 69 for 29-31 Dec

2026-08-18T08:21:39Z

M11 was the one entry in the missalemeum allow-list adjudicated against colitur, and it was right to be. The calendarium directs "Com. octavae Nativitatis" under each of 26, 27 and 28 December (LT.txt:5454-5459) and RG 109(c) makes a commemoration of the days within the Octave privileged. colitur emitted none. The cause was a reasoning error stated in Temporal_ef's own comment: "26-28 Dec are Stephen, John and the Innocents, hence sanctoral". Their office is sanctoral -- those II-class feasts win the day -- but they remain days WITHIN the Octave (RG 67, "Dies infra octavam sunt II classis"), and colitur built them as generic Class4 ferias. With no octave-day candidate there was nothing for the feast to be commemorated over. Building days 2-4 exactly as days 5-7 always were makes the commemoration fall out of the existing machinery rather than needing a special case: the feast wins on rank, the octave day loses, RG 109(c) privileges it, RG 111(c)'s single slot goes to it. A second, independent defect surfaced while fixing it. The octave-day branch covered 29-31 December unconditionally, so a Sunday falling there got a feria identity -- where RG 69 says a Sunday occurring 26-31 December SEMPER keeps its own office and commemorates the feast. Confirmed against the oracle rather than argued: missalemeum shows "Sunday in the Octave of Christmas" on 2035-12-30, a Sunday, where colitur showed a feria. Both named and anchors now exclude Sundays; anchors had asserted the octave slugs unconditionally and was wrong the same way. Blast radius, full sweep against the pre-change binary: 25251 days, every one 26-31 December, exactly two shapes, zero unclassified -- 21653 carrying an octave-day slug and 3598 that are all Sundays, the RG 69 correction. Allow-lists: M11 closed and removed. C6 narrowed 138 to 119, nineteen of its days having changed temporal identity rather than verdict. M15 widened 18 to 22 -- both streams now commemorate the octave, but the candidate is temporal-origin and carries no English name to match against missalemeum's own, this entry's documented limit on four more dates. Stated rather than glossed: this trades a substantive divergence, colitur omitting a commemoration the Missal directs, for a comparator limit, the commemoration existing but not being name-matchable. That is a real improvement, but what the oracle now proves is that both streams commemorate something on those days; the identity rests on the rubric and the calendarium. Register: section 6.17.

test(oracle): compare commemorations in the live windows

2026-08-18T07:59:48Z

Commemorations were checked against an oracle in the 2026-2027 fixture alone -- 227 days out of roughly 968 000 commemoration-bearing days in the domain, about 0.02%, and by some distance the thinnest axis in the project. Layer 3's 16 801 days compare none of them and never can: lectio's trailing "+slug" tokens are its losing candidates, not an RG 111 admitted set. About a third of all days carry a commemoration and admit is the most intricate code in the engine, so the gap was worth closing. 2035 and 2038 now compare presence, count and identity, reusing the 2026-2027 comparator's own identity_diff with the same limits: a sanctoral-origin commemoration resolves by colitur's English name, a temporal-origin one cannot and is reported as a counted, classified outcome rather than a silent pass. Observed-identity stays out deliberately -- that is M18's separate limit and folding it in would flood these windows with a class that says nothing about commemorations. 36 differing rows across 730 days, every one classified. The great majority of commemoration days agree, which is the headline. Four rows are not calendar differences at all but name forms -- colitur's "The Seven Sorrows of the Blessed Virgin Mary" against the oracle's "For Our Lady of the Seven Sorrows", "The Major Litanies" against "Pro rogationibus" -- which is this month's new entities appearing correctly in windows that had never seen them. One finding is genuinely new. On 2038-06-02 the Ascension Vigil admits one commemoration under RG 111(c) and two candidates compete: rogation-wednesday and sts-marcellinus-peter-erasmus. Both are Commemoration_only, so neither has a row in RG 91's table, band returns unclassified for both, RG 113 has nothing to order by, and admit falls through to its alphabetical slug tie-break -- which decides the day. missalemeum keeps the saints. That tie-break was already documented as existing only between two Commemoration_only candidates; this is its first live, externally-witnessed instance, and the decision is made by slug alphabet, which is arbitrary and not rubrical. There may be a real rule going unused: RG 113's first sentence is "Commemoratio de Tempore fit primo loco", and a Rogation is arguably de Tempore -- which turns on whether the entry should carry subject Temporal rather than the Saint it inherited from the Major Litanies precedent, a question the movable-date-specs spec deferred as behaviourally inert and which demonstrably is not. Not decided here. Adopting whichever answer matches the oracle is exactly the reasoning this project refuses, so it is recorded and cited for a task that can weigh it on its own terms. Register: section 6.16.

feat(data): ship a worked example overlay calendar

2026-08-18T07:26:26Z

`--overlay` shipped last week with nothing to point at. The only example was a test fixture, explicitly labelled invented and living where no user would find it, so "colitur supports local calendars" was true but undemonstrated. data/ef/examples/diocesan-example.sexp is installed to /share/colitur/examples/ and is runnable documentation: every celebration in it is invented, with example- slugs that cannot collide, and its header explains the four directives, the three date shapes, and the field vocabularies before showing any of them. It demonstrates the range deliberately rather than the minimum: a fixed-date local patron with its own propers; a movable dedication on the first Sunday of October, I class because a church's own dedication anniversary is I class in that church and at III it would lose to the Sunday every year; an Easter-relative commemoration; an Edit raising a universal feast for local use; and a Suppress shown commented out, because suppressing a universal feast is a real liturgical act and an example should not invite it casually. Two things the header says plainly, since this is the one file that lets someone change what colitur computes: an overlay is applied ON TOP of the shipped calendar and never instead of it, and an overlay is applied, NOT validated -- the five test layers assert things about the shipped data and cannot vouch for a user's file. A test asserts it loads against the real EF rank vocabulary, still demonstrates at least four directives, and applies with NO diagnostics. The last matters most: a directive naming a slug the universal calendar lacks would warn, and an example that warns teaches the wrong lesson. It deliberately does not pin which days it produces -- those celebrations are invented, and pinning their dates would make an illustrative file behave like calendar data.

test(oracle): a third window, 2035, witnessing common-of-doctors

2026-08-17T20:38:01Z

Step 4's blind spot is now closed as far as the method allows. 2038 witnessed two of the five Common-routed saints; isidore-of-seville is the third and the last that any year in 2005-2050 can reach, being observed only in 2008, 2035 and 2046. He is also the only saint routing through common-of-doctors, so that Common had never been compared against any external source in any window. Three independent agreements on it: the scan (Commune Doctorum, scan1:41878ff, 2 Tim. 4, 1-8 / Mt. 5, 13-19), colitur, and missalemeum's own 2035-04-04 row. Asserted by date in its own test rather than folded into an aggregate count, so a regression there cannot hide. The remaining two saints are unreachable by construction, not for want of a fixture: gregory-the-great and patrick both sit in March and are impeded by Lent's privileged ferias in every one of the 46 years the differential covers. The blind spot is closed to its limit, not closed absolutely, and the register says so. The comparator is generalised rather than copied -- compare_live takes a fixture and a year -- so a fourth window would cost a fixture and a count list. 2035 differs on 3 days, both families pre-existing and already cited. 2035-04-02/03 are the Joseph/Annunciation transfer pair landing in the opposite order from missalemeum's: neither stream loses a feast, the sequence differs, which is C14's own RG 96 collision finally getting an oracle window. 2035-12-30 is the Sunday within the Christmas Octave against colitur's numbered octave-day slug, C6's family. Both are recognised by slug rather than by date, so a year exhibiting only half the shape would surface as unexplained rather than be quietly absorbed. 393 tests green with the exhaustive sweep. Register: section 6.15.

test(cli): the 3 January pin is a BVM Saturday, not a feria

2026-08-17T20:27:11Z

3 January 2026 is an unoccupied IV-class Saturday, so its office is Our Lady's and now its Mass is too -- the second of the Missal's five, assigned to Christmas through the Purification. The pin held the Christmastide feria's readings, which is what colitur said before RG 309(a) was implemented. Caught by make check on the 0.3.0 release, which is what that gate is for.

feat(ef): the votive Mass of Our Lady on Saturday (RG 309(a))

2026-08-17T19:45:47Z

RG 78's office has been built since ef-bvm-saturday: an otherwise unoccupied IV-class Saturday is de sancta Maria in sabbato, white, IV class. The Mass stayed the feria's, so the day observed Our Lady and then read Colossians on the parable of the weeds. That is M26 shape 1. RG 309(a) is the rule -- the Masses the Missal assigns "iuxta temporum diversitatem" -- and it prints five, each under its own season heading. All ten citations are transcribed from the scans with line numbers in the source. Masses II-V were confirmed twice, against the scan and against a live missalemeum capture of 2038 which names them and agrees on both readings. Mass I rests on the scan alone: no oracle year to hand has an Advent Saturday carrying this office. One witness where the others have two, and the code says so rather than blurring it. The mapping looked like the hard part and dissolved. The Missal's ranges are cut by civil dates and movable feasts, not by this rite's seasons -- II ends mid-season at the Purification, III spans four seasons. But measured against what a IV-class Saturday can actually be, it reduces to a seasonal mapping plus one date test at 2/3 February, with no Easter arithmetic at all: III's end to IV's start leaves the Triduum unassigned, unreachable because Holy Saturday is I class; IV's end to V's start leaves Pentecost week unassigned, also unreachable because that week's Saturday is an Ember Saturday. Time after Pentecost then begins exactly at Trinity, exactly where Mass V begins. Both gaps verified by sweep -- zero IV-class Saturdays in either across 2000-2059 -- not inferred. The office is identified structurally, never off the slug, which it deliberately shares with the ordinary feria: subject Bvm, IV class, Saturday. Blast radius: 87611 reading rows over the full domain, every one a Saturday. Allow-lists: M26 27 to 6, shape 1 gone, leaving only the Christ-the-King residue argued in colitur's favour last commit. The 2038 suite's BVM-SATURDAY-MASS class is removed rather than zeroed -- an id with no rows must not be declared. M18 355 to 376. C17 widened 397 to 445, taking its own Saturdays back from C1, C19 and C25, since one cause should not be filed under two ids; C31 89 to 103; C25 closed at 0 rows, its Holy-Name-week Saturdays now answered before step 3 is reached. Three unit tests pinned the old behaviour and are corrected rather than re-pinned: two asserted the day "keeps its ferial Mass", which was the honest thing to assert while this was unimplemented. The third still tests what it always did -- that step 4 refuses a temporal office -- and only what answers instead has changed. Register: section 6.13.

feat(ef): the Seven Sorrows of Passion Friday, and M16 reversed

2026-08-17T19:23:57Z

Not the II-class feast of 15 September, which colitur has had since the bootstrap, but the other Seven Sorrows: the movable commemoration of Passion Friday, of which colitur had no trace at all. The 1962 calendarium lists it at the foot of March, below the fixed dates, exactly where a movable entry belongs (LT.txt:5056): "Feria VI post dominicam I Passionis: Commemoratio septem Dolorum B. Mariae Virg." Note the word -- Commemoratio. Under the 1960 rubrics it is a commemoration, not a feast, so it can never win the day. Friday after Passion Sunday I is Easter-9, confirmed independently by both dates the oracle allow-list already disputed: Easter 2026 is 5 April and M16's date is 27 March; Easter 2027 is 28 March and M13's is 19 March. It could not be built before Date_spec grew Easter_offset -- the same wall Rogation Wednesday hit, and the second entity that work has now unblocked. M16 is re-adjudicated and its verdict REVERSED, from missalemeum to colitur. The entry existed because colitur admitted St John Damascene where missalemeum showed the Seven Sorrows, colitur having no candidate to admit. Both streams now name the Seven Sorrows and that mismatch is gone. What remains runs the other way, and the rubric is explicit: RG 111(d) admits TWO commemorations on a III-class day, RG 113 puts the seasonal one first, and RG 114 omits only what exceeds the number. 27 March 2026 is a III-class privileged Passiontide feria; colitur admits exactly two, the Seven Sorrows and John Damascene, a real III-class universal feast genuinely falling that day. missalemeum admits one and reports John Damascene as displaced, dropping a commemoration the rubric allows. That makes four divergences adjudicated colitur where missalemeum drops or mis-assigns something -- Monica's Epistle, Perpetua's Common, Christ the King's week, and this. Recorded as a pattern rather than four coincidences: the oracle stays a comparison instrument, but its error rate on adjudicated cases is no longer negligible. M13 is untouched and stays open: 19 March 2027 is a different dispute, whether Joseph is displaced from Passion Friday at all, and on a I-class day RG 111(a) admits one privileged commemoration which the feria takes. Blast radius, full 1583-9999 sweep against the pre-change binary: 7874 days, every one carrying the new commemoration, zero unclassified, line counts equal both sides. Register: section 6.12.

fix(lectionary): the week after Trinity says its own assigned Mass

2026-08-17T19:12:35Z

RG 299 located (scan1:1096-1098), which does two things at once. First it closes a standing gap: the ferial-Mass selection rule was recorded in the register as unconfirmed against the primary source, and step 3 said so in its own comment -- "lectio's own observed behaviour, not a confirmed Missal citation". It is confirmed now. "In reliquis feriis dicitur Missa dominicae praecedentis, nisi a rubricis aliter provisum sit", restated in the propers as "...nisi propria Missa assignetur". Second, that escape clause splits M26 shape 2 in half, which is why the shape was never resolvable as one thing. Shape 2(a), the week after Trinity, is fixed. Trinity is the temporal identity of its own Sunday, so a plain walkback lands on Trinity's Mass -- but the Missal prints a named formula for the following week, "Missa dominicae I post Pentecosten" (scan1:21758), precisely because the feast has taken that Sunday's own. Those ferias now resolve at step 2 from it and never reach the walkback. Shape 2(b), Christ the King's week, turns out not to be a bug at all. No proper Mass is assigned there -- checked directly, no rubric precedes that Mass heading (scan1:39163ff) -- so RG 299's default governs and "the Mass of the preceding Sunday" genuinely is Christ the King's own, which is what colitur emits and missalemeum does not. Kept open only because no rubric specific to that week was located either way; the verdict is now argued from the primary text rather than resting on oracle disagreement. No Thursday in the slug list: Corpus Christi is Easter+60, which IS that week's Thursday every year, so the ferial slug never exists. Found by the bootstrap's own reachability guard refusing to emit a key no Temporal_ef slug can match, not reasoned out in advance. Allow-lists: C35 opened (69 rows, verdict colitur -- lectio still walks back); C17 narrowed 406 to 397, nine Saturdays moving to C35 because they carry both a citation and a colour difference, with C35 gated to require the citation so a colour-only Saturday still falls to C17; M26 narrowed 30 to 27; M18 widened 352 to 355, the same three days keeping only their observed-identity difference. Register: section 6.11.