@jelou/cli 1.92.1 → 1.94.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jelou/cli",
-  "version": "1.92.1",
+  "version": "1.94.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.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"
+    "@jelou/cli-darwin-arm64": "1.94.0",
+    "@jelou/cli-darwin-x64": "1.94.0",
+    "@jelou/cli-linux-x64": "1.94.0",
+    "@jelou/cli-linux-arm64": "1.94.0",
+    "@jelou/cli-win32-x64": "1.94.0"
   },
   "keywords": [
     "jelou",
@@ -56,27 +56,27 @@
     "access": "public"
   },
   "jelou": {
-    "minVersion": "1.89.0",
+    "minVersion": "1.94.0",
     "release_notes": {
-      "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.",
+      "version": "1.94.0",
+      "date": "2026-08-13",
+      "headline": "WhatsApp Flow screens are now readable from the CLI, and `jelou tool push` no longer leaves a tool that pushes clean but can never return output.",
       "highlights": [
         {
-          "type": "fixed",
-          "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": "new",
+          "text": "`jelou channels flows <botId> --screens` returns each Flow's screens, ids and fields, so you can point a Flow node at a real screen id without leaving the CLI. Flows past the summary cap now report how many screens were left out instead of dropping them silently."
         },
         {
           "type": "fixed",
-          "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."
+          "text": "`jelou tool push` no longer leaves END nodes bound to an output the server does not have. A tool file carrying output ids the server never minted pushed clean, then returned nothing on every run. Push now adopts the server's id on the output and every END that selects it."
         },
         {
           "type": "fixed",
-          "text": "A bot with no Flows now reports exactly that, instead of failing as though the provider had answered with something unreadable."
+          "text": "`jelou test tool` blamed a no-output run on never reaching an END node, even when an END ran fine but selected a missing output. It now names both causes and points at `jelou tool show` to compare each END's `outputId`."
         },
         {
-          "type": "fixed",
-          "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."
+          "type": "heads_up",
+          "text": "Pushing a workflow now fails if a WhatsApp Flow node in `navigate` mode has no `parameters.flow_action_payload.screen`. Get screen ids with `jelou channels flows <botId> --screens` and author the screen's `id`, or set `flow_action: \"data_exchange\"`."
         }
       ]
     }