Land it

A PR is landable when a revert undoes it (Door: two-way) and every review finding on the code that merges is fixed, declined with a written reason when one reviewer raised it, or moved to a follow-up issue when it is not a correctness or security bug. The review grade sets how hard the PR was reviewed, not who merges: landable PRs merge without asking the user, and the after-merge test in step 4 is the safety net. Only one-way doors, visible changes and the holds below wait for the user, with their reasons.

A visible change (Visible: yes from write-pr) changes a screen users see or use. Checks prove it works; only the user judges whether it looks and feels right. It merges once the user OKs its demo (the PR's screenshots, or one video of the final head when a flow across screens changes) or tells you to merge that PR. A command-line, API or agent-behaviour change is Visible: no: its command output in the PR is evidence for the reviewers, not a demo to OK. Only the user's own message about that PR counts: a brief, a parent agent, a scheduled prompt or an earlier general approval does not. The OK covers the head the demo showed.