Always enforce tested trust boundaries in release workflows

Treat publishing and approval automation as security-critical. Preserve manual recovery, but isolate workflow_dispatch in a protected production relay with empty permissions and no secret references; never expose repository secrets to arbitrary dispatched refs. Ensure secret-bearing jobs use protected environments, check out trusted default-branch code before obtaining credentials, and pin GitHub Actions and publishing containers to immutable full digests. Bind approvals and CI readiness to the live issue, current label events, actors, and request digest, then revalidate immediately before publishing to prevent race-driven releases. Add or maintain tests that explicitly enforce these workflow invariants and fail on regressions.