@jelou/cli 1.90.0 → 1.91.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jelou/cli",
-  "version": "1.90.0",
+  "version": "1.91.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.90.0",
-    "@jelou/cli-darwin-x64": "1.90.0",
-    "@jelou/cli-linux-x64": "1.90.0",
-    "@jelou/cli-linux-arm64": "1.90.0",
-    "@jelou/cli-win32-x64": "1.90.0"
+    "@jelou/cli-darwin-arm64": "1.91.0",
+    "@jelou/cli-darwin-x64": "1.91.0",
+    "@jelou/cli-linux-x64": "1.91.0",
+    "@jelou/cli-linux-arm64": "1.91.0",
+    "@jelou/cli-win32-x64": "1.91.0"
   },
   "keywords": [
     "jelou",
@@ -58,25 +58,57 @@
   "jelou": {
     "minVersion": "1.89.0",
     "release_notes": {
-      "version": "1.90.0",
+      "version": "1.91.0",
       "date": "2026-08-10",
-      "headline": "Facebook and Instagram: page ids, the comments inbox, and why a connected page stays silent.",
+      "headline": "Thirteen findings from a QA pass over `jelou tool`. The common thread: the CLI knew what went wrong and reported something else.",
       "highlights": [
         {
           "type": "new",
-          "text": "`jelou channels list --type Facebook_Feed` (and `Instagram_Feed`) reaches the page comments inbox, which was previously invisible to the CLI. The filter is exact: `--type Facebook` stays Messenger DMs only."
+          "text": "`jelou tool unpublish <tool-id> <version>` removes one published version. This is the prerequisite for `jelou tool delete`, which the server refuses while any published version survives — and now says so."
         },
         {
-          "type": "new",
-          "text": "`jelou channels show` prints the Meta page id and a link to the page for Facebook and Instagram channels, mirroring the WhatsApp phone block. It is also on the JSON envelope as `pageId`."
+          "type": "improved",
+          "text": "Every 422 from the workflows API reports its real reason. The server buries it behind a fixed \"Unprocessable entity\", which is what you used to see for every failure, on every tool command."
+        },
+        {
+          "type": "improved",
+          "text": "`jelou tool show` accepts any slug `jelou tool list` prints, with no linked project — and reports a slug for a tool looked up by numeric id instead of null. A slug is derived from the tool name by the CLI; the server has no such field."
         },
         {
           "type": "improved",
-          "text": "Your agent now knows that connecting a Facebook page is only half the job: each skill needs its own Facebook channel entry, added in Studio, or the engine finds no workflow for that traffic and nothing replies. The skills also stop suggesting `jelou channels create --type whatsapp`, which the CLI has never accepted. Run `jelou agent install` after upgrading; skill content does not refresh on its own."
+          "text": "`jelou test tool` refuses a missing required input with exit 2 before the request goes out. The server answers a missing input with 500, which classified as retryable — so an agent would retry a call that could never succeed."
         },
         {
           "type": "improved",
-          "text": "The workflow-building skill no longer claims to be WhatsApp-only. It now says what is actually true — one workflow per channel, and the button and list caps it quotes are WhatsApp's, not every channel's."
+          "text": "`jelou test tool` distinguishes its three failures by code: TOOL_FAILED_OUTPUT (the graph fired a FAILED output on purpose), TOOL_NODE_FAILED (a node threw), TOOL_PARKED (no output, no failed node). Exit codes are unchanged."
+        },
+        {
+          "type": "improved",
+          "text": "A parked tool run now names the async TOOL node as a cause: with the `brain_async_tool_node` flag on, a nested TOOL node suspends by default and the parent never sees a result. Set \"async\": false to force the synchronous path."
+        },
+        {
+          "type": "fixed",
+          "text": "`--json` and `--agent` survive an argument error. A missing argument used to produce colored help on stdout and no error envelope at all."
+        },
+        {
+          "type": "fixed",
+          "text": "`jelou tool input|output add|update|delete` keep tools/<slug>.json and the lockfile in sync. They wrote only to the server, so the next `jelou tool push` deleted the fields you had just added."
+        },
+        {
+          "type": "fixed",
+          "text": "Push conflict diagnosis names the half that actually moved. A rename was reported as a contract change, sending authors hunting for input/output edits that never happened."
+        },
+        {
+          "type": "fixed",
+          "text": "`jelou workflow node-spec` tells a real node type with no authoring spec card apart from one that does not exist. PMA is a real node type — it is banned inside tools for a reason, and the command implied it was fictional."
+        },
+        {
+          "type": "fixed",
+          "text": "`jelou tool pull` names the scopes it searched. Only SHARED and PURCHASED tools are pullable; a BRAIN- or marketplace-scoped tool is absent from that catalog while being perfectly real."
+        },
+        {
+          "type": "heads_up",
+          "text": "`jelou tool clone` still cannot clone. The server's clone endpoint scopes its lookup by a parameter its own route never provides, so it returns \"not found\" for every tool id. The CLI now confirms the tool is reachable and tells you the endpoint is broken, with the manual workaround, instead of leaving you hunting for the right id."
         }
       ]
     }