# V2 release package verification — 2026-09-05 Release: Arcadia Studio 0.2.0, native x86_64 Windows and Linux. The Linux build targets the tested Ubuntu 24.04.2 runtime. Both final desktop executables were launched from their staging bundles and operated through Computer Use; their normal closes completed without application stderr. The Linux final pass reopened the Windows-authored Action fixture. See `verification-v2-native.md` and `review-v2-final-ui.md`. ## Outputs - `dist/ArcadiaStudio-Windows.zip` - `dist/ArcadiaStudio-Linux.tar.gz` - `dist/SHA256SUMS.txt` — SHA-256 of the final archives (kept outside them to avoid a self-referential hash). Each bundle contains the two platform executables, START-HERE, README, LICENSE, all current docs (including both rendered/source reST contracts and OpenAPI), examples, deployment recipes, and V2 harness state/review/verification records. It is a binary bundle; repository source is required for the documented Cargo/Docker build commands. Historical V1 release executables are absent. Explicitly named legacy examples are retained for migration. ## Verification The archive builder checks every staged regular file against its repository source or final build output before assembling. It reads and SHA-256 compares every archived regular file against staging, checks duplicate names and required contents, and checks ZIP CRC integrity. Linux tar headers use executable mode 0755 for binaries/directories and 0644 for other files, with root ownership metadata. No extraction or elevated installation is required for these integrity checks. An initial staging check correctly rejected outdated copies of `server.md`/`validation.md` after the independent reviewer improved their quickstart/evidence attribution. Those files were recopied; assembly and full inventory verification passed. The final pass includes this package record and finalized PLAN/STATE and repeats the complete comparison. Raw structured results are at `D:/CodexBuilds/Capella2-v2-01a06e2e/release-packages.json`; archive hashes are available directly in dist. | Platform binary | SHA-256 | |---|---| | Windows desktop | `e2aec2ac935e270c6185729cbb76f8323b381654c04dbde7aae90c4628a98a20` | | Windows server | `d33edae56308035781856ae54358def59818cc93242380bc29c874f7dc7c53e4` | | Linux desktop | `df88c9dd2f4759c95514c32c0c50ad225642fff085b67162e6bebafafad01b04` | | Linux server | `0df8a6eaaa9bb548669cf38d9b7e452d11171affe075652b9d561ddef2281814` | The binaries in both archives equal these final release outputs. Earlier service process checks still apply because both server binaries are unchanged. This verification does not claim signed installers, a fresh-machine runtime installation, broad Linux distribution/GPU compatibility, Docker execution or remote deployment.