Always require fail-closed, request-bound release authorization

When changing publish approval flows, preserve strict separation between human and automated authorization. Human approvers must have live GitHub repository permission at write, maintain, or admin level and must not self-approve. Automated bot requests must never authorize through collaborator permissions or by trusting the Internal App label actor alone; require the exact parsed repository/release path in auto-approve-repos.txt and a trusted attestation bound to the live request. Revalidate the issue’s open state, title, requester, current accepted-label actor/event, and relevant attestations before producing authorization or publishing. Treat malformed, missing, stale, mismatched, or changed state as unauthorized and fail closed.