ce-reviewlisted

# Review **Invocation input:** Feature to review (optional): $ARGUMENTS Independently review the **code** of an implemented feature — for correctness the tests miss, security, performance, maintainability, simplicity, and conformance to the spec and the interface-foundation contract. It reports **evidence-backed findings** and **escalates**. It never patches code or edits source, plans, or specs; outbound mode writes only its review and evidence artifacts. This is the **code-quality sibling of `verify`**: verify checks that the software *behaves* as the spec says (suite, criteria, journeys); review checks *how the code is written*. The discipline chain gains a sibling: ``` plan ◄── spec ◄── implement ◄── { verify · review } ``` **Independence is the point.** A reviewer that did **not** write the code catches what the author's own context cannot — the same argument behind `ce-auto-build`'s fresh worker contexts. Standalone, `/core-engineering:ce-review` runs in a fresh invocation; under `ce-auto-build`, it is a spawned review subagent whose only inputs are the code on disk and the spec as contract. It runs in two **directions**, auto-detected by the Stage-0 mode probe: - **Outbound** (the default) — *generate* findings by walking the six lenses over a feature's diff. This is everything below. - **Inbound** (PR review comments pasted in) — *verify* findings someone else made: each comment is a **claimed** finding, checked against the code, triaged, and answered wi