docs: record why RG 112(b)/(c)/(d-saint) are unbuilt

They have been carried as a bare 'unbuilt' for weeks. The reason is not
neglect, and it differs per clause -- now measured across 1583-9999 rather
than asserted.

(c) cannot fire in this architecture at all: Temporal_ef.temporal returns one
office per day, so two de Tempore candidates never coexist. Nothing to build.

(b) is already produced by RG 16(a), which is implemented: 0 days in either
direction, because a Lord feast takes an occurring Sunday's place with no
commemoration, and no Class1 Sunday shares a date with any of the four
Lord-subject entries.

(d)'s saint half has no candidate pair. Three apparent pairs are distinct
saints sharing a forename -- recorded so the false positive is not rediscovered
-- and the one real pair, agnes and agnes-secundo, is 7 days apart and
co-occurs 0 times.

(b) and (d) are data-unreachable rather than architecture-unreachable, so an
overlay can make either live. That is the entry_14_movable_band shape. Left as
an explicit open decision rather than silently resolved.

0 files changed, 0 insertions, 0 deletions