@jelou/cli 1.39.0 → 1.41.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jelou/cli",
-  "version": "1.39.0",
+  "version": "1.41.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.39.0",
-    "@jelou/cli-darwin-x64": "1.39.0",
-    "@jelou/cli-linux-x64": "1.39.0",
-    "@jelou/cli-linux-arm64": "1.39.0",
-    "@jelou/cli-win32-x64": "1.39.0"
+    "@jelou/cli-darwin-arm64": "1.41.0",
+    "@jelou/cli-darwin-x64": "1.41.0",
+    "@jelou/cli-linux-x64": "1.41.0",
+    "@jelou/cli-linux-arm64": "1.41.0",
+    "@jelou/cli-win32-x64": "1.41.0"
   },
   "keywords": [
     "jelou",
@@ -56,47 +56,39 @@
     "access": "public"
   },
   "jelou": {
-    "minVersion": "1.39.0",
+    "minVersion": "1.41.0",
     "release_notes": {
-      "version": "1.39.0",
-      "date": "2026-05-27",
-      "headline": "Workflow files now use `workflowName` / `workflowDefault` / `workflowDescription` / `workflowConfiguration` — the rename finishes the migration started years ago when `workflowId` replaced the legacy top-level key, and your existing files keep working unchanged.",
+      "version": "1.41.0",
+      "date": "2026-05-28",
+      "headline": "Build skill now catches HTTP body and retry config that Studio would silently drop.",
       "highlights": [
         {
-          "type": "improved",
-          "text": "Workflow files in `workflows/<slug>.<channel>.json` now use `workflowName`, `workflowDescription`, `workflowDefault`, `workflowConfiguration`. Existing files keyed under `skillName`/etc. keep working — your next `jelou pull` rewrites them to the new keys. Hashes are recognized under both forms during the transition; you should not see a single spurious \"modified\" or `LOCKFILE_DRIFT` after upgrading."
+          "type": "new",
+          "text": "`bin/workflow-lint` (step 6.5 of the `jelou-build-workflow` skill) hard-fails on HTTP `body.type` / `retryCondition` / `retryDelay` values that Studio's canvas can't render. Push exits 4 with a specific code (`HTTP_BODY_TYPE_INVALID`, `HTTP_BODY_CONTENT_SHAPE`, `HTTP_RETRY_CONDITION_INVALID`, `HTTP_RETRY_DELAY_INVALID`, `HTTP_MULTIPART_ITEM_TYPE_INVALID`) plus a `fix_hint`. Also warns on `HTTP_BODY_METHOD_MISMATCH` (POST/PUT/PATCH without body, GET/DELETE with body). Applies to `HTTP` and `SOAP` nodes."
         },
         {
-          "type": "improved",
-          "text": "`jelou workflow list` and `jelou workflow skill <id>` now show the `default` flag per workflow (in both human and `--json` output)."
+          "type": "new",
+          "text": "New `references/HTTP_NODE_GUIDE.md` documents the 6 canonical body shapes (string for JSON/XML/text, array of `{ id, key, value, enabled, type? }` for multipart/form-urlencoded, null for no-content) and the full retry/timeout block."
         },
         {
-          "type": "improved",
-          "text": "`jelou push --json` now surfaces `meta.lockfile_refreshed[]` so agents see when a silent hash-format migration happened on their lockfile."
-        },
-        {
-          "type": "improved",
-          "text": "`jelou workflow validate` and `jelou push` now warn on AI_TASK authoring gaps — missing or uncommon `instructions_lang`, missing `splitMessages: true`, and `messageHistory.count` outside the 1–15 range. Warnings only; never block push."
-        },
-        {
-          "type": "improved",
-          "text": "The bundled `jelou-build-workflow` skill now documents the seven recommended AI_TASK settings (`instructions_lang`, `canRemind`, `splitMessages`, `pdfDocumentSupport`, `readImageUrlWithCaption`, `expiration`, `messageHistory`) with semantics and defaults."
+          "type": "fixed",
+          "text": "Agent-built HTTP POST nodes no longer ship with `body.type: \"raw\"` — bundled templates now use the canvas-recognized values. Previously Studio reset `body.content` to `null` the moment a user picked the right type from the dropdown, silently wiping the payload."
         },
         {
           "type": "fixed",
-          "text": "`jelou push` now refuses when more than one local workflow asserts `workflowDefault: true` — the server enforces one default per project, so pushing two would silently produce a lie after dispatch. The error hint walks you through the safest recovery and explicitly warns against `jelou pull` if you have other un-pushed work."
+          "text": "Retry enum templates use the canonical `is_network_or_idempotent_request_error` / `always_retry` and `no_delay` / `exponential_delay` / `custom_delay` strings. The doc also corrects a long-standing lie: `custom_delay` is **linear** backoff (`retryCount × milliseconds`), not constant wait."
         },
         {
           "type": "fixed",
-          "text": "`jelou push --dry-run` no longer silently mutates the lockfile on disk when a legacy-form hash refresh would have triggered."
+          "text": "`bin/workflow-lint` no longer truncates its stdout envelope on workflows with many issues (the 64 KB pipe buffer cap on Node 22). Large issue arrays now survive the pipe to the agent."
         },
         {
-          "type": "fixed",
-          "text": "Several read paths (`pull`, `status`, `incoming accept-local`, `incoming accept-server`, `incoming diff`) now tolerate stored hashes recorded under the previous canonical form, so an in-flight incoming artifact captured pre-upgrade no longer trips spurious `NEW_REMOTE_DRIFT`."
+          "type": "heads_up",
+          "text": "Workflows pulled from older production brains may carry `retryCondition: \"\"` / `retryDelay: \"fixed\"` on HTTP nodes (residue from earlier skill templates). These now fail `bin/workflow-lint` at step 6.5 with `HTTP_RETRY_CONDITION_INVALID` / `HTTP_RETRY_DELAY_INVALID`. The fix is a one-line substitution per offending node; the `fix_hint` in the lint output shows the canonical value to use."
         },
         {
           "type": "heads_up",
-          "text": "`minVersion` floor raised to `1.39.0`. CLIs below this surface the soft \"Update available\" prompt on next invocation (and `below_floor: true` on the agent-mode envelope). Nothing is blocked — the CLI still runs either way. The floor bump exists because every read path that compares a stored hash needs the upgrade-compat awareness; older CLIs would see phantom drift errors against lockfiles updated by 1.39.0."
+          "text": "`minVersion` floor raised to `1.41.0`. CLIs below this version see the soft \"Update available\" prompt on next invocation and receive `meta.update_available.below_floor: true` on agent-mode envelopes. Nothing is blocked; commands still run."
         }
       ]
     }