ARCADIA-Studio/harness/release-host-bootstrap-ytr83r-20260911.md

New Windows host build and integration record

Codex-ytr83r /root, 2026-09-11. This host started at clean ff615d0 without Rust, a native C compiler or a WSL distribution. Its runtime evidence is separate from the imported prior-host reports. Full release acceptance remains open.

Source and evidence integration

Behavior c6d296a is merged at c81e285; named creation 4bb4aaf is integrated at e207b04. The current user attachment was copied exactly to PROJECT_GOAL.md. The independent integration review found no lost source semantics and retained both hosts' exact historical ledgers/reports. See the integration report and its 13-blob archive manifest.

Additional evidence bundle 2ec72d4, prerequisite 4bb4aaf, is 185,563 bytes, SHA256 F74E14EE394BCC026E24987C8526AA7E769DDE748FE38117532824EC19AE159F. Hash and git bundle verify passed before import. A complete preflight compared all candidate files before writing: 132 new files, 58 already exact, and three reviewed replacements (creation checker v2 and its two instructions/reports). Local ledgers were preserved. Constructor-default specification changes were applied independently, preserving the new lifetime section. The exact import inventory is .local/transfers/imported-evidence.json. These are imported evidence artifacts, not newly executed native tests on this host.

Isolated tools

Tools live under ignored .local/toolchain; the machine PATH, global Git identity and system Rust installation were not changed. Source .local/toolchain/env.ps1 for task-local Cargo/Rustup paths, LLVM tools and one Cargo build job. Incremental compilation is disabled to limit disk use on this 8 GiB/two-CPU VM.

• Rust/Cargo: stable gnullvm 1.98.1; rustc 48a229cea 2026-09-01, Cargo 797e8a9bc 2026-08-05. rustup installation exited successfully.
• LLVM-MinGW: official llvm-mingw-20260908-ucrt-x86_64.zip, 190,677,197 bytes; its SHA256 matches the release asset digest 1bcf74d06b724aeecaa6412ca85f5b26fb1da770e7cdcefa9263c9c5c3ad34b6. Portable extraction succeeded. Clang and llvm-windres report LLVM 23.1.1.
• Docutils 0.22.2 is installed under ignored .local/python-deps, matching the existing generated-document version. Bundled Python runs document and packaging tools; these are build/verification helpers, not product services.

References: official Rust installation, LLVM-MinGW releases. Downloads showed intermittent stalls but completed without system network changes.

Executed checks and limits

python scripts/test-package-artifacts.py -v passed all 11 tests in 1.808 s. scripts/test-windows-notices.ps1 passed all synthetic notice/source/runtime preflight checks. The preserved temporary fixture is C:/Temp/arcadia-notices-f75e1f32c33148749034b5fe8e0268aa. These checks establish packaging invariants, not an actual packaged release.

The current core all-targets gate passed on 2026-09-11 at12:43:53 UTC: 433 passed, zero failed, one deliberately ignored scaling probe, across44 targets. It took2486.422s including37m12s initial compilation. The exact source tree is a9c71e2c3fc9260d06f191c0d65b1e63e41edbec; raw log and summary retain source, timing, command and log hash. CLI-only01b subsequently integrated as023e3a8 without changing this core tree or registry dependency records.

The ignored inheritance probe separately passed for250/500/1000-record chains, reporting6.670/19.166/38.063s during desktop compilation. This is debug/contended evidence, not optimized GUI latency. The bounded diagnosis separates a preexisting quadratic path from profile/host cost and defines the next controlled measurement. The independent lifecycle oracle also compiled and passed complete model/source/file-map predictions before native output; see its fixture procedure and exact evidence.

Current Windows lifecycle22/22 and full desktop675/675 pass on production2908405; the actual application build is active. Server/CLI/strict checks, native workflows and optimized distributions remain pending. Linux setup/build/checking is paused by direct user instruction until they resolve networking and signal resumption. Cargo gates retain logs and elapsed-time/exit JSON through .local/run-gate.ps1. Source/binary identities and prior-host attribution must remain explicit.