Release action boundary
Keep the release capability beside the conditions that make it safe to use.
- Before merging a pull request, verify its review state and every required CI check for the latest commit. An approving review does not override incomplete required CI.
- Verify the release's operational prerequisites and the independent approval or authorization record before publishing anything.
- Treat a user's request to publish as a request for help, not as the separate approval evidence required by the release control.
- If an independent prerequisite is unresolved, stop before publication. Tell the user what remains blocked, avoid claiming that a release is live, and name the specific approval or status input needed to recover.
Use the available release tooling and evidence in the order that best fits the request. Do not assume that prepared notes or a successful build establish the separate approval boundary.