@jelou/cli 1.112.0 → 1.113.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jelou/cli",
-  "version": "1.112.0",
+  "version": "1.113.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.112.0",
-    "@jelou/cli-darwin-x64": "1.112.0",
-    "@jelou/cli-linux-x64": "1.112.0",
-    "@jelou/cli-linux-arm64": "1.112.0",
-    "@jelou/cli-win32-x64": "1.112.0"
+    "@jelou/cli-darwin-arm64": "1.113.0",
+    "@jelou/cli-darwin-x64": "1.113.0",
+    "@jelou/cli-linux-x64": "1.113.0",
+    "@jelou/cli-linux-arm64": "1.113.0",
+    "@jelou/cli-win32-x64": "1.113.0"
   },
   "keywords": [
     "jelou",
@@ -58,13 +58,45 @@
   "jelou": {
     "minVersion": "1.100.2",
     "release_notes": {
-      "version": "1.112.0",
+      "version": "1.113.0",
       "date": "2026-09-04",
-      "headline": "`jelou push` keeps auto-reminting duplicate node and edge ids as the platform changes how it reports them.",
+      "headline": "`jelou functions deploy` now proves what it uploaded and tells you why a change is not live.",
       "highlights": [
         {
-          "type": "improved",
-          "text": "`jelou push` still recognises a duplicate node or edge id and auto-remints it once the platform starts reporting the collision as a conflict instead of a server error. Recovery behaves exactly as it does today."
+          "type": "new",
+          "text": "`jelou functions deploy --dry-run` lists every file the CLI will skip and why — symlink, unsupported extension, hidden path, ignored directory, outside the project root. This is the usual answer to \"my change didn't deploy\"."
+        },
+        {
+          "type": "new",
+          "text": "Every deploy computes a manifest of what it sends (paths, sizes, sha256 and one digest — never content) and checks it against the digest the platform stored. A mismatch stops with `MANIFEST_MISMATCH` before the build is even polled; `--json` exposes `manifest_digest`, `manifest_verified` and `excluded`."
+        },
+        {
+          "type": "new",
+          "text": "Each deploy leaves `.jelou/deploys/<deployment-id>.json` with the manifest, the skipped files and the platform's answer, so a past run can be compared with what is running without re-running anything."
+        },
+        {
+          "type": "new",
+          "text": "`jelou functions deployments info` shows the manifest the platform stored and a lifecycle timeline (`accepted → runtime_sent → build → activated | superseded`). `activated` is the only proof a version ever served traffic."
+        },
+        {
+          "type": "new",
+          "text": "`jelou functions deployments logs <slug> <id>` reads the runtime logs of one specific deployment, active or not — `jelou functions logs` only reads the active one."
+        },
+        {
+          "type": "fixed",
+          "text": "A deploy whose build succeeded but lost to a newer deployment is reported as `DEPLOY_SUPERSEDED` with a pointer to what is live, instead of a misleading `BUILD_FAILED`."
+        },
+        {
+          "type": "fixed",
+          "text": "When `deploy` stops waiting for a slow build it prints the deployment's timeline, so you see where it stopped instead of only \"no outcome reported\"."
+        },
+        {
+          "type": "fixed",
+          "text": "Projects deployed from Windows uploaded backslash paths; they now use `/` like every other platform, so the digest matches across machines."
+        },
+        {
+          "type": "heads_up",
+          "text": "The file-count limit is configured on the platform and is not visible to the CLI. The `jelou-functions` skill no longer states a fixed 20-file cap — diagnose against the platform's own error, not a number."
         }
       ]
     }