@jelou/cli 1.122.0 → 1.122.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jelou/cli",
-  "version": "1.122.0",
+  "version": "1.122.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.122.0",
-    "@jelou/cli-darwin-x64": "1.122.0",
-    "@jelou/cli-linux-x64": "1.122.0",
-    "@jelou/cli-linux-arm64": "1.122.0",
-    "@jelou/cli-win32-x64": "1.122.0"
+    "@jelou/cli-darwin-arm64": "1.122.1",
+    "@jelou/cli-darwin-x64": "1.122.1",
+    "@jelou/cli-linux-x64": "1.122.1",
+    "@jelou/cli-linux-arm64": "1.122.1",
+    "@jelou/cli-win32-x64": "1.122.1"
   },
   "keywords": [
     "jelou",
@@ -58,25 +58,29 @@
   "jelou": {
     "minVersion": "1.100.2",
     "release_notes": {
-      "version": "1.122.0",
+      "version": "1.122.1",
       "date": "2026-09-09",
-      "headline": "Phone capture with \"Solicitar contacto\" is now validated end to end, and `jelou channels show` reports the provider behind a WhatsApp number.",
+      "headline": "Fixed `jelou workflow evaluate`, and corrected what the bundled skills teach about AI step history.",
       "highlights": [
         {
-          "type": "new",
-          "text": "`jelou channels show` now reports `provider`, the vendor behind the channel. On WhatsApp it decides whether a `carousel` or `cta_url` message can actually be delivered — the channel type alone does not tell you."
+          "type": "fixed",
+          "text": "`jelou workflow evaluate` returns a routing verdict again instead of failing on every invocation. It now asks for `--expected` up front rather than spending a call to come back with a validation error that named no field."
         },
         {
-          "type": "fixed",
-          "text": "`jelou workflow validate` now catches a blocking contact request that would strand the conversation. It requires both the `default` and `expire` branches and rejects `exit`, which never fires on that step."
+          "type": "improved",
+          "text": "New AI steps no longer start with conversation history seeding switched on. It replayed the person's previous conversation into a new one, so a bot could answer one customer with another's details."
         },
         {
-          "type": "fixed",
-          "text": "The `CHANNEL_MESSAGE` spec documents the retry message (`settings.optionNotFoundMessage`) and how to read the captured number: it arrives as `$message.contacts[0]` and is never stored in memory."
+          "type": "improved",
+          "text": "The workflow-authoring skills now describe how an AI step really behaves: which menu the platform picks from your option count, the three ways an options list silently degrades to plain text while reporting success, and the runtime limits no prompt can fix."
         },
         {
-          "type": "fixed",
-          "text": "The cost review no longer extrapolates a spend total from a handful of sampled conversations, no longer prints a currency figure it has no rate card for, and no longer leaves operator messages out of the volume it reports."
+          "type": "improved",
+          "text": "Tool-authoring guidance covers the contract a model reads, not just the graph: keep required fields to what the tool cannot run without, since a required field the user has not given leaves the model no move but to invent it."
+        },
+        {
+          "type": "heads_up",
+          "text": "`jelou workflow evaluate` now requires `--expected <skillId>`. Nothing is lost by naming one: every result still reports the workflow the router picked and the full shortlist, whatever the match says."
         }
       ]
     }