surface-reviewlisted

# Surface Review — 11 Gates + Smoothness Loop Review a change against the surface it deformed, not just the lines it touched. **Input:** a list of changed files (from `git diff --name-only <base>..HEAD`, or supplied). **Output:** `code-review-<id>.md` and, on convergence, `smoothness-achieved-<id>.md`. ## Configuration Read `.flow-surface.json` from the repo root if present. It adapts the gates to the project. See `references/config-schema.md`. Every key is optional — with no config file, the gates degrade to stack-neutral defaults and still run. ## Tier structure The gates run in three tiers, each tier consuming the previous tier's findings. Run each tier's gates **in parallel as subagents** where the harness supports it — each reviewer gets a clean context window, which matters because the implementing session has usually consumed most of the main one. Where subagents aren't available, run them sequentially. | Tier | Question | Gates | | :--- | :--- | :--- | | 1 — Point | Is the code correct *here*? | 1–5 | | 2 — Region | Did this deform anything *adjacent*? | 6–9 | | 3 — Shape | Is the *whole system* moving toward its ideal? | 10–11 | | Loop | Did our fixes deform anything? | Smoothness | Skip rules are per-gate and stated below. A skipped gate is recorded as `SKIPPED` with its reason — never silently omitted. A `SKIPPED` that is not a skip-rule skip is legal in two further cases only: a named missing capability that leaves nothing to examine, or a second examinati