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

REPAIR45 — whole unit remains incomplete

REPAIR45 — implementation ready for submission

The supplied byte-verified M engine-free context resolved the REPAIR44 UID dependency. UID controls: all 14 PASS, exit 0. Both supplied helper SHA-256 pins match exactly. AST and explicit fresh BUILD-cfile py_compile passed for all eight touched Python files, with python3 -B and PYTHONDONTWRITEBYTECODE=1. No source was changed in REPAIR45; retained passing controls were not rerun. The no-pyc static check passed again (exit 0); generated compile files exist only under allocated BUILD. The prior UID failure remains recorded as failed, not replaced with a PASS.

Sequential check-only S1, S2a, S2b, S3, S4 and S5 each returned exit 2: ValueError: checkout is not clean The initial missing-tested-tree argument refusals are also retained. The later attempt used the actual HEAD tree solely as a guard input, not a claim of final Q, clean source or C. No engine started. Root executes clean exact-Q check-only after automatic submission. Full argv/stdout/stderr and compile paths are in REPAIR41_STATIC_CHECKS.json. No Git writes, Runner or native run were performed.

Implementation is ready; the whole original unit remains incomplete and P04 credit remains 0. Deferred Root conditions, in order: freeze final Q; affected pure controls; clean exact-Q check-only; capacity check; one heavy lease with fresh native S1–S4 and all ten S5 cases; independent Reader and adapters on actual raw (including fresh Reader order positives); fresh collect; full 184 suite once; index; --verify-only; registered validation before review; independent whole-unit Opus review; normal prepare / exact C / integration / final / Root DB join / ledger / main push. Native Reader and acceptance remain pending. patience_release stays pending unless fresh S3 raw shows it. Product freeze, M, allowed paths, REQUIRED membership/thresholds, all seven domains, G1/G2, R40–R44 and the existing one-trailing-LF spec protocol remain unchanged.

REPAIR44 — original whole unit incomplete

Worker status is blocked, not ready for Root native execution. UID pure control could not read the supplied Q checkout's tools/run_all_tests.py (PermissionError). See ../REPAIR41_STATUS.md and ../REPAIR41_STATIC_CHECKS.json. AST/build compilation for every touched Python file and check-only S1–S5 remain unexecuted; resume worker verification before freezing a final Q.

Native Reader and acceptance remain pending. The current ten-case roster is S5A_PURE, S5B_DEPENDENCY, S5C_DESTRUCTION_COMMAND, S5D_DESTRUCTION_RAID, S5D_IN_FLIGHT, S5D_PAID_BEFORE_INCIDENT, S5E_MIDNIGHT, S5F_EXIT, S5G_SHIFT_1080, S5H_PAUSED_MIDNIGHT.

The new case supplies a typed raw derivation for N completion/payment, public event destruction after payment, and N+1 failure/release of the secondary. It does not supply executed native evidence. The D05 destruction gate requires it in addition to every existing command/guard/idle/in-flight gate. patience_release stays pending unless fresh S3 raw proves it.

r35, r36, R40 native and R43 native remain FAILED. Q37 is a local PASS for its own version only. R43 Writer 2749/0, seven Writer-only derivers plus G1/G2, twelve pure controls and six check-only steps retain their limited historical scope; none is independent Reader proof. Original credit 30/88, formal credit 16/88, P04 credit 0; no new task/unit/worker or completion claim.

REPAIR41_STATIC_CHECKS.json records only worker checks actually executed. Root must freeze final Q, then follow S5_ROOT_RUN.md, including fresh S1–S5, Reader/adapters, collect, full 184 suite once, index, verify-only, registered validation, independent review and normal integration. Historical text below does not replace this order or the current ten-case roster.

Historical 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.