Merge

A merge request authorizes landing the scoped work, closing fully resolved issues, and cleanup of task-owned temporary resources. Honor the user's limits. Return readiness blockers to the caller; fixes belong to pr or the caller.

1. Scope. Identify the repository, target PRs, landing branch, and readiness evidence. If the scoped work has no PR, invoke pr in preparation-only mode to prepare and publish it, then return here with readiness evidence. This invocation retains the original merge request. For stacks, use gh-stack to resolve the exact merge set and command target; authorization must cover every included layer. Already merged PRs proceed directly to issue completion and cleanup. Register scoped PRs using thread registration's T3 linking rules, even when preparation is already complete.

2. Check readiness. Read current GitHub state and reuse applicable handoff evidence. Verify head/base commits, checks, approvals, review threads, accepted fixes, and mergeability. Stale or missing verification and unmet requirements block landing. So do closing links that would close unfinished issues; return them to the caller for correction.

   For every PR, including docs-only changes, require current head/base review that includes Show, Don't Tell, plus required verification. Reuse matching evidence. If missing or stale, invoke pr in preparation-only mode and return refreshed evidence here. After repairs or restacking, recheck every affected layer. Before local history changes, apply Preserve local files and verify retained files after success or recovery. Land the original merge set only after all its PRs meet readiness requirements.

3. Land. Follow repository merge settings, protections, and queues. For a single PR, use gh pr merge with --match-head-commit <verified-head>; leave branch deletion to cleanup. For stacks, use gh-stack and require guards against unverified head changes on every layer: head preconditions or enforced current-head checks and fresh approvals after pushes. If unavailable, report the blocker; see branch protection. Confirm GitHub reports each PR merged; queued work remains pending. After a failed or timed-out submission, check GitHub state before retrying.
4. Finish issues. Check linked or task-scoped issues against their acceptance criteria and intended delivery branch. Confirm automatic closure or close a fully resolved open issue as completed with the merged PR link. Keep partial issues and those depending on unmerged layers open. Check existing state and comments before posting. An intermediate stack merge does not prove delivery; automatic closing links apply when work reaches the default branch.
5. Clean up. Use repo-cleanup for confirmed merges, passing merge results, proven merge-time source heads, branches/bases, worktrees, and known task resources, including device installs. Identify resources needed by remaining stack layers. Issue-update failures do not prevent eligible cleanup.

Report merged and pending PRs, issue results, cleanup results, and blockers.