@wix/himalaya-cli 0.1488.0 → 0.1490.0

package/guides/widgets.md

@@ -46,13 +46,23 @@ bindings, only **resolved literal values**. Reading the clock is the one allowed
 the last produce (see [refresh](#refresh-taps-and-previews)). A `render` that throws, or returns a
 tree with a binding in it, makes that widget fail to produce.
 
-### There is no live-data path yet
-
-Data your worker fetches **cannot** reach a widget today. `refresh.pushTopic` exists in the type
-definitions, but nothing consumes it yet: setting it does not make the widget update when data
-changes. Plan the widget around what you know when the app is built — a call to action, a
-constant, or a schedule (see [timelines](#content-whose-future-you-know-live-time-and-timelines)) — and let the
-tap take the user into the app, where the live data is.
+### Live data reaches a widget only through the app on the device
+
+The produce above has no credential, so data your worker fetches **cannot** reach a widget through
+`defineWidget`. The one path for live data runs on the device, in the app: the app fetches the
+widget's descriptors, runs their worker **headlessly** with the signed-in session, resolves every
+`$service:` binding to a literal, and publishes the frozen tree itself —
+`WidgetSnapshotSync.publishLocal` on iOS, `WidgetSnapshotSync.publishLocalBlocking` on Android.
+Owner Lite's Today widget works this way (`OwnerLiteHomeWidget`): it refreshes when the app runs or
+the OS grants a background refresh, never on its own. An app that embeds Himalaya apps gets the same
+produce from `HimalayaEmbedSurfaces.publishWidgets` (see
+[embedding → widgets](embedding-sdk.md#home-and-lock-screen-widgets)).
+
+`refresh.pushTopic` exists in the type definitions, but nothing consumes it yet: setting it does not
+make the widget update when data changes. Without a device produce, plan the widget around what you
+know when the app is built — a call to action, a constant, or a schedule (see
+[timelines](#content-whose-future-you-know-live-time-and-timelines)) — and let the tap take the user
+into the app, where the live data is.
 
 ## A widget that stays inside the contract
 
@@ -217,6 +227,9 @@ not, because the car lays out its own rows. It never goes through `defineWidget`
   request, not a schedule.
 - **`deepLink`** is where a tap takes the user. Point it at the screen that shows the live version
   of what the widget summarises.
+- **`GET /v1/widgets?site=<metaSiteId>`** (and `/v1/widget/<id>?site=`) is accepted for a host that
+  shows one app on many sites. The snapshot is still the app's — nothing is produced per site — and
+  the response says so with `x-himalaya-widget-scope: app`.
 - **Preview a widget** while you work: `himi run --watch --content .` serves it at
   `GET /v1/widget/<widget id>`, and `GET /v1/widgets` lists every widget the app produces.
   `himi surfaces --measure-widgets` reports which families your package actually produces.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/himalaya-cli",
-  "version": "0.1488.0",
+  "version": "0.1490.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": "eda28cbf9b0757670a64bf4f2e5d095b82109dc86c7446f6fe7472fb"
+  "falconPackageHash": "cb54373a9c2a773492e66c5579403c0720caa00367681b4479fbc0e3"
 }

package/templates/beauty-salon/config.ts

@@ -217,6 +217,13 @@ export default defineApp({
         "parentScreenId": "himi_account",
         "tabId": "profile"
       },
+      {
+        "screenId": "himi_agenda",
+        "isPublic": true,
+        "paramKeys": [],
+        "parentScreenId": "himi_services",
+        "tabId": "book"
+      },
       {
         "screenId": "himi_plans",
         "isPublic": true,
@@ -366,6 +373,12 @@ export default defineApp({
           "label": "Book",
           "icon": "calendar"
         },
+        {
+          "id": "drawer_agenda",
+          "screenId": "himi_agenda",
+          "label": "Agenda",
+          "icon": "list"
+        },
         {
           "id": "drawer_plans",
           "screenId": "himi_plans",