loopx-pr-merge

# LoopX PR Merge Optional maintainer workflow. It lives in the repository and stays outside the default installed skill set, so a host that never merges LoopX pull requests is not affected by it. Install or copy it deliberately when a host needs to make merge decisions. The built-in `pull-request-review` capability owns review depth, evidence requirements, completeness, and verdict policy. This skill owns one narrower decision: whether this pull request may be approved or merged now, under which authority, and with what recorded validation. ## Decision Precondition A merge, approval, self-merge, or admin-bypass decision requires review evidence for the exact head being merged. A merge decision without this evidence is not authorized: a diff read, green CI, or pull-request metadata is not a substitute. 1. Run `loopx --format json pr-review --state all`, or use the installed `loopx-pr-review` skill, and preserve `agent_response_contract.review_execution_contract`. Execute the review plan, `review_template`, and `evidence_commands` it names for every changed surface. 2. Apply `completion_gate` literally, and re-read the remote head immediately before the decision. 3. Immediately before the merge, run `loopx --format json pr-review --goal-id GOAL --repo OWNER/REPO --check-merge-readiness NUMBER@HEAD_OID`. Merge only when it returns `ready=true` for that unchanged head; this records the compact Goal readiness observation consumed by future review queue...