safe-bash: publish Worker-compatible optional node command runtime composition

[kamilio]

Current integration scope excludes both the safejs command and the external op integration. The node command remains requested in our Cloudflare Worker. The 79-command portable preset is usable with the bounded provider; curl is separately configured. The optional node command needs a supported Worker-compatible import/runtime path. SafeJS matters here only as its documented injected runtime implementation.

Evidence from published 0.1.491 tarballs and export maps:

• ./commands/node exports createNodeCommand/nodeCommands and accepts the documented NodeSafeJsCommandOptions { runtime: SafeJsRuntime }, but its module also eagerly re-exports createNodeWorkerProvider; commands/node/worker-provider.js imports Worker from node:worker_threads. The injected SafeJS path therefore still brings the host-only provider into the import graph.
• safeJsCommands exists but is exported only by the root entry; no public ./commands/safejs subpath exists. The current root entry has Node-only exports (the separate default-entry work is tracked in safe-bash: make agentCommands portable by default with optional regexExecutor injection #669/safe-bash: remove remaining node: builtins from the default agentCommands graph (crypto/zlib/stream/perf_hooks/timers) for a zero-nodejs_compat Workers bundle #672).
• @poe-platform/safe-js@0.1.491 exports . and ./core with browser: null. The public SafeJsRuntime injection contract is clear, but there is no published Worker/browser runtime entry to supply it. We do not want to implement an interpreter or reach into unpublished internals.

Requested outcome: publish a supported Worker-compatible way to register and execute node using the intended bounded runtime, with the worker-thread Node provider restricted to an explicit host-only import. A documented composition example should use only public exports and preserve source/output/step/memory/abort limits. Exercise the supported node -e profile with filesystem read/write, cancellation, and a runaway-program refusal in actual workerd. If this command intentionally cannot be supported in Workers, please make that distinction explicit rather than requiring an application shim.

This is separate from regex executor injection: #669 alone does not currently identify the optional SafeJS runtime/export requirement. This report is based on the published module graph/export map; it does not claim a new full-runtime reproduction beyond those concrete import constraints.

[kamilio]

Validated against current source and the actual packed/offline-installed default-entry candidate. Even a named nodeCommands import still reaches the host Worker provider; browser bundling also reports native path/util/stream imports. The SafeJS root and core exports explicitly refuse browser resolution. A diagnostic graph inspection confirms that merely removing browser: null would not solve the underlying native context/crypto/filesystem dependencies.

The optional-node request is therefore valid and separate from the default 79-command preset. Public-export composition passes six focused Node controls covering VFS I/O, runaway/source/output/data limits, and cancellation-reason preservation; that is not Worker acceptance. The requested safejs command and op integration remain excluded from this scope. No speculative runtime/export-map change has been made, and historical 0.1.491 tarballs were not independently re-downloaded for this validation.

[kamilio]

Our current Poe integration scope has changed: the product now explicitly excludes the node command, along with safejs and op. We no longer need this issue to unblock that integration. The documented public Worker-compatible optional-node composition gap remains valid for other consumers; this scope update does not claim the API is implemented or ask to close the issue.