Files
ARCADIA-Studio/harness/release-cli-prerelease-published-20260911.md
T

4.5 KiB

Published standalone CLI prerelease — 2026-09-11

Owner: Codex-9e8r6t /root/palette_finish. This task preserves publication evidence and independently checks read-only release/tag metadata. It performs no production edits, Git operations, compiler or native input, credential access, upload, asset download or repeated runtime tests.

Published milestone

Arcadia CLI — standalone Windows authoring preview is release 2, published 2026-09-11 12:50:39 UTC, draft: false, prerelease: true. Fresh Gitea MCP get_release(id:2) and get_tag readbacks independently agree on tag cli-v0.2.0-preview.authoring.20260911 and target 27df4a3945ebc97cd7cbde61f6aeea7a91c680d3.

The publication roles are deliberately distinct:

Role Commit Meaning
Semantic source 01b76a1e89e93b7992f39e63560aa8b2ca2f69e0 Preserved source CLI implementation, workspace and lock corresponding to the verified BAD169F8 executable
Packaging assembly a0a48e82bd43be181caca1fe2c1514c21f2bc405 Isolated packaging-only changes used to assemble the verified ZIP
Release integration 27df4a3945ebc97cd7cbde61f6aeea7a91c680d3 Published tag checkpoint integrating the packaging files and evidence; not relabeled as original compiler inputs

Preserved upload results

Root's original readback records report three uploaded assets, each downloaded and hash-verified by the publisher. This preservation task does not repeat those downloads.

Asset / id Bytes SHA256
ArcadiaCLI-0.2.0-preview.authoring.20260911-x86_64-pc-windows-gnullvm.zip / 4 5091267 2b051f8ce1ea4f59ee7e233e1fbd516d423aadbfbca5d549755cbe78fcde1af6
ZIP .sha256 / 5 140 0dc3f12d2f79edfb735e311298d1528cbdb828b775ec885b3badde24e66bceef
VALIDATION.md / 6 50297 5a0206b493bf1ca98fe931243452a9092cdf2acf10f4e3fd0a7ee9a7d8f56ec8

The ZIP contains 114 files and the exact BAD169F8 CLI plus F456 runtime, with 27 dependency packages. Author packaging and independent runtime gates are documented in release-cli-packaging-20260911.md and release-cli-packaging-review-20260911.md; the latter records 156 assertions across 10 fresh extracted CLI processes. These existing results are attributed to those runs, not newly executed here.

Exact-byte evidence

New durable directory: harness/experiments/cli-prerelease-20260911/. README.md and manifest.json inventory the exact copies, source paths, byte lengths and hashes:

Copied record Bytes SHA256
upload-binaries-verified.json 678 e945e2724020c48bfe15be7b4258861bd6c01291b98eae036eca786bb022ebde
upload-validation-verified.json 277 73581acbb5b5fe4aca1fda1b626f80a28bcb3d6c036f7ce793c62bf5a8ef4a72
published-verified.json 382 b5fe8a38579fb8399c78bca9db9fd91b64e8b7b7de7c664049cf5e615a671100
RELEASE-NOTES.md 2010 86a1b5b0744c8f63f6ed640e14b23bdbcb34b63a25320d67eb1fa7da4128a0a5

All four copies match their private originals byte for byte and retain CRLF. Only these sanitized records were copied; no credentials or upload helpers were read or included. Additional files hold the preserving checker, its result, disclosed initial checker failure, parsed MCP observations and the inventory.

One evidence distinction was verified explicitly: published-verified.json stores notes_sha256 = 1b83b9c904a79ff7acbde421851c9da9b520f3fa0aea920bf55fb71bea392a9d, which matches the 1988-byte LF public release body. It does not equal the 2010-byte raw CRLF Markdown hash above. CRLF-to-LF conversion alone reproduces the public body exactly, including the final newline. An initial checker incorrectly assumed this was a raw-file hash and stopped; its failure is retained, and the corrected check passed without changing any source record or public content. A temporary comparison command also had a corrected PowerShell syntax error and made no changes.

Recommended exact-byte rule for root to add before Git integration:

harness/experiments/cli-prerelease-20260911/** -text

This worker did not edit attributes or Git state. Root owns integration, common ledger/Wiki updates and any further publication work.

This is a development-profile Windows CLI milestone. It is not full OA/SA product acceptance, current Linux runtime acceptance, a saved-plan/digest protocol, or complete large-model textual ergonomics acceptance.