@jelou/cli 1.40.0 → 1.41.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jelou/cli",
-  "version": "1.40.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.40.0",
-    "@jelou/cli-darwin-x64": "1.40.0",
-    "@jelou/cli-linux-x64": "1.40.0",
-    "@jelou/cli-linux-arm64": "1.40.0",
-    "@jelou/cli-win32-x64": "1.40.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,39 +56,39 @@
     "access": "public"
   },
   "jelou": {
-    "minVersion": "1.40.0",
+    "minVersion": "1.41.0",
     "release_notes": {
-      "version": "1.40.0",
+      "version": "1.41.0",
       "date": "2026-05-28",
-      "headline": "AI model references in `AI_TASK` nodes now use the canonical `provider/model` form (`openai/gpt-4.1`, `anthropic/claude-sonnet-4-6`) — the form Studio actually writes when you pick a model. `jelou push` auto-expands bare names on the way out, so older workflows keep working unchanged.",
+      "headline": "Build skill now catches HTTP body and retry config that Studio would silently drop.",
       "highlights": [
         {
-          "type": "improved",
-          "text": "`jelou push` auto-expands bare AI model names to canonical `provider/model` form before validation. A workflow with `model: \"gpt-4.1\"` is rewritten on disk to `model: \"openai/gpt-4.1\"`; the JSON envelope reports the change under `meta.model_expansions`. Studio writes the canonical form, so this brings on-disk files in line with what the platform expects."
+          "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 models validate <id>` accepts either bare or canonical form; the response carries both the original `input` and the resolved canonical `model` so agents don't have to parse the message string."
+          "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 --dry-run` no longer writes anything to disk during the model-expansion pass — the preview now correctly reports what would change without changing it. `meta.model_expansions` appears in the dry-run envelope too."
+          "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": "improved",
-          "text": "Push refuses cleanly with `AI_MODEL_AMBIGUOUS` (exit 2) when a bare model name is served by multiple providers (e.g. `gpt-4o` lives under both `openai` and `azure`); the error lists the qualified candidates so the fix is one edit away."
+          "type": "fixed",
+          "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": "improved",
-          "text": "`jelou push` model validation now covers AI_TASK nodes that only set `fallbackModel.model` (previously these silently skipped the catalog check); typo'd bare names now also produce useful \"did you mean\" suggestions."
+          "type": "fixed",
+          "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": "improved",
-          "text": "The bundled `jelou-build-workflow` skill emits canonical-form models in every example, including the e-commerce specialist."
+          "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.40.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 workflows pushed by 1.40.0+ carry the canonical `provider/model` form on disk, which older CLIs flag as unknown until they auto-strip the prefix back to bare on the next push."
+          "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."
         }
       ]
     }