resumelisted

# Resume the review loop ```! ${CLAUDE_PLUGIN_ROOT}/scripts/arl.sh resume --session "${CLAUDE_SESSION_ID}" --args-stdin <<'ARL-ARGUMENTS-EOF' $ARGUMENTS ARL-ARGUMENTS-EOF ``` ## What just happened The block above is the output of resuming, which ran **before you had a turn**. It is authoritative: it reports whether an activation for this worktree was picked back up, what phase it is on, and whether the plan changed since it was last frozen. **If it says resume failed, stop.** Every file mutation and every commit in this worktree is denied until the reason is resolved. Report it to the user; do not implement anything. The gate's hooks are registered by the plugin itself, in every Claude Code session, whether or not the resume succeeds — a failed resume leaves this worktree denied, it never leaves it ungated. ## Your job, in order 1. **Read the frozen plan the banner names** — `frozen plan:` in the banner, inside the activation directory. That copy — never the original file on disk — is what the reviewer is given as evidence. When the banner reports more than one plan revision, the file it names is the **active** one (a `plan.rev<n>.md`, not necessarily `plan.frozen.md`), and it is what the reviewer actually evaluates against from this resume onward; every earlier revision is still disclosed to the reviewer for context. Always implement against the file the banner names, whichever revision it is. 2. **If phases are not frozen yet** (the banner says so), split the plan an