docs(review): reconcile stale `code-review` framing in quality-gate pr.md and README

[kyle-sexton]

Context

Surfaced while fixing #266 (documenting the boundary between quality-gate code mode and the built-in /code-review).

Problem

Two spots in the review plugin describe code-review as an optional claude-plugins-official marketplace plugin, but per current official docs /code-review is a bundled/built-in Claude Code skill (invoked bare, not namespaced), the successor to the old built-in /simplify:

• plugins/review/skills/quality-gate/context/pr.md (lines ~5-9) references a code-review orchestrator plugin invoked as /code-review:code-review "when installed".
• plugins/review/README.md (line ~61) lists code-review among "Optional orchestrator plugins ... from the official marketplace".

Additionally, pr.md's description ("parallel review agents with confidence scoring ... posts findings as a PR comment") appears conflated across surfaces: it partly matches the managed GitHub App Code Review service (@claude review, inline PR comments) and partly the local bundled /code-review --comment command — not a single installable plugin.

Why not folded into #266

#266 is scoped to code mode. Correcting pr.md/README needs its own verification pass to untangle which claims map to (a) the local bundled /code-review command, (b) the managed Code Review GitHub App service, and (c) any historical marketplace plugin — fixing by inference would violate the repo's research/verification discipline.

Suggested fix

Verify each surface against https://code.claude.com/docs/en/code-review and the commands/skills references, then reword pr.md and README so the code-review references name the correct surface(s) and drop the "must be installed" framing where the capability is actually built-in.

Related

• Refs docs(review): document quality-gate vs bundled /code-review boundary #266

Work-class: C2 (mechanical) — attended triage 2026-07-23, operator-ratified. 🤖

[kyle-sexton]

This was generated by AI on operator direction.

Superseded — this item was already ratified and should not have been queued.

The earlier first-drain ratification request on this issue was raised in error. The admission gate dispatches a C3 bug-fix-shaped item when it carries either its own recorded ratification or a completed first drain — and this issue already carried recorded ratification in its body from attended triage on 2026-07-23. The drain cycle applied the blanket first-drain rule without first reading bodies for an existing ratification, so it queued an item that was already admitted.

Restored to the autonomous frontier: agent-ready re-applied, needs-human removed. No human action is required, and this issue no longer appears in the attended queue's ratify view.