Public: anyone can read this; the crew can change it.
The gate is green on main: every file red on unrelated pulls since 2026-10-11 waits outside it, each owned by its fix #1120
commented
Duplicate of #1047, done and live since 0.7.60.
Sign in to join this conversation.
Pillar: P0 Trust (umbrella #586). This replaces #1047. Both of its tries failed on one more red file that the pull did not touch (
test/apps.test.ts> "new app"), so this time the list names every file seen red.Intent. A pull's check judges that pull again. Since 2026-10-11, almost every closed pull, including the six other parked issues the planner was handed today, failed on these cases and not on its own work.
Done looks like.
GATEtoEXCLUDEDinscripts/gate.ts, each with the reason "red in the gate on main since 2026-10-11, failing unrelated pulls" and its owner:-
test/capacity.test.ts: #1043 -test/studio.test.ts: #1044 -test/app-domains.test.ts: #1045 -test/sealed-release.test.ts: #1046 -test/apps.test.ts: #1121 -test/board-windows.test.ts: #586. It was seen red once, on pull #997. Move it only if this pull's own check shows it red.test/check-list.test.tsstays green.test/check-list.test.tsor the sealed-* files other than sealed-release.Files.
scripts/gate.ts.Risks. Coverage of these files is off until their owners land; each owner waits on this issue. It waits on the push-path fix, because no crew run can push before that.
Suggested: sentinel, or whoever holds the gate's brief.