@wix/himalaya-cli 0.816.0 → 0.818.0

package/guides/branded-lite-site-binding.md

@@ -61,7 +61,7 @@ To create/publish the site's Velo HTTP functions (`/_functions/`),
 | What you want | Mechanism | Not |
 |---|---|---|
 | Point a **local run** at a site | Env vars when starting the **dev-server** (and rebuild / rebake `auth.json`) | A CLI arg like `--msid` |
-| **MSID** for API scope | Comes from the Headless `clientId` (visitor token is site-bound). Optional runtime switch via `branded_lite.select_site` | A dedicated `HIMI_BRANDED_LITE_MSID` env today |
+| **MSID** for API scope | Comes from the Headless `clientId` (visitor token is site-bound) — one site per build, no runtime switch | A dedicated `HIMI_BRANDED_LITE_MSID` env today, or a site picker |
 | **Fixed binary** for users (name, icon, splash/launch color, site) | Edit `provisioning.json` + Wix auth env → `npm run prepare:customer` → build / dist / store | Only flipping an env at runtime |
 
 ---
@@ -129,11 +129,19 @@ Wix refuses to route the token elsewhere. Changing site means a Headless app on
 target site and a matching `clientId` (+ usually `siteUrl`). See
 [wix-auth strategies](../wiki/pages/wix-auth-strategies.md).
 
-Runtime multi-site UX uses `branded_lite.select_site` → `setActiveSite(msid)`
-(persisted under `himi.brandedLite.activeSiteId`). `provisioning.json` `siteId` feeds
-descriptor `defaultSiteId` — the checked-in value is the placeholder `"development-site"`.
-For a single-site white-label, fix **clientId + siteUrl + provisioning.siteId** to the
-real customer site.
+**Branded Lite is single-site, deliberately.** There is no runtime site switch, and a
+build talks to exactly the site its `clientId` was minted on. Profile used to carry a
+"Your sites" picker (`branded_lite.select_site` → `setActiveSite(msid)`, persisted under
+`himi.brandedLite.activeSiteId`); it moved the `wix-site-id` header and nothing else, so
+every read stayed on the baked site while the UI claimed the app had switched. It also
+listed sites through `querySites`, an owner-account API a consumer token cannot call, so
+in practice it showed one row labelled "This site". That path is deleted.
+
+Managing several businesses from one app is **Owner Lite's** job: account auth, a real
+Sites List, a persisted active business, and per-call site scope via `site.forSite(msid)`.
+
+To bind a build to a customer, fix **clientId + siteUrl** (and `provisioning.siteId` for
+the identity the CLI reports) to the real customer site.
 
 ---