@wix/himalaya-cli 0.1602.0 → 0.1604.0

package/guides/hhp.md

@@ -210,13 +210,13 @@ Declare the mockup each screen was designed from in `hhp.json`:
 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>]
+himi fidelity --content <dir> [--screen a,b] [--variant light,dark,rtl,tablet] [--ios <udid>] [--android <serial>] [--ios-tablet <udid>] [--android-tablet <serial>] [--app-id <id>] [--release <id>] [--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.
+2. **Captures the web render** from the app's recorded data, as `himi render` does by default. Native frames come from Himi Player on the devices you pass: `--ios <udid>` and `--android <serial>`, plus `--ios-tablet` and `--android-tablet` for the tablet variant. Only those devices are touched. For each variant the command sets dark or light appearance and, for `rtl`, the Hebrew language (iOS `AppleLanguages`, Android per-app locale, API 33+). It opens `himi://app/<app>/screen/<screen>` and captures once two frames match. Every setting it changed is restored afterwards, also on Ctrl-C. A variant with no device is reported `skipped`, never passed. Without `--release <id>` the Player shows the app's **live** release, not your working copy. A screen that declares `params` is skipped natively for now, because the Player's deep link does not carry them yet. On a fresh iOS simulator, open one `himi://` link by hand first and accept iOS's "Open in Himi Player?" prompt: the command cannot answer it, and until it is accepted every iOS capture shows the prompt.
 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.

package/guides/push-cli-onboarding.md

@@ -203,6 +203,42 @@ routes: [
 A notification whose link matches no route opens the app without navigating. `himi validate`
 warns when a declared route names a screen the app does not declare.
 
+#### Links from a legacy link space
+
+An app that replaces an older one may still receive that app's links: its old custom scheme
+(`legacyapp://widget/42`) or an old web host (`https://legacy.example.com/app/widget/42`).
+Declare those prefixes and route the rest:
+
+```ts
+push: {
+  linkPrefixes: ["legacyapp://", "https://legacy.example.com/app/"],
+  routes: [{ match: "widget/:id", link: "<scheme>://screen/<widget-screen>?id={id}" }],
+},
+```
+
+Before matching, the device strips a configured prefix from the link, so `widget/42` is matched
+against the routes. It applies these rules in order:
+
+1. With `payloadAdapter: "wix-ping"`, a Wix link is handled first, so a prefix inside the Wix link
+   space never applies.
+2. Otherwise the **longest** matching prefix is stripped. When a prefix starts with a scheme
+   (`legacyapp://`, `https://…`), its scheme and host match in any case and the rest matches
+   exactly. A prefix with no scheme (`legacy.example.com/app/`, `/app/`) matches exactly.
+3. A prefix only matches up to a `/`, `?` or `#`, so `https://old.example.com/m` does not strip
+   `https://old.example.com/mobile/…`.
+4. A relative link (`/widget/42`) is matched as is, with no prefix needed.
+5. Any other link passes through unchanged.
+
+`himi validate` warns about a prefix that can never apply: one inside the Wix link space under
+`wix-ping`, or a prefix list with no routes. It does not judge a prefix by its shape. A schemeless
+prefix strips links written without a scheme, and a dotted custom scheme strips its own links.
+
+With `wix-ping` and no `routes`, the build derives the routes from the site's verticals. A
+stripped link is then matched against those Wix notification paths only
+(`my-account/:site/stores/orders/:orderId`, …). If your legacy links use paths of their own,
+declare `routes` for them. A declared table replaces the derived one, so list the Wix routes you
+still need there too. `himi validate` warns when prefixes meet only derived routes.
+
 ### Notification action buttons
 
 Declare actionable categories in the app's source `config.ts`. The native shells render one

package/guides/wix-login-integration.md

@@ -68,6 +68,8 @@ node --import tsx tools/auth-bake/bake-auth.ts apps/<app> --ios apps/<app>/ios/<
 `auth.json` = `{ providerId, required, gateScreenId?, config }`. Read by `TemplateAppBoot.loadBakedAuth()` (iOS
 and macOS) / `TemplateAuth.boot()` (Android).
 
+A binary baked `providerId: "none"` (a `himi dist` build of a release declaring no auth) stays no-auth until it is rebuilt, whatever later releases serve: adding login to a no-auth app needs a new binary.
+
 ## Step 3 — wire the gate (per platform)
 
 ### iOS

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/himalaya-cli",
-  "version": "0.1602.0",
+  "version": "0.1604.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": [
@@ -72,5 +72,5 @@
       "artifactId": "himalaya-cli"
     }
   },
-  "falconPackageHash": "912a018c8faa872ff500b38a18a77faf8eded63603ce4eecaf8822e7"
+  "falconPackageHash": "d9895ee47dde266d1046d74260972f2c9428e600431befd9b0e4ddc6"
 }