@jelou/cli 1.126.0 → 1.127.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jelou/cli",
-  "version": "1.126.0",
+  "version": "1.127.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.126.0",
-    "@jelou/cli-darwin-x64": "1.126.0",
-    "@jelou/cli-linux-x64": "1.126.0",
-    "@jelou/cli-linux-arm64": "1.126.0",
-    "@jelou/cli-win32-x64": "1.126.0"
+    "@jelou/cli-darwin-arm64": "1.127.0",
+    "@jelou/cli-darwin-x64": "1.127.0",
+    "@jelou/cli-linux-x64": "1.127.0",
+    "@jelou/cli-linux-arm64": "1.127.0",
+    "@jelou/cli-win32-x64": "1.127.0"
   },
   "keywords": [
     "jelou",
@@ -58,53 +58,37 @@
   "jelou": {
     "minVersion": "1.125.0",
     "release_notes": {
-      "version": "1.126.0",
-      "date": "2026-09-11",
-      "headline": "New `jelou sites` command group: publish a built static site from the CLI and operate it — deploy, inspect, roll back, and open it as a real user sees it.",
+      "version": "1.127.0",
+      "date": "2026-09-12",
+      "headline": "`jelou sites` gains a local dev server and drafts: check a build, publish it, then decide when it goes live.",
       "highlights": [
         {
           "type": "new",
-          "text": "`jelou sites` publishes a built static site. `sites init` links the directory through the same `jelou.json` marker (with `site:` instead of `function:`), `sites deploy` uploads the build, and `sites list` / `info` / `create` / `update` / `delete` / `deployments` / `rollback` cover the rest."
+          "text": "`jelou sites dev` serves your build through the same wrapper the platform deploys — the site's own CSP, security headers, SPA fallback and `_redirects`/`_headers` rules, fetched for that site rather than reimplemented. What works locally works on the URL, and files are read per request so a rebuild needs no restart."
         },
         {
           "type": "new",
-          "text": "`jelou sites deploy` checks the build offline first — `index.html` at the root, 1000 files, 5 MB per file, 25 MB total, nothing under the reserved `__jelou/` — and uploads nothing when something blocks. `--dry-run` shows what would ship without touching the network."
+          "text": "`jelou sites deploy --draft` publishes without taking the site over. The build settles on its own preview URL and the live one keeps serving what it served before."
         },
         {
           "type": "new",
-          "text": "The file set the platform stored is verified against the one that was sent. A mismatch exits 6 and writes the evidence to `.jelou/deploys/<id>.json`."
-        },
-        {
-          "type": "new",
-          "text": "`jelou sites webview mint` mints the single-use session link a workflow would mint, so you can open a page as a real user sees it without building the workflow first."
-        },
-        {
-          "type": "new",
-          "text": "An organization root now lists `sites:` alongside `projects:` and `functions:`, and `jelou org init` picks up site directories when it scans."
+          "text": "`jelou sites activate <slug> <id>` takes a draft live, binding the site to a build that is already built rather than deploying it again."
         },
         {
           "type": "improved",
-          "text": "`jelou sites deployments list` and `info` say which deployment the URL is actually serving, as `Live` in the table and `live` in `--json`. The platform leaves every superseded deployment marked active, so the whole history used to read as current."
+          "text": "Deployments report `preview_url`, which is where a draft is looked at before it goes live."
         },
         {
           "type": "improved",
-          "text": "`jelou sites rollback <deployment-id>` works from a linked directory. A lone deployment id used to be read as a site slug and failed with a misleading \"not found\"."
+          "text": "`jelou sites create` and `jelou sites info` report `platform_url` — where the site will live, claimed when it is created, so you know the hostname before uploading anything."
         },
         {
           "type": "improved",
-          "text": "`jelou sites update --reset <field>` drops a header override (`csp`, `frame-ancestors`, `permissions-policy`) so it falls back to the platform default."
-        },
-        {
-          "type": "improved",
-          "text": "Running a `functions` command in a site directory, or the reverse, now says which kind the directory is linked to instead of calling it unlinked."
-        },
-        {
-          "type": "heads_up",
-          "text": "Security headers are compiled into the served bundle when it is built, so a `jelou sites update --csp` / `--frame-ancestors` / `--permissions-policy` / `--reset` change is stored immediately and reaches visitors only after the next `jelou sites deploy`. The command now says so and returns `requires_redeploy`."
+          "text": "Deploys and rollbacks now identify the CLI to the platform, so a deployment that came out wrong can be traced to what made it."
         },
         {
           "type": "heads_up",
-          "text": "`jelou sites delete` does not take a page offline. It removes the site and destroys every stored artifact, but the already-published bundle keeps answering on its URL. To stop serving content, deploy a replacement."
+          "text": "Only the newest build can be activated. If someone deploys after your draft, `jelou sites activate` refuses with exit 2 and you deploy again — binding an older build would be a silent no-op on the platform."
         }
       ]
     }