oonacode 0.3.205 → 0.3.207

package/README.md

@@ -2,7 +2,7 @@
 
 OonaCode is a Windows-first, multi-provider coding agent: the genuine Claude Code engine (driven
 through the official Claude Agent SDK) in an isolated profile, sessions in SQLite, any model
-provider through your own gateway, and personal remote access to your own machines.
+provider, and personal remote access to your own machines.
 
 This package is the **npm/pnpm/bun/yarn entry point**. It contains no binaries itself; the native
 build is pulled in through a per-platform optional dependency and linked into `bin/` by a
@@ -25,18 +25,18 @@ oona web           # open the local web UI
 
 ## Platform packages
 
-| Platform      | Package               | Status                                   |
-| ------------- | --------------------- | ---------------------------------------- |
-| Windows x64   | `oonacode-win32-x64`  | shipped                                  |
-| Windows arm64 | `oonacode-win32-arm64` | later (x64 build runs under emulation)  |
-| Linux x64     | `oonacode-linux-x64`  | later                                    |
-| Linux arm64   | `oonacode-linux-arm64` | later                                   |
-| macOS x64     | `oonacode-darwin-x64` | later                                    |
-| macOS arm64   | `oonacode-darwin-arm64` | later                                  |
+| Platform      | Package               | Status                                                  |
+| ------------- | --------------------- | ------------------------------------------------------- |
+| Windows x64   | `@oonacode/win32-x64` | shipped                                                 |
+| Windows arm64 | —                     | later (x64 build runs under emulation)                  |
+| Linux x64     | `@oonacode/linux-x64` | shipped with every release that carries Linux           |
+| Linux arm64   | —                     | later                                                   |
+| macOS         | —                     | not on npm (the terminal installer, `install.sh`)       |
 
-Each platform package carries `oona.exe` (the single-binary host + CLI), `oonaclaude.exe` (the pinned
-Claude Code engine sidecar — it must live on real disk next to `oona.exe`), the local web UI assets
-(`web-ui/`) and native addons (`build/`).
+Each platform package carries `oona.exe` (the single-binary host + CLI; `oona` on Linux), the local
+web UI assets (`web-ui/`), the provider registry and native addons (`build/`, `prebuilds/`). The
+pinned Claude Code engine sidecar, `oonaclaude.exe`, is in it only when the release bundled it;
+otherwise the PC downloads it once into its own store on the first message (`docs/engine-once.md`).
 
 `oonaclaude.exe` is a byte-for-byte copy of the pinned, **unmodified** engine binary from the Claude
 Agent SDK platform package. OonaCode does not fork or patch Claude Code; the file is renamed only so
@@ -44,7 +44,7 @@ it can never be confused with, or collide with, your own `claude` on PATH.
 
 ## How `oona` resolves the binary
 
-`bin/oona.js` looks for, in order: `bin/oona.exe` (linked by postinstall) → `oonacode-win32-x64/oona.exe`
+`bin/oona.js` looks for, in order: `bin/oona.exe` (linked by postinstall) → `@oonacode/win32-x64/oona.exe`
 in place → the JS CLI `@oonacode/cli/dist/main.js` when that package is a dependency (developer
 installs; slower start, needs an engine reachable via `OONACODE_CLAUDE_BIN`). The binary runs with
 inherited stdio and its exit code is forwarded verbatim. If nothing is found it prints how to fix
@@ -59,10 +59,9 @@ irm https://oonacode.oonak.ai/install.ps1 | iex
 - **pnpm / bun block lifecycle scripts by default.** Without the postinstall the wrapper still
   works (it resolves the platform package in place); linking only removes one resolution step.
 - Set `OONACODE_SKIP_POSTINSTALL=1` to skip the link step entirely.
-- Your own Claude subscription always runs direct to Anthropic from your PC; API-key providers go
-  through your own OonaCode gateway. No credential is ever shared between users.
-- `private: true` is set on this package until the first publish (TODO: flip in `package.json`
-  once the npm org is ready; the release workflow refuses to publish while it is private).
+- Your own subscriptions and your own API keys always run direct from your PC to the provider
+  (OonaCode translates on your PC where a provider needs it); only OonaCode's own pool goes through
+  the OonaCode gateway. No credential is ever shared between users.
 - In the monorepo `optionalDependencies` use `workspace:<version>` so pnpm links the sibling
   platform package. npm does not understand the workspace protocol, so what `packaging/release.ps1`
   publishes is a copy staged outside the repo by `packaging/scripts/stage-npm.mjs`, whose

package/bin/oona.js

@@ -5,7 +5,7 @@
  *
  * Resolution order (first hit wins):
  *   1. <this package>/bin/oona.exe             — hard-linked/copied there by postinstall.mjs
- *   2. <platform package>/oona.exe              — e.g. node_modules/oonacode-win32-x64/oona.exe
+ *   2. <platform package>/oona.exe              — e.g. node_modules/@oonacode/win32-x64/oona.exe
  *                                                 (used when the package manager skipped postinstall;
  *                                                  pnpm/bun block lifecycle scripts unless allowed)
  *   3. @oonacode/cli/dist/main.js via Node       — JS fallback when the monorepo CLI package is a
@@ -15,8 +15,8 @@
  * The native binary is spawned with inherited stdio and its exit code is forwarded verbatim, so
  * `oona -p ... --output-format json` works in pipes exactly like the bare executable.
  *
- * Windows and Linux x64 are published; the remaining platforms (arm64, darwin) are deferred —
- * see README.md.
+ * Windows and Linux x64 are on npm. macOS installs from the terminal (install.sh) and has no npm
+ * package yet; arm64 builds are not published — see README.md.
  */
 const fs = require('fs');
 const path = require('path');
@@ -28,7 +28,7 @@ const PLATFORM_PACKAGES = {
   // 'win32-arm64': 'oonacode-win32-arm64',   // deferred
   // 'linux-arm64': 'oonacode-linux-arm64',   // deferred — install.sh refuses aarch64 for the
   //                                             same reason: nothing is published for it
-  // 'darwin-x64': 'oonacode-darwin-x64',     // built (mac-builder.sh), NOT published: unsigned
+  // 'darwin-x64': 'oonacode-darwin-x64',     // no npm package: macOS installs with install.sh
   // 'darwin-arm64': 'oonacode-darwin-arm64', // not built yet
 };
 
@@ -41,13 +41,12 @@ const EXE_NAME = IS_WIN ? 'oona.exe' : 'oona';
 const ENGINE_NAMES = IS_WIN ? ['oonaclaude.exe', 'claude.exe'] : ['oonaclaude', 'claude'];
 const PLATFORM_KEY = `${process.platform}-${process.arch}`;
 
-// macOS: a build exists (packaging/mac-builder.sh) but is NOT published — it is unsigned, and Apple
-// signing is the owner's decision (2026-10-03) — so npm has nothing to install on a Mac, and says so
-// in words instead of a list of fixes that cannot work.
+// macOS: published since 0.3.202 for the terminal installer only (ad-hoc signed, no Apple
+// Developer ID yet — the owner's decision of 2026-10-03), so npm has nothing to install on a Mac.
+// Say where the real install is, instead of a list of fixes that cannot work.
 const MAC_HINT = [
-  `oonacode: OonaCode publishes no macOS build yet (${PLATFORM_KEY}): the macOS app is not signed yet,`,
-  '  so nothing for a Mac is on npm or on oonacode.oonak.ai.',
-  '  A local build installs with:  packaging/install.sh --archive oonacode-darwin-<arch>.tar.gz',
+  `oonacode: there is no npm package for macOS (${PLATFORM_KEY}). Install OonaCode from the terminal:`,
+  '      curl -fsSL https://oonacode.oonak.ai/install.sh | bash',
   '',
 ].join('\n');
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "oonacode",
-  "version": "0.3.205",
+  "version": "0.3.207",
   "description": "OonaCode — Windows-first multi-provider coding agent: the `oona` CLI, headless host service and local web UI. npm wrapper; the native binary is installed through the per-platform optional dependency.",
   "license": "UNLICENSED",
   "type": "commonjs",
@@ -35,6 +35,6 @@
     "test": "node --test test/wrapper.test.js test/packaging-scripts.test.js test/uninstall-scripts.test.js test/release-feed.test.js test/manifests.test.js test/set-version.test.js test/npm-stage.test.js test/ship-plan.test.js test/ship-checks.test.js test/release-platforms.test.js"
   },
   "optionalDependencies": {
-    "@oonacode/win32-x64": "0.3.205"
+    "@oonacode/win32-x64": "0.3.207"
   }
 }

package/postinstall.mjs

@@ -2,11 +2,11 @@
  * oonacode postinstall — link the platform-specific native binaries into ./bin so that
  * `oona` starts without a resolution step.
  *
- *   node_modules/oonacode-win32-x64/oona.exe        ->  ./bin/oona.exe        (hard link, falls back to copy)
- *   node_modules/oonacode-win32-x64/oonaclaude.exe  ->  ./bin/oonaclaude.exe  (engine sidecar — must sit next to oona.exe)
- *   node_modules/oonacode-win32-x64/web-ui/         ->  ./bin/web-ui/         (directory junction, falls back to copy)
- *   node_modules/oonacode-win32-x64/build/          ->  ./bin/build/          (native addons, same treatment)
- *   node_modules/oonacode-win32-x64/registry.json   ->  ./bin/registry.json   (hard link, falls back to copy)
+ *   node_modules/@oonacode/win32-x64/oona.exe        ->  ./bin/oona.exe        (hard link, falls back to copy)
+ *   node_modules/@oonacode/win32-x64/oonaclaude.exe  ->  ./bin/oonaclaude.exe  (engine sidecar — must sit next to oona.exe)
+ *   node_modules/@oonacode/win32-x64/web-ui/         ->  ./bin/web-ui/         (directory junction, falls back to copy)
+ *   node_modules/@oonacode/win32-x64/build/          ->  ./bin/build/          (native addons, same treatment)
+ *   node_modules/@oonacode/win32-x64/registry.json   ->  ./bin/registry.json   (hard link, falls back to copy)
  *
  * registry.json has to sit beside the LINKED binary, not only in the platform package: a compiled
  * oona.exe finds the provider registry only as `<dir of the executable>/registry.json`
@@ -23,7 +23,8 @@
  * platform package in place at runtime anyway and prints the same hint if nothing is available.
  *
  * Skipped silently when OONACODE_SKIP_POSTINSTALL=1 or when running inside the oonacode monorepo
- * (the platform package there is a skeleton without binaries until the release workflow injects them).
+ * (the platform package there is a skeleton without binaries: the published copy is staged outside the
+ * repo by packaging/scripts/stage-npm.mjs).
  */
 import { createRequire } from 'node:module';
 import fs from 'node:fs';