Adversarial review

A reviewer that assumes the code is wrong finds issues. You verify each one. The operator decides what gets fixed; in ship mode, that means anything beyond a verified local fix.

Repo layer first. Read the repo's AGENTS.md/CLAUDE.md and, if it exists, the overlay .agents/bento/bento-adversarial-review.md at the repo root; follow it under the overlay rules.

Three phases, in order. Never merge them, never skip phase 2.

Mode

Mode	When	Phase 3
interactive (default)	the user runs the review directly	present, block, fix only approved numbers
ship	only when called by a ship flow: `bento-ship`, or a repo skill that plays its role	fix verified findings, return the human-decision ones

Phases 1 and 2 are identical in both modes.