@addai/node 0.20.0 → 0.21.0

package/dist/win.d.ts

@@ -28,6 +28,12 @@ export interface CliInvocation {
  * already route spawn errors into a clean per-request failure.
  */
 export declare function resolveCliInvocation(bin: string, args: string[]): CliInvocation;
+/** Parse a package-manager .cmd shim for the `…\node_modules\…js` script it
+ *  executes. Returns the absolute script path or null. Two shim dialects:
+ *  npm's cmd-shim writes `"%dp0%\<rel>.js"` (a variable it SETs earlier);
+ *  pnpm/yarn-classic write `"%~dp0\<rel>.js"` (batch parameter expansion —
+ *  note: no trailing `%`). */
+declare function resolveNpmShimScript(shimPath: string): string | null;
 /**
  * Kill an agent child process. POSIX: SIGINT (graceful — CLIs flush and
  * exit). win32: `taskkill /T /F` — Node's SIGINT emulation is a hard
@@ -65,3 +71,9 @@ export declare function linkOrCopyFile(real: string, dest: string, maxCopyBytes?
 /** Directory link that works unprivileged on win32 ('junction' is ignored
  *  by Node on POSIX, where a normal symlink is created). */
 export declare function linkDir(real: string, dest: string): void;
+/** Exposed for tests only: the shim parsing is pure file-shape logic and is
+ *  worth exercising on any platform, not just on a Windows box. */
+export declare const __testables: {
+    resolveNpmShimScript: typeof resolveNpmShimScript;
+};
+export {};

package/dist/win.js

@@ -60,7 +60,7 @@ var __importStar = (this && this.__importStar) || (function () {
     };
 })();
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.IS_WINDOWS = void 0;
+exports.__testables = exports.IS_WINDOWS = void 0;
 exports.whereLookup = whereLookup;
 exports.npmShimCandidates = npmShimCandidates;
 exports.findCliBinary = findCliBinary;
@@ -212,11 +212,37 @@ function resolveNpmShimScript(shimPath) {
     catch {
         return null;
     }
-    const m = body.match(/"%(?:dp0%|~dp0)[\\/]([^"]+\.(?:m|c)?js)"/i);
-    if (!m)
-        return null;
-    const script = path.join(path.dirname(shimPath), m[1]);
-    return fs.existsSync(script) ? script : null;
+    // Two shim shapes, and for a long time only the first was handled.
+    //
+    //   package bin shim   "%~dp0\..\pkg\dist\cli.js"
+    //   npm's OWN npm.cmd  SET "NPM_CLI_JS=%~dp0\node_modules\npm\bin\npm-cli.js"
+    //
+    // The old pattern required the quote to sit immediately before %~dp0, which
+    // the first shape satisfies and the second never does — after its quote
+    // comes NPM_CLI_JS=. So every package shim resolved and npm.cmd itself did
+    // not, which is precisely the binary the auto-updater has to spawn. The
+    // result was a node that could not update itself on Windows at all: the roll
+    // failed with "could not resolve the node script it wraps" and the machine
+    // stayed on whatever version it was first installed with.
+    //
+    // So: find every %~dp0-relative .js in the file, wherever it sits, and take
+    // the first that is actually on disk. Order matters — npm.cmd names the
+    // local CLI before the global-prefix one, and the local one is the right
+    // answer when both exist.
+    const candidates = [];
+    const re = /%(?:~dp0|dp0%)[\\/]([^"\s]+\.(?:m|c)?js)/gi;
+    for (const m of body.matchAll(re))
+        candidates.push(m[1]);
+    for (const rel of candidates) {
+        // Shims always write backslashes. Split on either separator and re-join
+        // with the platform's, so the same parsing is exercisable off Windows —
+        // path.join treats a backslash as an ordinary character on POSIX, which
+        // would otherwise make every one of these silently unresolvable.
+        const script = path.join(path.dirname(shimPath), ...rel.split(/[\\/]+/));
+        if (fs.existsSync(script))
+            return script;
+    }
+    return null;
 }
 /**
  * Kill an agent child process. POSIX: SIGINT (graceful — CLIs flush and
@@ -315,3 +341,6 @@ function linkDir(real, dest) {
     }
     catch { /* target exists or FS refuses — caller treats as best-effort */ }
 }
+/** Exposed for tests only: the shim parsing is pure file-shape logic and is
+ *  worth exercising on any platform, not just on a Windows box. */
+exports.__testables = { resolveNpmShimScript };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@addai/node",
-  "version": "0.20.0",
+  "version": "0.21.0",
   "description": "Daemon that pairs a machine with your +Ai account and runs Claude / Codex / Kimi / Gemini agents on its behalf. Reachable via Supabase from Vault, Entity Studio, or any other +Ai surface.",
   "license": "MIT",
   "keywords": [