docs: a name that matched no scan, and a blocker that was not real

Two corrections from the fix-round review, both to the record.

"Sabbato Sancto" is attested zero times in either photographic scan. The
scans print SABBATO SANCTO as the heading (once) and "Sabbato sancto" as
the running header (28x and 30x); the shipped casing appears only in the
electronic transcription's table of contents -- the source this
project's own methodology rule deprecates -- while the comment beside it
called the value "both photographic scans, word for word". Recased to
the running-header form, which is the convention the other three Latin
names in the file already follow, with a source note recording the
count. Third source-fidelity slip this week, and the first where the
wrong value came from the deprecated source itself.

The Major Litanies deferral was recorded with two false blockers. It
claimed a kernel signature extension was needed to suppress the feast in
transfer years: admit already takes ~temporal and disposition already
takes ~winner, both carrying the Easter office on 25 April, so a
rite-local slug test does it with zero kernel surface. And it implied
Easter Monday is unmarkable: ef-easter-1-monday occurs exactly 8417
times in 8417 years, as reliable as ef-easter-sunday. So the guarded
build -- never scored -- is a strict improvement, 8223 years newly
correct against 194 unchanged, and "worse than the gap" was true only of
the unguarded one.

Deferring is still right, for a reason nobody had found: 25 April is St
Mark, II class, so under RG 111(c) a privileged Litanies commemoration
would displace the day's existing ordinary commemoration in ~97.7% of
years -- an unmeasured blast radius through layers 3 and 4. That
measurement is the prerequisite. The 194 figure is exact and reproduces.

Also corrects a subject-audit list that named five months for six
entries, omitting the Precious Blood on 1 July.

1 files changed, 41 insertions, 14 deletions

diff --git a/CLAUDE.md b/CLAUDE.md
index f1a673f..68cb906 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -531,20 +531,47 @@ candidate is exactly one and already spoken for).
    date's own candidate pool (both Peter and Paul are ordinary Fixed-date
    sanctoral entries); neither the Major Litanies' Easter+2 target nor
    Rogation Wednesday's own Mass commemoration has any such pre-existing
-   candidate to find. Major Litanies' ORDINARY case (the ≈97.7% of years
-   RG 80's transfer clause does not trigger) is independently buildable
-   today with zero new machinery — a `Commemoration_only` `Fixed(4,25)`
-   sanctoral entry, `Precedence_ef.privilege_of`'s already-present, dead RG
-   109(f) branch wired to it — but building only that would leave the
-   transfer years with a NEW wrong answer (a phantom commemoration on
-   Easter Sunday/Monday itself, which RG 80 explicitly forbids), not merely
-   the old, understood gap, so it was not built either. Full reasoning,
-   including the paths considered and rejected (a kernel signature
-   extension threading Easter-offset into `disposition`/`admit` closes half
-   of the Major Litanies problem — suppression — but not the relocation
-   half, and Rogation Wednesday has no equivalent half-solution at all): the
-   `ef-triduum-litanies` task report and register (Rogations/§4, and the two
-   narrowed open items in §6).
+   candidate to find.
+
+   **The real reason to defer the Major Litanies, corrected by the
+   fix-round review** — the version above was wrong in two load-bearing
+   ways and is retracted:
+
+   - It said the suppression half needs "a kernel signature extension
+     threading Easter-offset into `disposition`/`admit`". It does not.
+     `admit` **already** takes `~temporal` (added for exactly this class of
+     question during the RG 16(a) task) and `disposition` already takes
+     `~winner`; on 25 April in a transfer year both carry the Easter Sunday
+     or Easter Monday office. A rite-local slug test suppresses it with
+     **zero** kernel surface.
+   - It implied Easter Monday is unmarkable. Measured over the whole
+     domain: `ef-easter-1-monday` occurs **exactly 8 417 times in 8 417
+     years** — once every year, never displaced, since it is an I-class
+     octave day — making it precisely as reliable a marker as
+     `ef-easter-sunday`. The stated asymmetry between the two trigger
+     conditions does not exist.
+
+   So the **guarded** build (a `Commemoration_only` `Fixed(4,25)` entry, RG
+   109(f) wired, plus slug-based suppression on the two Easter slugs) is a
+   strict improvement, not a regression: 8 223 years newly correct, 194
+   unchanged, zero new wrong answers. "Worse than the recorded gap" was
+   true only of the *unguarded* build, which is the only option that was
+   scored.
+
+   Deferring is still right, for a reason nobody had identified: **25 April
+   is St Mark, II class**, so under **RG 111(c)** a *privileged* Litanies
+   commemoration (RG 109(f)) would **displace** whatever ordinary
+   commemoration the day currently carries, in ≈97.7% of years — a live,
+   unmeasured blast radius straight through layers 3 and 4. That
+   measurement is the prerequisite, and it makes this its own task rather
+   than a rider on another. The 194 figure is exact and reproduced twice
+   (Easter = 25 April in 67 years, Easter Monday = 25 April in 127).
+
+   Full reasoning: the `ef-triduum-litanies` task report and register
+   (Rogations/§4, and the two narrowed open items in §6). **Rogation
+   Wednesday remains genuinely blocked** — Easter+38 coincides with the
+   Ascension Vigil by construction, so there is no `(month, day)` pair a
+   `Fixed` spec could anchor to and no partial build exists at all.
 
 ## How to work here