@jelou/cli 3.12.1 → 3.13.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jelou/cli",
-  "version": "3.12.1",
+  "version": "3.13.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": "3.12.1",
-    "@jelou/cli-darwin-x64": "3.12.1",
-    "@jelou/cli-linux-x64": "3.12.1",
-    "@jelou/cli-linux-arm64": "3.12.1",
-    "@jelou/cli-win32-x64": "3.12.1"
+    "@jelou/cli-darwin-arm64": "3.13.0",
+    "@jelou/cli-darwin-x64": "3.13.0",
+    "@jelou/cli-linux-x64": "3.13.0",
+    "@jelou/cli-linux-arm64": "3.13.0",
+    "@jelou/cli-win32-x64": "3.13.0"
   },
   "keywords": [
     "jelou",
@@ -58,29 +58,33 @@
   "jelou": {
     "minVersion": "3.4.0",
     "release_notes": {
-      "version": "3.12.1",
-      "date": "2026-10-02",
-      "headline": "`jelou marketplace list --category payments` finds the connected payment gateways, and `jelou tool show 6177` works for every company.",
+      "version": "3.13.0",
+      "date": "2026-10-03",
+      "headline": "`jelou marketplace inspect` now returns everything an app needs to become a workflow node, so builds find integrations from what you have installed instead of guessing tool ids.",
       "highlights": [
         {
           "type": "new",
-          "text": "`jelou marketplace list --category <id|slug|name|payments>` lists one category's apps, with `enabled` on each. With `payments`, each app also says `payment_gateway: true|false`."
+          "text": "`jelou marketplace inspect <slug> --agent` returns `node_path` (`native` or `external`) and `wraps[]` with every TOOL or SKILL the app wraps, including its inputs, outputs and version. Use `--installation <id>` when the app is installed more than once."
         },
         {
-          "type": "improved",
-          "text": "`jelou workflow node-spec --types` without `--knowledge-phase` uses the offline `authoring` phase instead of failing. Unknown types point at the payment and KYC MCP recipes."
+          "type": "new",
+          "text": "`jelou tool show <id> --app <slug>` shows a tool only if that app wraps it."
         },
         {
-          "type": "fixed",
-          "text": "`jelou tool show 6177` returns the JelouPay payment inputs for every company. It used to fail with `NOT_FOUND`, because the server shows that tool only to its owner. Now the CLI answers from its bundled payment contract and marks it `contract_source: \"bundled-snapshot\"`."
+          "type": "improved",
+          "text": "`jelou marketplace list --installed-only` now includes what each installed app wraps, its `node_path` and the ids of its MCP tools."
         },
         {
-          "type": "fixed",
-          "text": "The build skills point at the field `tool show` really emits, `inputs[].configuration.requiredWhenInputs`, and no longer forbid reading `tool show` output with python."
+          "type": "improved",
+          "text": "The workflow build skill discovers integrations from your installed apps first, for payments, calendars, KYC or any other app, and never relies on a fixed tool id."
         },
         {
           "type": "improved",
-          "text": "`jelou workflow validate` takes the RANDOM node's route limits (2 to 20 today) from the server's node-types catalog when it can reach it, and otherwise falls back to cached or bundled limits, which can be stale. A RANDOM node with more than 20 routes is now an error too."
+          "text": "`jelou workflow validate` accepts every native payment entity, including payment skills, not only one specific tool."
+        },
+        {
+          "type": "heads_up",
+          "text": "`jelou tool show --gateway <slug>` is deprecated. Use `--app <slug>`; `--gateway` still works and prints a notice."
         }
       ]
     }