2.8 KiB
Repair 32 — partial implementation submitted; no acceptance claim
Only new concrete32 files were added. Existing partial31 files, including the checker and s5/PENDING.md, were not edited. No condition credit is claimed: formal 16/88, original 30/88, P04 credit 0, all 15 conditions plus EV, frozen Mc0 and all six approved D05 items remain unchanged.
Implemented, unexecuted:
- S5 power driver pair and S4-derived wrapper: public bath pure depletion and cafeteria/kitchen reason-priority depletion; public spend/recovery commands; observed completion; same-key replay; full typed/JSON phase points; formal save/independent Reader load/replay. No disconnect or direct resource mutation.
- Hashed raw semantic adapter for existing power_stop, dependency_stop and recovery_completion measurement keys. It does not qualify native provenance.
- Read-only normal_c_join over actual Runner task/candidate/main_base, approval, validation/review and integration/final records. No future C hash is frozen. Root must retain an actual approved Runner snapshot before integrate deletes approval; later final records come from the current Runner database.
- Root-run synthetic normal join controls and explicit-scratch adapter for preserved Git fixtures. No fixtures were executed.
- S5_ROOT_RUN.md and NORMAL_C_BOUNDARY32.md explain boundaries and limitations.
Actual verification: Python AST/compile for five new Python files and textual probe controls passed. No pycache, engine, Godot parse, Git command, Runner operation, fixture, formal validation, independent review or integration ran. The shell rejected a here-document temporary-file allocation; subsequent commands used python -c. An attempted documentation addition at the repository root was rejected and no file was created there; the document was added within allowed_paths.
Remaining implementation limitations:
- The old checker still deliberately rejects normal C: preserving partial31 means this standalone Runner-record join is not connected to its role output. It does not assert Git structure/Q equivalence and cannot bypass that gate.
- The S5 wrapper retains historical S4 template identity/count bindings. Fresh-Q plumbing is outside this step and remains pending; this is not batch admission.
- S5 destruction/midnight/exit, fresh-Q/full184/329, truthful collection/index, exact-version applicability, independent review and ordinary gates remain pending. None was attempted together or counted as a new unit.
- Scratch adapters preserve the old fixtures' assertions; positive normal-C structure fixtures under the eventual integrated boundary are still pending.
Runner/Root must run the permitted static fixtures in external scratch, review the added source, and resolve boundary integration before the established once-only genuine-Q/native/full sequence. No evidence or completion is invented.