@jelou/cli 1.88.0 → 1.89.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jelou/cli",
-  "version": "1.88.0",
+  "version": "1.89.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.88.0",
-    "@jelou/cli-darwin-x64": "1.88.0",
-    "@jelou/cli-linux-x64": "1.88.0",
-    "@jelou/cli-linux-arm64": "1.88.0",
-    "@jelou/cli-win32-x64": "1.88.0"
+    "@jelou/cli-darwin-arm64": "1.89.0",
+    "@jelou/cli-darwin-x64": "1.89.0",
+    "@jelou/cli-linux-x64": "1.89.0",
+    "@jelou/cli-linux-arm64": "1.89.0",
+    "@jelou/cli-win32-x64": "1.89.0"
   },
   "keywords": [
     "jelou",
@@ -56,47 +56,43 @@
     "access": "public"
   },
   "jelou": {
-    "minVersion": "1.80.0",
+    "minVersion": "1.89.0",
     "release_notes": {
-      "version": "1.88.0",
-      "date": "2026-08-09",
-      "headline": "New `jelou context`, retry-safe database provisioning, and a working `jelou tool` authoring loop.",
+      "version": "1.89.0",
+      "date": "2026-08-10",
+      "headline": "`jelou metrics` now reads your company's whole analytics catalog — ecommerce, payments, voice, biometrics, brain, AI and inbox — instead of seven fixed numbers.",
       "highlights": [
         {
           "type": "new",
-          "text": "`jelou context` — identity, linked project and workflow drift, database inventory with collections, secret and api-key names, the model allowlist, and the node-type digest, all in one call. Replaces the seven-command discovery sequence agents used to run at the start of every build. Sections degrade independently: one that fails is named in `degraded[]` instead of failing the command, and secret values are never emitted."
+          "text": "`jelou metrics list` shows every metric your company can read, live from the platform, with its category and the filters it accepts. `--category ecommerce` narrows it to one area."
         },
         {
           "type": "new",
-          "text": "A validate-on-write hook runs `jelou workflow validate --partial` the moment an agent writes workflow JSON, so diagnostics arrive in the same turn instead of three turns later. Advisory only — it never blocks the write."
+          "text": "`jelou metrics get <key>` fetches any of them and draws it the way it is meant to be read: a card, a line, a KPI grid, a table, a heatmap, a word cloud or a funnel."
         },
         {
-          "type": "improved",
-          "text": "`jelou databases collections create` is now get-or-create. An existing collection whose shape matches is reused and reported with `reused: true`, so a retried build no longer fails on its own earlier progress. A collection that differs is never silently handed back — the command refuses with the exact delta."
-        },
-        {
-          "type": "improved",
-          "text": "`jelou databases api-keys regenerate` now confirms before invalidating a live token. Pass `--yes` in scripts."
+          "type": "new",
+          "text": "`jelou metrics dashboard --template ecommerce` renders a whole board in one command. Templates ship for ecommerce, payments, brain, ai, biometrics and operators; a saved dashboard renders by name."
         },
         {
-          "type": "fixed",
-          "text": "`jelou workflow validate` understands tool files. It no longer flags `$output.set()` inside a tool's CODE node — that is how a tool returns a value — it validates `tools/*.json` alongside `workflows/*.json`, and it runs the real tool rules, so a tool that would fail `jelou tool push` can no longer pass validation first."
+          "type": "new",
+          "text": "`--last 7d|30d|90d|12m` picks a rolling window without spelling out dates."
         },
         {
-          "type": "fixed",
-          "text": "`jelou test tool` is findable. It now leads `jelou test --help` instead of sorting last under a description that mentioned only chat testing."
+          "type": "new",
+          "text": "New filters where the metric supports them: `--bot-id`, `--team-id`, `--provider`, `--currency`, `--environment`, `--type-biometric`, `--skill-name`, `--node-id`, `--skill-id`, `--criterion-name` and `--app-id`. Pass one a metric does not accept and the CLI tells you which ones it does."
         },
         {
-          "type": "fixed",
-          "text": "`jelou databases collections create` rejects a malformed `--field` or `--name` with exit 2 before making any network call, as `--describe` always advertised."
+          "type": "improved",
+          "text": "Metrics no longer need a second set of credentials — they authenticate with the token you already logged in with."
         },
         {
-          "type": "heads_up",
-          "text": "`jelou tool create` now creates SHARED tools by default instead of brain-scoped ones. This is the fix for a new tool vanishing from `jelou tool list` and `jelou tool pull --all` immediately after you created it — those only ever list app-shared tools, and `pull --all` went on to report the new tool as deleted. For the old behavior, pass `--scope BRAIN --brain <id>` explicitly."
+          "type": "improved",
+          "text": "Your agent gets the numbers-with-caveats guidance in the same update: which ecommerce figures are estimates, which lists deliberately do not add up, and how fresh the aggregates are. Run `jelou agent install` after upgrading; skill content does not refresh on its own."
         },
         {
           "type": "heads_up",
-          "text": "`jelou databases api-keys create` now refuses a duplicate name with exit 2 instead of minting another key. A key's token cannot be re-read after creation, so silently \"reusing\" one would hand you a key you cannot store. The error tells you whether the existing key was ever used, so you know if rotating is safe; rotate with `jelou databases api-keys regenerate --yes`."
+          "text": "The seven original metric slugs keep rendering exactly as before. One change: they now reject filter flags they cannot actually send, instead of quietly dropping them and reporting success."
         }
       ]
     }