fix(ordo): correct L5/F3 misadjudication -- Cum Sanctissima, not a gap

data/ef/expected-divergences-lms.sexp's L5 (16 dates, LMS Ordo Gloria=true
vs colitur's false) and data/ef/expected-divergences-fiuv.sexp's F3 (6
dates, FIUV Te Deum=true vs colitur's false) were both misadjudicated as
colitur's own gap under an RG 302(b)/431(b) hypothesis. Both are wrong.

These are occurrence differences from the 2020 decree Cum Sanctissima,
which colitur excludes from its 1962 core by binding design (CLAUDE.md
decision 2). RG 303(b) ("dici potest tantum si occurrit dies liturgicus IV
classis") already prohibits 302(b) on the Class3 privileged ferias both
entries cover -- the original text quoted 303(b) but never followed it to
its conclusion. Decisively, the FIUV Ordo prints BOTH readings on the six
shared dates, separated by a literal "-VEL-" token: the primary, strict-
1962 reading (feria wins, sine Gloria, no Te Deum) matches colitur exactly;
the second, Cum-Sanctissima reading (saint kept, Gloria, Te Deum) matches
the LMS Ordo exactly.

F3 itself was never a real Te Deum finding: tools/extract_fiuv_ordo.ml's
extract_te_deum scanned each block unbounded for "Ad Mat.", so on these six
days -- whose primary office states no "Ad Mat." of its own -- it silently
read the second office's own Te Deum instead. Fixed with a new
split_at_alt_office, cutting every block at "-VEL-" before any field
extraction runs; the alternative is captured, not discarded, in a new
alt_te_deum field. A hard characterisation probe asserts the split fires on
exactly the six known dates.

Auditing for the same trap elsewhere (this is the third such manufactured
divergence in this project) found a related but narrower marker, "Vel (sec.
decretum <<Cum sanct.>>) Missa ...", offering an alternate Mass formulary
within a single office. It never corrupted Gloria/Credo (always stated
before the marker on all 20 real instances, confirmed by diff), only the
uncompared praef field; hardened defensively anyway, before it could ever
fire live. The LMS Ordo (all three editions) carries no equivalent
dual-print mechanism at all. expected-divergences-missalemeum.sexp's M27
is the same genus but was already correctly adjudicated, not touched.

Both allow-list entries are rewritten, not deleted: the original SHAPE/
CITATION/WHY-NOT-FIXED-HERE reasoning is preserved verbatim as a recorded,
superseded hypothesis, matching this project's own correction convention.
test_lms_ordo.ml's matching predicate is unchanged (the 16-date population
still fires, and always will, because it reflects a standing exclusion,
not a bug); only its citation comment is corrected. test_fiuv_ordo.ml's
F3-specific predicate/count assertion is removed, matching this file's own
prior F2/F4 closure discipline.

lib/ is untouched. dune test: 676/676. make check
(COLITUR_EXHAUSTIVE_SWEEP=1, full 1583-9999 domain): 678/678.

1 files changed, 114 insertions, 34 deletions

diff --git a/data/ef/expected-divergences-fiuv.sexp b/data/ef/expected-divergences-fiuv.sexp
index 6a40838..c8f1e21 100644
--- a/data/ef/expected-divergences-fiuv.sexp
+++ b/data/ef/expected-divergences-fiuv.sexp
@@ -41,6 +41,14 @@
 ; separate regression this same fix round found and reverted (a first
 ; attempt at "every Sunday says Te Deum" wrongly excluded Christ the
 ; King, caught by the LMS Ordo's own Gloria axis, 2024-10-27).
+;
+; F3 was ALSO found to be the same GENUS of extractor bug -- a different
+; PARSER shape (not a negation word, an unbounded scan reading a second,
+; "-VEL-"-separated printed office instead of the primary one) -- and is
+; likewise now CLOSED (l5-f3-readjudication task, 2026-08-22). See F3's
+; own rewritten entry below for the full account, including why the
+; original finding was misadjudicated as "colitur's own gap" rather than
+; recognised as an extraction defect from the start.
 
 ; F1 -- OPEN, adjudicated FOR colitur. Fired once: 2026-04-03, Good
 ; Friday.
@@ -108,39 +116,111 @@
 ; itself rather than on "every other authority disagrees" -- which is the
 ; stronger footing, and the one this project's own standard asks for.
 
-; F3 -- OPEN, single-witnessed, colitur's own possible gap (Te Deum
-; axis). Fires 6 times, every one of the six dates
-; data/ef/expected-divergences-lms.sexp's own L5 already found for
-; Gloria: 2026-03-06/07/09/12/21/24, a privileged Lenten or Passiontide
-; feria (Class3, RG25) whose own office is impeded and carries exactly
-; one commemoration of a Class3 saint. colitur's [te_deum] reads [false]
-; (a plain ferial office by every branch {!Rite_ef.Rubrics_ef.te_deum}
-; checks); FIUV reads [true] in all six -- confirmed directly against
-; the raw pdftotext dump, not merely the fixture: e.g. 12 March, "Ll. 1a
-; et 2a (= 2a+3a) de Scr. occ., 3a de festo, Te Deum." -- a genuine,
-; unnegated "Te Deum" (neither of the two negative phrasings the
-; extractor now checks for), so this is NOT the same failure mode F2/F4
-; were.
+; F3 -- CLOSED, MISADJUDICATED, NOW FIXED AT THE SOURCE
+; (l5-f3-readjudication task, 2026-08-22). This entry previously read
+; "OPEN, single-witnessed, colitur's own possible gap" -- WRONG, and not
+; a Te Deum question at all: it was tools/extract_fiuv_ordo.ml's own
+; [extract_te_deum] reading the WRONG PRINTED OFFICE on these six dates.
+;
+; THE ORIGINAL, SUPERSEDED FINDING -- preserved below verbatim, the same
+; "retain the wrong reading and say why it was wrong" convention this
+; file's own F1 history and data/ef/expected-divergences-lms.sexp's own
+; L3/L5 already establish, NOT deleted: fires 6 times, every one of the
+; six dates data/ef/expected-divergences-lms.sexp's own L5 already found
+; for Gloria: 2026-03-06/07/09/12/21/24, a privileged Lenten or
+; Passiontide feria (Class3, RG25) whose own office is impeded and
+; carries exactly one commemoration of a Class3 saint. colitur's
+; [te_deum] reads [false] (a plain ferial office by every branch
+; {!Rite_ef.Rubrics_ef.te_deum} checks); FIUV reads [true] in all six --
+; confirmed directly against the raw pdftotext dump, not merely the
+; fixture: e.g. 12 March, "Ll. 1a et 2a (= 2a+3a) de Scr. occ., 3a de
+; festo, Te Deum." -- a genuine, unnegated "Te Deum" (neither of the two
+; negative phrasings the extractor now checks for), so this is NOT the
+; same failure mode F2/F4 were. (This description of what the raw text
+; SAYS is still accurate -- the error was reading it from the wrong
+; PLACE in the block, below, not misreading the words themselves.)
+;
+; CITATION [SUPERSEDED, see THE CORRECTION below]: the same
+; n.302(b)/RG431(b) text L5 already cites (LT.txt -- a MISSAL rubric, not
+; a Breviary one, so its literal text governs the MASS's own Gloria, not
+; Matins' Te Deum) does not directly license this finding at all --
+; 237/238 (the BREVIARY rubric {!Rite_ef.Rubrics_ef.te_deum} actually
+; implements) has no clause naming a commemoration as grounds for Te
+; Deum. What this finding suggested, not established: the DIVINE OFFICE
+; may treat a commemorated day more generously than the MASS does for
+; exactly this shape (a commemorated saint's own lessons are read at
+; Matins even on an impeded day, which could plausibly extend to Te Deum
+; by an unwritten or unlocated convention) -- genuinely speculative,
+; offered as a research lead for a follow-on task, not a citation this
+; entry treated as settled. (There was no such convention: see below.)
+;
+; WHY NOT FIXED HERE [SUPERSEDED]: SINGLE-WITNESSED (the LMS fixtures
+; never captured Te Deum at all, so there is no second Ordo to
+; corroborate this shape the way the Sacred-Triduum/BVM-Saturday/vigil
+; findings elsewhere in this task were cross-checked). Fixing it would
+; need the SAME kernel signature widening L5 already declines for the
+; identical reason (`~commemorations` on {!Colitur_kernel.Rite.t.gloria},
+; and by extension a parallel widening of [te_deum] if the two were ever
+; to diverge in their own inputs) -- out of a task briefed to follow
+; creed's existing seam exactly. Left OPEN for the same follow-on task L5
+; recommends. (No kernel change was ever needed -- the bug was entirely
+; inside the EXTRACTOR, tools/, never inside lib/.)
+;
+; THE CORRECTION, in full (l5-f3-readjudication task, 2026-08-22): FIUV
+; prints a "-VEL-" ("or") separator on these exact six dates, dividing
+; each day's block into a PRIMARY, strict-1962 office (the feria wins,
+; "sine Gloria", the saint commemorated, no "Ad Mat." lessons mentioned
+; at all -- an ordinary privileged feria's Matins needs no special note)
+; and a SECOND, complete alternative office under the 2020 decree Cum
+; Sanctissima (the saint kept outright, "Off. ordinarium", with its OWN
+; "Ad Mat. ... Te Deum" lessons). tools/extract_fiuv_ordo.ml's own
+; [extract_te_deum] scanned the WHOLE block for "Ad Mat." unbounded, so
+; on these six days it silently read the SECOND office's own Te Deum
+; instead of the PRIMARY's -- manufacturing a same-day contradiction with
+; colitur that this entry first recorded as "colitur's own possible
+; gap". There was never a genuine Office-vs-Mass question, and no
+; DIVINE-OFFICE convention naming a commemoration as grounds for Te
+; Deum: the "unnegated Te Deum" the original finding quoted was real
+; text, just read from the wrong printed office.
+;
+; Fixed in tools/extract_fiuv_ordo.ml's own [split_at_alt_office] (see
+; its own citation, module header point 5): every field extractor now
+; reads the PRIMARY office only, cut at the "-VEL-" token before any
+; field extraction runs. [te_deum] now reads [None] (unresolved) on
+; these six dates -- the primary office states no "Ad Mat." of its own,
+; so there is nothing to positively confirm either direction from, the
+; same meaning [None] already carries elsewhere in this fixture. The
+; alternative office's own Te Deum is captured, not discarded, in a new
+; [alt_te_deum] field (still [true] on all six -- the extraction was
+; never wrong about what the SECOND office says, only about which
+; office [te_deum] itself should report).
 ;
-; CITATION: the same n.302(b)/RG431(b) text L5 already cites (LT.txt --
-; a MISSAL rubric, not a Breviary one, so its literal text governs the
-; MASS's own Gloria, not Matins' Te Deum) does not directly license this
-; finding at all -- 237/238 (the BREVIARY rubric {!Rite_ef.Rubrics_ef.
-; te_deum} actually implements) has no clause naming a commemoration as
-; grounds for Te Deum. What this finding suggests, not yet established:
-; the DIVINE OFFICE may treat a commemorated day more generously than the
-; MASS does for exactly this shape (a commemorated saint's own lessons
-; are read at Matins even on an impeded day, which could plausibly extend
-; to Te Deum by an unwritten or unlocated convention) -- genuinely
-; speculative, offered as a research lead for a follow-on task, not a
-; citation this entry treats as settled.
+; VERIFIED, not merely argued: re-extracted from the SAME pdftotext dump
+; (SHA-256 of the source PDF unchanged, fixture header above). Exactly 6
+; of 400 rows changed, every one Te Deum true->unresolved, on precisely
+; these six dates and no others (a hard characterisation probe in
+; tools/extract_fiuv_ordo.ml now asserts this population is EXACTLY
+; these six, not merely observed once). Gloria, Credo, class_, title and
+; praef are UNCHANGED on all 400 rows, confirmed by a direct diff of the
+; fixture before and after -- those fields were already correctly
+; bounded to the primary office (a Vespers-line token always intervened
+; before "-VEL-" on all six real instances), so this was never a
+; Gloria-axis bug, consistent with F1 and with L5's own six-date subset
+; agreeing with colitur throughout.
 ;
-; WHY NOT FIXED HERE: SINGLE-WITNESSED (the LMS fixtures never captured
-; Te Deum at all, so there is no second Ordo to corroborate this shape
-; the way the Sacred-Triduum/BVM-Saturday/vigil findings elsewhere in
-; this task were cross-checked). Fixing it would need the SAME kernel
-; signature widening L5 already declines for the identical reason
-; (`~commemorations` on {!Colitur_kernel.Rite.t.gloria}, and by extension
-; a parallel widening of [te_deum] if the two were ever to diverge in
-; their own inputs) -- out of a task briefed to follow creed's existing
-; seam exactly. Left OPEN for the same follow-on task L5 recommends.
+; VERDICT: colitur correct; the LMS Ordo (L5) and the FIUV Ordo's own
+; "-VEL-" alternative both, correctly, describe the SAME Cum-Sanctissima
+; calendar colitur excludes by binding design (CLAUDE.md decision 2).
+; See L5's own rewritten entry (data/ef/expected-divergences-lms.sexp)
+; for the full account, including the "-VEL-" dual printing quoted there
+; as the decisive evidence for BOTH entries. NOT an active
+; machine-checked [id] entry, matching this file's own F1/F2/F4
+; precedent -- the real enforcement was test_fiuv_ordo.ml's own
+; [is_f3_lenten_commemoration] predicate and [f3_count] assertion, BOTH
+; REMOVED (same task): with the extractor fixed, this shape produces no
+; mismatch at all any more (matched by the general [None]-skips-
+; comparison branch every other unresolved-Te-Deum row already uses),
+; so a dedicated predicate/count pin would be dead code -- the same "an
+; entry that stops firing is a real change, not silently absorbed"
+; discipline data/ef/expected-divergences-lms.sexp's own L1/L3 closures,
+; and this file's own F2/F4 closure, already establish.