rite(ef): the Annunciation's RG96 exception is conditional, not unconditional

The register was transcribed faithfully but was itself wrong: RG 96's
Attamen (a), primary-source-verified from the scans and now corrected
in the register, reads 'festum Annuntiationis B. Mariae Virg., quando
est transferendum post Pascha, transfertur ... in feriam II post
dominicam in albis' -- the Monday-after-Low-Sunday seat applies ONLY
'quando est transferendum post Pascha', when the feast is to be
transferred PAST EASTER. The unconditional transcription made the
exception fire on every impeded Annunciation regardless of cause.

transfer_target now computes the general RG 96 target first, for every
candidate, and overrides to the Monday after Low Sunday only when that
general target itself falls after Easter Sunday -- testing the rubric's
own condition directly rather than re-deriving a date-proximity rule
from first principles.

Confirmed against three real years the review named: 2007, 2012 and
2057 all previously sent the Annunciation to Easter + 8 (16 April,
16 April, 30 April respectively) when the correct, now-produced target
is the next free day before Easter (26 March in each case -- Passion
Sunday in 2007/2012, Lent III Sunday in 2057). Verified with actual CLI
output for all three, before and after.

Also cites RG 96 Attamen (b), the same primary-source passage, as the
direct authority for All Souls' own move to the following Monday when
impeded by a Sunday -- previously inferred from RG 91 entry 8's
parenthetical plus the general walk, which happened to produce the
right date; now stated directly.

Rewrote the two existing Annunciation unit tests, whose synthetic
occupants no longer trigger the (now correctly conditional) exception,
and added a 2057 regression test using the real Temporal_ef.temporal as
occupant plus a real-data cram pin -- both mutation-verified against
the unconditional reading.

1 files changed, 22 insertions, 10 deletions

diff --git a/lib/rites/rite_ef/precedence_ef.mli b/lib/rites/rite_ef/precedence_ef.mli
index 7318ccd..8234bf3 100644
--- a/lib/rites/rite_ef/precedence_ef.mli
+++ b/lib/rites/rite_ef/precedence_ef.mli
@@ -187,11 +187,23 @@ val annunciation_slug : string
     RG 96's own rule: the next following day whose currently-resolved
     occupant is not I or II class (read off [Vocab_ef.rank], RG 8's dignity
     -- not {!band}'s finer occurrence-table entry, the same distinction
-    {!admit} draws for RG 111). RG 96's own named exception: the
-    Annunciation ({!annunciation_slug}) does not search from [origin + 1] at
-    all -- it starts at the Monday after Low Sunday for [origin]'s own civil
-    year, searching onward from there only if that day is itself occupied by
-    a blocking class.
+    {!admit} draws for RG 111). This general target is computed for EVERY
+    candidate, always, first.
+
+    RG 96's own named exception (Attamen (a), primary-source-verified --
+    see {!annunciation_slug}'s comment for the Latin and the register's own
+    correction note): for the Annunciation specifically, IF that general
+    target would fall after Easter Sunday itself ("quando est transferendum
+    post Pascha" -- when it is to be transferred past Easter), the
+    Annunciation is placed instead at the Monday after Low Sunday (its
+    [sedes propria]), searching onward from there only if that day is
+    itself occupied by a blocking class. The exception is CONDITIONAL, not
+    unconditional: an Annunciation impeded for a reason that resolves
+    BEFORE Easter (e.g. an ordinary Lent Sunday with a free feria the next
+    day) takes the general target like any other I-class feast. Operationally
+    the condition holds exactly when 25 March falls close enough to Easter
+    that the general walk crosses it -- concretely, when 25 March itself
+    falls within Holy Week or Easter Week.
 
     Total, terminating, and its result is always strictly later than
     [origin] -- {!Colitur_kernel.Rite.t}.transfer_target's own obligations,
@@ -205,10 +217,10 @@ val annunciation_slug : string
     [domain_max_date]), not by an argument about the real 1962 calendar's
     own structure, so a rite/data shape this function has not anticipated
     fails FINITELY rather than hanging or crashing the caller. Strictly
-    later than [origin]: the ordinary search
-    starts at [origin + 1] and only ever advances forward from there; the
-    Annunciation's own starting point is provably later than 25 March for
-    every representable year (Easter's documented range, register §0) --
-    see the .ml for the full argument. *)
+    later than [origin]: the general search starts at [origin + 1] and only
+    ever advances forward from there; the Annunciation's own alternate
+    starting point is provably later than 25 March for every representable
+    year (Easter's documented range, register §0) -- see the .ml for the
+    full argument. *)
 val transfer_target :
   Vocab_ef.rank Precedence.candidate -> Date.t -> (Date.t -> Vocab_ef.rank Celebration.t) -> Date.t