DC-LEDGER-PHASE2-03

STATUS FLIPPED partial -> enforced at BND-2d (2026-08-16) on the live evidence cited above; the transition itself was never in question, only whether the resolver could be POSITIONED to feed it, which is what BND-2d fixed. Originally recorded as: STATUS IS partial DELIBERATELY: the in-tree proof is complete (2252 tests green, four gates passing) but the LIVE bar is not yet met. Live closure requires, on a fresh v5 store: the real accumulator walk resolving the collateral input at 130,350,133 through the reduced checkpoint, the cursor advancing THROUGH that block past 130,350,114, and a warm restart reproducing the resulting accumulator state -- none of which a unit test can stand in for. Flip to enforced only on that evidence. The four rewritten unit tests replaced assertions that encoded the UNIMPLEMENTED state ('fail closed because discarding is not implemented'); each now asserts the Cardano rule itself and carries a non-vacuous control (the governance ones assert gov state is UNCHANGED and that the SAME block with the tx valid DOES capture the proposal). A load-bearing discovery during implementation: process_block_certificates walked every tx and applied its certs, relying entirely on the removed guard firing first -- removing the guard without gating that walk would have silently applied a discarded tx's certificates, which is the exact bug class BND-2a fixed on the UTxO side. ID CORRECTION (BND-2d): this rule was first recorded as DC-LEDGER-03, an id already held by a long-standing rule, which broke registry uniqueness (ci_check_registry_unique_ids.sh was red from that commit until BND-2d). The older holder keeps the id; this entry -- three commits old and referenced only by its own slice doc -- takes the fresh DC-LEDGER-PHASE2-03.