This local archive preserves the original 3aa80de89c5b79200286926781e8f3a192bc61f4 gate and three closed Windows native runs. It is evidence of bounded OA/State attachment editing, persistence, history and eligibility behavior. It is not blanket acceptance of that GUI: immediate post-menu State Escape failed and was addressed by a separate candidate whose native evidence is not included here.

Contents and outcomes

gates/00-frozen-01: earlier 79cc9d555144d5bba34962bf08b5628f1456bc1d failed gate, including tests exit101. Failure is preserved.
gates/01-frozen-02: successful frozen original candidate gate, raw commands/receipts/logs and before/after input manifests. Shared dependency cache was reused; this is not a clean-build claim.
native: original staging manifest/catalog/recipes/baseline and failed staging attempt; all three closed runs; supplemental reconnect predeclaration, validation and rationale. Original receipts and absolute paths are unchanged.
reviews: eight independent source/gate/native reviews, including per-run scope and limitations.

There are 48 distinct native capture files across the three runs. Run1 has nine passing complete Project checkpoints. Run2 has 19 completed comparisons: 15 pass, four midpoint-offset mismatches remain failed (.51/.51 circle, .49/.52 diamond). It also retains a blocked comparison attempt through the shared-build incident record. Run3 has one exact S5 reopen/save checkpoint. Thus there are 29 completed comparison receipts, 25 passing and four failed; a preflight-blocked attempt is not counted as a comparison. All three runs close exit0 with empty GUI logs.

Original R1 reconnect-to-Choice was invalid and correctly refused. The untouched R1 expectation and its validation failure remain, alongside a separately predeclared valid R2 reconnect-to-Final and exact Undo to S5. The supplemental expectation was not retrofitted from GUI output.

The shared target executable was temporarily overwritten during Run2 by a concurrent corrected build. The incident records artifact preservation and restoration before a fresh successful comparison. Original staged GUI/evaluator stayed unchanged. Later input equality and the close flag are observations at their checkpoints, not continuous immutability. The original Escape defect, failed midpoint attempts and this interruption must accompany any publication claims.

No native continuous held-preview, held Escape/wheel or away-return claim is made. Small State symbols required pixel/zoom alignment; some Fit labels overlap or ellipsize. Automated event tests complement these bounded native observations. The separate corrected Escape stage and its active runs are deliberately excluded.

Portable verification

Fetch both source commits into a repository, then run:

python verify-build.py verify --archive . --repo /path/to/ARCADIA-Studio

archive-manifest.json maps 340 copied originals to their archive paths and exact byte counts/SHA256 values. source-map.json maps 5,496 captured source records across the two pins to Git blobs or exact raw overrides. For 3aa80de the split is 2,730 Git-exact + 19 overrides; for 79cc9d5 it is 2,728 Git-exact + 19 overrides. Source overrides preserve captured raw CRLF bytes rather than reformatting receipts or duplicating the whole source tree. The source map itself is hash-bound by the archive manifest. .gitattributes disables Git text conversion throughout this evidence directory.

verification.json records the executed portable check: all 340 originals and 5,496 source records verified; 14,066 of 14,117 receipt references resolve to available identical bytes. The remaining 51 references identify eight paths containing intentionally excluded GUI/CLI/evaluator/runtime binaries. Their original hashes remain in receipts; the verifier does not pretend to rehash absent binaries or reexecute a gate. No nonbinary artifact reference remains unresolved.

Private profiles, mutable working directories, packaged binaries, unrelated working directories, and corrected-stage runs are excluded. Immutable saved source checkpoints remain included. Peers on separate machines use the Git pins and maps, not the original machine paths. This is a staged local directory only; no commit, push or release has occurred.