precedence(ef): fix round 1 (F2, F7) -- correct a false transcription claim, cite RG95's real primary authority

F2: the disposition comment for RG112(a) claimed the electronic
transcription "carries NEITHER this paragraph's own worked example
NOR its own more specific Mass-proper rubric... exactly the
transcription's documented defect" -- wrong on both counts, checked
directly rather than taken on trust.

RG 112 has no worked example in any of the three source documents
(the transcription included) -- there was nothing to drop. The Holy
Family Mass propers' own 13-January rubric is absent from the
transcription not because it silently drops content it otherwise
has (the project's own documented defect, dropped calendarium
commemoration lines) but because that specific document (a 2006 web
capture) contains almost no Mass-propers text of any day: 5
Introit-line occurrences across 26,322 lines, against 61 and 402 in
the two photographic scans; its own "Proprium de Tempore" page is a
table of contents linking to PDFs the capture never pulled in. A
coverage gap in a partial web capture, not an instance of the
narrower, different defect the methodology note actually describes.
The ruling is unaffected -- the propers' quotation is real, on two
independent photographic scans, and settles 13 January on its own --
only the attribution is struck, here and in test_precedence_ef.ml
(the register and the task report are corrected separately).

F7: RG 95's own second paragraph -- present in all three documents,
including the transcription -- is a more direct, occurrence-level
authority for the exact collision than RG 112(a): "if two feasts of
the same Divine Person... occur together, the one higher in the
table is kept, the other omitted." Added as the primary citation on
disposition's RG112(a) branch, with RG 112(a) and the propers' note
kept as corroboration. Also corrects RG 112(b)'s own framing: it is
bidirectional ("et vicissim"), and only the Lord-feast-wins direction
(RG 16(a)) is implemented -- the Sunday-wins direction has no witness
anywhere in this codebase's data and was wrongly described as already
covered.

1 files changed, 11 insertions, 6 deletions

diff --git a/lib/rites/rite_ef/precedence_ef.mli b/lib/rites/rite_ef/precedence_ef.mli
index 239a254..7d0bc98 100644
--- a/lib/rites/rite_ef/precedence_ef.mli
+++ b/lib/rites/rite_ef/precedence_ef.mli
@@ -159,13 +159,18 @@ val sunday_marker : string
       commemoration of a losing SAINT freely, with no such class-keyed
       gate);
     - a loser whose [subject] is [Lord] AND whose WINNER's [subject] is also
-      [Lord] is [Omit] (RG 112(a) -- a feast or mystery of one Divine Person
-      excludes a commemoration of another feast or mystery of the SAME
-      Divine Person; live witness: Holy Family, RG 17(b), excluding the
-      fixed Commemoration of the Baptism of the Lord on the years 13
+      [Lord] is [Omit] (PRIMARY authority: RG 95's own second paragraph,
+      present in all three source documents including the electronic
+      transcription -- "if two feasts of the SAME DIVINE PERSON... occur
+      together, [the Office] is made of the one higher in the table of
+      precedence, and the OTHER IS OMITTED"; corroborated by RG 112(a) --
+      a feast or mystery of one Divine Person excludes a commemoration of
+      another feast or mystery of the SAME Divine Person -- and by the Holy
+      Family Mass propers' own more specific 13-January rubric on both
+      photographic scans; live witness: Holy Family, RG 17(b), excluding
+      the fixed Commemoration of the Baptism of the Lord on the years 13
       January is itself Holy Family's own date -- see the .ml's own comment
-      for the primary text, including the Holy Family Mass propers' own
-      more specific 13-January rubric, on both photographic scans);
+      for the full primary text of all three);
     - everything else -- including an impeded I-class Sunday, and a
       SANCTORAL loser of any rank below I class -- is [Commemorate],
       carrying its real RG 109 privilege (see {!admit} below); RG 109(a)