@wix/himalaya-cli 0.1052.0 → 0.1054.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Binary file
@@ -101,7 +101,10 @@ fills, and a published draft or the handover is celebrated once. The tab title c
101
101
  ("(5/8) salon"), and the owner can switch on Sound and desktop notices from the board itself — both
102
102
  start off, so never promise them either. The board can also rewind the whole build — drag its timeline or
103
103
  press Replay for a thirty-second making-of, checks included — pop the live phone out into an
104
- always-on-top window, and show the owner their website next to their app the moment the brand lands. `himi test` writes one PNG per
104
+ always-on-top window, and show the owner their website next to their app the moment the brand lands.
105
+ To put the preview on the owner's phone, run `himi run --watch --lan` instead: it prints a QR (and
106
+ the board shows one) that a phone on the same Wi-Fi opens as the real app, full screen, repainting as
107
+ you edit. Say that anyone on that network can open it; it is read-only. `himi test` writes one PNG per
105
108
  screen to `.himi/shots/` on every run, so take the new screens from there instead of rendering each
106
109
  one again; a bare `--png` on `himi render` writes `.himi/shots/<id>.png`. `himi progress` copies each image into `.himi/history/`
107
110
  as it was when you journaled it, so a later render cannot change what the record says the owner saw;
@@ -145,6 +145,13 @@ Same collector, three doors:
145
145
  | `POST /v1/site/analyze` (BO-only) | JSON book + overlays + media URLs (no PNG bodies) |
146
146
  | MCP `himi_site_analyze` | Same JSON via `structuredContent` |
147
147
 
148
+ `clientId` is optional on the HTTP and MCP doors too, as `--client-id` is on the CLI: a body of
149
+ `{ "siteUrl": "https://…" }` alone is the URL-only pass — vertical probes `skipped`, no `wix` block
150
+ in `provisioningOverlay`, and the response carries `urlOnly: true` plus a `note` saying the catalog
151
+ counts and the binding need a `clientId`. `"apply": true` without a `clientId` is refused with
152
+ `400 apply_needs_client_id`, the HTTP twin of `--apply` exiting 2. The door stays BO-only, and
153
+ `siteUrl` is judged by the same public-host guard whether or not a client id is sent.
154
+
148
155
  The plane has no headless browser (`look.unavailable: no_browser_on_plane`). Owner token is a **request field**, never spawned via `wix token` on the guest. Blobs in the book are **URLs** (Media Manager / wixstatic), not S3 and not base64.
149
156
 
150
157
  `--apply` writes `appearance.homeLayout` + `navigation.navKind` plus identity/colors. It never silently overwrites committed Amit1 `apps/himi-branded-lite/provisioning.json`.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@wix/himalaya-cli",
3
- "version": "0.1052.0",
3
+ "version": "0.1054.0",
4
4
  "type": "module",
5
5
  "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.",
6
6
  "keywords": [
@@ -65,5 +65,5 @@
65
65
  "artifactId": "himalaya-cli"
66
66
  }
67
67
  },
68
- "falconPackageHash": "418916efab2e1d4bc74db7d4eeb30ad2b9c0d20534c7d5757fcec730"
68
+ "falconPackageHash": "045caa3e88a506e031fb787279f23cc802f48565167f69eb533939ab"
69
69
  }