Files
ARCADIA-Studio/harness/experiments/text-diagnostics-20260913/cleanup/closed-binary-reclaim-candidates.md
T
sorokin.oleg.edu 9fd76aef3a Add current-draft diagnostic underlines and passive hover
Preserve raw include diagnostic provenance and derive bands from the existing shaped editor. Retain deferred tooltip paragraphs through rendering. Include source, regression, failure and native-trial evidence; corrected native acceptance remains pending.
2026-09-13 01:43:22 -07:00

23 lines
4.3 KiB
Markdown

# Closed binary reclaim candidates — read-only audit
Six duplicate executable files can recover **534,808,064 bytes (510.0327 MiB)**, subject to the parent's final before-delete hash/process check. Nothing was deleted or moved. No registry/shared target/cache cleanup, build, GUI, process control, network, WSL or VPN inspection occurred. Inventory was limited to owned `.local/source-rename-*` and `.local/text-navigation-*` historical directories; no navigation files are needed to reach the target.
`closed-binary-reclaim-candidates.json` contains all six resolved absolute paths, full SHA256/size, retained counterparts, actual ZIP entry names, closure receipt paths/hashes and process snapshot. Its SHA256 is `9e3a1f2f0b3c6f1f753c6dbe56fcd33405e8bad9f00840dc6bb9667fa0e33f6e`.
| Candidate beneath the main repository `.local` | Bytes | Retain identical binary beneath `.local` |
| --- | ---: | --- |
| source-rename-native-20260912/trial-attempt-6/bin/arcadia-studio.exe | 113,854,464 | source-rename-integration-20260912/attempt-6/arcadia-studio.exe |
| source-rename-native-followup-20260912/trial-attempt-7/bin/arcadia-studio.exe | 113,879,552 | source-rename-integration-20260912/attempt-7/arcadia-studio.exe |
| source-rename-package-review-20260912/runs/attempt-1/extracted/ArcadiaStudio-0.2.0-preview.rename.20260912-x86_64-pc-windows-gnullvm/arcadia-studio.exe | 113,883,648 | source-rename-integration-20260912/attempt-8/arcadia-studio.exe |
| source-rename-package-review-20260912/runs/attempt-1/extracted/ArcadiaStudio-0.2.0-preview.rename.20260912-x86_64-pc-windows-gnullvm/arcadia-server.exe | 39,653,376 | source-rename-server-build-20260912/attempt-1/arcadia-server.exe |
| source-rename-package-review-20260912/runs/attempt-2/extracted/ArcadiaStudio-0.2.0-preview.rename.20260912-x86_64-pc-windows-gnullvm/arcadia-studio.exe | 113,883,648 | source-rename-integration-20260912/attempt-8/arcadia-studio.exe |
| source-rename-package-review-20260912/runs/attempt-2/extracted/ArcadiaStudio-0.2.0-preview.rename.20260912-x86_64-pc-windows-gnullvm/arcadia-server.exe | 39,653,376 | source-rename-server-build-20260912/attempt-1/arcadia-server.exe |
All candidate and counterpart bytes were independently hashed equal. The four package executables additionally match read/CRC-verified entries in retained `C:/arcadia-rename-package-2/packages/ArcadiaStudio-0.2.0-preview.rename.20260912-x86_64-pc-windows-gnullvm.zip`, 33,074,937 bytes, SHA256 `d2433b5b384256b551672bf115bab40b3496aeee115e067922aedb5becf34d7e`. This is the already-published asset's known byte pin, verified locally; no remote publication requery occurred.
Closure: trial6 PID9108 exit0 at2026-09-12T12:45:42.336483Z; trial7 PID9808 exit0 at22:20:26.337292Z. Both report unchanged binaries/runtime. Checker attempt1 is a completed FAIL at23:53:33.553492Z (timestamp provenance comparison), attempt2 completed PASS at2026-09-13T00:04:44.156465Z. Both were static and explicitly did not launch the extracted applications. Subsequent attempt2 packaged GUI PID8424 exited0 at00:26:58.697468Z with package/archive unchanged. Packaged server PIDs4324/7220 were explicitly terminated after persistence checks with actual exit1 observed at00:05:46.610777Z and00:05:46.820795Z; these are intentional stops, not normal/graceful exit claims. The runtime result is complete PASS. Corresponding original receipts are hash-bound in JSON.
Targeted Win32_Process readback for `arcadia-studio.exe` and `arcadia-server.exe` returned no processes; exact timestamp/filter are preserved in `reclaim-process-readback.json`. This is a point-in-time check, not an ownership lock. Parent remains sole operator, must recheck immediately before deletion and preserve a scoped before/after disposal receipt.
Removing these copies leaves historical launch paths and the two extracted complete-package inventories incomplete. Keep all original receipts/manifests/captures/source/fixtures and the retained gate binaries/ZIP; do not rewrite historical PASS records. Any later whole-package or original-path verification must first restore the exact pinned bytes. This explicit restoration requirement is the provenance cost of reclaiming duplicate executable storage, not a claim that the original trial did not use those paths. Do not remove the retained counterparts or expand cleanup to directories/caches.