fix round 1: RG 110(c)'s ordering was inverted; M19 lacked an identity gate

RG 110(c), word for word: "quoties vero oratio unius Apostoli addenda
est ad modum commemorationis, huic orationi additur altera immediate,
ante omnes alias commemorationes." "Huic orationi" (dative, "to this
oration") refers to the trigger's own oration; "additur altera" means
the companion is added to it, i.e. follows it. "Ante omnes alias
commemorationes" governs the pair's position relative to other,
unrelated commemorations, not the pair's own internal order. The
previous build prepended the companion uniformly in both RG 110
shapes, citing this same clause for both -- correct for (a)/(b) (the
day's own oration, not a list member, has nothing to order against),
backwards for (c), where the trigger is itself a list member and the
companion belongs after it. Fixed in rg110_additions: shape (a)/(b)
still prepends; shape (c) now splices the companion in immediately
after its own trigger. Re-pinned the unit test that had asserted the
wrong order, and corrected both rows' comments to cite the clause that
actually governs each shape.

No layer in this codebase compares commemoration order: the lectio
differential never compares commemorations, the oracle sorts both
sides into a multiset, and the golden tests' own describe function
sorts its commemorations field too. Recorded as a new, permanent blind
spot in CLAUDE.md and the register, not merely fixed around -- the
admit_cases unit table is the only place order is asserted at all.

Re-measured the full blast radius against the same pre-change binary:
same 14,627 differing days, same four shapes and counts, confirming
the fix changed only the content of the 593 shape-(c) rows and nothing
else. Mutation-tested: reverting the splice back to a uniform prepend
reddens exactly the shape-(c) unit test; a new golden pin for a real
shape-(c) day (2004-02-22) stays green under the same mutation, living
proof that golden pins cannot see this axis, not merely a claim.

Separately, M19's own predicate checked a date and a diff shape but
not which candidate -- proved insufficient by fabricating a second,
bogus companion on 30 June and confirming the whole suite stayed
green. Fixed by requiring the admitted commemoration to be exactly
commemoration-of-st-peter, mirroring C16's own identity guard. Added a
golden pin for 30 June, the only assertion of that entry's identity
outside the allow-list.

Also: corrected a false claim in the task report that the electronic
transcription carries no corroboration of the Holy Name fallback --
its own table of contents does, at a line not checked on the first
pass. Added two further citations, both re-verified against the scan:
RG 17's own closing paragraph, settling the Sunday shape's Sunday-
exclusion at the rubric level rather than only in the propers; RG
124(c), which assigns red to 30 June by paragraph number rather than
by the generic apostle/martyr default. Noted the fragility of deriving
the Sunday shape's RG 109(a) privilege from a slug-substring match
rather than from a citation. Cosmetic: a stray blank line and an
indentation inconsistency.

1 files changed, 52 insertions, 0 deletions

diff --git a/test/test_golden.ml b/test/test_golden.ml
index 80e2c9d..0f90ee7 100644
--- a/test/test_golden.ml
+++ b/test/test_golden.ml
@@ -691,6 +691,51 @@ let test_holy_name_fallback_2029 () =
     "2029-01-02 tuesday season=christmastide week=- slug=ef-holy-name rank=class-2 colour=white \
      subject=lord comms=[] in=- out=[]"
 
+(* RG 110 (docs/research/rules-register.md §4, Caput XIV), fix round 1
+   (coordinator findings F1/F2): two golden pins neither existed before this
+   round -- F2 named 30 June's own total absence of golden coverage
+   directly ("no golden pin on any 30 June date"), and F1 named the
+   shape-(c) collision as a real day this suite otherwise never exercises
+   end-to-end against real data (both new [admit_cases] rows are synthetic
+   candidates, not `Calendar.day` over the real committed layer).
+
+   *** BOTH PINS ARE BLIND TO COMMEMORATION ORDER -- STATED HONESTLY, NOT
+   CLAIMED AS PROOF OF F1's OWN FIX ***
+
+   [describe]'s own `comms` field (this file's header, above) sorts the
+   commemoration list alphabetically before rendering
+   (`List.sort compare`) -- deliberately, so a golden pin's own STRING
+   comparison is not accidentally order-sensitive where nothing textual
+   requires it to be. That means this file, like the differential and the
+   oracle's own [identity_diff] (test_oracle.ml), CANNOT see whether
+   [rg110_additions] emits `chair-of-st-peter, paul` or `paul,
+   chair-of-st-peter` -- both sort to the same string. The ONLY place in
+   this codebase's test suite that asserts commemoration ORDER at all is
+   `test_precedence_ef.ml`'s own [admit_cases] table (`Alcotest.(check
+   (list string))`, not a sorted string) -- see precedence_ef.ml's own
+   [rg110_additions] comment for the citation this uses to fix the order,
+   and CLAUDE.md's "know what each layer cannot see" section for this as a
+   permanent, structural limit, not a gap this task's own pins happened not
+   to close. These two pins prove PRESENCE and IDENTITY of both
+   commemorations on a real, `Calendar.day`-resolved date -- genuine
+   ground no other pin in this file currently covers -- not order. *)
+let test_rg110_june_30_2026 () =
+  check ~msg:"2026-06-30: RG 110's 30-June direction -- In Commemoratione Sancti Pauli Apostoli observed, \
+              +commemoration-of-st-peter (data/ef/adjustments.sexp's own `Add` directive) the sole \
+              commemoration -- missalemeum shows neither (M19, verdict colitur)"
+    2026 6 30
+    "2026-06-30 tuesday season=time-after-pentecost week=5 slug=in-commemoratione-sancti-pauli-apostoli \
+     rank=class-3 colour=red subject=saint comms=[commemoration-of-st-peter:ordinary] in=- out=[]"
+
+let test_rg110_shape_c_2004 () =
+  check ~msg:"2004-02-22: RG 110 shape (c) -- Chair of St Peter itself loses the day to an ordinary \
+              (Septuagesima, not I-class) II-class Sunday and is admitted only as a commemoration under \
+              RG 111(b)'s own rank floor; Paul rides along too, uncapped (`date -d 2004-02-22 +%A` = \
+              Sunday, independently confirmed)"
+    2004 2 22
+    "2004-02-22 sunday season=septuagesima week=3 slug=ef-septuagesima-sunday-3 rank=class-2 colour=violet \
+     subject=temporal comms=[chair-of-st-peter:ordinary,paul:ordinary] in=- out=[]"
+
 (* 2025-02-02, the other real instance of the SAME pattern -- not a
    contrasting second direction, per this task's fix round 1 (CRITICAL
    finding, item 1, reverted; see register §6.0 for the full account).
@@ -857,6 +902,13 @@ let suite =
          the window)"
         `Quick test_holy_name_fallback_2029;
       Alcotest.test_case
+        "RG110: 30 June, In Commemoratione S. Pauli Apostoli + commemoration-of-st-peter (2026-06-30)" `Quick
+        test_rg110_june_30_2026;
+      Alcotest.test_case
+        "RG110 shape (c): Chair of St Peter admitted only as a commemoration of an ordinary Sunday, Paul \
+         rides along (2004-02-22)"
+        `Quick test_rg110_shape_c_2004;
+      Alcotest.test_case
         "ef-rebootstrap: RG91 entry24 (III-class feast) outranks entry28 (class-4 feria) -- the six dates \
          deferred since 2038's own Easter-extreme pin (2008-04-02/04/05, 2038-03-06/08/09)"
         `Quick test_iii_class_feast_wins_class4_feria