3.3 KiB
Current evidence plan — repair22, NOT RUN
Use s4/S4_ROOT_RUN.md for the exact finite fresh plan and complete input, QA, source and output footprints inside own B. One native collection has four phases: import, parse, Writer, Reader. Do not rerun C/S1/S2a/S2b/S3. Preserve all existing raw and full R17 relocation. External old paths are provenance only.
After S4 succeeds on this auto-submitted source, Root runs the existing eight local suites once. The worker has executed none. First run these seven from the submitted checkout:
export B=/Users/korizatou114/Projects/TheTree-managed-worktrees/p04-01/.runtime/P04-01/build
export E=docs/plans/original-completion-2026-10-02/execution/p04-01
export BUILD_OUTPUT_DIR="$B"
export PYTHONDONTWRITEBYTECODE=1
python3 "$E/bulk_reader_equivalence.py"
python3 "$E/checker_negative_fixtures.py"
python3 "$E/checker_applicability_fixtures.py" --native-bundle "$B/audit-support/native-first-current"
python3 "$E/checker_native_fixtures.py" "$B/audit-support/native-first-current"
python3 "$E/checker_series_fixtures.py" --build "$B"
python3 "$E/checker_encoder_fixtures.py"
python3 "$E/checker_join_fixtures.py" --build "$B"
The read-only R verifier/collector must then bind the new verifier to all existing raw plus S4. This does not launch native runs or overwrite old collections:
python3 "$E/collect_p04_native.py" --build "$B"
Its exclusive destination is B/audit-support/p04-raw-collect-r22. The index builder/checker now reference that collection and all five series. Root must prepare the corresponding current index through the normal schema2 path before its role/cross-gate controls can succeed; an old r20 index is not valid new evidence. After the new R collection and normal index preparation, run the eighth suite against that refreshed index:
python3 "$E/checker_role_fixtures.py" --build "$B" --evidence "$B/p04-evidence"
No Root command or metadata bypass is invented here. Use registered runner.validate("P04-01") with its unchanged timeout and exact new submission, then the normal independent review/integration process.
Rebind support53cb through its normal registered task after the new P04 source is known. Do not edit metadata to force applicability. Source-only preparation does not wait for future Root-native/index/cross-gate work.
The existing21615-check full proof is immutable. Its1339 selected map contains exactly the R17 product1338 plus the checker; static raw-map comparison found no product hash difference. The178 product suites do not execute this checker; the316-file .gd parse roster excludes .py. Thus the prior proof is a QA-only product applicability candidate, conditional on Root checking the complete source/config/input/environment dependencies. It is not new-checker validation, S4 evidence, a byte-identical1339 proof, or final acceptance. Never splice raw from different versions.
No blanket full run now. If formal policy requires an exact final1339 run, perform it once only after all fixes, S4 raw, local checks/eight suites and the support rebind are bundled on the final source, to a fresh destination. Existing full/parse/marker outputs are neither regenerated nor relabelled by this worker. 15 conditions + EV, seven domains, three safety outcomes,30/88 and original 13/88 remain unchanged. S4 and all new validation are pending.