PR Review Loop

Iterate a PR to plan-alignment through review comments. The leading word is converge: every round must either approve or produce actionable comments that shrink the gap to the plan — never a rubber stamp, never vague feedback.

This is the review counterpart to arc-work-issue --ship pr: implementation produces an open PR, then this loop supplies the judgment. Merge authority stays with the caller unless --merge-on-approve is passed.

Orchestrator route guidance

• Route a bounded correctness, regression, security, or acceptance-criteria review to codex-check.
• Route high-taste UI/UX, API, architecture, copy, docs, prompt, or skill critique to opus-review. This is a content-triggered review route, distinct from availability fallback.
• Route a bounded read-only investigation needed before review to codex-explore.
• Route clear mechanical comment fixes to composer-implement (the Cursor/Composer implementation lane) and difficult or debugging-heavy fixes to codex-implement.
• When Codex is unavailable, opus-check and opus-implement are the matching availability fallbacks; opus-explore is available if a read-only investigation phase is needed. There is no separate cursor-implement route.