@wix/himalaya-cli 0.856.0 → 0.857.0

package/guides/mobile-ux.md

@@ -135,6 +135,10 @@ driving a native shell, record the result—not an assumption—with `himi ux re
 is required for `passed`/`failed` and names what you actually drove; an unavailable platform drove
 nothing, so it takes no checks and needs a `--reason` instead.
 
+`himi render --width`/`--device` writes into the same `.himi/ux-audit.json`, appending the width it
+rendered. That is what the width marker below reads first, so rendering the screen at two widths is
+itself the evidence — see the strict audit contract.
+
 ### Strict audit contract
 
 **Two commands read this contract.** `himi validate` reports a gap as a **warning**, so a rewrite
@@ -162,12 +166,31 @@ better document, were refused, and pasted the sentence back:
 - *or literally*: the phrase `one primary CTA per state` appears anywhere. It is not deprecated —
   a document that passes today keeps passing.
 
-The remaining marker, **width evidence**, is graded by **content, not by phrase** — it is a
-fact about what you rendered rather than a string, so there is nothing to paste. Satisfy it either
-way:
-
-- Name two pixel widths spanning compact → wider, **each spelled as a width on itself**, within
-  about 400 characters of each other so they read as one statement: one **below 600px** (compact)
+The remaining marker, **width evidence**, is graded by **what you rendered, not by a phrase** — it
+is a fact rather than a string, so there is nothing to paste. Three things satisfy it, and they are
+tried in this order:
+
+- **A recorded render — the primary path, and the one to prefer.** `himi render <screenId>
+  --content <app> --width 390`, then the same screen again at `--width 834` (or `--device iphone`
+  and `--device ipad`), appends the width each run actually rendered to `.himi/ux-audit.json` —
+  the same structured evidence file `himi ux record` writes. A recorded render **below 600px**
+  plus one **at 600px or wider** satisfies this marker on its own: the document need not name a
+  width anywhere. The gate is then reading a fact the tool produced instead of a sentence you
+  typed, which is the whole point of the marker.
+
+  Each entry carries the screen, the width, the `--device` preset when you used one, and the PNG
+  when `--png` wrote one. Re-rendering the same screen at the same width **replaces** that entry
+  rather than appending another, so a long dev loop leaves one line per screen and width, and a
+  native audit already recorded in the same file is never disturbed. A render with **no**
+  `--width`/`--device` records nothing on purpose: without one the PNG viewport is the headless
+  browser's desktop default, and writing that down would manufacture the very expanded render the
+  marker exists to prove. Recording never fails or slows a render — if the file cannot be written
+  the render still succeeds, and the paths below still apply. `.himi/` is gitignored, so this is
+  evidence about your checkout rather than something a pull request carries.
+
+- Or name two pixel widths in the document, spanning compact → wider,
+  **each spelled as a width on itself**, within about 400 characters of each other so they read as
+  one statement: one **below 600px** (compact)
   and one **at 600px or wider** (medium or expanded). A number is spelled as a width when it
   carries a **unit** — `320px`, `320 px`, `320pt`, `320dp`, `320 pixels`, `320 wide` — or sits in a
   **screenshot filename** — `home-320.png`, `home-834-dark.png`, `home-390x844.png`. That is the
@@ -211,9 +234,17 @@ way:
   `expanded` must follow within about 400 characters, so keep them in the same sentence or bullet
   rather than in separate sections.
 
+The two written paths are a **fallback, not a deprecation**: plenty of real renders are not driven
+by `himi render` at all — a simulator, a real phone, or an automated UI driver leaves no entry in
+`.himi/ux-audit.json` — so a document that satisfies this marker today still satisfies it. A render
+record can only **add** a way to pass; it never takes one away, and a record showing fewer size
+classes than your document claims is not itself a finding.
+
 When the marker fails, the error names **which** of the four things went wrong — no compact width,
 no wider width, two widths too far apart to be one statement, or no number spelled as a width — and
-says so alongside the height-axis rule if that is what discarded your numbers. Read the branch it
+says so alongside the height-axis rule if that is what discarded your numbers. When the render
+record holds something, it also names what it holds and the single command that would complete it
+("holds 390px — compact only. Render the same screen again at 600px or wider"). Read the branch it
 gave you rather than pasting the example: the example is a form that works, not the only one.
 
 **HTML comments are stripped before any of this runs.** The scaffold ships a `<!-- LOAD-BEARING -->`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/himalaya-cli",
-  "version": "0.856.0",
+  "version": "0.857.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": [
@@ -63,5 +63,5 @@
       "artifactId": "himalaya-cli"
     }
   },
-  "falconPackageHash": "82a824b69c0914106e80e0fb205b046bd8e669b53f46887b3adf0eed"
+  "falconPackageHash": "629ade3aa68530bbdcfe1842b24b52fcb778d8e8f85ff394bc3372fb"
 }