# Second closed binary reclaim audit — final six candidates

Parent narrowed the scope to preserve the rename desktop attempt8/server attempt1 gate binaries promised by the first cleanup. **Only six candidates remain: 605,763,584 bytes (577.7012 MiB).** Nothing was removed or moved. No shared target/cache/toolchain/WSL/VPN inspection or cleanup occurred. The earlier eight-item exploratory JSON is retained only as `closed-binary-reclaim-candidates-2-superseded-draft.json`; it is not an approved candidate set.

Final authoritative paths, byte/SHA256 pins, retained counterpart/ZIP entries and closure receipt hashes are in `closed-binary-reclaim-candidates-2.json`.

Candidates relative to main `.local`:

1. `text-navigation-native-20260911/bin/arcadia-studio.exe` —113,197,056B, retains exact `text-navigation-desktop-20260911/gui-v2.exe` (df7126b8…4ceabd).
2. `text-navigation-native-20260911-v3/bin/arcadia-studio.exe` —113,204,224B, retains exact `text-navigation-desktop-20260911/gui-v3.exe` (5478e783…724f).
3. `text-repair-save-20260911/gui-repair.exe` —113,206,272B, retained published navigation ZIP entry (b183ef31…168848).
4. `text-repair-save-native-20260911/trial/bin/arcadia-studio.exe` —same byte count/hash and ZIP entry.
5. `navigation-package-review-20260911/extracted/ArcadiaStudio-0.2.0-preview.navigation.20260911-x86_64-pc-windows-gnullvm/arcadia-studio.exe` —same byte count/hash and ZIP entry.
6. Same extracted package `/arcadia-server.exe` —39,743,488B, retained published navigation ZIP entry (efeeb89c…5fe665).

Retained ZIP, independently hashed and both executable entries read with CRC and full size/SHA equality: `C:/Users/User/Documents/Git/ARCADIA-Studio/.local/nav-repair-retry-20260911/packages/ArcadiaStudio-0.2.0-preview.navigation.20260911-x86_64-pc-windows-gnullvm.zip`, 32,971,712B, SHA256 `d7228c542f162663933ea002739a78c722bcca41e437df63b7c868ea2af201f1`. It is the known published asset pin; remote publication was not queried. Do not delete this ZIP or the gui-v2/v3 counterparts.

Closure precision: old v2/v3 native runs have historical after-close binary readbacks at2026-09-11T19:00:35.429459Z /20:26:05.407841Z; these records do **not** establish a captured normal exit code. Repair native after-close20:59:59.044480Z explicitly records caller-observed absence and disclaims helper process/exit observation. Their eligibility is historical closed observation plus current absence and preserved identical bytes, not an invented normal exit0. Repair GUI build has a completed artifact-bound gate receipt. Navigation package artifact review endedPASS21:22:41Z. Its real GUI PID1348 has a separate same-creation closed-process receipt at21:32:12.206331Z with actual queried exit0; the failed original closure helper remains distinct. Package server PIDs2440/5504 exited1 after explicit termination; completed runtimePASS21:23:19Z is not graceful-shutdown acceptance.

Targeted Win32_Process readback for arcadia-studio.exe / arcadia-server.exe / gui-repair.exe is empty, timestamped in `reclaim-process-readback-2.json`. This is not a lock: parent must recheck hashes/process absence immediately before any six explicit file removals and preserve a before/after disposal receipt.

All source, screenshots, fixtures, logs, manifests and unique binaries remain preserved. Historical full-package/native/gate path verification will require restoring the removed exact bytes first; do not rewrite historical receipts to hide that limitation. The published ZIP permits restoration of repair/package binary copies; its retention is essential. The first cleanup's rename gate binaries remain excluded even though the read-only audit also verified their published ZIP correspondence.