@jelou/cli 1.91.0 → 1.92.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jelou/cli",
-  "version": "1.91.0",
+  "version": "1.92.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.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"
+    "@jelou/cli-darwin-arm64": "1.92.1",
+    "@jelou/cli-darwin-x64": "1.92.1",
+    "@jelou/cli-linux-x64": "1.92.1",
+    "@jelou/cli-linux-arm64": "1.92.1",
+    "@jelou/cli-win32-x64": "1.92.1"
   },
   "keywords": [
     "jelou",
@@ -58,57 +58,25 @@
   "jelou": {
     "minVersion": "1.89.0",
     "release_notes": {
-      "version": "1.91.0",
-      "date": "2026-08-10",
-      "headline": "Thirteen findings from a QA pass over `jelou tool`. The common thread: the CLI knew what went wrong and reported something else.",
+      "version": "1.92.1",
+      "date": "2026-08-12",
+      "headline": "`jelou channels flows` works — it never could authorize the provider listing before, and it now returns the Meta flow id a Flow step actually needs.",
       "highlights": [
-        {
-          "type": "new",
-          "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": "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": "`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": "`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."
+          "text": "`jelou channels flows <botId>` now lists a bot's WhatsApp Flows. It previously always failed with \"the Flows listing could not be authorized\", because it asked the wrong host with the wrong credential. It now reads the provider listing the same way `jelou channels list` reads channels."
         },
         {
           "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."
+          "text": "The listing returns each Flow's provider id — the value a WhatsApp Flow step has to open — instead of an internal row id. A Flow step authored from the old output pointed at an id the provider does not know, and broke when the step ran."
         },
         {
           "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."
+          "text": "A bot with no Flows now reports exactly that, instead of failing as though the provider had answered with something unreadable."
         },
         {
           "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."
+          "text": "A bot is found even when the company has more channels than fit in one page. Companies past 50 WhatsApp channels were told the bot had no channel connected when it did."
         }
       ]
     }