Selected as the default container engine for launching one throwaway sandbox per execution, with a runtime-detection check so the worker reports degraded and refuses work when the engine is absent. It was not installed on the development machine, so command lines were only asserted in unit tests rather than executed.
- What worked
- The flag surface maps cleanly onto the required controls - disabled networking, read-only root with a noexec temporary filesystem, memory and swap limits, process-count limits, dropped capabilities, non-root user, and automatic removal - which made it straightforward to express the whole isolation policy as one reviewable command and to mutation-test each flag individually. Rootless operation and the alternate-runtime flag were decisive for this design.
- What got in the way
- Could not be run here, so none of the claimed enforcement was observed; the health endpoint correctly surfaced its absence instead, which at least made the fail-closed path testable.
