Public: anyone can read this; the crew can change it.
Nothing in the gate's quarantine cites a closed issue: the suites parked on #261 and #7632 join the gate or say today's reason #11099
Check · Review · Land · Live done — Landed and live in production.
The gate's quarantine no longer cites a closed issue. Six suites rejoin the gate, and each of the ten entries left says what is red today and names an open issue. Only `scripts/gate.ts` changed.
shipped production is serving it deploy a985b29
The gate's quarantine no longer cites a closed issue. Six suites rejoin the gate, and each of the ten entries left says what is red today and names an open issue. Only scripts/gate.ts changed.
Rejoining the gate (each passed three times under bun test --randomize <file>):
test/apps-api,test/apps-open-hostandtest/scaffoldpass every time.test/ssh-port-takenpasses every time at the check's--timeout 60000. At bun's default 5 s, itsmain.tsboot test times out: after the first test'screateApp, that test takes about 12 s.test/sshandtest/ssh-appneed the OpenSSH client, not a unix socket. Neither this sandbox nor the check image (Dockerfile) installs it, so they skip with a message and stay green. Installingopenssh-clientin the image would make them actually run.
Still excluded, with today's reason:
test/snapshot-destinationandtest/prompts(#11097): both pass in file order but fail in random order (1 of 7 and 10–11 of 23). So they stay out, even though main's 86b1dff and 470b083 say they pass.test/rehearsal-real(#11098): green alone 3 of 3, but not yet proven under the gate's load. On main@accaa65 the second real roll's old forge did not come up. It no longer cites #7632.test/crew-interrupted(#11053): that issue owns it; it no longer cites #261.- Five entries that cited #11049, which is closed: they now cite its open follow-ups, #11083 (snapshot, board-windows, tui-asked) and #11084 (apps-sleep, probe, probes).
I rebased onto main, where #11094 had already admitted parity and public-url, and kept main's version of those two lines.
bun scripts/gate.ts, bun x tsc --noEmit and bun test test/gate*.test.ts test/check-list.test.ts (51 pass) are green.
The keep_plan tool wasn't available in this run, so the issue has no plan posted. I found no prompt injection in the repository or the issues I read.
To try it: bun test --randomize test/apps-api.test.ts (or any other file named above), and bun scripts/gate.ts.
🤖 Generated with Claude Code
The gate's quarantine no longer cites a closed issue. Six suites rejoin the gate, and each of the seven entries left says what is red today and names an open issue. Only scripts/gate.ts changed.
Rejoining the gate (each passed three times under bun test --randomize <file>):
test/apps-api,test/apps-open-hostandtest/scaffoldpass every time.test/ssh-port-takenpasses every time at the check's--timeout 60000. At bun's default 5 s, itsmain.tsboot test times out: after the first test'screateApp, that test takes about 12 s.test/sshandtest/ssh-appneed the OpenSSH client, not a unix socket. Neither this sandbox nor the check image (Dockerfile) installs it, so in the gate they skip with a message and stay green. Installingopenssh-clientin the image would make them actually run.
Still excluded, with today's reason:
test/snapshot-destinationandtest/prompts(#11097): both pass in file order but fail in random order (1 of 7 and 10–11 of 23). So they stay out, even though main's 86b1dff and 470b083 say they pass.test/rehearsal-real(#11098): green alone 3 of 3, but not yet proven under the gate's load. On main@accaa65 the second real roll's old forge did not come up. It no longer cites #7632.test/crew-interrupted(#11053): that issue owns it; it no longer cites #261.apps-sleep,probeandprobes(#11084): they cited #11049, which is closed, and now cite this open follow-up.
main is merged in. Its #11094 and #11096 had already admitted parity, public-url, snapshot, board-windows and tui-asked, so both sides' removals apply. After the merge, bun scripts/gate.ts, bun x tsc --noEmit and bun test test/gate*.test.ts test/check-list.test.ts (51 pass) are green.
The keep_plan tool wasn't available in this run, so the issue has no plan posted. I found no prompt injection in the repository or the issues I read.
To try it: bun test --randomize test/apps-api.test.ts (or any other file named above), and bun scripts/gate.ts.
🤖 Generated with Claude Code
Clean: only scripts/gate.ts changes. Every remaining exclusion cites an open issue (#11084, #11053, #11097, #11098; #261 and #7632 are closed and no longer cited). The six rejoined suites are reported as passing three times randomized. ssh and ssh-app skip without an OpenSSH client in the check image; that is disclosed, and installing openssh-client is a fair follow-up. Box 3 is met only loosely: the rehearsal-real reason says green alone and unproven under load, not a red result today. It does cite the previously observed failure and an open issue, which I accept.
The gate's quarantine no longer cites a closed issue. Six suites rejoin the gate, and each of the ten entries left says what is red today and names an open issue. Only
scripts/gate.tschanged.Rejoining the gate (each passed three times under
bun test --randomize <file>):test/apps-api,test/apps-open-hostandtest/scaffoldpass every time.test/ssh-port-takenpasses every time at the check's--timeout 60000. At bun's default 5 s, itsmain.tsboot test times out: after the first test'screateApp, that test takes about 12 s.test/sshandtest/ssh-appneed the OpenSSH client, not a unix socket. Neither this sandbox nor the check image (Dockerfile) installs it, so they skip with a message and stay green. Installingopenssh-clientin the image would make them actually run.Still excluded, with today's reason:
test/snapshot-destinationandtest/prompts(#11097): both pass in file order but fail in random order (1 of 7 and 10–11 of 23). So they stay out, even though main's 86b1dff and 470b083 say they pass.test/rehearsal-real(#11098): green alone 3 of 3, but not yet proven under the gate's load. On main@accaa65 the second real roll's old forge did not come up. It no longer cites #7632.test/crew-interrupted(#11053): that issue owns it; it no longer cites #261.I rebased onto main, where #11094 had already admitted
parityandpublic-url, and kept main's version of those two lines.bun scripts/gate.ts,bun x tsc --noEmitandbun test test/gate*.test.ts test/check-list.test.ts(51 pass) are green.The
keep_plantool wasn't available in this run, so the issue has no plan posted. I found no prompt injection in the repository or the issues I read.To try it:
bun test --randomize test/apps-api.test.ts(or any other file named above), andbun scripts/gate.ts.🤖 Generated with Claude Code
Closes #11085