@jelou/cli 1.86.0 → 1.87.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jelou/cli",
-  "version": "1.86.0",
+  "version": "1.87.1",
   "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.86.0",
-    "@jelou/cli-darwin-x64": "1.86.0",
-    "@jelou/cli-linux-x64": "1.86.0",
-    "@jelou/cli-linux-arm64": "1.86.0",
-    "@jelou/cli-win32-x64": "1.86.0"
+    "@jelou/cli-darwin-arm64": "1.87.1",
+    "@jelou/cli-darwin-x64": "1.87.1",
+    "@jelou/cli-linux-x64": "1.87.1",
+    "@jelou/cli-linux-arm64": "1.87.1",
+    "@jelou/cli-win32-x64": "1.87.1"
   },
   "keywords": [
     "jelou",
@@ -58,37 +58,33 @@
   "jelou": {
     "minVersion": "1.80.0",
     "release_notes": {
-      "version": "1.86.0",
+      "version": "1.87.1",
       "date": "2026-08-07",
-      "headline": "Tools — the reusable subgraphs your workflows call — can now be pulled into the repo, edited as files, pushed, tested, published and versioned from the CLI.",
+      "headline": "Fixed the `jelou tool` workflow end to end — testing, publishing, and canvas layout all work against real tools now.",
       "highlights": [
         {
-          "type": "new",
-          "text": "`jelou tool` manages a tool end to end: `list` / `show` to find one, `pull` to write it to `tools/<slug>.json` as one self-contained file (envelope, inputs, outputs and graph together), `push` to ship your edits back, `publish` to freeze an immutable version, `versions` to see who pins what, and `bump` to repoint the workflows that call it. Envelope and contract editing (`create`, `update`, `clone`, `delete`, `input`, `output`) moved under the same namespace. Tools belong to the **app**, so every project under that app shares them — which is why `jelou pull` and `jelou push` still never touch them and each tool command acts on one named tool at a time."
+          "type": "fixed",
+          "text": "`jelou test tool` now actually runs your tool. Every run against a real tool came back \"returned no output\" because the request never identified an end user."
         },
         {
-          "type": "new",
-          "text": "`jelou test tool <slug>` runs a tool server-side and reports which output fired. Without `--version` it runs the live draft, so you can check an unpublished edit before any caller sees it; a run that ends on a failure branch exits non-zero so CI can gate on it."
+          "type": "fixed",
+          "text": "A run that produces no output now names the node that failed and its error, instead of blaming conversational nodes your tool does not have."
         },
         {
-          "type": "new",
-          "text": "`jelou status` grows a tools section once the lockfile tracks tools — graph drift, contract drift, read-only markers and callers whose pinned version no longer exists. `jelou push` warns, and never fails, when `tools/*.json` has edits you have not shipped."
+          "type": "fixed",
+          "text": "`jelou tool publish` works on version labels you have not used before. Those previously failed with a server error."
         },
         {
-          "type": "new",
-          "text": "`jelou workflow validate` checks tool files: one START node, every END resolving to a declared output, no conversational step inside a tool graph (a tool run has no bot or conversation, so those park it forever), and no tool calling itself."
+          "type": "fixed",
+          "text": "`jelou tool push` lays the canvas out left to right instead of shipping the coordinates in your file, so a pushed tool opens readable in the editor. Nodes you positioned yourself are still never moved."
         },
         {
-          "type": "heads_up",
-          "text": "Publishing a tool does not move its callers. Each `TOOL` step runs the version string pinned in its own configuration, so a new version reaches nobody until `jelou tool bump <slug> --to <version>` rewrites those pins and an ordinary `jelou push` ships the rewritten workflow files."
-        },
-        {
-          "type": "heads_up",
-          "text": "`jelou.lock` is now version 3. An older CLI reads a v3 lockfile fine, but the moment it rewrites one — any `pull` or `push` — it silently drops the `tools` map. Everything else survives. Recover by running `jelou tool pull` again on the up-to-date CLI; nothing on the server is affected. If your team shares a repo, upgrade everyone before pulling tools into it."
+          "type": "new",
+          "text": "`jelou test tool --user-id <id>` runs consecutive tests as the same end user. Without it every run gets a fresh one, so runs no longer leak state into each other."
         },
         {
           "type": "heads_up",
-          "text": "`jelou workflow tool ...` is now a hidden alias for `jelou tool ...` and will be removed in a future release. Existing scripts keep working today; move them to the short form."
+          "text": "The bundled tool-authoring guide was wrong about how data moves through a tool — it said to read inputs from `$memory` instead of `$input` / `$context` / `$output`. Run `jelou agent install` after upgrading; skill content does not refresh on its own."
         }
       ]
     }