merge-pr

# Merge a pull request Work the steps in order. A pair of hooks runs alongside them and refuses the shortcut: a direct `gh pr merge`, and any merge whose message the reviewer hasn't seen in its current form. Left alone, GitHub writes the squash message by concatenating every commit on the branch. That text has never passed a commit-msg hook, and it arrives on the default branch where the rest of the toolchain assumes those hooks ran. Nothing lints it afterwards. This workflow writes the message itself and puts it through what a commit answers to. ## Preflight !`bash ${CLAUDE_SKILL_DIR}/scripts/preflight.sh ${ARGUMENTS}` ## Step 0: open the task list Create these with `TaskCreate`, then move each through `in_progress` and `completed`. 1. Confirm the pull request is mergeable 2. Settle the published description 3. Write the squash message in SQUASH_AGENTMSG 4. Review the message with review-squash-message 5. Run the commit-msg gates 6. Confirm the message with the operator 7. Merge and clean up Stop before any of it where preflight reports a missing precondition, a draft pull request, or a failing check. Say what's wrong and hand back. ## Step 1: confirm the pull request is mergeable Preflight printed the state, the check rollup, and the review decision. Merging needs an open pull request that nobody marked as a draft, with every check green. A failing check goes to `fix-pr`, and a running one goes to `watch-pr`. Neither belongs here, and the merge script refuses bot...