3.1 KiB
Preserved strict readback refusal and narrow evidence amendment
The first final97a8703 readback ran inspect_runtime.py SHA-256 bdf2bb33dd54916440b8dfde1b8bd38d61d3975d8c760deeccf1c92eb562c8d3 with arguments 97a8703adc75467a7f8e75f5c6cb00ca542b707c 97a8703 6. It stopped at line190:
assert old_blocks == new_blocks, 'Failure bodies differ beyond thread PID'
AssertionError: Failure bodies differ beyond thread PID
No successful readback JSON was created by that attempt. Exact original helper bytes are preserved as inspect_runtime_strict_original.py. This is a real comparison refusal, not a source/test failure; it is not erased by the later scoped checker amendment.
Only language::nesting_tests::checked_in_example_supports_cross_file_reparent_without_changing_allocations differs. The old8d52dab full log SHA is 1a31c94c3f0a0b6157be381118ee6a9d708b3241c545c8d7f99bc3de94d78871 (independently hashed raw file, also bound by the baseline archive). The final97a8703 raw full log SHA is 7cd8ac2de3b641e0421f48196be255c6b79706049e814e9f62ca2936794f8f71.
After numeric thread-PID replacement only, the old block SHA is cd6ec346dde1f43b82ca244a8b56754d209cf8108693caed8bb00a1a8ef32e1e; the new block SHA is d074bcb3e4edbd2622b3cf1a0ed4cac1aa752f9761cb5ffc526540aed4fb1c04. The sole removed byte sequence is exactly this LF-terminated line:
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Old block, with numeric PID replaced:
thread 'language::nesting_tests::checked_in_example_supports_cross_file_reparent_without_changing_allocations' (<PID>) panicked at crates\oa-core\src\language_nesting_tests.rs:502:69:
called `Result::unwrap()` on an `Err` value: [SourceDiagnostic { path: "project.arcadia", diagnostic: Diagnostic { severity: Error, code: "invalid_source", object_id: None, field: None, line: 1, column: 9, message: "Unsupported schema version: expected arcadia 3, 4, 5, 6 or 7.", span: Span { start: 8, end: 9 } }, related: [] }]
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
The new block is exactly the above block minus that one hint line, including identical surrounding LF bytes. No location, diagnostic, panic message or whitespace changes are permitted. Initial6b0ef99 full log SHA 80f3ada1357adcbe213a43c60ae0aea62e8f5aaa900c3177c8c01ea96b341c17 has exactly the same single changed block and the same normalized new-block SHA; its other15 blocks are also exact after PID replacement.
Parent explicitly selected a narrowly documented exception. Updated checker requires exactly this one changed named block, exact old/new block hashes, one old hint occurrence, no new hint occurrence, and exact equality after removing that one old line. It does not broadly normalize framework output. Result reports15 PID-only identical blocks plus1 documented delta; all269 prior outcomes must still be unchanged.
The new successful catch_unwind refund test may consume a process-once Rust backtrace hint before the first inherited failure; this is an inference, not an independently observed causal trace. No source/test changes or runtime reruns were made to obtain matching text.