green-gatelisted

# Green gate The gate is what makes an unattended run trustworthy. Without it the agent's report is a claim; with it, the report is a set of exit codes. ## The order Cheapest and most localising first, so a failure is found in seconds rather than after a six-minute build: 1. **Typecheck** — the project's own typecheck command, or `tsc --noEmit` 2. **Lint** — where the repo enforces module boundaries, this is where an illegal import surfaces 3. **Unit tests** 4. **Build** — catches what typecheck alone misses: dependency graph, bundler config, tree-shaking of side effects 5. **E2E** — slowest, so last, and often the only gate that proves the feature actually works Take the exact commands from `docs/agent/repo-map.md` → **Gates**, and the scope from its **Workspace** section: the changed-set command, or the fallback rung that repo uses. A project with no test command skips that gate — and the skip is recorded as a skip, never as a pass. During the step loop, run gates 1–3 over the changed set. Before handover, run all five over the full changed set against the base branch. When the map says the changed set came from a low fallback rung, widen the final run — an imprecise scope is a reason to gate more, not less. **The step loop stays serial.** Cheapest-first is the whole point: a typecheck error found in eight seconds costs nothing, and running the build alongside it to save time throws that away. **The final run parallelises across projects.** Once the loop is done and