TheTree_mock/docs/plans/original-completion-2026-10-02/execution/p04-01/s5/PENDING.md

REPAIR43 — native evidence and formal acceptance pending

The R42/R43 implementation batch now includes the public-restored G1/G2 journal shadows, independent typed adapter oracle, exact-N idle OBJECTIVE breach, S5D_IN_FLIGHT event destruction, S5G_SHIFT_1080, S5H_PAUSED_MIDNIGHT, and S5E public same-minute advance_to after formal restore. See ../REPAIR41_STATUS.md and ../REPAIR43_SOURCE_FACTS.json for source bodies, lines, hashes and the spec EOF protocol. The closed-field/file-freeze blockers are superseded. The spec passes its existing checker protocol without edits.

Implementation is not native proof. Root must run the fresh nine-case S5 Writer/Reader and adapters alongside fresh S1–S4 in the prescribed single batch. The new shift/paused/replay keys are emitted only after fresh typed raw derivation; paused_midnight is then removed from the adapter pending list. patience_release remains pending unless fresh S3 independently supplies it. Future-raw positives and mutations are Root-only. No historical run supplies these new keys. All 15+EV requirements and thresholds remain mandatory.

Pure results are in ../REPAIR43_PURE_RESULTS.json; static results are in ../REPAIR41_STATIC_CHECKS.json. r35/r36/R40 native remain FAILED, Q37 is only its own-version local PASS, and P04 credit remains 0. Registered validation precedes formal independent whole-unit review. No native/full run was performed by this worker; no completion claim or new counted unit is made.

Historical REPAIR41 partial repair (superseded implementation status)

See ../REPAIR41_STATUS.md: M serializes an additional command_queue.accepted metadata row for both guard failures, outside the explicitly enumerated G1/G2 queue deltas. Its inclusion needs clarification before claiming exact equality. Only the mandatory-condition diagnostic and historical/fresh S4 wrapper separation are implemented and supersede their earlier repair-pending entries. S5D re-scope/G1/G2/breach, S5G/S5H, same-minute replay, adapter derivations and fresh-condition wiring remain pending. R40 native S5D remains FAILED; its prior source implementation below is not an accepted fixture. No P04 credit is earned.

Historical REPAIR40 implementation supersession

The implementation-pending statements below are superseded only for S5A/S5B power, S5C command destruction, S5D automatic raid destruction, S5E paid midnight and S5F command/planned exit. The single CASE_TABLE now dispatches these cases. No case is relabelled as an executed proof. Root must establish every outcome from fresh Q raw; an unalignable raid or unsupported condition fails normally.

The S5 order adapter does not infer patience_release or paused_midnight. Fresh S3 can supply patience_release only from its own actually observed raw. The remaining frozen REQUIRED conditions, including shift_completion, same_minute_replay and paused_midnight, are not supplied by historical union. The final checker must remain failed if any required condition is missing.

The earlier text is retained as historical planning context:

S5 — pending implementation, not a native run plan

No S5 executable driver or native receipt is supplied by this partial repair. Do not start the once-only Q native/full batch from this directory.

The four required cases remain unchanged:

1. Real mana depletion, NO_POWER, no charge/progress, reservation retained, recovery and one completion. S4's disconnect_nodes is not depletion. The existing cafeteria fixture has an operating kitchen prerequisite; global depletion can select RELATED_FACILITY_INACTIVE first. A driver must observe that distinction rather than relabel the reason or mutate power availability directly. A separate combined-cause case must prove the approved RELATED-before-NO_POWER reason priority.
2. Actual accident or raid destruction during completion: valid minute-N sale; next-minute failure/release for unfinished affected work; compare command destruction before completion. S3 B4a/B4b use a registered event with SET_FACILITY_STATE and must not simply be renamed an actual raid.
3. 00:00 completion: retain the S2a paid-midnight setup and full typed snapshots, add phase observations proving prior-day settlement/upkeep precede the sale, and independently join the sale to the new accounting day. Retain replay/no-double-settlement proof.
4. Command exit versus AI planned exit at completion: retain actual public commands and guest/service/reservation/ledger joins. Observe the AI DECIDING predicate after completion, without forcing guest state or treating a due exit time as universal active-service cancellation.

All prices, durations, resource rules and thresholds come from the selected Q definitions and current public runtime. No new original values or rules are supplied here. These notes identify implementation work; they are not engine evidence and confer no condition credit.