- Add ninth capability word (bits9), STOCK_V9, FEATURE9_*; bump feature bits doc to 11 - Extend seed RPCs, channel wiring, replication/staging adjuncts; bare_os_proc_index schema 5 - Wave 9 /proc JSON via bare-os-wave9-proc.js + VFS aliases; ctx API 1.18.0 + d.ts hooks - Boot policy v9 + kernel/init.js enforcement; extensions registry schema 6; strict bits9 caps - NDJSON lifecycle 8, OTel 6, audit 6; SOCKS proxy map, worker/WASM/env passthrough - Coreutils openssl stub (bare-crypto doc); mediaproc:* worker group; http-fetch SOCKS lookup - CI: verify-kernel-roadmap-wave9.mjs, wave3/ctx/dts/compat updates; pretest chain - Docs: roadmap Wave 9 table, ADR §12, kernel-extensions/capabilities/matrix/protocol/handbook/ developer-guide (node-to-bare-modules, privacy), kernel README, scripts README, changelogs - Sync packages/bare-os-seeder/kernel (init.js, README); refresh booter /proc readdir test list
/lib/bare (system image)
Self-contained ctx.bare support on the system Hyperdrive:
bare-module-manifest.json— copy of the booter manifest (same keys and packages as host resolution).manifest.json— drive loader index:bundleslists IIFE paths that assign intoglobalThis.__bare_os_stdlib__;bundleStatssummarizes esbuild success vs stub-only placeholders.bundles/*.js— one file per manifest row. Successful builds are full IIFE bundles; failures are no-op stubs (see file header). Regenerate withnpm run build -w bare-os-bare-libs.
At boot the booter runs drive bundles first, then (unless BARE_OS_BARE_HOST_IMPORTS=0) fills any missing keys via host import().
Trusted image only: executing these bundles is equivalent to running seeded /bin utilities.