@wix/himalaya-cli 0.1010.0 → 0.1012.0

package/guides/headless-loop.md

@@ -78,14 +78,18 @@ 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 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
 himi progress                                                            # the journal: current step, elapsed, every postcard
 ```
 
-`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. `himi progress` copies each image into `.himi/history/`
+`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
+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;
 `--step` takes the journey step's number or name, and `--notify` also raises a desktop
 notification for an owner who stepped away. Nothing here is sent anywhere, and `.himi/` and a

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/himalaya-cli",
-  "version": "0.1010.0",
+  "version": "0.1012.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": "0dd9633f3f713d8f6b1f430b169d90d44339b48f5d2ff5e265ae72da"
+  "falconPackageHash": "e35f79cf127f1c7cbedf8abdcd5b92c12f3d7456c71abc3b741b08fb"
 }