Prefer exhaustive, evidence-based reviews of the exact publish lifecycle

When reviewing this repository, inspect the current implementation end to end and report precise file-level behavior rather than broad summaries or assumptions. Track workflow entry points, environment variables, parsing and error behavior, outputs, label transitions, issue/event snapshot binding, revision and workspace validation, and failure handling. Treat release security invariants—trusted-code checkout, revalidation after CI, and preventing changed, renamed, or re-approved issues from reaching ci-ready—as mandatory. Preserve exact strings and conditions where relevant, cite current file:line evidence when requested, distinguish verified facts from findings, and do not mutate the worktree during a read-only review.