@jelou/cli 1.80.0 → 1.81.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jelou/cli",
-  "version": "1.80.0",
+  "version": "1.81.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.80.0",
-    "@jelou/cli-darwin-x64": "1.80.0",
-    "@jelou/cli-linux-x64": "1.80.0",
-    "@jelou/cli-linux-arm64": "1.80.0",
-    "@jelou/cli-win32-x64": "1.80.0"
+    "@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"
   },
   "keywords": [
     "jelou",
@@ -58,33 +58,33 @@
   "jelou": {
     "minVersion": "1.80.0",
     "release_notes": {
-      "version": "1.80.0",
-      "date": "2026-08-01",
-      "headline": "`jelou functions deploy` now refuses to deploy a project into the wrong company, and checks your code against the Deno v2 runtime before uploading anything.",
+      "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.",
       "highlights": [
         {
-          "type": "heads_up",
-          "text": "A deploy is now **refused** when the project belongs to a different company than your active profile. `jelou.json` records the owning organization, and a mismatch exits 2 without uploading. Previously the CLI would either create a duplicate function in the wrong company or silently overwrite a different function that happened to share the slug — in both cases reporting success. If you hit the refusal, the error names both organizations; run `jelou auth list` then `jelou auth switch <name>`. To deliberately re-point a project, use `jelou functions init --mode link --force`."
+          "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."
         },
         {
-          "type": "heads_up",
-          "text": "Projects created before this release are stamped on their next successful deploy, so the first deploy after upgrading always goes through."
+          "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": "`jelou functions check` validates a project against the Deno Deploy v2 runtime without touching the network — run it before a deploy or in CI."
+          "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."
         },
         {
-          "type": "new",
-          "text": "`deploy` runs the same checks and stops on anything that would fail at boot, most importantly `Deno.openKv()` at module scope, which v2 rejects because the KV binding is not attached yet. `--dry-run` reports without blocking."
+          "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."
         },
         {
           "type": "fixed",
-          "text": "`jelou functions dev` overwrote an existing `deno.json` instead of merging into it, discarding tasks, lint and compiler options. It now preserves every key, and leaves the file untouched when it cannot parse it."
+          "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."
         },
         {
-          "type": "fixed",
-          "text": "`jelou push` reported `LOCKFILE_DRIFT` on a workflow you had just pulled and barely touched, and `--force` then failed with `POST_PUSH_DIVERGENCE` — the lockfile never refreshed, so every retry repeated it. Workflows that are a project's default entry flow, or that are hidden or carry routing rules, were affected. `push`, `status` and `workflow incoming` now all compare the same shape `pull` writes."
+          "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."
         }
       ]
     }