@jelou/cli 1.38.0 → 1.39.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jelou/cli",
-  "version": "1.38.0",
+  "version": "1.39.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.38.0",
-    "@jelou/cli-darwin-x64": "1.38.0",
-    "@jelou/cli-linux-x64": "1.38.0",
-    "@jelou/cli-linux-arm64": "1.38.0",
-    "@jelou/cli-win32-x64": "1.38.0"
+    "@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"
   },
   "keywords": [
     "jelou",
@@ -56,19 +56,47 @@
     "access": "public"
   },
   "jelou": {
-    "minVersion": "1.38.0",
+    "minVersion": "1.39.0",
     "release_notes": {
-      "version": "1.38.0",
+      "version": "1.39.0",
       "date": "2026-05-27",
-      "headline": "`jelou logs` now defaults to a 30-day window for conversation history (was 7).",
+      "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.",
       "highlights": [
         {
           "type": "improved",
-          "text": "`jelou logs conversations list` and `jelou logs chat` default `--from` to 30 days ago instead of 7. The backend has no range cap; override with `--from <iso>` for any other window."
+          "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": "improved",
+          "text": "`jelou workflow list` and `jelou workflow skill <id>` now show the `default` flag per workflow (in both human and `--json` output)."
+        },
+        {
+          "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": "`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."
+        },
+        {
+          "type": "fixed",
+          "text": "`jelou push --dry-run` no longer silently mutates the lockfile on disk when a legacy-form hash refresh would have triggered."
+        },
+        {
+          "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": "`minVersion` floor raised to `1.38.0`. CLIs below this version will 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."
+          "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."
         }
       ]
     }