test/crew-sandbox-real.test.ts runs on the check host's shape, or its exclusion names the exact cause #10735

Left open by #10602 (shipped): its first box only.

Done:

• [x] Run test/crew-sandbox-real.test.ts under the check cell's limits (the shape scripts/gate.ts runs shards in). If it passes three runs in a row, delete its entry from EXCLUDED in scripts/gate.ts so the gate runs it.
• [ ] If it cannot, the entry's reason names the one concrete cause (a syscall, a mount, a missing binary) and the test skips by that name.
• [x] bun test test/gate*.test.ts passes.

Files: scripts/gate.ts, test/crew-sandbox-real.test.ts Risks: a sandbox test red under load; keep a named skip rather than a flaky gate. Brief: mason (gate and sandbox).

Reviewed pull #10743 at its head: ticked Run test/crew-sandbox-real.test.ts under the check cell's limits (the shape scripts/gate.ts runs shards in). If it passes three runs in a row, delete its entry from EXCLUDED in scripts/gate.ts so the gate runs it.; bun test test/gate*.test.ts passes.. left open: If it cannot, the entry's reason names the one concrete cause (a syscall, a mount, a missing binary) and the test skips by that name. — Applies only if the test cannot run; this pull takes the passing branch, so the box stays open..

Left open after pull #10743 landed: 1 unticked item remains (If it cannot, the entry's reason names the one concrete cause (a syscall, a mount, a missing binary) and the test skips by that name.). 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.