code-reviewlisted

# Reviewing a Zion change Zion ships Bash hooks, Markdown prompts that agents execute, and JSON manifests. `AGENTS.md` is the contributor guide and wins on conflict. Code rules: the `engineering-principles` skill (`plugins/crew/skills/engineering-principles/SKILL.md`). This file is the one rubric and owns the output format; Copilot reads it directly and Claude Code's `zion-review` skill loads it. ## Scope: one full pass, then only what changed - **First review: every changed hunk ends as a finding or a Passed line.** Also read what the diff makes newly reachable: a new caller, a pattern now matched against a different input. - **Re-review after a push: review the new commits.** Raise an old, unchanged hunk only if it is Blocking. Never reopen a resolved thread with the same point reworded. - **One root cause, one finding.** When findings share a cause (the same parser, the same missing case), report the cause once as a design finding and stop listing instances. ## Severity: earn it with an input - **Blocking** needs a concrete command, payload or file state, and the wrong verdict it gives that the base branch did not. No input, no Blocking. - **A bypass through a documented gap is not a finding.** The Bash guards are floors, not sandboxes: newline flattening, `bash -c`, interpreters, `$(...)` and the raw-read scope are open on purpose (`AGENTS.md`, "The Bash guards are floors, not sandboxes"). Flag only a change that widens a gap or tries to close one with