safe-bash: remove remaining node: builtins from the default agentCommands graph (crypto/zlib/stream/perf_hooks/timers) for a zero-nodejs_compat Workers bundle

[kamilio]

Goal

Make the default agentCommands() graph loadable on Cloudflare Workers and browsers without nodejs_compat — a true zero-node:-builtin bundle. Today the full command inventory runs on workerd with nodejs_compat (verified on real workerd, 2026-09-08), but the eager node: imports below mean the ordinary entry cannot load when compatibility_flags = [].

This is the sibling of #669 (portable-by-default agentCommands / injectable regexExecutor, which removes node:worker_threads) and #671 (the two contracts/ leaks). #669 gets the default entry onto workerd-with-compat; this issue removes the remaining Node builtins so no compat flag is needed.

Node builtins in the createAgentCommands graph (beyond #669/#671)

Verified against current src (all reached from plugins/composition.ts):

• node:crypto
  • commands/bytes/checksums/index.ts:3 — createHash (sha256sum/sha1sum/md5sum/cksum).
  • commands/bytes/compression/files.ts:1 — randomUUID.
  • commands/metadata/mktemp.ts:1 — randomInt (mktemp).
• node:zlib
  • commands/bytes/compression/gunzip.ts:5 — createInflateRaw.
  • commands/bytes/compression/stream.ts:4 — createGzip.
  • commands/archive/stream.ts:1 — createGunzip, createGzip (tar gz).
• node:stream / node:stream/promises
  • commands/bytes/compression/stream.ts:1-2 — Readable, PassThrough, pipeline.
• node:perf_hooks / node:timers
  • commands/timeout/scheduler.ts:1-2 — performance, setTimeout/clearTimeout.
• node:worker_threads (expr BRE path)
  • commands/expr/bre-worker.ts:1 — isMainThread (in addition to the regex executor covered by safe-bash: make agentCommands portable by default with optional regexExecutor injection #669).

Portable replacements (all have Workers/browser-standard equivalents)

• node:crypto createHash → Web Crypto crypto.subtle.digest (async; checksums already stream, so a digest accumulator fits) or a small pure-JS hash for md5/cksum where subtle has no algorithm. randomUUID → global crypto.randomUUID(). randomInt → crypto.getRandomValues.
• node:zlib → a portable inflate/deflate (pure-JS such as fflate, or wasm) behind the existing bounded/streaming interfaces; keep the current gzip-bomb output-budget checks.
• node:stream → Web Streams (TransformStream/ReadableStream, already globals in workerd/browsers), matching the safe-bash: documented @poe-platform/safe-bash/browser Workers entry fails to start without nodejs_compat — contracts/io.ts imports node:stream/web, contracts/path.ts imports node:path #671 fix in contracts/io.ts.
• node:perf_hooks → global performance; node:timers → global setTimeout/clearTimeout (the code already has a scheduler-binding indirection).

Acceptance

• Bundle the default entry with esbuild --conditions=workerd,worker,browser and assert zero node: specifiers.
• Load and run representative commands (sha256sum, gzip/zcat, tar, mktemp, timeout, expr) on real workerd with compatibility_flags = [].
• Preserve current budgets, cancellation, gzip-bomb caps, and explicit unsupported-mode errors; no unbounded native fallbacks.
• Where a portable primitive forces a tradeoff (e.g. async digest, restricted zlib), document it rather than weakening a guarantee.

Depends on / pairs with #669 and #671.

[kamilio]

Validated independently against the freshly installed public package candidate: an unshimmed browser/workerd-conditions bundle of /portable fails on the actual emitted node:crypto, node:stream, node:stream/promises, zlib, and timer-related imports. This is a real remaining full-inventory portability gap; the /browser claim in #671 was separately disproved against published 0.1.470 and closed without a speculative patch. #670 removes the portable expr engine dependency on the Node wrapper.

I am finishing delivery of the validated #670 and mixed-entry #669 fixes now, then continuing #669 under the updated scope and #672. Streaming hashes/codecs must retain input/output/work limits and cancellation; no whole-input digest shortcut, native unbounded-regex fallback, or silent loss of gzip/tar semantics. No claim of a zero-Node full preset yet. Reproduction log: /tmp/kamilio-672-portable-browser-red.log.

[kamilio]

Final delivery verification: remote main fd9ba58 matches the product tree of the freshly installed artifact tested in actual workerd. All 29 flags=[] cases pass, all 79 command names are present, and the installed graph has zero Node/external edges. Full maintained npm test, normal build, lint, installed Node/Bun, strict browser types and browser smoke pass. Fresh hashes, SRI bindings and runtime cleanup are recorded in docs/plans/issue-672-workerd-validation.md. The issue is closed after push; release publication is still being monitored separately.

[poe-code-agent]

Issue was resolved by #fd9ba58

Update poe-code via npm install -g poe-code@14.0.93

[kamilio]

Publication is now verified: all three scoped packages (@poe-platform/safe-bash, safe-fs, safe-js) are npm latest 0.1.499. Scoped release run 34276528355 attempt 2 passed installed tarball verification and all three provenance-backed publishes for fd9ba58. The zero-Node default entry is therefore published, not just a local candidate. poe-code@14.0.93 is published too.