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, 30 insertions, 1 deletions

diff --git a/lib/kernel/precedence.mli b/lib/kernel/precedence.mli
index ae054dd..09376d7 100644
--- a/lib/kernel/precedence.mli
+++ b/lib/kernel/precedence.mli
@@ -34,12 +34,41 @@ type ('s, 'r) rules = {
       (** RG 92-95: the loser's fate, which depends on the loser's own rank. *)
   admit :
     observed:'r candidate ->
-    ('r candidate * privilege) list ->
+    temporal:'r candidate ->
+    ('r candidate * privilege * int) list ->
     ('r candidate * privilege) list;
       (** RG 108-111: how many commemorations are admitted, and in what order;
           anything filtered out here is recorded in {!resolution.omitted}, not
           dropped.
 
+          Each input triple's trailing [int] is that candidate's own {!band}
+          value, computed once by {!resolve} (RG 113: "in admittendis et
+          ordinandis aliis commemorationibus, servetur ordo tabellae
+          praecedentiae" -- ADMITTING and ORDERING commemorations is governed
+          by the same table-of-precedence order {!band} already supplies for
+          picking the day's own winner; docs/research/rules-register.md §4
+          "Commemorations"). Supplied rather than left for [admit] to compute
+          itself because [admit] has no [context] (date/season/weekday) of
+          its own -- {!resolve} already holds one and calls {!band} with it
+          for every candidate regardless. A rite's [admit] is free to ignore
+          the value entirely (e.g. fall back to [Vocab.rank] alone), the same
+          as it may ignore [temporal] below.
+
+          [temporal] is {!resolve}'s own [~temporal] argument, passed through
+          unchanged -- the day's temporal-cycle candidate, regardless of
+          whether it won. Fix round 1 (RG16(a) task): before this, a rite's
+          [admit] could only infer properties of the CIVIL DAY (chiefly "is
+          this a Sunday", RG 111(b)'s own two-tier admission rule) from
+          [observed]'s own fields -- a proxy that breaks the moment something
+          OTHER than the day's own temporal candidate can be [observed], the
+          exact shape RG 16(a) introduces (a Feast of the Lord standing in
+          the impeded Sunday's place "cum omnibus iuribus et privilegiis",
+          RG 91 entry 14). This is NOT a kernel definition of "Sunday" --
+          the kernel does not gain any rite-specific knowledge by this
+          parameter, it only threads through a value {!resolve} already
+          holds; a rite's own [admit] is free to ignore it entirely, the
+          same as [observed].
+
           OBLIGATION ON THE IMPLEMENTATION, not enforced by this type: every
           candidate this function returns must be a value taken UNCHANGED
           from its input list, never rebuilt (e.g. via a [{ c with ... }]