# Public checked-save failure — Windows analysis847

Closed execution of one existing public regression against source `847b1caa7e75bb82f6ce5193c45bcfc45973ad1a`. **Compilation succeeded; the test failed** when decoding source that checked-save had successfully written. This is finite failure evidence, not acceptance of the analysis candidate or its private JSON/depth codec.

The [short evidence report](../../release-analysis-checked-save-20260913.md) states the result and next repair boundary. [Original detailed handoff](run/README.md), [exact command/result](run/result.json), [full Cargo output](run/cargo.log), [raw committed input manifest](run/inputs.json), [toolchain/environment preflight](run/preflight.json), and [direct one-test listing](run/membership.stdout.log) retain actual evidence. All512 input hashes and the clean source remained unchanged; the listing selected exactly one test. Cargo returned101;0 passed,1 failed,14 filtered out.

The original result's `log_test_failed: false` is preserved. Its auxiliary matcher expected the test name and FAILED on one uninterrupted line, while nocapture inserted panic text. Cargo's exit/counts, named failure, panic at review_regressions.rs464 and executable membership are authoritative. No result was rewritten to hide this imperfect diagnostic.

`archive-manifest.json` inventories every payload except itself. Files under `run/` and the exact original runner under `tools/` are byte-for-byte copies. Original handoff/helper paths refer to the original local workspace; archived placement is evidence, not a claim that those paths automatically relocate. The archive helper is retained for review, not intended for a second create attempt at existing output paths.

[external-bindings.json](external-bindings.json) identifies the excluded30,458,368-byte failed integration executable, retained local target, runtime candidate and source commit. The executable hash was rechecked during archival: `c6b9a47856ace723de47ee714122d598994eeef21223c1f80558ae76eb4b9cec`. The large target/executable and toolchain are not copied. The test's temporary saved model was dropped by its unchanged tempfile lifetime on panic; no saved-model snapshot is claimed. The runtime record identifies a PATH candidate, not a captured loaded module.

Compiler/test lease was released after the actual failure and exact listing. Archival performs no compiler, test, native, network or package operation. Parent owns source correction, further execution, coordination and integration.