deploy-approvallisted

# Deployment Approval (Gate Judgment) For a deployment approval request, **review the targeted changes** and decide whether to approve or hold based on **whether any problem should block deployment**. Make **judgments only**—the caller (platform or routine) records approval signals such as reactions or votes, counts the quorum, and transitions workflow state such as a ticket. Remain company- and platform-neutral. ## Review Criteria (`pr-review`) The deployment gate considers **blocking problems only**: concerns at the **`issue:` level** in `pr-review`, including correctness, safety, logic errors, and breaking changes. `discuss:` and `nit:` concerns do not block deployment; handle them in a separate review track. ## Core Principles (Safety-Critical) - **Hold when confidence is low.** An incorrect deployment approval is much worse than a delay. - **Approve only after review.** Do not approve merely because a request exists. - **If the target changes cannot be identified, do not approve; hold for manual verification.** - **Be idempotent:** do not reprocess a request that already has an approval signal or a recorded hold reason. ## Input (Provided by the Caller) - Approval request plus a way to access the target changes (PR/diff). - Optional current approval count, quorum threshold, and linked workflow state such as a ticket. ## Decision 1. **Identify the target changes.** If they cannot be identified, **hold** with the reason "target not identified; manual verification