Publish releases from the release environment

[jeremy]

The release job now runs in the release environment, so a v* tag waits for a reviewer before the binaries are built and published.

Why: the release job publishes the GitHub Release and its binaries. Until now any v* tag push published straight away. The release environment already exists, admits only v* tags, and requires a reviewer.

Releasing now: push the v* tag as before. The run waits at the release job until someone approves it under "Review deployments" on the run page.

Who approves: kevinmcconnell or a member of sip. Self-review is allowed, so the person who pushed the tag can approve it.

If #117 lands first, close this PR instead: #117 moves releases to a dispatch on main, and the release environment will admit main for it.

Nothing else needs configuring when this merges. Merging is the owners' call.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-08T01:36:04.426748Z	79bf56e	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.