1.8 KiB
Exact target-path spelling exception
First final readback invoked strict inspect_runtime.py SHA256 5ea98b7c5f46c09f434c040f37495f43536fd79fb6b61c8ba111dd5716936c8e, args edf096cd33350865ecfc3c65ec266a6c0d3c4000 edf096c 11. It failed before creating JSON:
File "C:\Users\User\Documents\Git\ARCADIA-Studio\.local\analysis-output-acceptance-review-20260925\inspect_runtime.py", line 140, in <module>
assert data['cwd'] == str(root) and data['environment'] == expected_env
AssertionError
Original bytes remain unchanged as inspect_runtime_strict_original.py. All five current receipts differ from baseline only in the literal CARGO_TARGET_DIR separator spelling:
old: C:/Users/User/Documents/Git/ARCADIA-Studio/.local/analysis-checked-save-target-20260913
new: C:\Users\User\Documents\Git\ARCADIA-Studio\.local\analysis-checked-save-target-20260913
Parent approved only this exact pair after resolution to the expected absolute workspace target. The amended checker hardcodes both raw strings, asserts baseline old spelling, resolves both equal to the explicit workspace target, then requires the complete new environment dictionary exactly. All other fields and all five current raw spellings must match. It does not normalize unknown paths, relax source/artifact matching or normalize failure bodies beyond numeric thread identifiers. Parent attributes the spelling to Join-Path setup; no gate rerun was performed to change evidence.
Amended helper SHA256 8fdf8c0ba848d8f61cb09739961239c316fdb0eb17e4b64b88ae34274cce0f53 completed the entire readback with exit0. JSON preserves both raw environment dictionaries plus the explicit exception. This documented evidence-format correction is not a source/test repair and does not erase the initial strict refusal.