Merge branch 'ef-rg16a': RG 16(a), RG 111(b), RG 113, and commemoration identity

Closes the largest known-wrong-output item on record (RG 16(a): a Feast
of the Lord occurring on a II-class Sunday leaves the Sunday
uncommemorated -- 5996 wrong days over 1583-9999) together with RG
111(b)'s rank floor on the day it holds, and gives the oracle layer the
ability to compare commemoration identity rather than only presence and
count.

Also corrects a methodological defect that had produced wrong rulings in
both this project and its sibling: docs/research/ holds an electronic
transcription alongside two photographic scans, and the transcription
silently drops commemoration lines -- seven across the year. Reasoning
from its silence had convicted the oracle wrongly on 14 August and
ruled a genuine 9 August commemoration spurious. The scans are the
primary source; the rule is now recorded at the top of the register.

RG 113 replaces an alphabetical same-rank tie-break that had no
rubrical warrant. A bare Commemoratio has no row in RG 91's table at
all, so band no longer hands one the entry of a III-class universal
feast: 4451 days, all four reordered pairs verified against a
photographic scan, zero observed-day changes.

1 files changed, 91 insertions, 30 deletions

diff --git a/lib/rites/rite_ef/precedence_ef.mli b/lib/rites/rite_ef/precedence_ef.mli
index 55f947e..b283a17 100644
--- a/lib/rites/rite_ef/precedence_ef.mli
+++ b/lib/rites/rite_ef/precedence_ef.mli
@@ -68,10 +68,21 @@ val unclassified : int
     text states an exception: entry 8 (All Souls) reads "yields to an
     occurring Sunday", so on a Sunday this returns a value that
     loses to entry 15 rather than the literal integer 8 (see the comment on
-    entry 8 in precedence_ef.ml for the exact value and why). Total over
-    every candidate {!Precedence.resolve} or {!Calendar} can construct,
-    including shapes the 1962 table itself does not describe (see
-    {!unclassified}). *)
+    entry 8 in precedence_ef.ml for the exact value and why). ALSO
+    {!unclassified} for any [Cel.Commemoration_only] candidate, checked
+    first, ahead of every rank-keyed branch -- CORRECTED, Task B fix round
+    1 (coordinator finding 1): RG 91's own table enumerates only "dies
+    liturgici" (entry 24's own text, "Festa III classis..." -- FEASTS), so
+    a celebration reduced to a bare commemoration was never a row in the
+    table to begin with, confirmed by the calendarium's own notation (a
+    genuine feast carries a class number on its occurrence line; a bare
+    "Commemoratio" carries none). Before this fix, a [Commemoration_only]
+    candidate silently borrowed the SAME entry number as a genuine [Feast]
+    of its own [rank] -- manufacturing ties {!Precedence.compare_by} and
+    {!compare_precedence} both then had to break some other way, that RG 91
+    itself never created. Total over every candidate {!Precedence.resolve}
+    or {!Calendar} can construct, including shapes the 1962 table itself
+    does not describe (see {!unclassified}). *)
 val band : Vocab_ef.season Precedence.context -> Vocab_ef.rank Precedence.candidate -> int
 
 (** RG 33's marker: every Sunday slug this rite's temporal cycle produces
@@ -164,33 +175,82 @@ val nativity_octave_prefix : string
     so the two cannot silently drift apart. *)
 val september_ember_prefix : string
 
-(** [admit ~observed comms]: RG 108-111 (docs/research/rules-register.md §4,
-    "Commemorations"). How many of [comms] -- each already tagged with its
-    real RG 109 privilege by {!disposition} -- RG 111 admits, and which,
-    given the day actually observed:
+(** [admit ~observed ~temporal comms]: RG 108-111 (docs/research/rules-register.md
+    §4, "Commemorations"). How many of [comms] -- each already tagged with
+    its real RG 109 privilege by {!disposition}, and its own {!band} value
+    (RG 91's table-of-precedence entry, computed once by
+    {!Precedence.resolve} -- see {!Precedence.rules.admit}'s own doc) -- RG
+    111 admits, and which, given the day actually observed:
     - [observed] a [Class1] day: none, except at most one privileged
-      commemoration (the highest-dignity one, if several are due) -- an
-      ordinary one is never admitted here, no matter how many are due;
-    - [observed] a [Class2] Sunday (its slug carries {!sunday_marker}): one,
-      subject to TWO conditions, not one -- (i) a privileged commemoration,
-      whenever due, categorically takes the day's one slot over any
-      ordinary one, not by comparing dignity, so an ordinary commemoration
-      that would otherwise win on dignity is still dropped; (ii) failing
-      that, the slot is reserved for a [Class2] candidate SPECIFICALLY
-      ("de festo II classis", RG 111(b)'s own wording -- a RANK FLOOR, not
-      "whichever ordinary candidate has the best dignity"): a III- or
-      IV-class ordinary loser has no standing for this slot at all and is
-      admitted nothing, even when it is the only candidate due;
-    - [observed] any other [Class2] day: one, by dignity alone -- no
-      privilege override and no rank floor, unlike the Sunday case
-      immediately above;
-    - [observed] a [Class3] or [Class4] day: at most two, by dignity alone.
+      commemoration (the highest-{!band}-precedence one, if several are
+      due) -- an ordinary one is never admitted here, no matter how many
+      are due;
+    - the CIVIL DAY is a [Class2] Sunday ([temporal]'s slug carries
+      {!sunday_marker} -- CORRECTED, fix round 1, RG16(a) task: read off
+      [temporal], not [observed]; see below): one, subject to TWO
+      conditions, not one -- (i) a privileged commemoration, whenever due,
+      categorically takes the day's one slot over any ordinary one, not by
+      comparing table position, so an ordinary commemoration that would
+      otherwise win on table order is still dropped; (ii) failing that, the
+      slot is reserved for a [Class2] candidate SPECIFICALLY ("de festo II
+      classis", RG 111(b)'s own wording -- a RANK FLOOR, not "whichever
+      ordinary candidate has the best table position"): a III- or IV-class
+      ordinary loser has no standing for this slot at all and is admitted
+      nothing, even when it is the only candidate due;
+    - the civil day is any other [Class2] day: one, by {!band}'s table order
+      alone -- no privilege override and no rank floor, unlike the Sunday
+      case immediately above;
+    - [observed] a [Class3] or [Class4] day: at most two, by {!band}'s table
+      order alone.
 
-    "Dignity" here is [Vocab_ef.rank] (RG 8's four classes), NOT {!band}'s
-    finer RG 91 entry number -- {!band} needs a [context] (date/season/
-    weekday) this function does not receive (see {!Precedence.rules.admit}).
-    Ties break on slug, matching {!Precedence.compare_by}, so the result
-    never depends on the order [comms] arrives in.
+    CORRECTED, Task B (branch ef-rg16a): this used to sort by
+    [Vocab_ef.rank] (RG 8's coarse four-class "dignity") and break same-rank
+    ties alphabetically by slug -- an engineering convention with no
+    rubrical warrant, cited nowhere. Measured, fix round 1 (2005-2050,
+    reproducible via a temporary [git worktree] at the pre-fix commit):
+    a same-[rank] tie existed in the candidate pool offered to [admit] on
+    599 days, most never reaching a real decision (RG 111's own admission
+    count often has room for both, e.g. a III-class day admits two); of
+    those, reversing the slug tie-break ALONE actually changed the ADMITTED
+    SET on 65 days and only the printed ORDER of an already-admitted pair
+    on a further 149 (docs/research/rules-register.md §6.1's own full
+    account, superseding this comment's earlier, unreproduced "66 days"
+    claim). RG 113's own second sentence, previously uncited
+    (docs/research/rules-register.md §4's RG 113 entry), is the real rule:
+    *"in admittendis et ordinandis aliis commemorationibus, servetur ordo
+    tabellae praecedentiae"* -- admitting and ordering commemorations both
+    run on {!band}'s own finer RG 91 table, not RG 8's four classes.
+    {!band} needs a [context] (date/season/weekday) this function does not
+    receive on its own, so {!Precedence.resolve} computes it once,
+    generically, and hands each candidate its own value as the trailing
+    [int] on [comms]'s triples (see {!Precedence.rules.admit}). Ties break
+    on slug ONLY within one identical [band] value -- CORRECTED, fix round
+    1 (coordinator finding 1): [band] itself used to hand a
+    [Cel.Commemoration_only] candidate the same table entry as a genuine
+    [Cel.Feast] of its own rank (RG 91's table has no row for a bare
+    commemoration at all), manufacturing most of the "identical [band]
+    value" ties this comment used to describe as RG 113's own residual.
+    Fixed in [band] itself; checked afterward (2005-2050 and the full
+    1583-9999 domain, register §6.1) and found EMPTY of any remaining
+    "two different real table entries tied" case -- the slug fallback below
+    is exercised only between two [Commemoration_only] candidates both at
+    {!unclassified}, still an uncited engineering convention (register §6
+    "RG 113 tie-break"), matching {!Precedence.compare_by}'s own fallback,
+    so the result never depends on the order [comms] arrives in.
+
+    [temporal] -- CORRECTED, fix round 1 (RG16(a) task): this function used
+    to read the Sunday/non-Sunday split off [observed]'s own slug, which
+    silently assumed [observed] IS the day's temporal-cycle office. RG 16(a)
+    breaks that assumption on purpose: a Feast of the Lord holds an impeded
+    II-class Sunday's own place "cum omnibus iuribus et privilegiis"
+    (RG 16(a)'s own text), so the day still counts as a "dominica II
+    classis" for RG 111(b) even though [observed] is now the FEAST.
+    [temporal] -- {!Precedence.rules.admit}'s own parameter, the day's
+    temporal-cycle candidate regardless of who won -- is the reliable
+    signal; oracle-confirmed (6 August: Sunday excludes a Class3 saint
+    Sixtus II from the freed slot, an ordinary weekday admits him). Every
+    row of the previous behaviour where [observed] and [temporal] coincide
+    (no RG 16(a) displacement occurred) is unaffected.
 
     Every candidate this returns is a value taken unchanged from [comms],
     never rebuilt: {!Precedence.resolve}'s own [dropped]/[omitted]
@@ -202,7 +262,8 @@ val september_ember_prefix : string
     itself total over an empty or arbitrarily long [comms]. *)
 val admit :
   observed:Vocab_ef.rank Precedence.candidate ->
-  (Vocab_ef.rank Precedence.candidate * Precedence.privilege) list ->
+  temporal:Vocab_ef.rank Precedence.candidate ->
+  (Vocab_ef.rank Precedence.candidate * Precedence.privilege * int) list ->
   (Vocab_ef.rank Precedence.candidate * Precedence.privilege) list
 
 (** The Annunciation's own bootstrapped slug (data/ef/sanctoral.sexp, Task