Review-Commit

Stage 5 of the dev-pipeline: everything after the build, through commit and deploy. This file and its references/ hold the PROCESS. Lessons from past loops (SQLite, MCP, REST, sync, mobile, test-quality traps, CLI quirks) live in the separate review-lessons skill — load a lesson file only when its case comes up, never at stage start.

Before you start: tier, lanes, budget

1. Tier — risk-derived review tier from orchestrator/references/risk-routing.md (compatibility table: size-tiers.md). It sets how many reviewers run and how many confirm rounds the loop may spend. Say it: "T2: two reviewers, R1 + up to 2 confirm rounds."
2. Lanes — which model builds and which review: orchestrator/references/lanes.md (the only place model names live).
3. User overrides — "review loop 3 times", "all three reviewers" — set the budget or reviewer set for this task.

The review sequence