Files
ARCADIA-Studio/harness/experiments/edge-attachments-53d01a3-20260923/corrected/README.md
T

4.2 KiB

Corrected State attachment Escape evidence

This staged archive covers GUI commit 53d01a3d44, packaged GUI SHA256 9c7aa0249378cec31639bbbff5ea7b3eaab782333d1637b8ab5e8f3be5d65d2c. It is a bounded correction of the original immediate post-menu State attachment Escape failure. The complete saved-Project evaluator remains pinned separately to 3aa80de89c; unchanged committed core/Cargo inputs support that reuse.

Evidence and limits

gates/ preserves targeted, desktop, strict clippy, build and toolchain receipts/logs and the source input manifests. Historical receipts describe the then-uncommitted changes over 3aa80de; they were not rewritten after committing. Commit-readback ties the tested raw bytes to 53d01a3. failed-stage-01/ preserves the prior unsuccessful staging contents. native/provenance/ discloses artifact relocation and evaluator reuse. The corrected stage binds its preserved/package artifact, never the mutable shared target.

Corrected Run1 has nine captures and four exact complete Project checkpoints: B, A1, B, A1. The two arm→Escape visual sequences support return to Select/move for source and target without a canvas click, as recorded by the operator. The B checkpoint occurs after both cancellation attempts together, not once after each; individual tool-state claims depend on the native observations and captures, not separate saved-model checks. A1 differs from B only in State view200, relation41 source_attachment Right/.5→Top/.25; opposite end, waypoint, label, semantics and other views remain exact. Subsequent Undo and Redo produce B and A1.

Corrected Run2 has three captures and one exact A1 checkpoint after reopening and saving. Its distinct process is chained to Run1's close. Both normal-close receipts report exit0 and empty GUI logs. Run1 close-action utc is a retrospective recording time, not the exact input time; Run2 names its metadata timestamp recorded_utc. Observer process-exit times remain separate. All 12 original captures are retained, along with four independent reviews.

This evidence does not establish continuous held-motion preview, arbitrary held keyboard/wheel cancellation, full accessibility or every attachment scenario. The native tool supplied complete drags. Guidance is truncated and small labels can remain dense at Fit. The original archive retains the original Escape defect, midpoint failures and shared-target interruption; this corrected trial does not erase that history or imply continuous historical immutability.

Portable verification

Keep the separately prepared original-stage-01 archive, unchanged, as a prerequisite. Its archive manifest SHA256 is 2379fb100e529772ea6149554fee71aca80ab956539e97aa4d288b189ff55131. Fetch the source commits, then run:

python verify-build.py verify --archive . --repo /path/to/repository --related-archive /path/to/original-stage-01

archive-manifest.json maps 132 raw originals to archive paths and hashes. Original receipt paths/content are unchanged. source-map.json maps all 2,750 corrected captured source records directly to exact Git blobs at 53d01a3, with no raw overrides needed. The verifier also rechecks the prerequisite archive's originals/source records to resolve reused evaluator/gate provenance without duplicating the full source or original archive. .gitattributes prevents text conversion.

verification.json records successful verification: all originals/source records match; 30,392 of 30,422 receipt references resolve to available exact bytes. The remaining 30 references are only eight intentionally excluded GUI/evaluator/runtime binary paths. No nonbinary reference remains unresolved. Their declared binary hashes remain preserved; absent executables are not falsely described as rehashed by the portable verifier.

Binaries, private profiles, mutable working directories and unrelated working directories are excluded; immutable saved checkpoints remain. No publication, commit or push is performed by this archive preparation. Native claims and limitations are assessed in reviews/; reproduce across separate peer machines using the commit identities, maps and receipts, not the original absolute paths.