oonacode 0.3.130 → 0.3.132

package/README.md

@@ -64,5 +64,8 @@ irm https://oonacode.oonak.ai/install.ps1 | iex
 - `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).
 - In the monorepo `optionalDependencies` use `workspace:<version>` so pnpm links the sibling
-  platform package; `packaging/scripts/prepare-npm.mjs` rewrites it to the concrete version right
-  before `npm publish` (npm does not understand the workspace protocol).
+  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
+  `optionalDependencies` are concrete versions and name only the platforms that release built
+  (until 0.3.131 this directory was published as it was, and `npm i -g oonacode` failed with
+  `EUNSUPPORTEDPROTOCOL` — review C18/C26, 2026-09-23).

package/bin/oona.js

@@ -135,6 +135,16 @@ function run() {
   const native = resolveNative();
   const bundled = native ? null : resolveBundledJs();
   if (native) {
+    // A release is packed on Windows, which carries no POSIX mode into the tarball: postinstall
+    // sets the exec bit, and this covers an install whose lifecycle scripts were blocked (pnpm,
+    // bun). Best effort — a tree we may not write reports its own spawn error below.
+    if (!IS_WIN) {
+      try {
+        fs.chmodSync(native.bin, 0o755);
+      } catch {
+        /* not ours to change */
+      }
+    }
     engineEnv(env, [native.dir, __dirname]);
     child = spawn(native.bin, args, { stdio: 'inherit', env, windowsHide: false });
   } else if (bundled) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "oonacode",
-  "version": "0.3.130",
+  "version": "0.3.132",
   "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",
@@ -32,10 +32,9 @@
   ],
   "scripts": {
     "postinstall": "node postinstall.mjs",
-    "test": "node --test test/wrapper.test.js test/packaging-scripts.test.js test/release-feed.test.js test/manifests.test.js test/set-version.test.js"
+    "test": "node --test test/wrapper.test.js test/packaging-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"
   },
   "optionalDependencies": {
-    "@oonacode/win32-x64": "workspace:0.3.130",
-    "@oonacode/linux-x64": "workspace:0.3.130"
+    "@oonacode/win32-x64": "0.3.132"
   }
 }

package/postinstall.mjs

@@ -6,6 +6,13 @@
  *   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`
+ * (host-service provider-service.ts), and the host refuses to start without one. On Linux the
+ * binaries also get their exec bit here — a package packed on Windows carries no POSIX mode, and
+ * an engine that cannot be spawned hangs the SDK instead of failing.
  *
  * `oonaclaude(.exe)` is a byte-for-byte copy of the pinned, UNMODIFIED Claude Code binary from the
  * Claude Agent SDK. OonaCode does not fork or patch it — the filename differs only so it can never be
@@ -39,6 +46,7 @@ const ENGINE_NAME = IS_WIN ? 'oonaclaude.exe' : 'oonaclaude';
 /** Pre-rename filename, still linked when a package published before the rename is installed. */
 const LEGACY_ENGINE_NAME = IS_WIN ? 'claude.exe' : 'claude';
 const LINKED_DIRS = ['web-ui', 'build', 'prebuilds', 'lib'];
+const LINKED_FILES = ['registry.json'];
 
 const log = (msg) => console.log(`[oonacode] ${msg}`);
 const INSTALL_HINT =
@@ -65,6 +73,16 @@ function linkFile(src, dst) {
   }
 }
 
+/** Give a POSIX binary its exec bit; a no-op on Windows and never a failure. */
+function makeExecutable(file) {
+  if (IS_WIN) return;
+  try {
+    fs.chmodSync(file, 0o755);
+  } catch {
+    /* read-only install tree: bin/oona.js reports the spawn error */
+  }
+}
+
 function linkDir(src, dst) {
   fs.rmSync(dst, { recursive: true, force: true });
   try {
@@ -131,6 +149,15 @@ function main() {
     const src = path.join(pkgDir, dir);
     if (fs.existsSync(src)) parts.push(`${dir}/ ${linkDir(src, path.join(binDir, dir))}`);
   }
+  for (const name of LINKED_FILES) {
+    const src = path.join(pkgDir, name);
+    if (fs.existsSync(src)) parts.push(`${name} ${linkFile(src, path.join(binDir, name))}`);
+  }
+  // Both copies: the platform package's is what bin/oona.js runs when this script was skipped.
+  for (const name of [EXE_NAME, engineName].filter(Boolean)) {
+    makeExecutable(path.join(pkgDir, name));
+    makeExecutable(path.join(binDir, name));
+  }
   log(`ready: ${parts.join(', ')} -> ${binDir}`);
 }