7.6 KiB
Published navigation Windows prerelease
v0.2.0-preview.navigation.20260911 is published as Gitea release 4 with draft: false, prerelease: true. Root's actual publish command ended successfully; final metadata, exact tag target and all three asset downloads passed at 2026-09-12 10:54:02.303380 UTC. The publish PATCH began at 10:53:54.264100 UTC. The API's publishedAt: 10:52:54Z is the draft-creation timestamp and is not evidence of public visibility at that earlier time.
This is a bounded Windows development milestone, not final application acceptance. The published validation gives launch instructions, provenance, verification and known limitations; its exact bytes are also archived.
Download and launch
Download the Windows ZIP and checksum. Extract the complete ZIP into a writable folder and run arcadia-studio.exe, retaining libunwind.dll beside the executables. No Rust compiler or machine PATH change was required in the tested Windows runtime. Home and Engineering guide provide offline help. Copy all of examples/release1 into a working area before opening its project.arcadia; keep its supporting evidence files.
Optional server from PowerShell in the extracted folder:
.\arcadia-server.exe --bind 127.0.0.1:8080 --data-dir "$env:LOCALAPPDATA\ArcadiaStudio\server-data"
Consult docs/server.md and docs/openapi.json for server use. Cargo/Docker builds require the source checkout, not only the binary ZIP; docs/windows-packaging.md records build prerequisites. The binary uses the recorded development profile; optimized or reproducible binary output is not claimed.
Exact published bytes and provenance
| Asset ID | Asset | Bytes | SHA256 |
|---|---|---|---|
| 10 | Windows ZIP | 32,971,712 | d7228c542f162663933ea002739a78c722bcca41e437df63b7c868ea2af201f1 |
| 11 | ZIP.sha256 | 144 | 435b6fff3fbc1640b4db31c5d848dbcde101aa54cc86fe0eef9c8da6a501ccac |
| 12 | VALIDATION.md | 6,987 | 9abcb45e665e2bf553a6ef91f1e73fd403d7c9552b01962d0d9713cf52660ff2 |
The 559-file package contains B183…8848 Studio, historical EFEE…E665 server and F456…E7D4 DLL. The tag points exactly to 802855f7e6f2f00a107a12196b458b267f586b8d, the reconstruction of all 500 raw desktop build inputs, including 15 measured newline restorations. The actual build captured eeeaa126 plus the repair delta later committed as 33c6d83; reconstruction is not the original build commit. The server retains its separately verified September 7 provenance and was not rebuilt from this tag. Producer evidence and independent review give exact binary hashes and source relationships.
Publication sequence and retained failure
The initial tag preflight at 10:49:06–07 UTC refused because the published source branch moved. It did not reach tag push. Root's stored inspection found exactly three single-parent commits modifying only AGENTS.md, with inspected branch head 0c9ee1505774a0f64c5f3a58b0da64a4673d5000. The independently reviewed adjustment pins that exact branch head separately from the unchanged 802855… tag target, rather than accepting arbitrary descendants or moving source. Source-advance review preserves the evidence and narrow correction.
Root published acceptance records at f5e1c734dadd6e0203288065dac7b2e3f140cacf before release visibility and reports exact remote Git blob readback of both native and independent reports. The archived acceptance push receipt independently records the successful branch push; the blob readback is attributed to root's tool observation rather than invented as a separate raw receipt.
The fresh nonforce tag attempt passed at 10:52:41 UTC. Root created owned draft release 4, uploaded assets 10/11/12 and downloaded each for exact byte verification, finishing at 10:53:30 UTC. Publication downloaded and verified all assets again before changing visibility, then rechecked final metadata/tag/assets/download hashes. The terminal receipt at 10:54:02 UTC records success with the same three asset identities and public prerelease state. No foreign release adoption, replacement asset, forced tag or silent version substitution occurred in this sequence. Later fresh MCP metadata readback, shared records and integration are root-owned and are not claimed by this archive.
Accepted scope and limitations
The corrected desktop gates recorded 755 passing tests, zero failed, one ignored, strict all-target Clippy, formatting and a matching development build. Independent artifact review passed 6,002 checks; packaged server review passed 1,801 checks including exact Unicode project persistence across restart. Server processes were explicitly terminated after acknowledged persistence (Windows exit 1); graceful drain and comprehensive API editing were not tested.
Packaged native acceptance records real Windows Open of the four-source Unicode fixture, offline guide, F12, one lexical reference excluding prose/comments, Back, dirty/stale feedback, Undo, Apply and explicit Save. Exact model, identities, four reachable sources and four disk files matched. All 126 modules were under Windows or package paths. The original closure helper failed without capturing the Win32 error; a separate query established the same process creation exited with code 0 and unchanged ZIP/full package map. The original failure remains distinct. This package trial used a 1440×900 client and did not repeat the earlier minimum-size, 30-file engineering or corrected repair/rollback trials linked in integrated navigation evidence.
Text alias rename is not implemented. Newer peer canvas/lifecycle work, full quantities/calculations/constraints, maintained model libraries, comprehensive OA/SA graphical/text/REST parity, remaining engineering workflows and final independent application review are not accepted by this release. Linux/WSL setup, diagnostics, builds and checks remain paused by the user.
Preserved publication evidence
Archive preserves 34 original files (103,111 bytes), exact final notes/validation/bindings, initial historical adapter manifest/README, predecessor helpers, three static review stages, source inspection and failed/successful attempt records. An explicitly labeled reconstruction reproduces the initial reviewed E679…2C99 adapter hash; it is not represented as a retained original execution snapshot. The read-only archive verifier checks hashes and receipt relationships without importing publication code or accessing network, credentials, applications or original packages. No runtime, server, package or GUI tests were repeated during archival.