@jelou/cli 1.122.0 → 1.122.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jelou/cli",
-  "version": "1.122.0",
+  "version": "1.122.2",
   "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.2",
+    "@jelou/cli-darwin-x64": "1.122.2",
+    "@jelou/cli-linux-x64": "1.122.2",
+    "@jelou/cli-linux-arm64": "1.122.2",
+    "@jelou/cli-win32-x64": "1.122.2"
   },
   "keywords": [
     "jelou",
@@ -58,25 +58,21 @@
   "jelou": {
     "minVersion": "1.100.2",
     "release_notes": {
-      "version": "1.122.0",
+      "version": "1.122.2",
       "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 help text and errors that called a branch checkout read-only when `jelou push` publishes from one.",
       "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 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."
+          "text": "`jelou pull --branch --help` no longer says `push`, `lockfile refresh` and `workflow adopt` refuse until you go back to the draft. All three work on a branch — and the same paragraph already said the next push writes the branch's first commit."
         },
         {
           "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."
+          "text": "Pulling a branch that leaves your edited files untouched now names `jelou push` as the way to publish them, instead of saying a branch checkout is read-only and the edits are stuck there."
         },
         {
           "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."
+          "text": "The refusal for a command that genuinely needs the draft now says which write is impossible instead of calling the whole checkout read-only, and a branch with nothing published tells you how to write its first commit."
         }
       ]
     }