@poe-platform/safe-js 0.1.799 → 0.1.800

package/README.md

@@ -8,6 +8,8 @@ built-ins. It is suitable for capability-controlled scripts and agent workflows.
 Complete ECMAScript conformance has not been established; see
 [development status](#development-status) and [meaningful limitations](#meaningful-limitations).
 
+Under `workerd` and `browser` conditions, the standalone root and `/core` exports select the portable interpreter with `makeFsModule`, `makeEnvModule`, `makeTimeModule`, `makeFailModule`, `makeMetricModule`, and `makeHarnessModule`. The `/modules/fs` entry is also portable; supply a filesystem adapter for host file access.
+
 ## Quickstart
 
 Install the public ESM package. Its declared Node.js minimum is 18.18+, but
@@ -36,7 +38,7 @@ console.log(result.returnValue);
 
 `run()` takes source text, not a file path. Success returns `ok`, `returnValue`, `snapshot`, and `stats`. Handle both an `ok: false` result and a rejected promise: parsing, budget exhaustion, cancellation, and some execution failures can reject. Top-level `await` in this example lets rejections reach Node.
 
-`@poe-platform/safe-js/core` exposes `run`, `createRealm`, `defineExtension`, `lint`, `Budget`, and replayable-random helpers. The `/core`, `/workerd`, and `/modules/fs` workspace entries bundle with the `workerd` or `browser` condition without Node built-ins. Supply a `@poe-code/safe-fs` adapter for filesystem capabilities; `createRootedSourceResolver(root, adapter)` grants portable source imports. File snapshots, migrations, harnesses, and file-running helpers also accept an `adapter`. The shared filesystem lives in `@poe-platform/safe-fs`, with a portable `/core` entry. Existing `@poe-platform/safe-js/fs`, `/fs/core`, and `/fs/node` imports re-export it. Legacy `poe-code/safe-js` imports remain available through the CLI package but use a separate runtime; keep factories and errors within one import family.
+`@poe-platform/safe-js/core` exposes `run`, `createRealm`, `defineExtension`, `lint`, `Budget`, and replayable-random helpers for Node.js. In Workers, the `@poe-platform/safe-js` root selects `/workerd`: it exports the portable core API plus `declareHostOperation` without requiring `nodejs_compat`, including the runtime hooks needed by Safe Bash's `nodeCommands()`. The `/core` and `/modules/fs` workspace entries also bundle with the `workerd` or `browser` condition without Node built-ins. Supply a `@poe-platform/safe-fs/core` adapter for filesystem capabilities; `createRootedSourceResolver(root, adapter)` grants portable source imports. File snapshots, migrations, harnesses, and file-running helpers also accept an `adapter`. The shared filesystem lives in `@poe-platform/safe-fs`, with a portable `/core` entry. Existing `@poe-platform/safe-js/fs`, `/fs/core`, and `/fs/node` imports re-export it. Legacy `poe-code/safe-js` imports remain available through the CLI package but use a separate runtime; keep factories and errors within one import family.
 
 ## Supported features