@jelou/cli 1.81.0 → 1.82.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jelou/cli",
-  "version": "1.81.0",
+  "version": "1.82.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.81.0",
-    "@jelou/cli-darwin-x64": "1.81.0",
-    "@jelou/cli-linux-x64": "1.81.0",
-    "@jelou/cli-linux-arm64": "1.81.0",
-    "@jelou/cli-win32-x64": "1.81.0"
+    "@jelou/cli-darwin-arm64": "1.82.0",
+    "@jelou/cli-darwin-x64": "1.82.0",
+    "@jelou/cli-linux-x64": "1.82.0",
+    "@jelou/cli-linux-arm64": "1.82.0",
+    "@jelou/cli-win32-x64": "1.82.0"
   },
   "keywords": [
     "jelou",
@@ -58,33 +58,33 @@
   "jelou": {
     "minVersion": "1.80.0",
     "release_notes": {
-      "version": "1.81.0",
-      "date": "2026-08-03",
-      "headline": "Broken WhatsApp nodes are now caught before they ship: a Flow step must point at a Flow that really exists, and contact cards finally get validated.",
+      "version": "1.82.0",
+      "date": "2026-08-04",
+      "headline": "`jelou models list` now shows what each model costs, and `push` warns before a step runs on a model that cannot read the images or PDFs it will be sent.",
       "highlights": [
         {
           "type": "new",
-          "text": "`jelou channels flows <bot-id>` lists the WhatsApp Flows a bot's provider actually holds. It exits `NO_WHATSAPP_FLOWS` when there are none and `WHATSAPP_FLOWS_UNAVAILABLE` when the provider has no Flows API or the listing cannot be authorized — so \"none exist\" and \"could not check\" never look alike."
+          "text": "`jelou models list` shows what each model costs. Two new columns (`In $/M`, `Out $/M`), plus `--sort catalog|name|input-cost|output-cost` and `--max-input-cost` / `--max-output-cost` to find the cheapest model that still does what the step needs. Ordering is unchanged unless you ask for it, and models with no published price are always listed last and never removed by a cost filter — an unknown price is not evidence of being expensive."
         },
         {
-          "type": "fixed",
-          "text": "A WhatsApp Flow step authored without a real `flow_id` — or with the one from the docs — now fails validation instead of pushing clean and failing to render when the message is sent."
+          "type": "new",
+          "text": "`push` now warns when a step is set up to receive images or PDFs but the model it runs cannot read them, naming the node and the model. The cheapest models are often text-only, and that pairing used to publish cleanly and then quietly stop answering those messages. It is a warning, not a block. Where the catalog does not say whether a model supports an input, you get a distinct \"unknown — confirm before relying on it\" warning rather than silence."
         },
         {
           "type": "fixed",
-          "text": "Flow nodes missing `text`, `title` or `parameters.flow_cta` are now validated on the pulled-workflow path too, not only on locally authored drafts."
+          "text": "`push` no longer reports `POST_PUSH_DIVERGENCE` for a contacts card. The server mints its own ids for the phone, email, address and URL rows, and a push that had written correctly compared them against your id-less local file, called it a divergence, and withheld the lockfile refresh — leaving you re-pushing a workflow that was already saved. Real content changes, like an edited phone number, are still detected."
         },
         {
           "type": "fixed",
-          "text": "Contact cards were invisible to the CLI: `contacts` messages resolved to no known node kind, so nothing validated them and nothing filled the row ids the editor keys its phone/email/address/url lists by. Cards now get those ids, keep any the editor already assigned, and a card with no first name is rejected."
+          "text": "Workflows that read or write Datum records now install correctly in another company. The credential examples taught an arbitrary secret name, and a template install only rewrites a Datum credential when the name starts with `DATUM_APIKEY` — so installs stopped on a Credentials Required card asking for a token the installing user could not get. The examples now require `DATUM_APIKEY_<SLUG_UPPER>`, derived from the database slug."
         },
         {
           "type": "fixed",
-          "text": "`jelou models list` and `jelou models show` reported wholesale model prices rather than what your company is actually charged. The cached catalog is now keyed per company, so two companies driven from one machine can no longer read each other's rates."
+          "text": "`jelou models list --capability <bogus>` exited 1 while `--describe` advertised 2. Both it and the new `--sort` now exit 2 with `INPUT_ERROR`."
         },
         {
-          "type": "heads_up",
-          "text": "Existing installs keep their old agent skill files. Run `jelou agent install` to pick up the new build guidance — an agent adding a Flow step now checks which Flows exist and asks you which one to use, instead of inventing an id."
+          "type": "fixed",
+          "text": "`--describe` no longer publishes a hardcoded provider list for `models list --provider`. Providers are server-side data and the list had gone stale, so an agent reading it would treat valid providers as invalid."
         }
       ]
     }