# Navigation prerelease producer preparation — 2026-09-11

Codex-9e8r6t `/root` owned preparation, packaging and source publication; `/root/release_audit` prepared the adapters, `/root/behavior_audit` independently reviewed them, and `/root/linux_readiness` preserved and checked the evidence.

Producer preparation and package readback passed for `0.2.0-preview.navigation.20260911`, Windows gnullvm. The ZIP contains **559 files / 32,971,712 bytes**, SHA256 **`d7228c542f162663933ea002739a78c722bcca41e437df63b7c868ea2af201f1`**. This is producer integrity evidence: independent extracted-package, server/native and release-publication results remain separate.

## Attempts and exact source

The first preparation started at 21:03:07 UTC and failed during `git checkout-index --all` at 21:03:40. Its helpers, static admission, failed result and partial reconstruction identity **613c480a27426dd25f17b339803f789ac3dbf0ea** are preserved. Original Git stderr was not retained. A later audit found seven missing paths of 260–266 absolute characters among 2,174 tracked paths; all present paths were at most 259 characters. This strongly supports a Windows path-length limit without proving the missing diagnostic.

The independently reviewed retry used a fresh shorter directory, command-local `git -c core.longpaths=true`, and failure logging, preserving exclusive-output and root-state guards. It succeeded at **21:09:43 UTC**, without compiling an executable or changing root HEAD/index/tracked state. It verified **500 GUI inputs**, **15 measured newline-only restorations**, shared build resources, and **120 separately historical server inputs**. No count or newline transformation was assumed from the older package.

Successful reconstruction **802855f7e6f2f00a107a12196b458b267f586b8d** has the same tree `09741096d6074291e22a967855e7b81e247d3e09`, parent `33c6d83e9ba9a5b1310b1b627d7c40affcbcf15c`, identity and message as the first reconstruction; only author/committer timestamps differ. Actual commit objects and the reconstructed attributes are preserved. These source reconstruction commits are not the original GUI build commit. The GUI was built from captured `eeeaa126` plus the three-file repair delta, committed equivalently at `33c6d83`; its [500-file gate archive](experiments/text-navigation-native-20260911/repair-save-correction/README.md) retains the original provenance.

Root published the [exact reconstruction source](http://217.177.34.108:3000/sorokin.oleg.edu/ARCADIA-Studio/src/commit/802855f7e6f2f00a107a12196b458b267f586b8d) on `codex/navigation-repair-prerelease-source-20260911` at **21:17:00 UTC**. The branch was absent beforehand; a normal push and exact remote readback passed. The helper and receipt are preserved. That operation created no tag, release or asset upload.

## Binary and dependency boundaries

The package retains GUI **B183**, SHA256 `b183ef31f16b3986538b3f2aba8435eab45978635c47f99ca01be6e72b168848`, 113,206,272 bytes. Its prior full desktop gate was 755 passed / 0 failed / 1 ignored, with strict Clippy and a matching development GUI build. The separately recorded [native-v4 repair trial](release-text-repair-save-native-v4-20260911.md) passed missing/duplicate/journal repair flows; it was not a launch of this ZIP. Root's raw-index admission initially refused ignored native logs; the final 168 raw blobs were verified and published at `8cf64ce` rather than treating the first attempt as complete.

Server **EFEE**, SHA256 `efeeb89c0d2e0f93df4472cb3e9f48b2b722a37ae1043c90a5a56f2e845fe665`, 39,743,488 bytes, is the unchanged September 7 development artifact. It was not rebuilt from navigation source. Current GUI core changes `language.rs` and adds `language_outline_tests.rs`; these are not silently attributed to the historical server.

Fresh byte-level inspection proves all **120 original core/server files** equal both the historical tar and the Git blobs at published [b2c3e54001fc19a05423bcd5808ceea78d13ff59](http://217.177.34.108:3000/sorokin.oleg.edu/ARCADIA-Studio/src/commit/b2c3e54001fc19a05423bcd5808ceea78d13ff59), consistent with the [committed contextual review](release-contextual-source-prerelease-review-20260911.md). Their paths, Git blob identities, SHA256 and sizes are preserved. Thus this input set is recoverable without the local tar. The **full 459-file tar** remains a separately identified artifact: 2,089,801 bytes, SHA256 `cbb371a93a562e1e641d7629fe351e016d63e66fc9112499b3fed6d5cd171f78`. Its member inventory and five original workspace Cargo/build files are retained, without claiming the 120-file proof reconstructs the entire tar or executable. Historical top-level Cargo/docs/compiler claims retain their original scope.

The unique original dependency-notice inventory is preserved separately from current generated notices. Producer readback verified **263 historical registry packages** are covered, **266 current notice packages** across desktop/server roots, exact relevant notice/font payloads, and **17 local documentation links**. DLL import records are in package metadata. This does not establish a new server build or runtime pass.

## Producer execution and preservation

One locked, offline, target-filtered Cargo metadata call passed at **21:10:26 UTC**. Packaging passed at **21:12:50 UTC**; producer readback passed at **21:13:15 UTC**, verifying the staged package, actual ZIP, checksums, 500 reconstructed GUI inputs, historical server input set, binaries and notices. No application or compiler was launched by the archive worker, and no validation was rerun while preserving these records.

[The raw archive](experiments/navigation-prerelease-20260911/manifest.json) preserves both adapter sets and independent static reviews, actual receipts/logs, reconstruction records, package metadata/checksum, historical source proof and notice inventories. Reused exact GUI gate and old server-build records are linked to verified committed copies. Executables, the ZIP itself, clones, caches, profiles and the full historical tar are excluded; identities and locations are retained. Original adapter READMEs and `VALIDATION.pending.md` remain historical, without rewriting their pre-execution assertions into results.

Archive verification passed for **56 payload files / 4,032,493 bytes**, plus manifest/readback. Manifest SHA256: `dc35192a128ff6164835fe7176c8664f971d47799ff085953e748a886b060e93`. Readback SHA256: `2b78aa3ae108274dd7f418c17e59c320a3122c6676d4726328342ba8cee3832e`. Copied originals and reused committed equivalents were matched byte-for-byte; the verifier checks the whitelist, hashes and receipt consistency without running packaging or runtime checks.

Independent artifact/extracted server/native acceptance and final tag/release publication remain pending in this producer record. Linux/WSL is paused. No full application acceptance is claimed.