docs: fix round 1 -- Purification reversal, the admit fix, RG112, layer blindness

CLAUDE.md's own carried-item record, updated to match the register's full
account: the Purification retag reversed (follow the oracle, not the
calendarium title, per the user's ruling), the admit/~temporal kernel
signature change (a genuine one, unlike RG16(a) itself), RG112 recorded as
a newly-found, unimplemented rule (a feast/mystery of one Divine Person
excludes a commemoration of another of the same Person -- confirmed live
on 13 January in seven real differential-window years, independent of the
subject question), and the Dedication-of-a-Church classification question
(measured, not applied: St Michael's own Dedication, 29 September, may
also be a feast of the Lord -- 1200 days domain-wide if so).

Extends the existing 'commemoration identity is unasserted' item: this is
the exact gap the whole RG16(a) fix round exploited both ways -- the
original bug and the review's own catch (Pope Sixtus II wrongly admitted,
both golden pins promoted from output) were both invisible to every layer
except unit tests and two golden pins.

1 files changed, 47 insertions, 17 deletions

diff --git a/CLAUDE.md b/CLAUDE.md
index f772405..174bf30 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -199,24 +199,54 @@ nowhere in git (`docs/` is gitignored).
 
 **The two behaviour items, in order:**
 
-1. **RG 16(a) — RESOLVED (RG16(a) task, branch `ef-rg16a`, 2026-08-12).** Was
-   the largest known-wrong output on the branch: a Feast of the Lord occurring
-   on a II-class Sunday takes the Sunday's place *"cum omnibus iuribus et
-   privilegiis: de dominica, proinde, **nulla fit commemoratio**"*, and colitur
-   used to commemorate the Sunday anyway (**5 996 wrong days over 1583–9999**,
-   369 of them in 1583–2100, re-confirmed exactly by this task's own
-   independent re-measurement). Fixed in `Rite_ef.Precedence_ef.disposition`
-   with **no signature change** — `disposition` already took `winner:...`
-   (RG 33's own vigil-omission branch already read it); the earlier note here
-   claiming a signature change was needed was itself wrong, corrected in
-   register §6.0. Landed together with a sanctoral data fix (two of six
-   `subject = Lord` entries were themselves wrong — the Purification and the
-   Most Holy Name of Mary are BVM feasts, not the Lord's) via a new
-   `data/ef/adjustments.sexp` overlay; see register §6.0 for the full account,
-   the sanctoral audit, and one further `subject` defect found but left open
-   (13 January, Baptism of the Lord, currently mistagged `Saint`).
+1. **RG 16(a) — RESOLVED (RG16(a) task, branch `ef-rg16a`, 2026-08-12; ONE
+   FIX ROUND of review after the first pass — see register §6.0 for the full,
+   corrected account).** Was the largest known-wrong output on the branch: a
+   Feast of the Lord occurring on a II-class Sunday takes the Sunday's place
+   *"cum omnibus iuribus et privilegiis: de dominica, proinde, **nulla fit
+   commemoratio**"*, and colitur used to commemorate the Sunday anyway
+   (**5 996 wrong days over 1583–9999**, 369 of them in 1583–2100,
+   re-confirmed exactly, twice, independently). Fixed in
+   `Rite_ef.Precedence_ef.disposition` with **no signature change** —
+   `disposition` already took `winner:...` (RG 33's own vigil-omission branch
+   already read it). A SECOND, related bug needed a genuine kernel signature
+   change: `Precedence.rules.admit` gained a `~temporal` parameter, because
+   RG 16(a) also breaks the assumption that `observed` IS the day's own
+   temporal-cycle office for RG 111(b)'s Sunday rank-floor check (an
+   unrelated saint could otherwise be wrongly admitted into the freed slot —
+   confirmed on 1 178 real days, 6 August, before this second fix).
+   **The sanctoral data question was more contested than the first pass
+   found**: the Purification (2 Feb) was FIRST retagged `Bvm` (calendarium
+   title argument), then REVERTED to `Lord` in fix round 1 on the user's own
+   ruling — follow the oracle, which treats the Purification as taking an
+   occurring Sunday's place outright, unlike an ordinary Marian feast (real
+   primary-text counter-evidence, RG 120(b)'s colour rule, remains on record
+   as the argument the other way). Only `most-holy-name-of-mary` stays
+   retagged `Bvm`. A related, unresolved primary-source finding: the Common
+   of the Dedication of a Church's own classification (*"Festum
+   Dedicationis Ecclesiae est festum Domini"*) means St Michael's Dedication
+   (29 Sep) may also be `Lord`, not `Saint` — measured, not applied (1 200
+   days domain-wide if it were). Two further open items recorded, not fixed:
+   13 January (Baptism of the Lord, mistagged `Saint`, and separately, RG 112
+   — a feast/mystery of one Divine Person excludes a commemoration of
+   another of the SAME Person — entirely unimplemented, confirmed live on 7
+   real years).
 2. **Commemoration identity is unasserted** outside ~3 test rows (see the layer
-   caveats above). Related: `compare_dignity` breaks same-rank ties
+   caveats above) — **the exact gap the RG 16(a) fix round exploited**: the
+   lectio differential compares season/slug/rank/colour only, never
+   commemorations, so of the 5 996 days RG 16(a) changes, the differential
+   sees at most the handful where the OBSERVED slug itself also changes (the
+   Purification's own 1 200, and only because it happens to change who is
+   observed) — RG 16(a) proper moved ZERO differential rows either round.
+   The missalemeum oracle window (2026–2027) contains zero live RG 16(a)
+   instances at all. Every finding in the RG 16(a) fix round, both the
+   original bug and the fix-round-1 review's own catch (Pope Sixtus II
+   wrongly admitted, both golden pins promoted from output rather than
+   independently derived), rested entirely on unit tests and two golden
+   pins — this is precisely how a defect of this shape gets through
+   undetected for as long as it did, and precisely how the review's own
+   correction had to be caught by the same narrow means. Related:
+   `compare_dignity` breaks same-rank ties
    **alphabetically**, with no RG warrant, and over 2005–2050 the admission cut
    falls between two same-rank candidates on **66 days**.