gh-reviewlisted

# gh-review Drive an issue from `documented` through `in-review` to `done`. ## Two-phase operation ### Phase 1: request_review (Gate 4) 1. Read issue → confirm current status is `documented` 2. Verify a branch exists with the work — if not, ask user for branch name 3. Verify a PR exists for that branch with `Closes #{N}` in the body. If not: - Open it via `mcp__github__create_pull_request` with body containing `Closes #{N}` and the PR template - Push commits if not pushed (`git push origin {branch}`) 4. Build self-review comment with required sections: ```markdown ## Summary {what was done at a high level} ## Quality {code quality notes — tests pass, no lint warnings, no console.error, etc.} ## Checklist - {file path 1} — {what changed} - {file path 2} — {what changed} ``` 5. Validate via `lib/validate-evidence.sh` — must pass 6. **CI gate**: run `${CLAUDE_PLUGIN_ROOT}/lib/check-pr-checks.sh <PR>`. Refuse if exit ≠ 0 unless `--ignore-checks "<reason>"` was passed (records the reason in a `## Check overrides` section of the evidence comment). 7. **(optional) AI reviewer**: if `--ai-review <agent-name>` was passed (e.g. `code-reviewer`, `security-engineer`), spawn that sub-agent with the PR diff + the issue's body as context. Capture its review and post it as a PR review via `gh pr review`. Findings are categorized as `blockers / suggestions / nits` — only **blockers** block Gate 4. Override per-finding with `--accept <id>` or accept all s