test(ef): reach RG 91 entry 27 through the real pipeline, end-to-end

Entry 27's band branch has been unreachable for the right reason since
it was written: precedence_ef.ml's own comment on it acknowledged the
row existed, but the one test exercising it built a hand-typed
candidate, never a real Temporal_ef.temporal output, and nothing built
the office itself. Closes that gap on both sides:

- The band-table row now sources its candidate from Temporal_ef.temporal
  directly (of_temporal), the same review-finding-3 discipline the
  Ember/vigil rows already use, so a future regression in the office's
  own construction fails this row too, not only the unit-level test.
- Two new resolve-level end-to-end tests, using the real band/
  disposition/admit triple (not stubs): the office winning a real
  otherwise-unoccupied Saturday and admitting an ordinary commemoration
  alongside it (1 August 2026, Holy Machabees -- the task brief's own
  worked oracle example), and the office genuinely losing to a real
  competing feast and being omitted under RG 26, with no confusion from
  the one live data witness that also carries subject Bvm (12 September,
  Most Holy Name of Mary) -- proving RG 26's rank-keyed omission fires
  before any subject-keyed rule ever could.
- Two golden pins mirroring the same two dates, checked by hand against
  `colitur day 2026` before being typed in, following this file's own
  "a golden test blesses whatever it is given, verified independently"
  discipline. The existing 2038-03-06 pin (RG 91 entry 24 outranking a
  Class4 candidate) is corrected in passing: that date is itself a
  Saturday, so the displaced candidate the pin's own omitted-list check
  names is now precisely entry 27's own shape, not entry 28's bare
  catch-all -- the win/lose outcome the pin proves is unchanged, only
  its own more precise citation.

Mutation-tested (recorded in the task report): reverting
is_bvm_saturday to a constant false reddens the dedicated unit test, the
new end-to-end resolve test, and the 2026-08-01 golden pin, while
leaving the 2026-09-12 "loses to a real feast" pin untouched, exactly as
expected since that date's outcome never depended on the fix.

0 files changed, 0 insertions, 0 deletions