release - Versioning Stage

Invariants

Release only merged Ready To Ship tasks.
Close the loop: a task moves to Shipped only when its post-deploy checks (listed in the PR / test report) have been run against the live system and their results recorded in the test report, or when the user explicitly waives them for that task. Merged is not the same as working.
Keep changelog entries user-focused.
Do not include unmerged pull requests.
Do not rewrite existing tags without explicit user approval.
After moving released items to Shipped, re-read TASKS.md to confirm each row left Ready To Ship. A stale tracker blocks downstream and headless sessions.

Runtime adapters may expose this stage as a slash command, menu action, or natural-language skill invocation. The portable stage name is release.

Supported version inputs: