code-review

# Code Review ## Purpose Independent review of a diff against the spec contract, locked decisions, and FLOW_RULES — before commit, deploy, or merge. Distinguishes blockers (must fix) from non-blockers (should fix). ## When to invoke - Operator says "review this" / "is this safe to ship?" / "look at the diff" - AI Developer-session gate report has been pasted and `validation-and-qa` ran clean — code-review is the next step before deploy - About to merge a PR (team mode) - Major refactor in flight and operator wants midpoint review ## Do not invoke when - No diff exists yet (review needs concrete code) - Clarifications are unresolved or scope is not yet locked — review against an incomplete contract is noise - Operator wants the code fixed — review surfaces issues; fixes go through implementation ## Required inputs | Input | Where it lives | If missing | |---|---|---| | Diff | `git diff <baseline>..HEAD` or PR diff URL | Stop; ask which diff to review | | Spec | `docs/specs/<slug>/spec.md` | Stop; review without spec is style-only and limited | | Decisions | `docs/specs/<slug>/decisions.md` | Stop; cannot verify decision adherence | | Tasks | `docs/specs/<slug>/tasks.md` | Stop; cannot verify scope adherence | | CLI edition map, for Fusebase Apps work | `docs/fusebase-cli-edition.md` | Continue with Flow-only review, but mark app-domain review criteria unknown | ## Procedure 1. **Trust the recorded gate verdict (review boundary).** When `validation-and-qa` has recorde...