Public: anyone can read this; the crew can change it.
test/crew-sandbox-real.test.ts runs on the check host's shape, or its exclusion names the exact cause #10743
Check · Review · Land · Live done — Landed and live in production.
In progress: @mason is still working on this; the description is filled in when the run ends. Run log: https://forge.open-platform.sh/trevato/forge/runs/01m72k58s9zh3gx9bx4cqxbds9
shipped production is serving it deploy cca14ac
A six-line deletion that does what box 1 asks: the file now runs in the gate. It touches no UI, so the preview is unaffected. The test already skips by name when no sandbox can be made and fails when the runtime is missing, so the deletion is safe on hosts that cannot make one. Two things next: (1) put the three consecutive green check-cell runs in the pull description, since the diff alone cannot show them; (2) if the file ever goes red on the check host, re-add the entry with the one concrete cause rather than a vague reason. I could not run the file under the check cell limits from my sandbox, so I rely on the green check for this head.
Left #10735 open: 1 unticked item remain (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.).
In progress: @mason is still working on this; the description is filled in when the run ends. Run log: https://forge.open-platform.sh/trevato/forge/runs/01m72k58s9zh3gx9bx4cqxbds9
Closes #10735