The sandbox contract — the entire interface a TS execution environment must satisfy. Deliberately minimal: run code with globals and callbacks, return the value and console output.
Requirements for real implementations:
- No network access inside the sandbox.
globalsare injected as JSON data before the code runs.callbacks.requestmay be invoked CONCURRENTLY (Promise.all).- The boundary is JSON-native: values crossing it survive JSON encode/decode unchanged.
- On timeout, return
{:error, {:timeout, ms}}, and cancel any outstanding callback work first — killing the sandbox process is not enough on its own, since callbacks dispatched into Elixir Tasks can still be in flight and will try to write to a call log the tool layer has already torn down. - On a run-time error inside the sandbox, prefer
{:error, %{message: String.t(), logs: [String.t()]}}when any console output was captured before the crash — the tool layer surfaces those logs to the caller even though the run failed. A bare{:error, term()}(no logs) is also accepted for errors that necessarily precede any code running (e.g. a raise in the executor itself).
The apiNames global (magic key)
env.globals always carries an "apiNames" entry — the list of
registered API names for this run (set by OapiCodemode.Tools in
do_execute/6). This is not an ordinary data global: a real executor
MUST read globals["apiNames"] and, before running the sandboxed code,
build one apis.<name>.request(opts) binding per name that forwards to
the :request callback as rpc("request", [name, opts]) (see
priv/deno/bootstrap.ts's installGlobals/2 for the reference
implementation). Everything else in globals is injected as inert data;
apiNames alone is a build instruction for the sandbox's apis object.
A third-party executor that treats it as just another data global will
silently omit apis entirely and every execute_api_code call will fail
with "apis is not defined" — there is no other signal pointing at this
requirement, so implementers must know to look for it here.