feat(agents): code-review + verifier subagents (review-infra lane)

[POWERFULMOVES]

Part of the 4090 review-infra lane (AGNOTE claim in the first commit). Companion to #1763 (which restored claude-code-review.yml — it had startup_failed for ~7 days on the oven-sh/setup-bun allowlist block).

What

Two new .claude/agents/:

• code-review — deep code-correctness reviewer (bugs / security / error-handling / type-safety). Read-only; reuses the pmoves-pair-review 4-class taxonomy (reasoning gap / semantic-naming drift / contract-correctness / defense-in-depth); emits [P1|P2|P3] <class> — file:line findings + an explicit per-class clean signal (evidence-of-absence). Model: opus.
• verifier — evidence-before-assertions claim checker. Maps each PR/commit claim to one concrete command, runs it, reports exact output + exit code (or UNVERIFIED (environment)), and surfaces falsified claims loudly. Model: sonnet.

Why (gap analysis)

A review-infra audit found control-agent does governance/merge-sequencing and test-runner runs pytest, but no agent does line-by-line correctness review or evidence-based claim verification. These two fill that gap without overlapping the CHIT (chit-compliance-reviewer), governance (control-agent), or thread-resolution (pr-trimmer) agents — each new agent's description states what it is NOT for.

Verification

Frontmatter matches the repo convention (name/description/tools/disallowedTools/model/maxTurns/effort), disallowedTools blocks Write/Edit so both stay read-only. This PR opening should trigger the now-fixed claude-code-review.yml — a successful run here doubles as confirmation that #1763 fixed the outage.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@POWERFULMOVES, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 13 minutes and 16 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: b71d2ea0-4239-490e-a969-ab579ddb5b57

📥 Commits

Reviewing files that changed from the base of the PR and between 5eef985 and 08df4ef.

📒 Files selected for processing (3)

• .claude/agents/code-review.md
• .claude/agents/verifier.md
• pmoves/docs/AGENTS/AGNOTE4482PHI.t1.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/review-infra-agents

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}