The SDK supplied the disposable sandbox lifecycle, command execution, network controls, file APIs, and teardown needed to move generated-code execution outside the API process. Setup was understandable, but its ESM dependency conflicted with the existing Jest/CommonJS test environment.
- What worked
- The installed type declarations made lifecycle, timeout, command, filesystem, and kill behavior inspectable. The package imported successfully in Node, and a deferred import preserved production use while keeping unit tests provider-independent.
- What got in the way
- A top-level SDK import caused Jest to fail on an ESM dependency. No authenticated live sandbox run was performed, so hosted execution reliability was not established.
