@wix/himalaya-cli 0.1528.0 → 0.1530.0

package/fixtures/wix-canned.json

@@ -2093,5 +2093,88 @@
   "POST /ecom/v1/checkouts/chk-0001/create-order": {
     "orderId": "order-0001",
     "paymentGatewayOrderId": "payment-0001"
+  },
+  "GET /ecom/v2/carts/current": {},
+  "GET /restaurants-operations/v1/operations": {
+    "operations": [
+      {
+        "id": "op-0001",
+        "name": "Ordering page",
+        "default": true,
+        "onlineOrderingStatus": "ENABLED",
+        "defaultFulfillmentType": "PICKUP",
+        "fulfillmentIds": [
+          "fm-pickup-0001",
+          "fm-delivery-0001"
+        ]
+      }
+    ]
+  },
+  "GET /fulfillment-methods/v1/fulfillment-methods": {
+    "fulfillmentMethods": [
+      {
+        "id": "fm-pickup-0001",
+        "type": "PICKUP",
+        "name": "Pickup",
+        "enabled": true,
+        "minOrderPrice": "0",
+        "pickupOptions": {
+          "address": {
+            "country": "US",
+            "subdivision": "US-CA",
+            "city": "San Francisco",
+            "formattedAddress": "500 Example St, San Francisco, CA"
+          }
+        }
+      },
+      {
+        "id": "fm-delivery-0001",
+        "type": "DELIVERY",
+        "name": "Delivery Area #1",
+        "enabled": true,
+        "fee": "0",
+        "minOrderPrice": "0",
+        "deliveryOptions": {
+          "deliveryTimeInMinutes": 30
+        }
+      }
+    ],
+    "pagingMetadata": {
+      "count": 2,
+      "hasNext": false
+    }
+  },
+  "GET /restaurants-operations/v1/operations/op-0001/first-available-time-slot-per-fulfillment-type": {
+    "timeslotsPerFulfillmentType": [
+      {
+        "fulfilmentType": "DELIVERY",
+        "timeSlot": {
+          "startTime": "2026-10-29T11:18:00Z",
+          "endTime": "2026-10-29T11:18:00Z",
+          "orderSchedulingType": "ASAP"
+        },
+        "fulfillmentInfo": [
+          {
+            "fee": "0",
+            "minOrderPrice": "0",
+            "maxTime": 60
+          }
+        ]
+      },
+      {
+        "fulfilmentType": "PICKUP",
+        "timeSlot": {
+          "startTime": "2026-10-29T10:48:00Z",
+          "endTime": "2026-10-29T10:48:00Z",
+          "orderSchedulingType": "ASAP"
+        },
+        "fulfillmentInfo": [
+          {
+            "minOrderPrice": "0",
+            "maxTime": 30
+          }
+        ]
+      }
+    ]
   }
 }

package/guides/hhp.md

@@ -195,6 +195,45 @@ and auth flows retain their existing transports and network-fixture seams.
 The studio preview adds compact, medium, and expanded presets. Existing worker state,
 action, and SDK inspection remain available through the dev drawer.
 
+## Design fidelity (`himi fidelity`)
+
+`himi fidelity` answers one question per screen: does what shipped look like what was designed? It is repo-only for now and advisory. No CI gate reads it. Its readers are the authoring agent, before it calls an app done, and the PR reviewer.
+
+Declare the mockup each screen was designed from in `hhp.json`:
+
+```json
+{ "version": "hhp/2", "screens": { "schedule": { "html": "screens/schedule.html", "mockup": "mockup/schedule.html" } } }
+```
+
+A screen may also carry `params` (the navigation input a device opens it with, used by native capture, #4935) and `fidelity: { "warn": 80, "fail": 60 }`. Thresholds can also be set app-wide at the top level.
+
+```bash
+himi fidelity --content <dir> [--screen a,b] [--variant light,dark,rtl,tablet] [--no-native] [--json] [--post-pr <n>]
+```
+
+For each screen and variant (`light`, `dark`, `rtl`, `tablet`), the command does four things:
+
+1. **Captures the mockup.** It draws the page in Chromium at the variant's width. Dark mode is drawn by emulating `prefers-color-scheme`. RTL is drawn by setting `dir=rtl` on the page.
+2. **Captures the web render** from the app's recorded data, as `himi render` does by default. Native frames come through a capture seam. Until #4935 lands, the seam reports iOS and Android as skipped.
+3. **Scores mockup↔web** with ImageMagick SSIM, globally and per tile. The worst tile says where the screens differ most.
+4. **Asks a fresh model** two questions, using the repo's fidelity judge prompt. The model never ran in the session that wrote the app.
+   - **Design:** does WEB look like the MOCKUP? This judges the port.
+   - **Parity:** do IOS and ANDROID look like WEB? This judges the native renderers.
+
+Each row gets a status:
+
+| Status | When |
+|---|---|
+| **fail** | The judge answers `mismatch` to either question, or the mockup↔web score is below a `fail` threshold you set. |
+| **warn** | `partial`, `cannot_tell`, a skipped surface, a mockup with no styling for the variant (`no_reference`), a missing mockup (`fidelity_mockup_missing`), or a score below `warn`. |
+| **pass** | Anything else. |
+
+The command exits 1 if any row fails. Output goes to `.himi/fidelity/<run>/`: `report.json` and one strip PNG per row. `--post-pr <n>` keeps one plain PR comment per app up to date. The comment opens with `<!-- himi-fidelity: app=<app> run=<id> -->`, and only your own comment is ever edited. It is never a review thread.
+
+The pixel score has no default threshold, on purpose. On the repo's four HTML-first fixture apps, a blank page scores 87–95 against a mockup, while faithful ports score 69–93. Native chrome also shifts every row, so a native bug and its fix score within a point of each other. The judge is the gate, and the score points at where to look. Set thresholds only for a screen whose port is meant to be pixel-close.
+
+Without the `claude` CLI, every verdict is `cannot_tell`, and no row passes. Outside the himalaya repo, the command refuses with `code: "fidelity_outside_repo"`.
+
 ## Qualification
 
 Automated tests cover v1

package/guides/himi-json-output.md

@@ -6,7 +6,7 @@ repurposed when human wording changes. New codes may be added; consumers must
 handle an unknown code as a failure, without parsing prose.
 
 **Rollout:** this contract is enforced for **`himi push`**, including `--only`,
-first, for **`himi store iap connect`**, for **`himi site member-app`**, and for the **`himi base44`** entity and function verbs. Other subcommands still have legacy failures without codes and are a
+first, for **`himi store iap connect`**, for **`himi site member-app`**, for **`himi fidelity`**, and for the **`himi base44`** entity and function verbs. Other subcommands still have legacy failures without codes and are a
 follow-up migration. This is an additive change: existing `error`, `errors`,
 `message`, `hint`, status, body, and gate-specific fields stay as they were.
 Some legacy envelopes have no singular `error` or `hint`; consumers must not
@@ -394,6 +394,27 @@ On success (`ok: true`, stdout, exit 0) `capabilities[]` lists the ids the gener
 `--force` to overwrite it). A skipped file is not a failure. `orphaned[]`, when present, lists
 generated files for entities no longer declared. They are never deleted.
 
+## `himi fidelity` codes
+
+`himi fidelity` failures print `ok: false` and `code`:
+
+- `fidelity_rows_failed`: the run completed and at least one screen × variant row failed (a judge
+  `mismatch`, or a score below a threshold `hhp.json` sets). The report follows in the same
+  envelope. Exit 1.
+- `fidelity_outside_repo`: the content directory is not inside a himalaya repo checkout, which
+  carries the fidelity judge; the command is repo-only for now. Exit 2.
+- `fidelity_not_hhp`: the content directory has no `hhp.json`. Exit 2.
+- `fidelity_unknown_screen`: `--screen` names a screen `hhp.json` does not declare. Exit 2.
+- `fidelity_bad_flag`: a flag value is invalid (a missing content directory, an unknown
+  `--variant`, or a `--post-pr` that is not a PR number). Exit 2.
+- `fidelity_post_failed`: `--post-pr` could not create or edit the PR comment. Exit 1.
+- `fidelity_error`: any other failure before a report existed, such as an unreadable `hhp.json`.
+  Exit 1.
+
+A row's own failure is not a command failure. A missing mockup gives that row
+`error.code: "fidelity_mockup_missing"`, and a capture, score or strip that throws gives it
+`error.code: "fidelity_row_failed"`. Both rows warn, and the other rows still run.
+
 ## Follow-ups
 
 - Migrate failure envelopes in subcommands other than `push`, keeping this contract.

package/guides/release-notes.md

@@ -14,6 +14,23 @@ areas, always in the same order, so you can skim for the one you care about.
 
 ---
 
+## 2026-11-01
+
+### Getting started & the CLI
+
+- `himi template screens`, `himi template inspect` and `himi template sweep` now work on a
+  template whose `dev/index.ts` is written by hand, not only on the generated `SCREENS` layout.
+  Before, all three refused every showcase and starter template (`banking-wallet`, `tip-calc`,
+  `weather`, …). `screens` and `inspect` read such a file by loading it the way `himi validate`
+  does, and their output says `"layout": "evaluated"`. `screens --show/--write/--add` and
+  `himi template trim` still need the generated layout. (#4985)
+- `himi template publish` now turns an app's own URL scheme (`himalaya-<app>`, in
+  `navigation.scheme` and in an auth `redirectUri`) into the scaffold's, so `himi init <name>
+  --template <t>` answers `himalaya-<name>` for a template published from a regular app too, as
+  it already did for the generated templates. The showcase and starter templates gave every
+  scaffold their own `himalaya-<t>` before. Apps scaffolded earlier keep the old value in
+  `config.ts` `navigation.scheme`. (#4985)
+
 ## 2026-10-22
 
 ### Getting started & the CLI

package/guides/templates.md

@@ -112,7 +112,7 @@ on the safe side ("may request"). The commands behind it:
 ```sh
 himi template recommend --text "a salon where clients book and buy products"   # rank the catalog (or --verticals / --book)
 himi template inspect                        # recompute the inventory after edits (--dry-run writes nothing)
-himi template screens                        # list dev/index.ts screens without reading the file
+himi template screens                        # list the screens and their workers (a hand-written dev/index.ts is evaluated)
 himi template screens --show himi_saved > saved.txt    # ONE screen's entry
 himi template screens --write himi_saved --from saved.txt   # put it back — re-parsed, refused if it breaks the file
 himi template screens --add himi_sellers --from sellers.txt --parent himi_branded_home   # a NEW screen, registered as linkable
@@ -127,6 +127,16 @@ descriptor it is an Icon id). A one-word literal elsewhere — a service name, a
 action id, a URL — is wiring, and is never rewritten. Every changed file is syntax-checked before
 anything is written.
 
+**Hand-written templates.** `inspect`, `screens` (the list) and `sweep` work on every template. A
+generated template's `dev/index.ts` is one `SCREENS` map, read without running anything. A
+hand-written one — the showcase apps, the starters, most apps published as templates — has no such
+map, so `inspect` and `screens` load `dev/index.ts` the way `himi validate` does, which runs its
+code, and build each screen to read its workers; the output says `"layout": "evaluated"`. `himi init`
+never does that, because a `--remote` template is its publisher's code: its adopt block is skipped
+for these, and `himi template inspect` is the next step. `screens --show/--write/--add` and `trim`
+rewrite the map's source text, so they still need the generated layout; edit a hand-written
+`dev/index.ts` directly.
+
 **Point a `branded-lite` (or vertical overlay) scaffold at your site.** Set
 `WIX_CLIENT_ID` (Headless OAuth client on that site) and `WIX_SITE_URL` before build /
 preview — the `clientId` **is** the site binding (no separate MSID field). Placeholders

package/guides/tier-5-add-a-screen.md

@@ -779,6 +779,10 @@ target is another tab's root screen does not select that tab — it pushes the s
 - An id the app is not showing right now — unknown, hidden by the nav worker, or any id when
   the app has no tab bar or sidebar rail (`single` / `drawer` navigation) — is ignored and
   logged as `nav_verb_dropped`. The user stays where they are.
+- A push identical to the one the router applied less than 500 ms before (same screen, same
+  params) is one push, logged as `nav_push_coalesced`: a worker that answers late answers every
+  tap it was given, and three taps on a busy main thread would otherwise land three screens
+  deep. Any other verb in between starts over, so push, back and the same push again all apply.
 - Asking for the tab the user is already on does nothing. It does **not** pop that tab to its
   root the way a second tap on the tab bar does — unless you ask for it with `reset: true`.
 - `reset: true` pops the selected tab to its root, even when it is the current tab. This is

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/himalaya-cli",
-  "version": "0.1528.0",
+  "version": "0.1530.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": [
@@ -71,5 +71,5 @@
       "artifactId": "himalaya-cli"
     }
   },
-  "falconPackageHash": "977ce0e45046b28615366bb368c7ceb90d7a1f9404024a58bee20404"
+  "falconPackageHash": "f0490b6c81aec1fb5f5ecf75b8397ad986b6ccfe13b57fc83e2441ec"
 }

package/templates/beauty-salon/config.ts

@@ -424,7 +424,7 @@ export default defineApp({
   // Your on-device database. It must declare every entity a worker reads or writes,
   // or those calls fail closed — keep it in step with `local_database` above.
   dataSchema: {
-    "version": 1,
+    "version": 2,
     "entities": [
       {
         "name": "products",
@@ -549,6 +549,17 @@ export default defineApp({
           }
         ]
       },
+      {
+        "name": "food_orders",
+        "encrypted": true,
+        "fields": [
+          {
+            "name": "id",
+            "type": "string",
+            "required": true
+          }
+        ]
+      },
       {
         "name": "member_bookings",
         "encrypted": true,