Release Astrid Runtime 2026.9.0 #1817

Outcome

Prepare and release Astrid Runtime 2026.9.0 from one exact reviewed commit on main. The release must carry a coherent source version contract, immutable signed artifacts, authenticated crates.io publication, and channel promotion only after the release is complete.

Scope and dependencies

• Establish the 2026.9.0 source version contract on main, including workspace versions, internal path-dependency requirements, rolled changelog, and the 29-crate publication plan. release: prepare Astrid 2026.9.0 #1811 tracks this slice.
• Resolve or explicitly defer every product change selected for the 2026.9.0 train. At minimum, Consolidate hosted runtime authority into one astrid.volume #1803, Make stop authoritative across daemon and MCP gateway #1804, Make AstridFS a hidden CLI-controlled FSKit container #1805, Resolve capsule artifacts from Cargo configured target directory #1807, fix(cli): make astrid run idle timeout configurable #1812, and fix(config): separate client, bootstrap, and runtime configuration authority #1816 need scope decisions before completion.
• Keep release tooling, publication metadata, and platform certification consistent with the selected 2026.9.0 scope.
• Preserve the separation between source preparation, immutable release creation, crates.io publication, and channel promotion.

Exit gate

This outcome is complete only when all of the following are true:

• one exact main commit carries the complete reviewed 2026.9.0 state;
• workspace and path-dependency versions are 2026.9.0, the changelog is rolled, and the publication gate accepts exactly 29 crates;
• required CI, release-contract, platform, and independent exact-head reviews pass;
• the signed v2026.9.0 tag points to that exact release commit;
• immutable signed artifacts are published and authenticated;
• all 29 planned crates are published to crates.io and their published checksums match the signed artifacts;
• stable channel promotion succeeds only after immutable release and crates.io publication are complete.

Claim boundary

A version bump, green tests, a draft release, a tag, or partial crates.io publication does not mean 2026.9.0 is complete. Platform or hosted-environment results do not substitute for native certification, and no publication or channel claim may precede its own durable evidence.

Verification

Record exact commit, tree, parent, artifact identities, checksums, signatures, workflow evidence, publication order, and channel state. Validate release-contract tests and a no-publication dry run before publication. Every external claim must point to durable signed or workflow evidence.