Twelve quarantined suites that pass alone run in the gate again #11061

Five of the thirteen suites listed in #11049 rejoin the gate. They passed bun test --randomize three times in a row, run together with test/gate*.test.ts and test/check-list.test.ts:

• test/reviews.test.ts
• test/studio-phone.test.ts
• test/spawn-placement.test.ts
• test/runs-lease.test.ts
• test/tui-boards.test.ts

The only change is to EXCLUDED in scripts/gate.ts. The issue's title says twelve, but its list names thirteen files; all thirteen were run.

Still excluded. The other eight failed when run on their own under --randomize, so they stay out. Each entry's reason now says what failed today instead of "not yet admitted", and points at #11049. #261, #555 and #2106 are closed, so they can no longer own these entries.

• apps-sleep: "an environment nobody asks for sleeps, and the next request wakes it" hits the 30-second timeout in 2 of 3 runs.
• board-windows: "the batch agrees with each account read alone" fails in 2 of 3 runs, depending on order.
• parity: reopening a pull, team listings and profile edits depend on state left by earlier tests (422s and wrong listings). It failed in all 3 runs.
• probe: "a scaffolded app obeys every cell" returns mismatch instead of ok in 1 of 3 runs.
• probes: "the first clean probe after closes the issue" returns down instead of ok in all 3 runs.
• public-url: "clone URLs name the public address" gets a 401 when it runs before signup, in 2 of 3 runs.
• snapshot: the retention, restore and upload tests share one store and depend on order; 1 to 6 fail per run.
• tui-asked: "the asked screen" lists asks that other tests filed. It failed in all 3 runs.

These need fixes inside the test files, so I didn't widen this pull to make them.

Not caused by this pull: test/gate-bypass.test.ts is already in the gate and also fails on its own under --randomize. "Three reds followed by a landing do not alarm" and the core landing test share state with earlier tests. It passes in file order, which is how the gate runs it, so I left it alone.

Checks run here: bun scripts/gate.ts passes, bun x tsc --noEmit is clean, and bun test test/gate*.test.ts test/check-list.test.ts gives 51 pass, 0 fail. I did not run the full sharded gate three times here; the forge's check runs it on this push.

🤖 Generated with Claude Code

Closes #11049

Five of the thirteen suites listed in #11049 rejoin the gate. They passed bun test --randomize three times in a row, run together with test/gate*.test.ts and test/check-list.test.ts:

• test/reviews.test.ts
• test/studio-phone.test.ts
• test/spawn-placement.test.ts
• test/runs-lease.test.ts
• test/tui-boards.test.ts

The only change is to EXCLUDED in scripts/gate.ts. The issue's title says twelve, but its list names thirteen files; all thirteen were run.

Still excluded. The other eight failed when run on their own under --randomize, so they stay out. Each entry's reason now says what failed today instead of "not yet admitted", and points at #11049. #261, #555 and #2106 are closed, so they can no longer own these entries.

• apps-sleep: "an environment nobody asks for sleeps, and the next request wakes it" hits the 30-second timeout in 2 of 3 runs.
• board-windows: "the batch agrees with each account read alone" fails in 2 of 3 runs, depending on order.
• parity: reopening a pull, team listings and profile edits depend on state left by earlier tests (422s and wrong listings). It failed in all 3 runs.
• probe: "a scaffolded app obeys every cell" returns mismatch instead of ok in 1 of 3 runs.
• probes: "the first clean probe after closes the issue" returns down instead of ok in all 3 runs.
• public-url: "clone URLs name the public address" gets a 401 when it runs before signup, in 2 of 3 runs.
• snapshot: the retention, restore and upload tests share one store and depend on order; 1 to 6 fail per run.
• tui-asked: "the asked screen" lists asks that other tests filed. It failed in all 3 runs.

These need fixes inside the test files, so I didn't widen this pull to make them.

Not caused by this pull: test/gate-bypass.test.ts is already in the gate and also fails on its own under --randomize. "Three reds followed by a landing do not alarm" and the core landing test share state with earlier tests. It passes in file order, which is how the gate runs it, so I left it alone.

Checks run here: bun scripts/gate.ts passes, bun x tsc --noEmit is clean, and bun test test/gate*.test.ts test/check-list.test.ts gives 51 pass, 0 fail. I did not run the full sharded gate three times here; the forge's check runs it on this push.

🤖 Generated with Claude Code

Left #11049 open: 1 unticked item remain (Their EXCLUDED entries are removed: test/board-windows, reviews, parity, public-url, studio-phone, spawn-placement, runs-lease, tui-asked, tui-boards, probe, probes, apps-sleep, snapshot (.test.ts)).