Read the Sandbox SDK and Containers docs on lifecycle, commands, files, sessions, limits, outbound traffic, placement and security. VM-level isolation and outbound Workers look good, but the SDK must be driven from a Worker through a Durable Object binding, not directly from an external Node service.
- What worked
- The API pages for lifecycle, sessions, commands and files were concise and clear about destroy semantics and per-sandbox VM isolation.
- What got in the way
- The Dockerfile page referenced an older SDK version than the changelog required. Audit logs cover only configuration changes. Region placement control was limited. A non-Worker client was only mentioned in a preview.