@wix/himalaya-cli 0.1115.0 → 0.1116.0

package/dist/cli.mjs

@@ -13140,7 +13140,6 @@ function resolveIdiom(tokens, ctx = {}) {
 var IDIOM_CONTEXTS, UNSAFE_KEYS;
 var init_idiom = __esm({
   "../../core/ts/src/idiom.ts"() {
-    "use strict";
     IDIOM_CONTEXTS = {
       ios: { native: ["ios"] },
       android: { native: ["material"] },
@@ -24719,7 +24718,6 @@ function shouldRevealError(args) {
 var EMAIL_RE, URL_HOST_RE, INTEGER_RE, NUMBER_RE;
 var init_validation = __esm({
   "../../core/ts/src/validation.ts"() {
-    "use strict";
     EMAIL_RE = /^[A-Za-z0-9._%+-]+@[A-Za-z0-9-]+(\.[A-Za-z0-9-]+)*\.[A-Za-z]{2,}$/;
     URL_HOST_RE = /^[A-Za-z0-9-]+(\.[A-Za-z0-9-]+)*(:[0-9]+)?$/;
     INTEGER_RE = /^[+-]?[0-9]+$/;
@@ -29120,7 +29118,6 @@ function validateWorkerSubtree(raw, slotId, policy, actionCatalog) {
 var WORKER_SUBTREE_CEILINGS, ID_PART, ACTION_ID;
 var init_worker_subtree = __esm({
   "../../core/ts/src/worker-subtree.ts"() {
-    "use strict";
     init_worker_subtree_safe_types_generated();
     WORKER_SUBTREE_CEILINGS = Object.freeze({
       maxEncodedBytes: 65536,
@@ -68216,6 +68213,7 @@ __export(cli_exports, {
   APPLY_NEEDS_CLIENT: () => APPLY_NEEDS_CLIENT,
   REDIRECT_NEEDS_CLIENT: () => REDIRECT_NEEDS_CLIENT,
   SITE_FUNCTION_USAGE: () => SITE_FUNCTION_USAGE,
+  applyNeedsClient: () => applyNeedsClient,
   assetFetchFor: () => assetFetchFor,
   noteWithWarnings: () => noteWithWarnings,
   ownerSiteFor: () => ownerSiteFor,
@@ -68224,6 +68222,10 @@ __export(cli_exports, {
 });
 import { readFileSync as readFileSync78 } from "node:fs";
 import { resolve as resolve52 } from "node:path";
+function applyNeedsClient(shell) {
+  if (shell === void 0 || !SHELL_NAMES2.includes(shell)) return true;
+  return !isSiteShell(shell);
+}
 function assetFetchFor(_opts) {
   return pinnedFetch2;
 }
@@ -68236,7 +68238,7 @@ function ownerSiteFor(opts, env = process.env) {
 async function runSiteAnalyze(opts) {
   if (opts.shell !== void 0) assertKnownShell(opts.shell);
   if (!opts.clientId?.trim()) {
-    if (opts.apply) throw Object.assign(new Error(APPLY_NEEDS_CLIENT), { exit: 2 });
+    if (opts.apply && applyNeedsClient(opts.shell)) throw Object.assign(new Error(APPLY_NEEDS_CLIENT), { exit: 2 });
     if (opts.redirectUri?.trim()) throw Object.assign(new Error(REDIRECT_NEEDS_CLIENT), { exit: 2 });
   }
   const fetchImpl = opts.fetchImpl ?? fetch;
@@ -68271,7 +68273,10 @@ async function runSiteAnalyze(opts) {
     try {
       const derived = deriveSiteShell({ siteUrl: result.book.input.siteUrl, look: result.book.look });
       result.provisioningOverlay.site = derived.site;
-      result.warnings = [...result.warnings ?? [], ...derived.notes];
+      const warnings2 = (result.warnings ?? []).map(
+        (w) => !opts.clientId?.trim() && w.startsWith("no --client-id:") ? `no --client-id: fine for --shell ${opts.shell} \u2014 a site shell binds no client, so --apply works without one. Only the vertical probes were skipped, so the catalog has no counts.` : w
+      );
+      result.warnings = [...warnings2, ...derived.notes];
     } catch (e) {
       result.warnings = [
         ...result.warnings ?? [],
@@ -72116,7 +72121,8 @@ var USAGE = `himi \u2014 the Himalaya authoring CLI (remote dev loop)
                                            a brandable shell's content package. --url alone is the
                                            visitor-only pass (published pages, look, copy); --client-id
                                            adds the vertical catalog counts and the app binding, and
-                                           --apply requires it. --shell takes the same
+                                           --apply requires it (not for a site shell, which binds no
+                                           client). --shell takes the same
                                            names 'himi dist --shell' does; default branded-lite.
                                            A SITE shell (brandy) also derives the site's page map
                                            (tabs/drawer from its menu) into the overlay's \`site\`
@@ -72231,7 +72237,7 @@ var COMMANDS = [
   { name: "login", summary: "obtain a scoped serve-control token from Wix identity and store it in ~/.himalaya/serve-targets.json (so push/promote need no hand-pasted token). Three modes: --browser (your own Wix account, no VPN/BO), --wix (HEADLESS \u2014 the machine's own Wix CLI credential; the mode a CI pod or agent container can satisfy), --dpx (Wix employee, reads ~/.dpx/session/token). RFC 0026 WS3.", required: "[--browser|--wix|--dpx] [--target <t>] [--issue-url <url>]" },
   { name: "logout", summary: "remove the stored control token for a target", required: "[--target <t>]" },
   { name: "notify", summary: "`setup` optionally configures Branded/Ping from local customer key files; `status --refresh` reads live backend readiness. Setup may be deferred while building. These use serve-control and require owner plus Wix account authentication. `send`, `tokens`, `doctor`: send a REAL push notification to registered devices (RFC 0036 WS5) \u2014 APNs .p8 over HTTP/2 for iOS, FCM v1 for Android. `send` targets one device (--token / --device <registry id>) or fans out to the whole app (--all), reporting a per-device result; a token the provider says is uninstalled (APNs 410 Unregistered / FCM UNREGISTERED) is auto-disabled, while a merely wrong one (BadDeviceToken \u2014 usually a sandbox/production mismatch) is recorded and left enabled. `tokens` lists the registry. `doctor` reports which credentials resolve and which sender each platform picks. Talks to the admin-server via --admin-url/HIMALAYA_ADMIN_URL, authenticated with --admin-session/HIMALAYA_ADMIN_SESSION. `send --provider ping` is the hosted alternative: the serve plane sends one test notification to one site member through Ping as Himalaya, with owner login instead of provider keys, and reports acceptance, never delivery. NOT `himi push`, which publishes a release.", required: "setup|status [--content <dir>] [--target <t>] [--refresh] [--yes] [--no-push-setup] | send --provider ping [--content <dir>] [--app <a>] [--site <msid>] --member-email <email> --title <s> [--body <s>] --link <url> [--request-id <uuid>] [--dry-run] [--json] | send|tokens|doctor [--app <a>] [--token <t> | --device <id> | --all] [--title <s>] [--body <s>] [--link <url>] [--platform ios|android] [--badge <n>] [--channel <id>] [--silent] [--dry-run] [--json]" },
-  { name: "site", summary: "PROVISION a Wix project, then analyze or extend it. `create` is the one door that makes a site instead of adopting one: POST /funnel/projects/v1/create (a WIX site, a HEADLESS backend, a BRANDED_APP, or a VIBE site), and for headless it also mints the OAuth app whose id IS the `WIX_CLIENT_ID` \u2014 with --redirect-uri already registered, because an unregistered redirect makes native signInDirect fail at redirect-session. `--verticals` REQUIRES `--template` and reports only what Wix confirmed: measured, installing onto a project created from the BLANK template returns 200 while the vertical's API answers 428 forever, because there is no site for it to attach to (the install asks for CREATE_SITE). A real template ships its verticals installed and populated, and installing further ones onto it then works. It MUTATES your Wix account and needs --yes; without it you get the payload and nothing is sent. `list` is the read-only site inventory (with each site's premium flag, which is what explains an installed-but-428 vertical). Auth is the account-scoped `wix token` (no --site), falling back to WIX_API_KEY + WIX_ACCOUNT_ID. `client` is the same OAuth step for a site that ALREADY exists \u2014 the one himi adopts rather than makes \u2014 so a clientId no longer means a manual trip to the dashboard: `client ensure` reconciles rather than mints, because a site can already carry a client with NO registered redirect and shipping that one fails signInDirect at runtime; it reuses a client that carries --redirect-uri, PATCHes one that matches --name but lacks it (unioning, so another app's redirect survives), and creates only when there is nothing to reuse (--new forces a fresh one). --name IS the idempotency key. `client` auth is SITE-scoped (`wix token --site <msid>`) because minting is owner-of-that-site, and --yes gates every mutation: a site that already has a usable client resolves WITHOUT it, but --write-provisioning needs --yes even then because it rewrites a manifest on disk (the dry run's planned.provisioning names the file). That query endpoint IGNORES paging (measured: query.paging, cursorPaging and a top-level paging all return the full set at offset 0), so when pagingMetadata reports more clients than came back, `ensure` REFUSES EVERY outcome \u2014 create, patch AND reuse. Reuse is refused too because pickClient breaks ties on the OLDEST createdDate, so an omitted older same-named MOBILE client with the same redirect would win a later complete read and the resolved clientId would MOVE between runs \u2014 and it gets written into provisioning.json; convergence is what makes a stray duplicate untidy rather than harmful. --name cannot narrow the query (no filter is sent; the name is applied to the rows after they arrive), so the recovery is the dashboard; --new skips the query entirely. A `patched` result is verified against what Wix STORED \u2014 the redirect list is read off the PATCH response, and re-read via GET when the response omits it, because falling back to the list himi just sent would make the guard pass vacuously on exactly the silent no-op it exists to catch. `client list` is the read-only inventory of a site's clients: act on its `shippable` column rather than `hasRedirect`, because shippable ALSO requires a MOBILE applicationType and `ensure` refuses a WEB client \u2014 a WEB one carrying your redirect looks right and is not a candidate \u2014 and it sets truncated:true rather than presenting a partial inventory as the whole one. `analyze --read-only` returns API-only generation context as JSON (identity, access probes, CMS permissions and selected redacted Velo source); it needs no URL/browser and never uploads or applies anything. `analyze` reads a site into a business-book folder (REST + Playwright, GET-only); `--url` alone is the visitor-only pass over the published pages, and `--client-id` adds the vertical probes and the app binding `--apply` requires; `site function` list/get/put/publish/invokes that site's Velo HTTP functions and is not `himi functions` (serve-plane jobs). `--apply` bakes into a brandable shell; `--shell` takes the same names `himi dist --shell` does and defaults to branded-lite, and a shell that ships no prepare:customer is refused by name rather than half-built. `--shell brandy` (the site shell, RFC 0062) also derives the site's page map from its published pages and header menu \u2014 Home first, up to four tabs for the pages a visitor returns to, the rest in the drawer \u2014 into the overlay's `site` block, so it can be edited before `--apply`; only a site shell ever receives that block. It never overwrites any shell's committed apps/<shell>/provisioning.json.", required: "create <name> [--type wix|headless|branded-app|vibe] [--template <guid>] [--verticals stores,bookings,\u2026] [--folder <guid>] [--redirect-uri <uri>] [--no-oauth-app] [--write-provisioning [path]] [--site-url <url>] [--json] --yes | list | client ensure|list --site <msid> [--name <name>] [--redirect-uri <uri>] [--new] [--write-provisioning [path]] [--site-url <url>] [--json] --yes | analyze --read-only [--site <msid>] [--client-id <id>] [--json] | analyze --url <https> [--client-id <id>] [--site <msid>] [--out <dir>] [--redirect-uri <uri>] [--apply] [--shell " + SHELL_ENUM + "] | function list|get|put|publish|invoke [--site <msid>] [--url <https>] [--method GET|POST|PUT|DELETE] [--source <file>] [--body <json>] [--publish] [--invoke]" },
+  { name: "site", summary: "PROVISION a Wix project, then analyze or extend it. `create` is the one door that makes a site instead of adopting one: POST /funnel/projects/v1/create (a WIX site, a HEADLESS backend, a BRANDED_APP, or a VIBE site), and for headless it also mints the OAuth app whose id IS the `WIX_CLIENT_ID` \u2014 with --redirect-uri already registered, because an unregistered redirect makes native signInDirect fail at redirect-session. `--verticals` REQUIRES `--template` and reports only what Wix confirmed: measured, installing onto a project created from the BLANK template returns 200 while the vertical's API answers 428 forever, because there is no site for it to attach to (the install asks for CREATE_SITE). A real template ships its verticals installed and populated, and installing further ones onto it then works. It MUTATES your Wix account and needs --yes; without it you get the payload and nothing is sent. `list` is the read-only site inventory (with each site's premium flag, which is what explains an installed-but-428 vertical). Auth is the account-scoped `wix token` (no --site), falling back to WIX_API_KEY + WIX_ACCOUNT_ID. `client` is the same OAuth step for a site that ALREADY exists \u2014 the one himi adopts rather than makes \u2014 so a clientId no longer means a manual trip to the dashboard: `client ensure` reconciles rather than mints, because a site can already carry a client with NO registered redirect and shipping that one fails signInDirect at runtime; it reuses a client that carries --redirect-uri, PATCHes one that matches --name but lacks it (unioning, so another app's redirect survives), and creates only when there is nothing to reuse (--new forces a fresh one). --name IS the idempotency key. `client` auth is SITE-scoped (`wix token --site <msid>`) because minting is owner-of-that-site, and --yes gates every mutation: a site that already has a usable client resolves WITHOUT it, but --write-provisioning needs --yes even then because it rewrites a manifest on disk (the dry run's planned.provisioning names the file). That query endpoint IGNORES paging (measured: query.paging, cursorPaging and a top-level paging all return the full set at offset 0), so when pagingMetadata reports more clients than came back, `ensure` REFUSES EVERY outcome \u2014 create, patch AND reuse. Reuse is refused too because pickClient breaks ties on the OLDEST createdDate, so an omitted older same-named MOBILE client with the same redirect would win a later complete read and the resolved clientId would MOVE between runs \u2014 and it gets written into provisioning.json; convergence is what makes a stray duplicate untidy rather than harmful. --name cannot narrow the query (no filter is sent; the name is applied to the rows after they arrive), so the recovery is the dashboard; --new skips the query entirely. A `patched` result is verified against what Wix STORED \u2014 the redirect list is read off the PATCH response, and re-read via GET when the response omits it, because falling back to the list himi just sent would make the guard pass vacuously on exactly the silent no-op it exists to catch. `client list` is the read-only inventory of a site's clients: act on its `shippable` column rather than `hasRedirect`, because shippable ALSO requires a MOBILE applicationType and `ensure` refuses a WEB client \u2014 a WEB one carrying your redirect looks right and is not a candidate \u2014 and it sets truncated:true rather than presenting a partial inventory as the whole one. `analyze --read-only` returns API-only generation context as JSON (identity, access probes, CMS permissions and selected redacted Velo source); it needs no URL/browser and never uploads or applies anything. `analyze` reads a site into a business-book folder (REST + Playwright, GET-only); `--url` alone is the visitor-only pass over the published pages, and `--client-id` adds the vertical probes and the app binding `--apply` requires; `site function` list/get/put/publish/invokes that site's Velo HTTP functions and is not `himi functions` (serve-plane jobs). `--apply` bakes into a brandable shell (a site shell needs no `--client-id`: it is visitor-only and binds no client); `--shell` takes the same names `himi dist --shell` does and defaults to branded-lite, and a shell that ships no prepare:customer is refused by name rather than half-built. `--shell brandy` (the site shell, RFC 0062) also derives the site's page map from its published pages and header menu \u2014 Home first, up to four tabs for the pages a visitor returns to, the rest in the drawer \u2014 into the overlay's `site` block, so it can be edited before `--apply`; only a site shell ever receives that block. It never overwrites any shell's committed apps/<shell>/provisioning.json.", required: "create <name> [--type wix|headless|branded-app|vibe] [--template <guid>] [--verticals stores,bookings,\u2026] [--folder <guid>] [--redirect-uri <uri>] [--no-oauth-app] [--write-provisioning [path]] [--site-url <url>] [--json] --yes | list | client ensure|list --site <msid> [--name <name>] [--redirect-uri <uri>] [--new] [--write-provisioning [path]] [--site-url <url>] [--json] --yes | analyze --read-only [--site <msid>] [--client-id <id>] [--json] | analyze --url <https> [--client-id <id>] [--site <msid>] [--out <dir>] [--redirect-uri <uri>] [--apply] [--shell " + SHELL_ENUM + "] | function list|get|put|publish|invoke [--site <msid>] [--url <https>] [--method GET|POST|PUT|DELETE] [--source <file>] [--body <json>] [--publish] [--invoke]" },
   { name: "doctor", summary: 'off-VPN preflight in one shot: probe the PUBLIC data plane (www.wixapis.com \u2014 reachable off-VPN), the INTERNAL serve/control plane for the selected target (VPN-gated), and report auth state (dpx session on disk + stored control token). --dpx additionally runs a live, EADDRINUSE-safe `dpx whoami`. Machine-readable with --json (an unreachable internal plane carries a stable code:"needs_vpn" so an agent branches on the code, not the prose); human-readable otherwise. Never loads the authoring runtime \u2014 works off-repo.', required: "[--target <t>] [--dpx] [--json] [--data-url <url>] [--timeout <ms>]" },
   { name: "upgrade", summary: "install the newest published CLI (`npm i -g @wix/himalaya-cli@latest`) and report what moved. This is the explicit door: himi also updates itself when the running build is more than a week old \u2014 unattended it just does it and re-runs your command, at a terminal it asks first \u2014 and `HIMI_NO_UPDATE_CHECK=1` turns that off, leaving this command as the way to catch up. Reports `unchanged` rather than claiming success when npm exits 0 without moving the version, which is what a registry mirror serving its own pinned copy looks like.", required: "[--json]" },
   { name: "push", summary: "lint + build + publish a release (default --draft: servable via ?release= but NOT live). REFUSES to publish on any error unless --force; --strict promotes warnings. Prints preview + agent-context links. A successful draft push also rebuilds the making-of (.himi/making-of.html, local and offline) and names it as `reel` \u2014 the file to hand the owner beside the preview link. Its postcard carries the home shot only when that shot is newer than the last source edit; otherwise the postcard says why and names `himi render <home> --png`, and the envelope's `postcardPicture: {skipped, render}` leads next[] with that render (the push never renders it itself). The published slug is NAMESPACED per owner \u2014 `<ownerPrefix>.<name>`, composed offline from the control token's ownerPrefix claim, so the CLI and the server derive the identical string and himalaya.content.json is NOT rewritten (a legacy token with no ownerPrefix publishes the declared name unchanged). An app claimed BEFORE namespacing is stored under its FLAT slug, so the claim route answers `alreadyYours` naming that slug and the push adopts it \u2014 reported as `adoptedSlug`, since it is the one case where the published `app` differs from what the declared name composes to. `--no-claim` skips the route that knows this, so a pre-namespacing app pushed with it still fails 403. --visibility public|unlisted decides whether /v1/apps + the Himi Player picker LIST the app (also declarable as `visibility` in himalaya.content.json; omitted, a brand-new app defaults to unlisted \u2014 share by link \u2014 and an existing setting is kept). --account-id names which account owns the app when your Wix session resolves to several (the auto-claim of a brand-new slug cannot guess \u2014 without it a multi-account caller is told to name one). An unforced push of a release that carries SCREENS also refuses when `.himi/ux-audit.json` holds no mobile-UX drive recorded against that release id, or holds one that FAILED (#2955) \u2014 a published draft IS the owner-private preview a customer is handed; `himi ux record` clears it and `--force` overrides it, which the success envelope then says out loud. `--only <selector>` publishes ONLY the named items as a release derived from the app's live release (or `--from-release <id>`), running the identical build + lint gate and simply publishing less; it requires an explicit `--draft` or `--live` because a partial publish has no safe default, never claims a slug, and carries neither attestation nor a source archive (both named in the output). Selectors are comma-separated in ONE `--only`: `changed` (every item whose bytes differ from the base), `screen:<id|glob>`, `bundle:<name>`, `tokens`, `app-config` \u2014 a selected screen drags its logic bundle and a selected bundle drags the screens that reference it, or the bytes land under a key nothing reads.", required: "[--content <dir>] [--draft] [--live] [--force] [--strict] [--label] [--notes] [--visibility public|unlisted] [--no-claim] [--account-id <id>] [--only <selector>] [--from-release <id>] [--accept-regressions] [--accept-partial] [--app <slug>] (--control-token)" },
@@ -79552,10 +79558,11 @@ ${report3.ok ? "OK \u2014 data + serve plane reachable." : typeof report3.hint =
           return 2;
         }
         const redirectFlag = str8(flags["redirect-uri"]);
-        if (!clientId && (flags.apply === true || redirectFlag)) {
-          const { APPLY_NEEDS_CLIENT: APPLY_NEEDS_CLIENT2, REDIRECT_NEEDS_CLIENT: REDIRECT_NEEDS_CLIENT2 } = await Promise.resolve().then(() => (init_cli(), cli_exports));
+        const { APPLY_NEEDS_CLIENT: APPLY_NEEDS_CLIENT2, REDIRECT_NEEDS_CLIENT: REDIRECT_NEEDS_CLIENT2, applyNeedsClient: applyNeedsClient2 } = await Promise.resolve().then(() => (init_cli(), cli_exports));
+        const applyWantsClient = flags.apply === true && applyNeedsClient2(str8(flags.shell));
+        if (!clientId && (applyWantsClient || redirectFlag)) {
           io.error(JSON.stringify({
-            error: flags.apply === true ? APPLY_NEEDS_CLIENT2 : REDIRECT_NEEDS_CLIENT2,
+            error: applyWantsClient ? APPLY_NEEDS_CLIENT2 : REDIRECT_NEEDS_CLIENT2,
             usage: analyzeUsage
           }));
           return 2;

package/guides/wix-business-context.md

@@ -161,11 +161,13 @@ The plane has no headless browser (`look.unavailable: no_browser_on_plane`). Own
 `himi-brandy`, the site shell, opens the customer's live website as native-framed tabs, so its contract is a `site` block: which website, and which of its pages are tabs, drawer rows or overflow rows. `--shell brandy` derives that block into `provisioning.overlay.json`:
 
 ```bash
-himi site analyze --url https://owner.wixsite.com/site --client-id <id> --shell brandy   # writes site.pages
+himi site analyze --url https://owner.wixsite.com/site --shell brandy   # writes site.pages
 # edit site.pages in .himi/business-book/provisioning.overlay.json if the map needs it
-himi site analyze --url https://owner.wixsite.com/site --client-id <id> --shell brandy --apply
+himi site analyze --url https://owner.wixsite.com/site --shell brandy --apply
 ```
 
+No `--client-id` is needed here: a site shell is visitor-only, its pages are the site itself, and its contract binds no Headless client. For an off-repo brandy app (`himi init --template brandy`), run the `--apply` inside the app folder: it writes the derived `site` block into the package's own `provisioning.json`, which the template's `config.ts` builds every tab and screen from.
+
 The map comes from what the analysis already reads without owner credentials, because Wix has no public menu API: the published page list (`look.sitePages`), the header menu the crawl saw (`look.navLinks`, label and href), and each page's role.
 
 - **Order and labels** follow the site's own menu. Links to other hosts, and repeat links to the same page, are dropped.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/himalaya-cli",
-  "version": "0.1115.0",
+  "version": "0.1116.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": [
@@ -67,5 +67,5 @@
       "artifactId": "himalaya-cli"
     }
   },
-  "falconPackageHash": "19c38309340f59147c2cb6f97746d920feacc058a4c256331d9f4422"
+  "falconPackageHash": "6d8f58d4b9f65728efd1d2728c9c1567bbe8ea1cb014bda9ee1afc50"
 }

package/templates/brandy/README.md

@@ -0,0 +1,60 @@
+# __HIMI_APP_NAME__ — your website as an app
+
+A **site shell**: your live Wix website, framed as a native app. Every tab and drawer row is one of
+your site's own pages, shown in a WebView under a native tab bar, drawer and splash in your brand
+colours. The site's own header, footer and Wix ads are hidden. It is the fastest way to ship an
+existing website as an app, and each tab can later be replaced by a native screen.
+
+## Point it at your site
+
+The whole app is the `site` block in `provisioning.json`:
+
+```json
+{
+  "site": {
+    "origin": "https://your-account.wixsite.com/your-site",
+    "kind": "wix",
+    "pages": [
+      { "id": "home", "title": "Home", "path": "/", "icon": "home" },
+      { "id": "blog", "title": "Blog", "path": "/blog", "icon": "newspaper" },
+      { "id": "contact", "title": "Contact", "path": "/contact", "icon": "mail", "placement": "drawer" }
+    ],
+    "chrome": { "hideSiteHeader": true, "hideSiteFooter": true, "hideWixAds": true }
+  }
+}
+```
+
+The placeholder origin above is not a real site. Replace it by deriving the block from your site's
+own menu, from inside this folder:
+
+```bash
+himi site analyze --url https://your-account.wixsite.com/your-site --shell brandy --apply
+```
+
+That writes the derived `site` block into this `provisioning.json` and your site's colours into
+`tokens.json`. No `--client-id` is needed, because a site shell reads nothing through a Wix client.
+To review the map first, leave out `--apply`: the block is then only written to
+`.himi/business-book/provisioning.overlay.json`. You can always edit the block by hand.
+
+- **`origin`** is your published site, `https` only. A free site's path (`/your-site`) is part of it.
+- **`pages`** are paths relative to the origin. Each needs a unique `id` (`a-z`, `0-9`, `_`) and must
+  not use `page`, which is reserved.
+- **`placement`** is `tab` (the default), `drawer` or `overflow`. At most four tabs are shown, and
+  `home` must be the first of them: the app opens on its first tab.
+- **`icon`** is a design-system icon name (`home`, `bag`, `calendar`, `ticket`, `newspaper`, `mail`,
+  `info`, `tag`, `photo`, `person`, `globe`, …).
+- **`chrome`** hides the site's own header (on inner pages), its footer and the Wix ads banner.
+  Every flag defaults to hidden.
+
+`config.ts` validates the block whenever the app loads, so an `http` origin, a duplicate id or a map
+with no tab fails `himi validate`, `himi render` and `himi push` rather than shipping.
+
+## Loop
+
+```bash
+himi build && himi validate --strict   # derive the screens and check them
+himi render site_home                  # the home tab (a WebView: headless render reports it, it does not paint it)
+himi push --draft                      # publish a draft release and open the web preview
+```
+
+Your colours live in `tokens.json` and your name in `config.ts`.

package/templates/brandy/config.ts

@@ -0,0 +1,76 @@
+// Your app's configuration — a SITE SHELL. Your live website is the app: every tab and drawer
+// row is one of its pages, shown in a native-framed WebView under a native tab bar and drawer.
+//
+// Nothing here names a page. The pages come from the `site` block of ./provisioning.json, so you
+// change the app by changing that block — by hand, or with
+//   himi site analyze --url https://<your-site> --shell brandy
+// which derives it from your site's own menu. Inspect the live values any time with
+// `himi context`; see `himi docs app-config`.
+import {
+  assertSiteShellConfig,
+  defineApp,
+  siteLinkableScreens,
+  siteNav,
+  siteNavConfig,
+  type SiteShellConfig,
+} from "@himalaya/core";
+import { ConsoleTelemetrySink } from "@himalaya/telemetry-console";
+import provisioning from "./provisioning.json" with { type: "json" };
+
+/** Your website and its page map. Validated here, so a mistake in provisioning.json (an http
+ *  origin, a duplicate page id, no tab) fails `himi validate`, `render` and `push` instead of
+ *  shipping a broken app. */
+export const site = provisioning.site as SiteShellConfig;
+assertSiteShellConfig(site);
+const nav = siteNav(site);
+// The app opens on its first tab, and everything that names the home screen (`himi init`,
+// `himi render`, agent tooling) names `site_home` — so the `home` page must BE the first tab.
+if (nav.tabs[0]?.screenId !== "site_home") {
+  throw new Error('provisioning.json: the "home" page must be the first tab — list it first in site.pages');
+}
+
+export default defineApp({
+  id: "__HIMI_APP_DOTID__",
+  name: "__HIMI_APP_NAME__",
+  bundleId: "__HIMI_APP_DOTID__",
+  applicationId: "__HIMI_APP_DOTID__",
+  // Placeholders — an over-the-air app never consumes these. Leave as-is.
+  schemaPackage: "@example/__HIMI_APP_SLUG__-schema",
+  schemaPackageRange: { min: 9900, max: 9909 },
+  // Placeholders — only a local server would read these. Leave as-is.
+  ports: { devServer: 8190, web: 5390 },
+  // Visitor-only: your site's own pages handle anything a visitor does.
+  auth: { providerId: "none", config: {} },
+  telemetry: ConsoleTelemetrySink(),
+  serverUrls: {
+    screen: "http://localhost:8190/v1",
+    actions: "http://localhost:8190/v1/actions",
+    sync: "http://localhost:8190/v1/sync",
+  },
+  capabilities: [],
+  // Your brand colours paint the NATIVE chrome (tabs, drawer, splash); the site paints its pages.
+  designTokensPath: "./tokens.json",
+  // "Ready" means the first page has painted, not just the app shell — otherwise the splash
+  // fades into a blank WebView. It still dismisses after 5s on a slow link.
+  splash: {
+    enabled: true,
+    backgroundColor: "accentPrimary",
+    caption: "__HIMI_APP_NAME__",
+    minVisibleMs: 400,
+    maxHoldMs: 5000,
+    readySignal: "first_content",
+  },
+  navigation: {
+    // Bottom tabs on a phone, a sidebar on a larger screen; the drawer lists every page that is
+    // not `overflow`. At most four tabs — each keeps its page loaded while you switch.
+    navKind: "responsive",
+    scheme: "himalaya-__HIMI_APP_SLUG__",
+    deepLinkPatterns: [],
+    linkableScreens: siteLinkableScreens(site),
+    // A notification or app link carrying one of your site's URLs opens that page's tab.
+    site: siteNavConfig(site),
+    tabBar: { items: nav.tabs },
+    drawer: { items: nav.drawer },
+  },
+  entities: {},
+});

package/templates/brandy/dev/index.ts

@@ -0,0 +1,25 @@
+// Your app's screens. Each one is a page of your website — a WebView screen built from the
+// `site` block of ../provisioning.json — so this file holds no screen of its own. Change the
+// pages by changing that block, never this file.
+import { siteScreens } from "@himalaya/core";
+import config, { site } from "../config.js";
+
+const SCREENS = siteScreens(site);
+// The home screen is always the `home` page's: `site_home`. A literal on purpose — `himi init`
+// and the agent tooling read `homeScreenId` from this file as written; config.ts refuses a map
+// whose first tab is anything else, so the literal and the tab bar cannot disagree.
+
+export default {
+  config,
+  homeScreenId: "site_home",
+  screens: {
+    // A fresh copy per build: descriptors are pure functions of the site block.
+    exact: Object.fromEntries(Object.keys(SCREENS).map((id) => [id, () => structuredClone(SCREENS[id])])),
+    templated: [],
+  },
+  actions: [],
+  createStore: () => ({}),
+  // Every page is seeded, so the whole tab bar and drawer work on a cold offline start (each
+  // WebView then shows its own offline state until the network returns).
+  seed: { screens: SCREENS, data: {} },
+};

package/templates/brandy/himalaya.content.json

@@ -0,0 +1,5 @@
+{
+  "name": "__HIMI_APP_NAME__",
+  "icon": "icon.png",
+  "target": "prod"
+}

package/templates/brandy/himalaya.template.json

@@ -0,0 +1,6 @@
+{
+  "title": "Brandy — your website as an app",
+  "description": "A site shell: the customer's live Wix website as a native app. Every tab and drawer row is one of the site's own pages in a native-framed WebView, with a native tab bar, drawer, splash and brand colours; the site's header, footer and Wix ads are hidden. The page map lives in provisioning.json (`site`), and `himi site analyze --url <site> --shell brandy` derives it from the site's own menu. Start here to ship an existing website as an app today and move tabs to native screens later.",
+  "tags": ["wix", "website", "site-shell", "webview", "tabs", "drawer", "no-code", "day-zero", "consumer"],
+  "category": "consumer"
+}

package/templates/brandy/platforms.json

@@ -0,0 +1 @@
+{"macos":false}

package/templates/brandy/provisioning.json

@@ -0,0 +1,12 @@
+{
+  "site": {
+    "origin": "https://your-account.wixsite.com/your-site",
+    "kind": "wix",
+    "pages": [
+      { "id": "home", "title": "Home", "path": "/", "icon": "home" },
+      { "id": "blog", "title": "Blog", "path": "/blog", "icon": "newspaper" },
+      { "id": "contact", "title": "Contact", "path": "/contact", "icon": "mail", "placement": "drawer" }
+    ],
+    "chrome": { "hideSiteHeader": true, "hideSiteFooter": true, "hideWixAds": true }
+  }
+}

package/templates/brandy/tokens.json

@@ -0,0 +1,128 @@
+{
+  "colors": {
+    "surfacePrimary": {
+      "light": "#FFFFFF",
+      "dark": "#0D1117",
+      "highContrast": "#000000"
+    },
+    "surfaceSecondary": {
+      "light": "#F4F7F8",
+      "dark": "#161B22",
+      "highContrast": "#111111"
+    },
+    "surfaceElevated": {
+      "light": "#FFFFFF",
+      "dark": "#1D2228",
+      "highContrast": "#111111"
+    },
+    "surfaceSubtle": {
+      "light": "#F8FAF9",
+      "dark": "#121821",
+      "highContrast": "#111111"
+    },
+    "surfaceTertiary": {
+      "light": "#E9EEF0",
+      "dark": "#232A32",
+      "highContrast": "#1A1A1A"
+    },
+    "textPrimary": {
+      "light": "#1F2328",
+      "dark": "#E6EDF3",
+      "highContrast": "#FFFFFF"
+    },
+    "textSecondary": {
+      "light": "#59636E",
+      "dark": "#848D98",
+      "highContrast": "#CCCCCC"
+    },
+    "textTertiary": {
+      "light": "#7D8791",
+      "dark": "#6E7681",
+      "highContrast": "#CCCCCC"
+    },
+    "textOnAccent": {
+      "light": "#FFFFFF",
+      "dark": "#FFFFFF",
+      "highContrast": "#000000"
+    },
+    "accentPrimary": {
+      "light": "#0969DA",
+      "dark": "#1E72C7",
+      "highContrast": "#58A6FF"
+    },
+    "accentSecondary": {
+      "light": "#087F5B",
+      "dark": "#1C8968",
+      "highContrast": "#FFFFFF"
+    },
+    "accentSurface": {
+      "light": "#E2EDF8",
+      "dark": "#0C2540",
+      "highContrast": "#FFFFFF"
+    },
+    "success": {
+      "light": "#1A7F37",
+      "dark": "#3FB950",
+      "highContrast": "#3FB950"
+    },
+    "successSurface": {
+      "light": "#E9F8EC",
+      "dark": "#12331B",
+      "highContrast": "#FFFFFF"
+    },
+    "warning": {
+      "light": "#9A6700",
+      "dark": "#D29922",
+      "highContrast": "#D29922"
+    },
+    "warningSurface": {
+      "light": "#FFF5D8",
+      "dark": "#3A2C0A",
+      "highContrast": "#FFFFFF"
+    },
+    "danger": {
+      "light": "#CF222E",
+      "dark": "#F85149",
+      "highContrast": "#FF5555"
+    },
+    "dangerSurface": {
+      "light": "#FFEDEA",
+      "dark": "#3A1513",
+      "highContrast": "#FFFFFF"
+    },
+    "border": {
+      "light": "#D8DEE4",
+      "dark": "#30363D",
+      "highContrast": "#FFFFFF"
+    }
+  },
+  "spacing": {
+    "xs": 4,
+    "sm": 8,
+    "md": 12,
+    "lg": 16,
+    "xl": 24
+  },
+  "typography": {
+    "title1": {
+      "size": 28,
+      "weight": 700,
+      "line": 1.2
+    },
+    "body": {
+      "size": 16,
+      "weight": 400,
+      "line": 1.5
+    },
+    "caption": {
+      "size": 13,
+      "weight": 400,
+      "line": 1.4
+    }
+  },
+  "radius": {
+    "sm": 4,
+    "md": 8,
+    "lg": 12
+  }
+}