@jelou/cli 1.84.0 → 1.85.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jelou/cli",
-  "version": "1.84.0",
+  "version": "1.85.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.84.0",
-    "@jelou/cli-darwin-x64": "1.84.0",
-    "@jelou/cli-linux-x64": "1.84.0",
-    "@jelou/cli-linux-arm64": "1.84.0",
-    "@jelou/cli-win32-x64": "1.84.0"
+    "@jelou/cli-darwin-arm64": "1.85.0",
+    "@jelou/cli-darwin-x64": "1.85.0",
+    "@jelou/cli-linux-x64": "1.85.0",
+    "@jelou/cli-linux-arm64": "1.85.0",
+    "@jelou/cli-win32-x64": "1.85.0"
   },
   "keywords": [
     "jelou",
@@ -58,29 +58,13 @@
   "jelou": {
     "minVersion": "1.80.0",
     "release_notes": {
-      "version": "1.84.0",
-      "date": "2026-08-06",
-      "headline": "Workflows are now validated against the channel they run on — a WhatsApp-only step fails the push.",
+      "version": "1.85.0",
+      "date": "2026-08-07",
+      "headline": "`jelou workflow validate` now catches image and PDF model mismatches before you push, instead of at the gate.",
       "highlights": [
         {
-          "type": "new",
-          "text": "`push` and `jelou workflow validate` now check a workflow against the channel it runs on. A WhatsApp-only construct — a Flow step or an HSM template — on a web, Instagram or Telegram workflow is an error that blocks the push, instead of publishing cleanly and arriving as a node Studio paints red. Studio product choices, such as web chat not rendering a list, come through as warnings that do not block. Channel types the platform has no restrictions for are skipped entirely, so nothing is penalised for rules that do not apply to it. `validate` reads the channel from the workflow's filename, `push` from the lockfile entry."
-        },
-        {
-          "type": "new",
-          "text": "`jelou channels flows <botId>` refuses with `WHATSAPP_NUMBER_REQUIRED` (exit 4) when the bot has no WhatsApp channel connected, naming the channel as the blocker. An empty Flows list used to look identical to a missing channel, so a Flow step could be authored — with an invented body — on a project that had no WhatsApp at all. If the channels lookup itself fails the command still proceeds to the Flows listing, so an outage cannot invent a blocker."
-        },
-        {
-          "type": "fixed",
-          "text": "`pull` writes a workflow's own name and description into the file. Both live on the skill, not the workflow, so a pulled file never expressed them — the router gate then warned the description was empty, an agent hand-wrote one to satisfy it, and because the server-compare form could not see that text every subsequent `push` emitted a phantom skill patch and the entry never reconciled. That is the \"node deletion does not persist\" report: permanent `local_only` drift and a divergence warning on a push that had actually succeeded. Both sides of the comparison now agree, an empty name is treated as unexpressed rather than as an instruction to blank it in production, and files pulled by an older CLI are still recognised."
-        },
-        {
-          "type": "fixed",
-          "text": "The workflow build and test skills no longer show you their internal wording helper's failures. A summary turn could end with \"The wording helper timed out; per its contract I'll apply the voice rules directly\" — the helper's documentation had literally told the agent to surface that. The reply is now the finished prose and nothing else. Its budgets were also cut so the deterministic fallback always wins: worst case drops from about 42s to 12s."
-        },
-        {
-          "type": "fixed",
-          "text": "`jelou channels list --type <type>` filters on the server. The type was applied only to the page already fetched, so a filtered list could come back short — or empty — while matching channels sat on later pages, and the reported totals described the unfiltered set. `--type Web` maps to the upstream `Widget` spelling."
+          "type": "improved",
+          "text": "`jelou workflow validate` now reports the same image/PDF capability warning that `push` does, so a step configured to receive photos on a text-only model is caught before you push rather than at the gate. Works for both JSON and TypeScript sources. The catalog lookup is best-effort: when it cannot be reached the check is skipped silently rather than reporting every model as unverifiable, and it no longer prints a catalog warning on offline runs."
         }
       ]
     }