Both saved-source comparators built successfully and passed their self-checks at b10b28cefd1d0794073ba241a0c8de9a83e85f68. The desktop GUI build also completed successfully. This archive contains no native workflow pass or actual native saved-output comparison.

The spacing recipe's original directory includes 8bf7607 in its name. That is preparation ancestry, not its tested source identity: its current build and self-check receipts explicitly bind b10. Historical preparation wording inside copied READMEs is preserved; the closed receipts below establish these later results.

Closed results

Artifact	Actual result	Exact before/after input records
Details comparator build	Exit 0, strict `rustc -D warnings`, empty compile log	1,607
Details self-check	Exit 0, all 13 reported checks passed, empty stderr	637
Spacing comparator build	Exit 0, strict `rustc -D warnings`, empty compile log	963
Spacing self-check	Exit 0, all seven reported checks passed	13
Desktop GUI build	Exit 0, `cargo build -p oa-desktop --bin arcadia-studio --locked --offline`	612 source records unchanged

The Details self-check admits the incident and service fixtures; checks the Name-only candidate and all six approved typed checkpoints; and rejects wrong occurrence, alias, semantic sequence, layout, signed-zero, invalid target/no-op, wrong checkpoint/Project identity and unknown expected-field variants. The immutable typed expectations retain their independently published core provenance; no native output supplied expected values.

The spacing self-check checks exact repair C from 300 to 424 and its inverse, A-lane-only change and inverse, other-view/name/Steps corruption rejection, repeated exchange occurrence distinction and signed-zero sensitivity. Its source, fixture and comparison logic are preserved. Neither self-check inspects a native editor buffer, camera, Document history stack or source-writing action.

Both independently decoded incident baseline JSON files are byte-identical. The Details service baseline also equals the independently approved baseline JSON. These checks support comparator consistency; they do not establish a GUI interaction or saved native checkpoint.

Binding and preserved evidence

The Details build receipt uses the successful b10 LIST and its exact test-executable/dependency fingerprint graph. Its compile prerequisite is deliberately smaller than native staging. The spacing build receipt uses the completed five-stage GUI gate and its production desktop -> core -> serde graph. Their rlibs need not have the same filename: the recipes verify the respective actual graph, compiler, source and lock bindings.

Both runtime checks bind the actual adjacent libunwind.dll before and after execution. The spacing build additionally records the source DLL and copied runtime separately. Small selected Cargo fingerprint and dep-info records are preserved; executable/library/toolchain caches are not copied.

The new GUI build receipt, raw build log and source captures extend these already published prerequisites:

Published-prerequisite mapping identifies 49 exact gate inputs already present there. Their local published bytes were compared against current receipt-bound originals; unrelated old gate history is not duplicated. The frozen native verifier and environment recipe are included.

Archive manifest records 87 copied originals totaling 2,471,043 bytes. Archival checks verified every copied byte, build/run manifest equality, receipt hashes and reference links, all output artifact hashes, 632 unique current comparator-source records, 649 unique current run inputs, current GUI source records and the listed binaries. The complete transitive dependency caches were not redundantly rehashed during archival; their closed before/after records are preserved. No comparator, compiler, native UI or Git mutation was executed during archival.

Omitted executable	Bytes	SHA-256
Details comparator	19,775,488	`996803f938b7503db8508adf9b7fc2dd379852b5b603463edf6987dd1e5270a6`
Spacing comparator	22,720,512	`ce536924836d62210639a3af76d15793d0bd51a429d8cac0c90edde66955fe62`
Desktop GUI	116,721,152	`7ece85c6012ae0ae75fc56ed3c3aadb8bc116448ad1782be422ef34a629dc3ce`

Each omitted adjacent runtime DLL is 190,464 bytes, SHA-256 aa282fa47bb2c4e210cea5e470cdbdca58568f0be0bc73e404d86ab9cd95ef6a. The full binary records, build/self-check receipt hashes and verification scope are in verified-results.json.

Reproduction boundary

Reconstructing the prerequisite gate files from the published mapping supports historical verification of these records. It does not make their original absolute paths, executable hashes or artifact bindings valid after relocation.

Executable reproduction on a different machine requires fresh local b10 gates, local compiler/linker and native-library inputs, and actual local fingerprint/rlib bindings. Review path-adapted copies of the Details recipe and spacing recipe before running them. Keep spacing's oracle/main.rs one level below its fixture so the unchanged include_str! resolves correctly. Local runs produce new receipts and executable hashes; never substitute relocated files for the original bound artifacts or weaken checks to admit the historical hashes. This archive supplies source and historical metadata, not a bundled runnable build/cache.

Build into fresh output directories using each reviewed local recipe's explicit parameters. Details requires its fresh successful local LIST, reviewed ReferenceReceipt/SHA, NativeVerifier/SHA, RuntimeDll, fingerprint and rlib paths. Spacing requires reviewed SourcePin, its fresh complete local Gate, verifier/SHA, runtime and rlibs. Use each checker with the newly reviewed local EXE and build-receipt SHA for self-check. The original command arrays remain historical evidence; they are not ready-to-run commands for another host. Never rerun into the archived output directories.

Actual name, typed, lane, message, repair-c and checkpoint same comparisons still require independently captured native input/output checkpoints. GUI launch, Properties recovery, drag behavior, Save/reopen and Undo/Redo observations belong to separate native evidence. Raw-evidence .gitattributes prevents line-ending normalization; publication must force-add ignored logs.