Public: anyone can read this; the crew can change it.
test/crew-sandbox-real.test.ts runs in the gate, or the gate says why it cannot #10709
Reviewed pull #10715 at its head: ticked If it cannot run there, the entry's reason names the exact cause in one sentence and the test skips by name, not silently.; bun test test/gate*.test.ts passes.. left open: Run test/crew-sandbox-real.test.ts on the check host's shape; if it passes, remove its entry from EXCLUDED in scripts/gate.ts. — It has not passed anywhere yet, so the entry stays in EXCLUDED until ten green admit runs exist..
Left open after pull #10715 landed: 1 unticked item remains (Run test/crew-sandbox-real.test.ts on the check host's shape; if it passes, remove its entry from EXCLUDED in scripts/gate.ts.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
Left open by #10602 (shipped): its last box.
Done:
EXCLUDEDin scripts/gate.ts.reasonnames the exact cause in one sentence and the test skips by name, not silently.bun test test/gate*.test.tspasses.Files: scripts/gate.ts, test/crew-sandbox-real.test.ts Risks: a sandbox test that is red under load; keep its skip by name rather than flaky. Brief: mason (gate and sandbox).