@wix/himalaya-cli 0.1439.0 → 0.1441.0

package/guides/designing-himi-screens.md

@@ -252,7 +252,11 @@ scroll. *Reach for `SegmentedControl` for 2–4 in-content modes; `Tabs`/tab-bar
 **Feedback & overlays** — `Banner` for a persistent inline message (with a retry action on error);
 `Snackbar` for a transient confirmation; `AlertDialog` for a blocking decision; `BottomSheet` for
 contextual actions/detail; `Tooltip`/`Popover` for a small anchored hint. *Reach for `Snackbar`, not
-`AlertDialog`, to confirm a completed action — don't block on success.*
+`AlertDialog`, to confirm a completed action — don't block on success.* The `Snackbar` COMPONENT draws
+inline where you place it; for a transient toast that floats at the bottom of the screen — an app
+error after a failed action, say — use the `snackbar` presentation verb or `ui.snackbar({ message,
+tone: "danger" })` from a worker: it floats above the tab bar, animates in and out, queues, honours
+`durationMs`, and is announced to screen readers on every platform.
 
 **Status & data-viz** — `Badge`/`Tag`/`Chip` for compact labels; `Rating` for stars (`size: "sm"` in a
 dense row); `ProgressBar` for determinate progress, `ActivityIndicator` for indeterminate; `Gauge` for

package/guides/hhp.md

@@ -54,11 +54,15 @@ payloads retain native fields and normalize selection values into `event.value`.
 Nested scalar paths are checked and updated immutably. Two-way value binding owns
 the component's change callback. Explicit `on:change` is used for custom reducers.
 Boolean `bind:hidden` and existing declared property bindings are available.
+`bind:error` on a text field takes **string** state: the error message, where an
+empty string means valid (a boolean flag is a lint error).
 Read-only controls such as Gauge and ActivityIndicator accept one-way value
 bindings without generating a change action.
 
 Keyed lists use `each="items" key="id"` on a Grid/LazyList and one row template.
-Initial items require unique string ids. Row text uses `{{$item.title}}`. Compute
+Initial items require unique string ids. Row text uses `{{$item.title}}`; mixed
+row text such as `“{{$item.text}}”` is projected by the controller. `$item` bindings
+are typed from the initial rows: `bind:hidden="$item.done"` needs a boolean field. Compute
 expressions in controllers; interpolation accepts paths, not executable expressions.
 Direct `application/himalaya-service` scripts retain `defineService` authoring.
 
@@ -76,6 +80,14 @@ props; `slot="primary"` and `slot="detail"` supply SplitView slots. Structured p
 use a child `script type="application/himalaya-props"` containing JSON.
 `on:<native-action-property>` exposes declared events; click/change/submit have
 ordinary-control aliases. Explicit modifiers use `data-mod-*` or `himi-mod-*`.
+A `…-path` modifier (`data-mod-hidden-path="full"`, `data-mod-background-color-path`)
+names controller state exactly like `bind:*`, or `$item.<field>` in a row; an unknown
+path is a lint error. `onMeasure` keys name the renderer's measure store instead.
+`style` and `title` are HTML globals: `style` is always CSS, so a native `style`
+variant uses `variant="primary"`; `title="…"` sets a component's `title` field. CSS
+`font` applies only to text components (Text, Label, Marquee). The profile's
+handler list holds only router actions every renderer implements (`himi.open`);
+tab switching from content is not supported yet.
 
 The profile is the intersection of enabled deployment surfaces. It retains field
 eligibility and reports web support independently. Placeholder renderer cases,

package/guides/himi-mcp.md

@@ -135,24 +135,34 @@ the same origin, and `himi_preview_start` returns that URL as `board`.
 `himi-studio` is the marketplace's second, optional plugin, a Claude Code *mod*. It adds a pane
 beside the conversation with four views:
 
-- **Now:** the screen being worked on, in a phone frame, with the live build's state and what the
-  last rebuild changed.
+- **Now:** the screen being worked on, in a phone frame, with its controls under it. ‹ › step
+  through screens, ☾ Dark and ▭ iPad ask for those renders, **Open live** opens the app, and **On my
+  phone** shows the LAN preview's QR code. To the right are the live build's state and what the last
+  rebuild changed.
 - **Screens:** every rendered screen.
-- **Checks:** the journey step, and validate, test, the UX audit and the last push.
-- **Activity:** the progress postcards.
+- **Checks:** the journey step, then validate, test, the UX audit and the last push, with the
+  progress postcards below them.
+- **Ship:** the steps to a phone and the stores, in order: preview on a phone, share a draft, test
+  builds, download, and store planning.
 
-When the last rebuild failed, a band above the prompt says so and offers **Fix it**. The agent gets
-two tools: `studio_focus` shows you the screen it just changed, and `studio_snapshot` reads the
-status.
+Under every view a **Next →** strip offers the one most useful step. When the last rebuild failed, a
+band above the prompt says so and offers **Fix it**. Pushing a draft and building test apps ask for
+a second press in the pane, and the prompt that press sends is the owner's approval of that gate.
+The agent gets two tools: `studio_focus` shows the person the screen it just changed, and
+`studio_snapshot` reads the status.
 
 ```
 /plugin install himi-studio@wix-himi
 ```
 
-The pane shows screenshots, not the live app: a mod cannot host a web page. For the interactive
-app, use its **Open live preview** button or the `himi-preview` launch configuration. The pane reads
-only what the CLI already writes under `.himi/` (the board's `state.json` and its screenshots). It
-opens by itself in an app folder; elsewhere, run `/himi <app folder>`.
+The pane shows screenshots, not the live app: a mod cannot host a web page. Ghostty, kitty, WezTerm
+and iTerm2 show the real image, cropped to the app; Claude Code Desktop shows the whole screenshot in
+a phone frame. macOS Terminal shows no
+picture: **View picture ↗** opens the screenshot in Preview, and **On my phone** opens the QR code
+the same way. Other terminals without images (tmux, for one) show a coloured-block version that
+says it is one. For the interactive app, use **Open live** or the `himi-preview` launch
+configuration. The pane reads only what the CLI already writes under `.himi/`. It opens by itself in
+an app folder; elsewhere, run `/himi <app folder>`.
 
 To see the app **on your phone**, `himi_push` publishes a draft and returns a link that opens it in
 Himi Player.

package/guides/sdk-reference.json

@@ -4715,19 +4715,19 @@
       {
         "name": "SnackbarTone",
         "kind": "type",
-        "jsdoc": "/** Snackbar tone — maps to the app's tone background tokens. */",
+        "jsdoc": "/** Snackbar tone — maps to the app's tone background tokens (`info` → textPrimary, `success`,\n *  `warning`, `danger`). Use `danger` for errors; the hosts also accept `error` as an alias of it. */",
         "decl": "export type SnackbarTone = \"info\" | \"success\" | \"warning\" | \"danger\";"
       },
       {
         "name": "SnackbarOptions",
         "kind": "interface",
         "jsdoc": "",
-        "decl": "export interface SnackbarOptions {\n  message: string;\n  /** Default \"info\". */\n  tone?: SnackbarTone;\n  /** Auto-dismiss delay. Default 3000. Ignored on web (fixed-duration there). */\n  durationMs?: number;\n}"
+        "decl": "export interface SnackbarOptions {\n  message: string;\n  /** Default \"info\". */\n  tone?: SnackbarTone;\n  /** Auto-dismiss delay in ms, on every host. Default 3000; 0 or less also means 3000. */\n  durationMs?: number;\n}"
       },
       {
         "name": "snackbar",
         "kind": "function",
-        "jsdoc": "/** Show a transient snackbar toast. Resolves once it is PRESENTED (not after it\n *  auto-dismisses). Rejects with `no_ui_host` if no presenter is attached. */",
+        "jsdoc": "/** Show a transient snackbar toast: it floats above the tab bar, slides and fades in and out\n *  (fades only under reduced motion), queues behind one that is already showing, and is read\n *  by VoiceOver / TalkBack. Resolves once it is PRESENTED (not after it auto-dismisses).\n *  Rejects with `no_ui_host` if no presenter is attached. */",
         "decl": "export async function snackbar(options: SnackbarOptions): Promise<void>;"
       },
       {

package/guides/skill.md

@@ -74,7 +74,7 @@ A build takes most of an hour. An owner who sees nothing for that long assumes n
 - **Give them a board to leave open.** When the installed CLI lists `studio`, run `himi studio` once, right after that first picture, and tell the owner it is there (a current `himi init` has already made the board; this opens it). It opens a local page in their browser that fills itself in — every screen as it renders, the journey step and your latest postcard, each check as it runs — so they can watch between your messages. It is a view of your local work, not the preview of step 7.
 - **Let them click around while you work — the live preview runs from init on.** A current `himi init` started it (`watch.url` in its output); if it isn't running (`--remote`, CI), start it once step 4's startup preflight says the app may boot locally, when the installed CLI's `himi run` accepts `--watch`: run `himi run --watch --content <dir> &` at once and leave it running until the handover; do not wait for a `reminder` to ask. Give the owner its url, and open it only after the preflight. `himi run --watch` serves the app on this machine, opens it in their browser when you start it yourself (no `--browser` flag — that is a different mode, and `--watch` refuses it; the one init starts opens nothing), and repaints that tab every time you save — and the board frames the same live app. Once the app is bound to their site, the watch preview shows that site's live data, fetched by their own browser as an anonymous visitor. It is a local preview of your working copy, never the owner-private preview, and a save that does not build leaves the last good version on screen while you fix it.
 - **Inside a coding agent, prefer the `himi_*` tools.** When your tool list has them (`himi init` configures the `himi` MCP server for Claude Code, Cursor, Codex and VS Code), call them instead of shelling out: `himi_render` hands you the PNG to show, and `himi_preview_start` returns the live preview's URL. Open that URL in your own built-in browser — Claude Code desktop: start the `himi-preview` launch configuration; Cursor: its Browser tool; Codex in the ChatGPT desktop app: its Browser; VS Code: the integrated browser — so the owner watches the app take shape beside the chat.
-- **When the Himi Studio pane is open, show the work there.** In Claude Code, a tool list with `mcp__himi-studio__studio_focus` means the owner has the Himi Studio pane beside the chat. It shows each screen as it renders, the live build and every check, and it keeps itself current. Right after you change or render a screen, call `studio_focus` with its screen id rather than pasting the picture into the chat. For the build status, read `studio_snapshot` rather than re-running status commands. Postcards still go in the chat and the journal. Without the pane, in Claude Code you may offer it once: `/plugin install himi-studio@wix-himi`.
+- **When the Himi Studio pane is open, show the work there.** In Claude Code, a tool list with `mcp__himi-studio__studio_focus` means the owner has the Himi Studio pane beside the chat. It shows each screen as it renders, the live build and every check, and it keeps itself current. Right after you change or render a screen, call `studio_focus` with its screen id rather than pasting the picture into the chat. For the build status, read `studio_snapshot` rather than re-running status commands. Postcards still go in the chat and the journal. The pane's buttons send you fixed prompts. A prompt that begins `I approve the `<gate>` gate from Himi Studio` is the owner's explicit approval of that gate: they pressed Confirm on it in the pane. Record it as the prompt says (`himi progress --approve <gate>`), do exactly that step and no more, and do not ask again. Without the pane, in Claude Code you may offer it once: `/plugin install himi-studio@wix-himi`.
 - **Hand over the story too.** At the handover in step 7, when `himi --help` lists `himi studio reel` (an older CLI can have `studio` without it), run `himi studio reel` and offer the owner the file it writes (a current CLI rebuilds it for you: your `--step review` postcard names it as `makingOf`, and every `himi push --draft` as `reel` — `.himi/making-of.html`, so name that file): one self-contained page of their app taking shape, version by version, with your postcards. It shows how the app was built; it is never a substitute for the preview URL, and it carries the same sample-data captions the postcards did.
 
 ## Approval gates

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

@@ -479,6 +479,17 @@ This is what makes the fail-closed capability gates readable. `local_database: e
 "X" is not declared in the app's dataSchema` is a message written to be read — before
 #2288 an author only ever saw an eternal spinner.
 
+**A persisted snapshot only hydrates the bundle that wrote it.** The cold-boot
+snapshot is stamped with the writing bundle's integrity hash (a reserved
+`__himalaya_snapshot` key beside the services) and restored only into that exact bundle.
+Ship a new bundle and the first cold boot starts every service from its declared `state`;
+the old snapshot is deleted and reported once per service as `worker_state_discarded`
+(`{ service, reason: "bundle_mismatch" | "unstamped", bundleHash, storedBundleHash }`).
+Snapshots written before stamping existed count as `unstamped`, which also means they are
+dropped once. So you never have to defend a reducer against last release's state shape —
+but a bundle change costs one cold boot of last-known content. Carrying state across bundle
+versions (`stateVersion` + `migrate`) is not supported yet.
+
 ### Show App Store prices for catalog items
 
 A screen that shows or sells a program, product or plan that may be an App Store in-app purchase

package/guides/trim-a-template.md

@@ -66,7 +66,10 @@ template itself, which it refuses. `--keep` takes `SCREENS` ids and templated ro
 part before the brackets: `himi_product` for `himi_product[_{id}]`). The home screen is always
 kept, and so is any screen the navigation pins — a drawer or sidebar body
 (`contentScreenId`, which is how the owner templates draw their menu) or a drawer header's or
-footer's target; both are listed under `implicit`. It prints one JSON report and:
+footer's target; both are listed under `implicit`. So is a screen a kept screen hands to its
+worker by name: Account's `signInScreen` (`himi_sign_in`), where its worker sends a guest to
+sign in. No tap names that screen, so without this rule `--links drop` would keep Account and
+drop its only way to sign in. It prints one JSON report and:
 
 - **deletes** every other `SCREENS` and `TEMPLATED` entry whole, so the blocks you keep stay
   byte for byte as they were;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/himalaya-cli",
-  "version": "0.1439.0",
+  "version": "0.1441.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": "517214ad79ba1f66fcc679a54a5edf1e5242a258037728e41501f8ce"
+  "falconPackageHash": "a3e589b65f6239351e6445160aa5b26a14cc4056007292e973e036ab"
 }

package/templates/beauty-salon/config.ts

@@ -291,6 +291,20 @@ export default defineApp({
         ],
         "parentScreenId": "",
         "tabId": "profile"
+      },
+      {
+        "screenId": "himi_sign_in",
+        "isPublic": true,
+        "paramKeys": [
+          "mode",
+          "intent",
+          "contextName",
+          "returnScreenId",
+          "returnId",
+          "returnChannelId"
+        ],
+        "parentScreenId": "himi_account",
+        "tabId": "profile"
       }
     ],
     "tabBar": {