Windows gates for a57c334 — 2026-09-11
Closed Windows build/test evidence for source a57c334b302eb13352b4bb65df1c75d94d002348 in .local/canvas-union-ytr83r-20260911. Baseline 32334c66317692befb6517a917dc7ae90641c11a retains production 865483b; the selective canvas union incorporates peer a31b40d0f8551ed87c8cd66250b9afb4809b3a79. Root supplied the exact source commit; the saved verify-head receipts independently identify matching HEAD inputs rather than embedding the full commit hash themselves. See the source-review archive for that source mapping and scoped independent reviews.
Closed commands and results
All dates below are 2026-09-11 UTC. Status completion times, not filesystem modification times, identify completion.
| Gate | Exact recorded command | Completed UTC | Result |
|---|---|---|---|
| Focused lifecycle | cargo test -p oa-desktop --offline --locked scenario_lifecycle -- --test-threads=1 |
19:55:46.4531913 | Exit 0; 27 passed, 0 failed/ignored, 725 filtered |
| Full desktop | cargo test -p oa-desktop --all-targets --offline --locked |
20:06:06.1170595 | Exit 0; 752 passed, 0 failed/ignored/filtered |
| Strict desktop Clippy | cargo clippy -p oa-desktop --all-targets --offline --locked -- -D warnings |
20:13:49.0390005 | Exit 0 |
| Studio build | cargo build -p oa-desktop --bin arcadia-studio --offline --locked |
20:20:48.7677661 | Exit 0; unoptimized dev profile |
The focused run began at 19:42:20, before the source commit; its exact frozen inputs were subsequently mapped to a57c334 by root. Both test logs identify the same test-binary path arcadia_studio-df984b90c0583184.exe. The 27 cases overlap the full 752; do not add their counts. Strict Clippy is scoped to desktop all-targets, not a claimed whole-workspace Clippy run.
The environment record identifies stable-x86_64-pc-windows-gnullvm, clang.exe, one build job, incremental compilation disabled, and the main checkout's target directory. The remaining-gates report identifies the existing run-gate/toolchain helpers; those referenced helpers were not executed or newly archived here. The included preserve-build.ps1 is the exact closed binary-preservation procedure, retained as source evidence only.
Input and binary provenance
The unchanged inputs.json was captured at 19:42:03.377142 UTC and still says “Uncommitted combined candidate.” That original text remains historical. Its 529 records total 9,712,849 bytes; SHA256 47FEC9CADC0E7FAE99D789376C111C02EEAAB7FAC3740DE48174A06F61FE16B3.
The included verify-head receipts report PASS against the same manifest at 20:08:39.612202 (before Clippy), 20:14:02.648124 (after Clippy), and 20:20:58.775988 (after build). Each records 529 files and the same byte total. Root's earlier 19:44:32 source-to-commit equality is summarized in the source-review archive; no separate original receipt for that earlier check was present in this selected directory. The archiver checked receipt consistency and manifest totals, not a fresh source/Git equality run.
At 20:21:10.007019 UTC, the preserved binary manifest records equal source-before/copy/source-after hashes and sizes, with read-only destination copies:
| Excluded binary | Bytes | Recorded SHA256 |
|---|---|---|
| arcadia-studio.exe | 113,028,608 | 69DBB90FA299B3B3D90140C7934891F79166025893AF9B35B2B8D754A37A0D40 |
| libunwind.dll | 190,464 | AA282FA47BB2C4E210CEA5E470CDBDCA58568F0BE0BC73E404D86AB9CD95EF6A |
Exact original and immutable-copy paths remain in binary-manifest.json. These are bound from the preservation receipt; binaries were not rehashed or copied by this archiver. exact-inputs.zip, executable/DLL directories and raw source snapshots are excluded. No ZIP container hash was recorded in the selected input manifest; the 529 constituent file hashes are preserved.
Archive and acceptance scope
Sixteen byte-exact payloads comprise four log/status pairs, the input manifest, three HEAD-verification receipts, environment and binary manifests, preservation script and remaining-gates report. All four statuses are closed exit 0; test-summary/log checks and receipt consistency found no unresolved gate ambiguity. verification.json records those archival checks. manifest.json freezes every original path, size, original/copy SHA256 and original modification time. readback.json records a second original/copy readback against that frozen manifest.
This is an evidence copy, not another execution of the gates. No Cargo, compiler, script execution, GUI, source, Git/index, Gitea or WSL action occurred while archiving. Prior archives and live records were untouched.
The new 69DB Studio has no native acceptance in this archive. Existing native child-work evidence for old 865483b/BF9 remains valid within its separate continuation scope; it does not validate new canvas pixels or interaction. Matching new-GUI native checks and package/release acceptance remain root-owned.