@jelou/cli 1.70.0 → 1.71.1

package/bin/jelou

@@ -1,6 +1,7 @@
 #!/usr/bin/env node
 
 const { execFileSync } = require("child_process");
+const fs = require("fs");
 const {
   PLATFORMS,
   platformKey,
@@ -36,9 +37,32 @@ if (!binPath) {
   process.exit(1);
 }
 
+// `platformBinaryPath()` resolves via require.resolve of the package.json, so it
+// returns a path even when the binary file itself has been deleted (the classic
+// antivirus-quarantine case: the package dir survives, the .exe does not). Guard
+// against it explicitly — otherwise execFileSync throws ENOENT and the catch
+// below would exit 0 (see the guard fix), reading as silent success.
+if (!fs.existsSync(binPath)) {
+  console.error(
+    `@jelou/cli: platform binary is missing at\n  ${binPath}\n\n` +
+      `The ${pkg} package is installed but its executable is gone. The most\n` +
+      `common cause is antivirus / endpoint-security software quarantining or\n` +
+      `deleting the unsigned binary. Check your antivirus quarantine, allowlist\n` +
+      `the binary, then reinstall:\n\n` +
+      `  npm uninstall -g @jelou/cli\n` +
+      `  npm install -g @jelou/cli\n\n` +
+      `You can also download a release binary manually from\n` +
+      `https://github.com/JelouLatam/jelou-cli/releases\n`,
+  );
+  process.exit(1);
+}
+
 try {
   execFileSync(binPath, process.argv.slice(2), { stdio: "inherit" });
 } catch (err) {
-  if (err.status !== undefined) process.exit(err.status);
-  throw err;
+  // Only a real child exit carries a numeric err.status. Signal death
+  // (err.status === null, err.signal set) and spawn failures like ENOENT
+  // (err.status === null, err.code === "ENOENT") must NOT map to exit 0.
+  if (typeof err.status === "number") process.exit(err.status);
+  process.exit(1);
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jelou/cli",
-  "version": "1.70.0",
+  "version": "1.71.1",
   "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.70.0",
-    "@jelou/cli-darwin-x64": "1.70.0",
-    "@jelou/cli-linux-x64": "1.70.0",
-    "@jelou/cli-linux-arm64": "1.70.0",
-    "@jelou/cli-win32-x64": "1.70.0"
+    "@jelou/cli-darwin-arm64": "1.71.1",
+    "@jelou/cli-darwin-x64": "1.71.1",
+    "@jelou/cli-linux-x64": "1.71.1",
+    "@jelou/cli-linux-arm64": "1.71.1",
+    "@jelou/cli-win32-x64": "1.71.1"
   },
   "keywords": [
     "jelou",
@@ -58,13 +58,13 @@
   "jelou": {
     "minVersion": "1.65.0",
     "release_notes": {
-      "version": "1.70.0",
-      "date": "2026-07-17",
-      "headline": "`jelou bot list` now uses the v2 bots endpoint ahead of the v1 deprecation, returning every bot in a single response.",
+      "version": "1.71.1",
+      "date": "2026-07-21",
+      "headline": "`jelou project list --json` now reports each project's real workflow count instead of a stale 0.",
       "highlights": [
         {
-          "type": "improved",
-          "text": "`jelou bot list` (and the bot eligibility / provisioning checks that back other commands) now call the `/v2/bots` endpoint instead of the deprecated `/v1/bots`, fetching every bot in one non-paginated response. No change to command usage or output shape — this keeps bot listing working once `/v1/bots` is retired."
+          "type": "fixed",
+          "text": "`jelou project list --json` reports each project's real workflow (skill) count. It previously copied a denormalized field that could read 0 for projects that actually have workflows; `jelou project show` was already correct."
         }
       ]
     }