@jelou/cli 1.150.0 → 1.151.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jelou/cli",
-  "version": "1.150.0",
+  "version": "1.151.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.150.0",
-    "@jelou/cli-darwin-x64": "1.150.0",
-    "@jelou/cli-linux-x64": "1.150.0",
-    "@jelou/cli-linux-arm64": "1.150.0",
-    "@jelou/cli-win32-x64": "1.150.0"
+    "@jelou/cli-darwin-arm64": "1.151.0",
+    "@jelou/cli-darwin-x64": "1.151.0",
+    "@jelou/cli-linux-x64": "1.151.0",
+    "@jelou/cli-linux-arm64": "1.151.0",
+    "@jelou/cli-win32-x64": "1.151.0"
   },
   "keywords": [
     "jelou",
@@ -56,43 +56,23 @@
     "access": "public"
   },
   "jelou": {
-    "minVersion": "1.150.0",
+    "minVersion": "1.151.0",
     "release_notes": {
-      "version": "1.150.0",
+      "version": "1.151.0",
       "date": "2026-09-22",
-      "headline": "New `jelou tool pull --accept-server` ends the deadlock where `tool push` sent you to `tool pull` and `tool pull` refused.",
+      "headline": "The cost report answers in years, and says so plainly when there is nothing worth cutting.",
       "highlights": [
         {
           "type": "new",
-          "text": "`jelou tool pull <slug> --accept-server` takes the server's copy and archives yours under `.jelou/discarded/`. No more copying a file aside, deleting it, and editing `jelou.lock` by hand. It must name its targets, and a tool whose archive cannot be written is left untouched rather than overwritten."
-        },
-        {
-          "type": "new",
-          "text": "The cost report can state what Meta will charge for service messages from 1 October 2026, with the message count the figure was computed over. It is referential — Meta issues the invoice, and the report says so."
-        },
-        {
-          "type": "fixed",
-          "text": "`jelou logs execution <id>` accepts a UUID. It used to refuse one on shape alone, claiming the id was \"a TOOL node's child execution id\" — which was wrong for every parent run, and a UUID's shape cannot tell parent from child. A tool's own run now reads like any other execution."
-        },
-        {
-          "type": "fixed",
-          "text": "The cost report names the flow the traffic actually came from, measured per execution instead of sampled from transcripts. The old sample once blamed a flow holding 1 avoidable message out of 8,056."
+          "text": "The cost report states what the period would cost over a year, beside the window you asked about, and names the days it rests on. A saving of $40 a fortnight is $1,043 a year. Under a week there is no projection: the report says the window was too short rather than multiplying noise."
         },
         {
           "type": "fixed",
-          "text": "`jelou tool push` and `jelou tool pull` now name `--accept-server` when they collide, so the way out is visible at the moment you hit the wall."
+          "text": "A project with nothing to cut gets a verdict, not an empty section. The report says what was checked, over which window, and which counts came back at zero — and tells a clean project apart from a window where the bot never answered, which return identical numbers."
         },
         {
           "type": "fixed",
-          "text": "`jelou graph` resolves a bare slug when exactly one file carries it."
-        },
-        {
-          "type": "fixed",
-          "text": "Assistants no longer ask you to approve the same destructive command twice, and no longer stall on one whose confirmation they were told never to pass."
-        },
-        {
-          "type": "improved",
-          "text": "The `jelou-graph` skill is findable from the words an operator actually uses, not just its command names."
+          "text": "The report keeps its operator line even when the outbound metric returns no operator row. The rule assumed that row always sits beside the bot's; on a bot operators never touched it is absent, not zero, so the line vanished where the rule promised to keep it. Absent now reads as no operator messages."
         }
       ]
     }