[M8] Harden standalone packaging, release automation, and public stability contracts

[Teakowa]

Parent: #9

Depends on: #49, #53

Planning status: provisional until the M7 gate is complete.

Goal

Turn the standalone native toolchain into reproducible release artifacts with explicit public CLI/machine-interface stability expectations.

Scope

• Define supported release targets/platforms from actual user/project needs.
• Produce standalone native artifacts that do not require Node/OverPy for supported workflows.
• Add reproducible release automation, version metadata, checksums/artifact verification where appropriate.
• Define pre-v1/v1 stability policy for CLI commands, exit codes, machine-readable result schemas, and embedding-facing contracts already exposed by M6.
• Define compatibility/rollback guidance for release regressions.
• Ensure public status/docs accurately reflect shipped capabilities as part of release acceptance.

Non-goals

• Shipping browser/editor extensions.
• Stabilizing internal HIR/WIR layouts as public APIs.
• Adding package-manager scope without evidence.

Acceptance criteria

• Supported release artifacts can be installed/run standalone and reproduce the declared M8 workflows.
• Release automation is repeatable and validates artifacts before publication.
• Public CLI/machine contracts have explicit versioning/stability expectations.
• Release documentation/status matches actual code and supported capabilities.

[Teakowa]

Delivered in commit 1611004 (scripts/release.sh, docs/release.md).

• Release automation builds the optimized binary, runs quality gates + v1 gates + scenarios + benchmarks, proves standalone operation with Node/OverPy absent from PATH, stamps version metadata (version.json: version, wright-result/v1 contract, commit, timestamp, requires: {node: false, overpy: false}), and packages target/wright-<version>.tar.gz.
• The packaged artifact reproduces the declared workflows standalone (verified by the release run).