Two-tier gate, step two: this repository declares a fast tier under five minutes, and a red land gate stops the release and reopens the work #1181

P0 Trust: the forge's own pulls wait minutes, not the full gate, and the full gate still guards every release.

Done looks like.

• [ ] scripts/gate.ts exports FAST (named files, under five minutes together on the check runner, with their times from scripts/test-times.json quoted) and test-shards.ts --fast runs them; test/check-list.test.ts proves FAST ⊆ GATE.
• [ ] forge.json check.fast is tsc --noEmit plus --fast; check.run stays the full gate.
• [ ] A red full gate on a landed commit opens or reopens the issue the pull closed, naming the failing test. The release already waits on main's check: do not touch .forgejo/workflows/release.yml or the chart (the direction forbids it).
• [ ] The pull quotes ask-to-live for one change before and after: push → green, land → live.
• [ ] The pull page and the MCP's reading of a check say which tier passed; main's red land gate shows on the board as one line.
• [ ] A look (screenshot) of the page that shows it, taken from the pull's preview, is in the pull.
• [ ] A test that goes red in this pull is fixed in this pull, whoever's it is.

Files. scripts/gate.ts, scripts/test-shards.ts, forge.json, test/check-list.test.ts, the reopen path in src/checks/service.ts. Not the release workflow, not the chart.

Risks. Red lands become more likely; the reopen must be loud and specific or main rots quietly.

Fits. Mason.

Before pushing. bun x tsc --noEmit and the test files named here, quoted in the pull. One pull, green on its first push.

One pillar: this serves exactly the one it is linked under. Done means reachable on the page, through MCP, in a test and by eye (#334).

Replaced by #1198, the owner's two-tier gate. It covers this issue's step two in its own shape: the fast set comes from the pull's diff, not a named FAST list, and a red full gate on land reopens the pull. Closing this so two builders don't build the same gate twice. #1198 now waits for #1180 (the check.fast key in forge.json), its first step.

I couldn't close this issue: this run's token can't change an issue's state. Until a person closes it as replaced by #1198, it waits for #1198, so no builder will pick it up.

Parked by the crew: the run ended without a pull: declined: #1181 has been replaced by #1198, the owner's two-tier gate, and atlas says so on the issue. #1198 takes a different shape from the one #1181 asks for. It builds the fast set from the pull's diff, not

Parked by the crew: the run ended without a pull: declined: I won't build #1181, because #1198 is closed and its fast tier is already in this repository. I checked the tree before deciding.

Parked twice since a person last spoke here, so it is the planner's now. Every reason:

1. the run ended without a pull: declined: #1181 has been replaced by #1198, the owner's two-tier gate, and atlas says so on the issue. #1198 takes a different shape from the one #1181 asks for. It builds the fast set from the pull's diff, not
2. the run ended without a pull: declined: I won't build #1181, because #1198 is closed and its fast tier is already in this repository. I checked the tree before deciding

The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.

Dropped: forge.json already declares check.fast (tsc plus test-shards.ts --tier fast --diff … --learned …), check.run is still the full gate, and the release waits on main's check. The two-tier gate this asked for is in the repository.