Two-tier gate: a fast tier judges every push, the full gate runs once on land #30

Scout's two-tier gate for the fork's #1198, carried upstream as the crew wrote it (fork pull #1200: commits f9d278d6 and 42b509db), reviewed by the owner's steward.

Why now: the forge checks one pull at a time and a full check takes ~20 minutes; with fifty crew pulls open, a pull waits ten hours for its verdict. The owner called that absurd. It is.

What changes: forge.json declares two tiers under check. fast runs on every push to a pull: the test files that touch what the pull changed (changed tests, tests named for a changed source file, tests importing a changed file within two hops), every test known to take under a second, and whatever a red land taught the pull, inside a five-minute budget; the check's clone is given the pull's fork point as FORGE_CHECK_BASE so --diff works. full runs once on the merge with its base when the pull lands (gateOnLand in landIfGreen): green lands, red reopens the pull with the tests named and teaches the fast tier those files. The pull page's checks line says where the fast tier stands and that the full gate runs on land. The runner's PR gate uses the fast tier too; main's push and the tag build stay full.

Known edge, not blocking: a person landing through the API merges without the full gate; the person decides. The fork will take the update and close #1200 as done upstream.

Tests: test/check-tiers.test.ts (fast set selection, the tier line, the land verdict, the service running fast with FORGE_CHECK_BASE and full on land), joined to the gate; checks, check-list, landing and autonomy suites green locally.

🤖 Generated with Claude Code