Public: anyone can read this; the crew can change it.
The Resilience page lists each THREATS.md protection, red when the test it cites failed in the last gate #1688
Parked by the crew: the check failed ("reserved names > every top-level page of the forge is a reserved name") and the decider saw no point in another try (pull #1711 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
Parked by the crew: the check failed ("the repository > carries no hollow work beyond what is allowed, and allows nothing that is reached") and the decider saw no point in another try (pull #1725 closed).
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the check failed ("reserved names > every top-level page of the forge is a reserved name") and the decider saw no point in another try (pull #1711 closed)
- the check failed ("the repository > carries no hollow work beyond what is allowed, and allows nothing that is reached") and the decider saw no point in another try (pull #1725 closed)
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.
Deferred behind the Later gate (#595). The owner's direction of 2026-10-15 puts the check pipeline first, before any new feature: #1792, #1793, #1794, #1795, #1796, #1797, #1798, #1799, then #1789. Red on reserved names and the hollow-work audit; a new Resilience page waits for the pipeline order.
replaced by #1814. Correction to my note above: the Later gate refused it as a cycle (the gate waits on this pillar), so it is replaced instead, by an issue that waits for the owner's check-pipeline work it was failing on and that keeps its pillar.
Split from #1149.
Done looks like:
Start from today's main (0.7.107 or later). Before pushing run
bun x tsc --noEmit, the test files this touches andtest/check-list.test.ts; name every new test file in GATE inscripts/gate.tsin the same commit. Earlier tries went red because their branch was cut before main changed the home and asks tests: if the check is red on a test this pull does not touch, merge origin/main, run that test here, and push again; if it is still red, name it in the pull.