@jelou/cli 1.108.1 → 1.109.0

package/bin/postinstall.js

@@ -9,8 +9,15 @@
 //    cold-start) with a relative symlink to the platform binary itself.
 //    When npm wires `<global>/bin/jelou` -> `<wrapper>/bin/jelou`, the
 //    chain now resolves straight to the native binary, no node hop.
+// 3. Record where that shim is, and what it points at, in
+//    `~/.jelou/install-manifest.json`. The CLI cannot rediscover this at
+//    runtime: `Deno.execPath()` returns the invoked path on macOS and the
+//    resolved one on Linux, so walking up to node_modules works on one and
+//    not the other. Writing it down here is the only reliable source.
+//    Best-effort — a manifest failure must never fail an install.
 
 const fs = require("fs");
+const os = require("os");
 const path = require("path");
 const {
   PLATFORMS,
@@ -50,6 +57,71 @@ if (!fs.existsSync(binPath)) {
   process.exit(1);
 }
 
+// --- install manifest ---
+// Keyed by shim path, and merged rather than replaced: one machine can carry
+// several independent global installs (e.g. a Homebrew node prefix and a
+// user-owned ~/.local one), each with its own postinstall. A single-record
+// manifest would let the last install to run claim a shim it does not own.
+function manifestPath() {
+  const home = os.homedir();
+  return home ? path.join(home, ".jelou", "install-manifest.json") : null;
+}
+
+function readManifest(file) {
+  try {
+    const parsed = JSON.parse(fs.readFileSync(file, "utf8"));
+    if (parsed && typeof parsed === "object" && parsed.installs) return parsed;
+  } catch (_) {
+    // Missing or corrupt — start fresh rather than refusing to install.
+  }
+  return { version: 1, installs: {} };
+}
+
+function recordManifest(shimKind) {
+  const file = manifestPath();
+  if (!file) return;
+  try {
+    let wrapperVersion = null;
+    try {
+      wrapperVersion = require("../package.json").version || null;
+    } catch (_) {
+      // Version is informational; a missing one must not skip the manifest.
+    }
+
+    const manifest = readManifest(file);
+    manifest.version = 1;
+
+    // Drop entries whose shim is gone (uninstalled prefix), but never touch a
+    // live sibling install. lstat, not existsSync: existsSync follows the
+    // link, so a sibling whose target is momentarily missing — that prefix
+    // running its own install — would look gone and be pruned.
+    for (const key of Object.keys(manifest.installs)) {
+      if (key === shimPath) continue;
+      try {
+        fs.lstatSync(key);
+      } catch {
+        delete manifest.installs[key];
+      }
+    }
+
+    manifest.installs[shimPath] = {
+      shimKind: shimKind,
+      baselineTarget: relativeTarget,
+      baselineBinary: binPath,
+      version: wrapperVersion,
+      writtenAt: new Date().toISOString(),
+    };
+
+    fs.mkdirSync(path.dirname(file), { recursive: true });
+    const tmp = file + ".tmp-" + process.pid;
+    fs.writeFileSync(tmp, JSON.stringify(manifest, null, 2) + "\n");
+    fs.renameSync(tmp, file);
+  } catch (_) {
+    // Best-effort by design. Losing the manifest only disables background
+    // updates; failing the install here would be far worse.
+  }
+}
+
 // --- fast-shim rewrite (Unix only for now) ---
 // On Windows npm generates `.cmd` and `.ps1` shims that hardcode
 // `node "<wrapper>/bin/jelou"`; replacing the wrapper script doesn't
@@ -71,28 +143,51 @@ const relativeTarget = path.relative(wrapperBin, binPath);
 try {
   const stat = fs.lstatSync(shimPath);
   if (stat.isSymbolicLink() && fs.readlinkSync(shimPath) === relativeTarget) {
+    // The shim is already right, but the manifest still has to be refreshed:
+    // relativeTarget is identical across versions, so this branch is the one
+    // taken on every ordinary upgrade.
+    recordManifest("symlink");
     process.exit(0);
   }
 } catch (_) {
   // shim not present yet — fine, we'll create it.
 }
 
-try {
-  fs.rmSync(shimPath, { force: true });
-} catch (_) {
-  // nothing to remove
+// Write through a tmp sibling + rename so the shim is never briefly absent.
+// The old rmSync-then-symlinkSync left a window where `<wrapper>/bin/jelou`
+// did not exist, and a concurrent `jelou` invocation got ENOENT. rename(2)
+// is atomic, so a reader sees the old shim or the new one, never neither.
+const tmpPath = shimPath + ".tmp-" + process.pid;
+
+function swapIn(write) {
+  try {
+    fs.rmSync(tmpPath, { force: true });
+  } catch (_) {
+    // nothing to remove
+  }
+  write(tmpPath);
+  fs.renameSync(tmpPath, shimPath);
 }
 
+let shimKind;
 try {
-  fs.symlinkSync(relativeTarget, shimPath);
-  process.exit(0);
+  swapIn((p) => fs.symlinkSync(relativeTarget, p));
+  shimKind = "symlink";
 } catch (err) {
   // EPERM (Windows w/o developer mode), EXDEV (cross-device install),
   // EROFS (read-only FS in some sandboxes). Fall back to a tiny shell
   // wrapper. Adds ~1-3ms vs ~0ms for symlink, but still much better than
   // the 20ms node-boot hop the wrapper script costs.
+  try {
+    fs.rmSync(tmpPath, { force: true });
+  } catch (_) {
+    // nothing to remove
+  }
   const safeTarget = relativeTarget.replace(/(["\\$`])/g, "\\$1");
   const shell = `#!/bin/sh\nexec "$(dirname "$0")/${safeTarget}" "$@"\n`;
-  fs.writeFileSync(shimPath, shell, { mode: 0o755 });
-  process.exit(0);
+  swapIn((p) => fs.writeFileSync(p, shell, { mode: 0o755 }));
+  shimKind = "shell";
 }
+
+recordManifest(shimKind);
+process.exit(0);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jelou/cli",
-  "version": "1.108.1",
+  "version": "1.109.0",
   "description": "Build AI agents on the Jelou platform — from your terminal or your AI editor.",
   "author": "Jelou Inc. (https://jelou.ai)",
   "license": "SEE LICENSE IN LICENSE",
@@ -23,11 +23,11 @@
     "THIRD_PARTY_NOTICES.md"
   ],
   "optionalDependencies": {
-    "@jelou/cli-darwin-arm64": "1.108.1",
-    "@jelou/cli-darwin-x64": "1.108.1",
-    "@jelou/cli-linux-x64": "1.108.1",
-    "@jelou/cli-linux-arm64": "1.108.1",
-    "@jelou/cli-win32-x64": "1.108.1"
+    "@jelou/cli-darwin-arm64": "1.109.0",
+    "@jelou/cli-darwin-x64": "1.109.0",
+    "@jelou/cli-linux-x64": "1.109.0",
+    "@jelou/cli-linux-arm64": "1.109.0",
+    "@jelou/cli-win32-x64": "1.109.0"
   },
   "keywords": [
     "jelou",
@@ -58,21 +58,29 @@
   "jelou": {
     "minVersion": "1.100.2",
     "release_notes": {
-      "version": "1.108.1",
-      "date": "2026-09-02",
-      "headline": "Marketplace nodes (biometría, payments) no longer render as \"Configuración incompleta\" in Studio.",
+      "version": "1.109.0",
+      "date": "2026-09-03",
+      "headline": "Updates now install themselves in the background — no more `npm install -g` after every release.",
       "highlights": [
         {
-          "type": "fixed",
-          "text": "Biometría and payment nodes created by `jelou push` no longer render in Studio with \"Configuración incompleta. Revisa los campos del nodo.\" The nodes always ran correctly — only the canvas warning was wrong."
+          "type": "new",
+          "text": "The CLI keeps itself current on its own. When a newer release exists, it downloads and activates in the background after your command finishes; the next `jelou` you run is already the new version and tells you so in one line. No prompt, and no second command to refresh skills — those come with it."
         },
         {
-          "type": "fixed",
-          "text": "`jelou push` now repairs marketplace nodes already saved without that flag. Previously no edit to the local file could fix them: the push diff ignored the field and reported nothing to do."
+          "type": "new",
+          "text": "`jelou update --rollback` undoes a background update, putting the previously installed binary back and pausing background updates for 30 days."
         },
         {
           "type": "improved",
-          "text": "The workflow build lint now fails on a marketplace node missing `isValidConfig`, so agents write it up front instead of shipping a node Studio flags."
+          "text": "Agents stop being told to run `npm install -g` for a release the CLI is already installing on its own."
+        },
+        {
+          "type": "heads_up",
+          "text": "Your `jelou` binary can now change without asking. It only ever moves forward to the version already published on npm — the same one the old prompt asked you to install. Set `JELOU_NO_UPDATE_CHECK=1` to turn it off entirely."
+        },
+        {
+          "type": "heads_up",
+          "text": "Background updates need macOS or Linux, an npm install, and a prefix you own. Windows, `sudo`-installed prefixes, and non-npm installs keep the previous behavior and simply tell you an update is available."
         }
       ]
     }