merge-prlisted

# Merge a pull request ## What this does `implement-issue` builds a PR and flips it to ready. This skill is the final step: it **lands** that PR cleanly and cleans up after itself. The job isn't just `gh pr merge` — a PR that's ready isn't necessarily *mergeable* minutes later, because `main` moves, CI runs, and reviewers leave comments. So this skill closes the gap: waits for CI, fixes whatever is actually blocking the merge, squashes the PR in, turns deferred work into tracked issues, and removes the throwaway branch and worktree. The shape mirrors `implement-issue`'s tail (sync-with-`main`, the profile's conflict hot-spots, the commit identity) — reuse that machinery. The one new piece is the **corrections loop**: keep clearing blockers and re-waiting until GitHub reports the PR `CLEAN`, then merge. ## Autonomy contract Run **hands-off** once started — the user points at a PR and walks away. See [ADR 0005](../../docs/adr/0005-the-lifecycle-skills-run-hands-off-triage-backlog-does-not.md) for the decision scope. Whenever a step *could* stop for a question, pick the reasonable default, state the assumption, keep going. Stop only for a genuine blocker: - `gh` not authenticated, or no merge/push rights. - The PR doesn't exist, is already merged/closed, or the number is ambiguous. - **CI stays red after a real fix attempt.** Don't merge over a red bar, don't disable a failing test, don't `--admin`-override a required check. Fix it for real or stop and show the failing out