@wix/himalaya-cli 0.1013.0 → 0.1015.0

package/guides/headless-loop.md

@@ -79,6 +79,7 @@ loop already makes the pictures — send them, and journal each one:
 ```sh
 himi render home --png shots/home.png --device iphone                    # the first picture, right after init
 himi studio                                                              # the build board: opens once, keeps itself current
+himi run --watch &                                                       # live preview: repaints the open tab on every save
 himi progress "Starting from branded-lite" --step implement --image shots/home.png
 himi render home --png shots/home-dark.png --device iphone --scheme dark
 himi progress "Your brand, light and dark" --step brand --image shots/home.png --image shots/home-dark.png
@@ -87,7 +88,10 @@ himi progress                                                            # the j
 
 `himi studio` writes `.himi/studio/index.html` and opens it; from then on every render, test,
 validate, push and progress entry refreshes it, and the page picks that up by itself — no server,
-nothing to re-run (`--no-open` prints its path instead, for SSH). `himi test` writes one PNG per
+nothing to re-run (`--no-open` prints its path instead, for SSH). `himi run --watch` rebuilds on every
+save and sends the open tab only what changed; a save that does not build keeps the last good preview
+on screen and prints `build_failed` with the reason. It stays up until you stop it, so start it in the
+background, and only after the template's startup requests are preflighted (step 4 of the entry skill). `himi test` writes one PNG per
 screen to `.himi/shots/` on every run, so take the new screens from there instead of rendering each
 one again; a bare `--png` on `himi render` writes `.himi/shots/<id>.png`. `himi progress` copies each image into `.himi/history/`
 as it was when you journaled it, so a later render cannot change what the record says the owner saw;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/himalaya-cli",
-  "version": "0.1013.0",
+  "version": "0.1015.0",
   "type": "module",
   "description": "himi — the Himalaya authoring CLI. Build a Tier-5 content package on your own machine, push it to the production serve as a draft, preview it on web + Himi Player, and read worker logs back — the remote dev loop. Wraps @himalaya/serve-cli for transport.",
   "keywords": [
@@ -65,5 +65,5 @@
       "artifactId": "himalaya-cli"
     }
   },
-  "falconPackageHash": "997481e9652da3d8aedd016c711987997556982fd0ac900d13dbc194"
+  "falconPackageHash": "c0e1f385355adc10424cf549036886d4cc8df1be98748efb2eb9a181"
 }