@wix/himalaya-cli 0.942.0 → 0.944.0

package/guides/component-reference.md

@@ -180,6 +180,36 @@ The two share a leaf name and mean opposite things — descriptor side takes the
 registry takes the HEX — so a validator error about `shadows.card.color` is not this table
 contradicting itself.
 
+## What a control sends (action payloads)
+
+A component's props say what it READS. This says what it SENDS: the value a control injects
+into the `Action` it dispatches, so a Tier-5 reducer can be written from this page instead of
+from trial and error.
+
+1. **The payload is in `args`.** `Action.args` is a `Value`, so it holds the real type
+   (bool / int / double / array), and every host merges `{...params, ...args}` with `args`
+   winning. Read `args` first.
+2. **`params` may mirror it, but only for a string.** `Action.params` is declared
+   `map<string,string>` in the descriptor schema; a number, bool or array there is a type
+   violation even where JavaScript tolerates it.
+3. **The key and the encoding below are normative.** A renderer that sends a different key —
+   or no payload at all — is a divergence, and every one that exists today is printed with the
+   component it affects, because that is precisely the case a reducer has to be written around.
+
+Every row here is generated from the platform's own payload contract and re-checked against
+all four renderers on every build, so it cannot drift from what the components actually send.
+
+**What it covers, and what it does not.** The contract is about **value controls** — the ones
+whose callback carries the thing the user chose or typed. A value callback absent from a
+component's block injects nothing: it dispatches the author's action verbatim, so any
+discriminator must come from the `args` the author wrote (`Chip.onRemove` and
+`DisclosureGroup.onToggle` are the two that work this way today).
+
+That is NOT a statement about every action a component can fire. Gesture and event callbacks —
+`Map.onMapTap` / `onMarkerTap`, a media player's progress events — inject payloads of their
+own and are outside this contract, so read the component's own prop documentation for those
+rather than concluding from a missing row here that nothing arrives.
+
 ## Props (verbatim from schema.ts)
 
 ### Core
@@ -379,6 +409,12 @@ export type TextProps = TextContent & {
    *  the current left-to-right behavior. Both renderers honor it (parity). */
   textDirection?: "auto" | "ltr" | "rtl";
   decoration?: "underline" | "strikethrough";
+  /** EXTRA SPACE BETWEEN LINES, in points/px — added ON TOP of the line height the `style`
+   *  token already sets. It is NOT a multiple: `lineSpacing: 6` means six points of extra
+   *  leading, not six times the font size, and every renderer agrees on that. To
+   *  change the line height as a ratio of the font size, set the typography token's `line`
+   *  instead; that is where a body style's 1.4/1.7 lives. Absent/0 = the token's own line
+   *  height, which is the right answer for almost every screen. */
   lineSpacing?: number;
   /** Per-item gate (usually an `$item.` field pre-substituted per row): when it
    *  resolves empty, the text collapses to zero size instead of taking layout. */
@@ -519,6 +555,21 @@ export interface TextFieldProps {
 }
 ```
 
+**Dispatches** — see [What a control sends](#what-a-control-sends-action-payloads):
+
+| callback | key | type |
+|---|---|---|
+| `onChange` | `value` | string |
+| `onSubmit` | `value` | string |
+
+> `onChange` — The typed text, clamped to maxLength by the renderer.
+
+> ⚠️ **`onChange` on ios + android + web — ALSO sends:** additionally injects `fieldId` when the text field is inside a Form, so one worker action can serve several fields. Additive, not conflicting, and shipped bundles already duck-type it. Every arm guards on the field actually being registered in a Form, so a standalone TextField still sends no `fieldId`. Still a divergence rather than a promoted contract key because RN does not send it and the contract does not require it.
+
+> `onSubmit` — The field's current text at return-key time.
+
+> ⚠️ **`onSubmit` on ios + android + web — ALSO sends:** additionally injects `fieldId` when the text field is inside a Form, so one worker action can serve several fields. Additive, not conflicting, and shipped bundles already duck-type it. Every arm guards on the field actually being registered in a Form, so a standalone TextField still sends no `fieldId`. Still a divergence rather than a promoted contract key because RN does not send it and the contract does not require it.
+
 #### Toggle
 
 ```ts
@@ -543,6 +594,16 @@ export interface ToggleProps {
 }
 ```
 
+**Dispatches** — see [What a control sends](#what-a-control-sends-action-payloads):
+
+| callback | key | type |
+|---|---|---|
+| `onChange` | `value` | boolean |
+
+> `onChange` — The NEXT state, not the previous one.
+
+> ⚠️ **`onChange` on ios — ALSO sends:** additionally injects `fieldId` when the control is inside a Form — via bindingForBool, for a Toggle nested in a FormField.
+
 #### Stepper
 
 ```ts
@@ -556,6 +617,16 @@ export interface StepperProps {
 }
 ```
 
+**Dispatches** — see [What a control sends](#what-a-control-sends-action-payloads):
+
+| callback | key | type |
+|---|---|---|
+| `onChange` | `value` | int |
+
+> `onChange` — The clamped next value. A no-change step must not dispatch.
+
+> ⚠️ **`onChange` on web + rn — DIVERGES:** mirrors the value into `params` as a NUMBER. Violates rule 2 — `Action.params` is `map<string,string>`. Harmless through the JS hosts, wrong on the wire.
+
 #### Avatar
 
 ```ts
@@ -712,6 +783,16 @@ export interface PickerProps {
 
 > ⚠️ **Implemented, but these props are inert on ios:** `optionsPath`, `placeholder` — `optionsPath` does not bind options; `placeholder` is not shown.
 
+**Dispatches** — see [What a control sends](#what-a-control-sends-action-payloads):
+
+| callback | key | type |
+|---|---|---|
+| `onChange` | `selectedId` | string |
+
+> `onChange` — The chosen option's id — an enum the reducer switches on, never an index.
+
+> ⚠️ **`onChange` on ios — DIVERGES:** inside a FormField, the non-text kinds store into the form bag and RETURN without dispatching — the renderer's own code. A formField({kind:'picker'}) onChange is a dead action on iOS while every other arm fires it.
+
 #### DatePicker
 
 ```ts
@@ -728,6 +809,20 @@ export interface DatePickerProps {
 
 > ⚠️ **Implemented, but these props are inert on ios:** `mode`, `minUnix`, `maxUnix`, `valuePath` — The picker itself renders as a native date wheel — these four props are inert: `mode: "time"` still renders a date wheel; `minUnix`/`maxUnix` do not clamp; `valuePath` does not bind.
 
+**Dispatches** — see [What a control sends](#what-a-control-sends-action-payloads):
+
+| callback | key | type |
+|---|---|---|
+| `onChange` | `value` | unix-seconds-string |
+
+> `onChange` — Unix SECONDS, string-encoded so the params mirror stays legal. iOS ships `valueUnix` as an int instead; RN ships nothing. The normative key is `value` because that is what three of four arms already use for every other scalar control.
+
+> ⚠️ **`onChange` on ios — DIVERGES:** sends `valueUnix` as an int instead of the contract's `value`. Only web conforms. This is the widest split in the vocabulary and the clearest argument for the file.
+
+> ⚠️ **`onChange` on rn — DIVERGES:** dispatches the bare action with no date at all.
+
+> ⚠️ **`onChange` on ios — DIVERGES:** inside a FormField, the non-text kinds store into the form bag and RETURN without dispatching — the renderer's own code. A formField({kind:'picker'}) onChange is a dead action on iOS while every other arm fires it.
+
 ### State envelopes
 
 #### StatefulSection
@@ -793,6 +888,17 @@ export interface SearchFieldProps {
 }
 ```
 
+**Dispatches** — see [What a control sends](#what-a-control-sends-action-payloads):
+
+| callback | key | type |
+|---|---|---|
+| `onChange` | `value` | string |
+| `onSubmit` | `value` | string |
+
+> `onChange` — Debounced by `debounceMs` before dispatch.
+
+> `onSubmit` — These two rows share a control and key, so they are NOT independently gated: a payload observation cannot say which callback produced it, and a helper-mediated dispatch does not name the callback at the write site at all. The gate proves the callback is still referenced in the component that dispatches, not that this callback carries the payload.
+
 #### FilterChips
 
 ```ts
@@ -807,6 +913,16 @@ export interface FilterChipsProps {
 }
 ```
 
+**Dispatches** — see [What a control sends](#what-a-control-sends-action-payloads):
+
+| callback | key | type |
+|---|---|---|
+| `onChange` | `selectedIds` | string-array |
+
+> `onChange` — The full selection AFTER the toggle, not the chip that moved.
+
+> ⚠️ **`onChange` on rn — DIVERGES:** mirrors `selectedIds` into `params` as an ARRAY. Rule-2 violation.
+
 ### Navigation primitives
 
 #### Tabs
@@ -827,6 +943,12 @@ export interface TabsProps {
 
 > ⚠️ **Implemented, but these props are inert on ios:** `style` — The tab bar itself renders — only `style` is inert: `swipe` still renders as top tabs.
 
+**Dispatches** — see [What a control sends](#what-a-control-sends-action-payloads):
+
+| callback | key | type |
+|---|---|---|
+| `onChange` | `selectedId` | string |
+
 #### SegmentedControl
 
 ```ts
@@ -840,6 +962,12 @@ export interface SegmentedControlProps {
 }
 ```
 
+**Dispatches** — see [What a control sends](#what-a-control-sends-action-payloads):
+
+| callback | key | type |
+|---|---|---|
+| `onChange` | `selectedId` | string |
+
 #### Carousel
 
 ```ts
@@ -1056,6 +1184,20 @@ export interface SliderProps {
 
 > ⚠️ **Implemented, but these props are inert on ios:** `debounceMs` — `debounceMs` does not throttle the onChange stream.
 
+**Dispatches** — see [What a control sends](#what-a-control-sends-action-payloads):
+
+| callback | key | type |
+|---|---|---|
+| `onChange` | `value` | double |
+
+> `onChange` — Range mode additionally sends `upperValue`.
+
+> ⚠️ **`onChange` on web — DIVERGES:** dispatches the bare action — the renderer's own code — with no injected value.
+
+> ⚠️ **`onChange` on rn — DIVERGES:** renders a static visual and never dispatches at all. RN Slider is unimplemented rather than divergent; listed so the gap is counted, not hidden.
+
+> ⚠️ **`onChange` on ios + android — ALSO sends:** range mode additionally sends `upperValue` beside `value`. Additive, and the contract's Slider note already describes it. Same problem as groupId: allowed by a hard-coded list rather than declared.
+
 #### SelectionControl
 
 ```ts
@@ -1074,6 +1216,20 @@ export interface SelectionControlProps {
 }
 ```
 
+**Dispatches** — see [What a control sends](#what-a-control-sends-action-payloads):
+
+| callback | key | type |
+|---|---|---|
+| `onChange` | `value` | boolean |
+
+> `onChange` — The next checked state. iOS additionally sends `groupId` for radio groups.
+
+> ⚠️ **`onChange` on web — DIVERGES:** dispatches the bare action — the renderer's own code — with no injected value.
+
+> ⚠️ **`onChange` on rn — DIVERGES:** mirrors the value into `params` as a BOOLEAN.
+
+> ⚠️ **`onChange` on ios — ALSO sends:** additionally sends `groupId` so a radio group can identify which set changed. Additive, not conflicting. It was previously hard-coded as an allowed key in the gate, which put it outside the contract — the one place this PR claims is the single source of truth.
+
 #### ActivityIndicator
 
 ```ts
@@ -1200,6 +1356,16 @@ export interface ChipsInputProps {
 
 > ⚠️ **Implemented, but these props are inert on ios:** `onAdd` — `onAdd` never dispatches.
 
+**Dispatches** — see [What a control sends](#what-a-control-sends-action-payloads):
+
+| callback | key | type |
+|---|---|---|
+| `onRemove` | `value` | string |
+
+> `onRemove` — The removed chip's value.
+
+> ⚠️ **`onRemove` on web — DIVERGES:** dispatches the bare action — the renderer's own code — with no injected value.
+
 ### Structure & disclosure
 
 #### Section
@@ -1296,6 +1462,20 @@ export interface RatingProps {
 }
 ```
 
+**Dispatches** — see [What a control sends](#what-a-control-sends-action-payloads):
+
+| callback | key | type |
+|---|---|---|
+| `onChange` | `value` | int |
+
+> `onChange` — 1-based star index.
+
+> ⚠️ **`onChange` on web + rn — DIVERGES:** writes the value into `params` ONLY, never `args`. Survives only because the Tier-5 hosts merge params into args. Any consumer reading `args` — which rule 1 says is the payload map — gets nothing.
+
+> ⚠️ **`onChange` on ios — DIVERGES:** sends `value` as .double where the contract says int.
+
+> ⚠️ **`onChange` on web + rn — DIVERGES:** stringifies the 1-based index into `params` (`String(i + 1)`) for a control the contract declares `int`. Rule 2 permits a params mirror only for string-encoded values, and Rating is int. The earlier expression heuristic missed it because `String(i + 1)` does not look like a literal — it surfaced only once rule 2 keyed off the declared encoding.
+
 #### Chart
 
 ```ts
@@ -1463,6 +1643,16 @@ export interface WheelPickerProps {
 }
 ```
 
+**Dispatches** — see [What a control sends](#what-a-control-sends-action-payloads):
+
+| callback | key | type |
+|---|---|---|
+| `onChange` | `selectedId` | string |
+
+> ⚠️ **`onChange` on rn — DIVERGES:** writes `params.value = String(id)` but `args.selectedId = id` — a different key in each map. Conforms on `args` (rule 1) but the params mirror uses the wrong key, so a params-reading consumer sees a key no other arm sends.
+
+> ⚠️ **`onChange` on web — DIVERGES:** renders a static window of options and never dispatches — the case has no onAction. Unimplemented on web rather than divergent. Surfaced by the missing-site assertion; the other four it reported were blind spots in the scan, now fixed.
+
 #### ColorPicker
 
 ```ts
@@ -1475,6 +1665,16 @@ export interface ColorPickerProps {
 }
 ```
 
+**Dispatches** — see [What a control sends](#what-a-control-sends-action-payloads):
+
+| callback | key | type |
+|---|---|---|
+| `onChange` | `value` | string |
+
+> `onChange` — Hex, including the leading '#'.
+
+> ⚠️ **`onChange` on web + rn — DIVERGES:** writes the value into `params` ONLY, never `args`. Survives only because the Tier-5 hosts merge params into args. Any consumer reading `args` — which rule 1 says is the payload map — gets nothing.
+
 #### OtpInput
 
 ```ts
@@ -1494,6 +1694,21 @@ export interface OtpInputProps {
 
 > ⚠️ **Implemented, but these props are inert on ios:** `onChange`, `onComplete` — Neither callback dispatches.
 
+**Dispatches** — see [What a control sends](#what-a-control-sends-action-payloads):
+
+| callback | key | type |
+|---|---|---|
+| `onChange` | `value` | string |
+| `onComplete` | `value` | string |
+
+> `onChange` — The assembled code. Only RN dispatches today; web, iOS and Android render the boxes read-only.
+
+> ⚠️ **`onChange` on web + ios + android — DIVERGES:** renders the digit boxes without wiring onChange — the control dispatches nothing. Unimplemented rather than divergent, but it must be declared: leaving OtpInput out of the contract is what let the gate whitelist RN's payload without checking it.
+
+> `onComplete` — Fires once the last box is filled, carrying the same assembled code as onChange. Declared separately because it is a second public callback — leaving it out left one outside the contract.
+
+> ⚠️ **`onComplete` on web + ios + android — DIVERGES:** renders the digit boxes without wiring onChange — the control dispatches nothing. Unimplemented rather than divergent, but it must be declared: leaving OtpInput out of the contract is what let the gate whitelist RN's payload without checking it.
+
 ### Cross-cutting & media
 
 #### Fab

package/guides/recipe-dynamic-list.md

@@ -14,6 +14,13 @@ lists) and `apps/family-cart` (cart list). The `examples/dynamic-list.*` pair th
 card grids). `Carousel` and `Menu` take `itemsPath` the same way. Do **not** hand-roll
 a "VStack of Cards" — that renders only static items and can't bind live data.
 
+**`Grid` is not a `LazyList` with one column.** It shares `itemsPath` and the row
+template, and nothing else: the gesture props in §5 (`onPullToRefresh`, `pagination`)
+and `stickyHeader`/`rowSwipeActions` are declared on `LazyListProps` only. A key `Grid`
+does not declare is **silently dropped** by the native decoders (`ignoreUnknownKeys =
+true`) — `himi validate` catches it and names the declared set, but nothing catches it
+at runtime. If you need pull-to-refresh or load-more, use `LazyList`.
+
 ## The shape (canonical off-repo)
 
 ```jsonc
@@ -70,6 +77,25 @@ including derived presentation fields (`initial` for an avatar letter, `hasImage
 booleans, pre-formatted date lines). Vertical-client responses are raw REST JSON —
 map them defensively; typed-looking fields can be absent at runtime.
 
+**One carve-out, and it is the useful one: a NESTED REPEATER may bind to the row's own
+array.** "Flat fields" is about *scalar* bindings — `$item.price`, not
+`$item.priceData.formatted.amount`. A `Carousel`/`LazyList`/`Grid` *inside* a row template
+may set `itemsPath: "$item.<field>"` and render that element's own array, with its own
+`$item.` scope one level down. All four renderers resolve it as of #2265; before that fix web
+rendered zero rows silently, which is why older guidance says it cannot be done. So a photo
+carousel per feed row **is** expressible:
+
+```jsonc
+{ "id": "photos_$item.id", "body": { "package": "himalaya", "type": "Carousel",
+    "props": { "itemsPath": "$item.images",           // ← the ROW's array, not a $service: path
+               "items": [ { "id": "photo_$item.url", "body": { "package": "himalaya",
+                            "type": "Image", "props": { "url": "$item.url" } } } ] } } }
+```
+
+`normalize()` still has to put a real array on the row (`images: []`, never `null`), and the
+inner template obeys every rule above — flat scalar fields, no strict-enum bindings. Keep the
+nesting to one level: a carousel of carousels is legal and unreadable.
+
 ## 3. The descriptor binds the array
 
 ```jsonc
@@ -130,8 +156,10 @@ full state-machine idiom: `himi docs recipe-four-state`.
 
 ## 5. Refresh + load-more gestures (RFC 0008)
 
-`LazyList` (and `Grid` in list mode) takes two optional gesture props — both are
-plain action wiring, no new worker concepts:
+`LazyList` takes two optional gesture props — both are plain action wiring, no new
+worker concepts. **`LazyList` only**: `GridProps` declares `items`, `columns`,
+`columnsMedium`, `columnsExpanded`, `spacing`, `itemsPath` and `staggerMs`, and the
+native decoders drop anything else without a word:
 
 ```jsonc
 "props": {
@@ -159,6 +187,21 @@ plain action wiring, no new worker concepts:
 - APIs that don't page (or v1 fallbacks without cursors) simply never set
   `nextCursor` — the gesture props are safe to leave in place.
 
+## 6. Tapping a row into a detail screen
+
+A row usually opens something, and the id space is usually unbounded (every product, every
+listing). **Use ONE canonical detail screen and pass the id as a nav param** — the row's action is
+`{ "actionId": "himi.open", "params": { "screenId": "property_detail", "id": "$item.id" } }`, and
+the detail worker reads `himalaya.input.id`.
+
+The alternative, a **templated route** (`screens.templated` with a `pattern`), is for a *bounded*
+catalog and nothing else. It resolves live for any id while you are developing, which is what makes it
+look like the general answer — but a production OTA release serves only `screens.exact`, so the
+build materializes one screen per id from the route's `seedIds` and a record created after that
+push is simply not in the release. Reach for it when the set is small and known (a handful of
+categories); reach for the canonical screen whenever the ids come from a live collection.
+Mechanics and the prod caveat in full: `himi docs tier-5-add-a-screen`.
+
 ## Gotchas (each of these has cost an agent a full push→drive cycle)
 
 - **`itemsPath` must bind to an array.** `himi validate` errors if the bound path's

package/guides/sdk-reference.json

@@ -6955,16 +6955,18 @@
       {
         "name": "queryBookings",
         "kind": "function",
-        "jsdoc": "",
+        "jsdoc": "/**\n * @scope owner — requires an owner / business identity — a visitor session gets 403.\n *\n * POST /bookings/v2/bookings/query\n */",
         "decl": "export function queryBookings(\n  req: WixQueryBookingsRequest = {} as WixQueryBookingsRequest,\n  opts?: WixCallOptions,\n): Promise<WixQueryBookingsResponse>;",
-        "http": "POST /bookings/v2/bookings/query"
+        "http": "POST /bookings/v2/bookings/query",
+        "scope": "owner"
       },
       {
         "name": "listBookings",
         "kind": "function",
-        "jsdoc": "",
+        "jsdoc": "/**\n * @scope owner — requires an owner / business identity — a visitor session gets 403.\n *\n * GET /bookings/v1/bookings\n */",
         "decl": "export function listBookings(\n  req: WixListBookingsRequest = {} as WixListBookingsRequest,\n  opts?: WixCallOptions,\n): Promise<WixListBookingsResponse>;",
-        "http": "GET /bookings/v1/bookings"
+        "http": "GET /bookings/v1/bookings",
+        "scope": "owner"
       },
       {
         "name": "getBooking",
@@ -10524,10 +10526,17 @@
       {
         "name": "queryDataItems",
         "kind": "function",
-        "jsdoc": "/** Query items in a collection — POST /wix-data/v2/items/query.\n *  Pass `returnTotalCount: true` to ask Wix to fill `pagingMetadata.total`\n *  (offset paging only; omitted by default because counting is extra work). */",
-        "decl": "export function queryDataItems(\n  dataCollectionId: string,\n  limit = 50,\n  filter?: Record<string, unknown>,\n  returnTotalCount = false,\n): Promise<WixQueryDataItemsResponse>;",
+        "jsdoc": "/** Query items in a collection — POST /wix-data/v2/items/query.\n *\n *  `filter` is the Wix Data v2 filter object, which the type cannot express (it is\n *  `Record<string, unknown>` by construction). A field name maps to a value for\n *  equality, or to an operator object:\n *\n *  ```ts\n *  await queryDataItems(\"Listings\", 20, { city: \"Tel Aviv\" });\n *  await queryDataItems(\"Listings\", 20, { price: { $lte: 2_500_000 } });\n *  await queryDataItems(\"Listings\", 20, { _id: { $in: [a, b] } });\n *  ```\n *\n *  `offset` pages: ask for `limit` rows starting at `offset`. Pair it with\n *  `returnTotalCount: true`, which fills `pagingMetadata.total` so a caller knows\n *  when to stop — it is omitted by default because counting is extra work, and it\n *  reports total for OFFSET paging only, which is the mode this function uses.\n *\n *  ```ts\n *  const first = await queryDataItems(\"Listings\", 50, undefined, true);\n *  const total = first.pagingMetadata?.total ?? 0;\n *  const rest  = await queryDataItems(\"Listings\", 50, undefined, false, 50);\n *  ```\n *\n *  To read ONE row, use `getDataItem` rather than a page plus a client-side\n *  `.find()` — that pattern breaks silently once the collection outgrows `limit`. */",
+        "decl": "export function queryDataItems(\n  dataCollectionId: string,\n  limit = 50,\n  filter?: Record<string, unknown>,\n  returnTotalCount = false,\n  offset = 0,\n): Promise<WixQueryDataItemsResponse>;",
         "http": "POST /wix-data/v2/items/query"
       },
+      {
+        "name": "getDataItem",
+        "kind": "function",
+        "jsdoc": "/** Read ONE item by id — GET /wix-data/v2/items/{dataItemId}?dataCollectionId=…\n *\n *  Reach for this on a detail screen. Before it existed the only read this package\n *  offered was `queryDataItems`, so a detail worker had to fetch a bounded page and\n *  find its row client-side:\n *\n *  ```ts\n *  const res = await queryDataItems(\"Listings\", 50);          // ← DON'T\n *  const row = (res.dataItems ?? []).find((it) => it.id === id);\n *  ```\n *\n *  That is correct against a handful of seeded rows and silently wrong once the\n *  collection outgrows `limit`. Ask for the row instead:\n *\n *  ```ts\n *  const { dataItem } = await getDataItem(\"Listings\", id);     // ← DO\n *  ```\n *\n *  The collection id rides the query string rather than a body, because the Wix\n *  gateway drops a GET body — and the string is built with `encodeURIComponent`\n *  rather than `URLSearchParams`, which the bare Tier-5 worker runtimes (JSCore /\n *  Hermes / QuickJS-ng) do not provide. */",
+        "decl": "export function getDataItem(\n  dataCollectionId: string,\n  dataItemId: string,\n): Promise<{ dataItem?: WixDataItem }>;",
+        "http": "GET /wix-data/v2/items/{…}?dataCollectionId={…}"
+      },
       {
         "name": "insertDataItem",
         "kind": "function",
@@ -19013,91 +19022,106 @@
         "name": "MuteStatus",
         "kind": "type",
         "jsdoc": "/** \"MUTED\" silences the topic on this channel; \"UNMUTED\" delivers it. */",
-        "decl": "export type MuteStatus = \"MUTED\" | \"UNMUTED\";"
+        "decl": "export type MuteStatus = \"MUTED\" | \"UNMUTED\";",
+        "verified": false
       },
       {
         "name": "Channel",
         "kind": "type",
         "jsdoc": "/** Delivery channel. The mobile push channel value is unconfirmed; \"MOBILE\" is\n *  the working default the bundle passes. */",
-        "decl": "export type Channel = \"MOBILE\" | string;"
+        "decl": "export type Channel = \"MOBILE\" | string;",
+        "verified": false
       },
       {
         "name": "PreferenceState",
         "kind": "interface",
         "jsdoc": "",
-        "decl": "export interface PreferenceState {\n  /** \"MUTED\" | \"UNMUTED\" — whether the topic is delivered on this channel. */\n  muteStatus?: MuteStatus;\n}"
+        "decl": "export interface PreferenceState {\n  /** \"MUTED\" | \"UNMUTED\" — whether the topic is delivered on this channel. */\n  muteStatus?: MuteStatus;\n}",
+        "verified": false
       },
       {
         "name": "PreferenceStateData",
         "kind": "interface",
         "jsdoc": "",
-        "decl": "export interface PreferenceStateData {\n  state?: PreferenceState;\n}"
+        "decl": "export interface PreferenceStateData {\n  state?: PreferenceState;\n}",
+        "verified": false
       },
       {
         "name": "PreferenceInfo",
         "kind": "interface",
         "jsdoc": "/** One topic×channel preference for the implicit recipient. */",
-        "decl": "export interface PreferenceInfo {\n  /** The notification topic id (matches NotificationTopic.id). */\n  topicId: string;\n  /** Delivery channel this preference applies to (e.g. \"MOBILE\"). */\n  channel?: Channel;\n  stateData?: PreferenceStateData;\n}"
+        "decl": "export interface PreferenceInfo {\n  /** The notification topic id (matches NotificationTopic.id). */\n  topicId: string;\n  /** Delivery channel this preference applies to (e.g. \"MOBILE\"). */\n  channel?: Channel;\n  stateData?: PreferenceStateData;\n}",
+        "verified": false
       },
       {
         "name": "NotificationPreferences",
         "kind": "interface",
         "jsdoc": "",
-        "decl": "export interface NotificationPreferences {\n  preferencesInfo?: PreferenceInfo[];\n}"
+        "decl": "export interface NotificationPreferences {\n  preferencesInfo?: PreferenceInfo[];\n}",
+        "verified": false
       },
       {
         "name": "GetMyNotificationPreferencesResponse",
         "kind": "interface",
         "jsdoc": "",
-        "decl": "export interface GetMyNotificationPreferencesResponse {\n  preferences?: NotificationPreferences;\n}"
+        "decl": "export interface GetMyNotificationPreferencesResponse {\n  preferences?: NotificationPreferences;\n}",
+        "verified": false
       },
       {
         "name": "NotificationTopic",
         "kind": "interface",
         "jsdoc": "/** A notification topic — its id is the PreferenceInfo.topicId; displayName is\n *  the row label shown in the UI. */",
-        "decl": "export interface NotificationTopic {\n  id: string;\n  displayName?: string;\n}"
+        "decl": "export interface NotificationTopic {\n  id: string;\n  displayName?: string;\n}",
+        "verified": false
       },
       {
         "name": "GetNotificationTopicsResponse",
         "kind": "interface",
         "jsdoc": "",
-        "decl": "export interface GetNotificationTopicsResponse {\n  topics?: NotificationTopic[];\n}"
+        "decl": "export interface GetNotificationTopicsResponse {\n  topics?: NotificationTopic[];\n}",
+        "verified": false
       },
       {
         "name": "UpsertMyNotificationPreferencesRequest",
         "kind": "interface",
         "jsdoc": "",
-        "decl": "export interface UpsertMyNotificationPreferencesRequest {\n  preferencesInfo: PreferenceInfo[];\n}"
+        "decl": "export interface UpsertMyNotificationPreferencesRequest {\n  preferencesInfo: PreferenceInfo[];\n}",
+        "verified": false
       },
       {
         "name": "UpsertMyNotificationPreferencesResponse",
         "kind": "interface",
         "jsdoc": "",
-        "decl": "export interface UpsertMyNotificationPreferencesResponse {\n  preferences?: NotificationPreferences;\n}"
+        "decl": "export interface UpsertMyNotificationPreferencesResponse {\n  preferences?: NotificationPreferences;\n}",
+        "verified": false
       },
       {
         "name": "muteStatusFor",
         "kind": "function",
         "jsdoc": "/** Map a UI \"on\" boolean to a MuteStatus: on ⇒ delivered (\"UNMUTED\"). */",
-        "decl": "export function muteStatusFor(on: boolean): MuteStatus;"
+        "decl": "export function muteStatusFor(on: boolean): MuteStatus;",
+        "verified": false
       },
       {
         "name": "getMyNotificationPreferences",
         "kind": "function",
         "jsdoc": "/** Get the signed-in member's notification preferences —\n *  GET /notifications/v1/preferences-by-implicit-recipient. */",
-        "decl": "export function getMyNotificationPreferences(): Promise<GetMyNotificationPreferencesResponse>;"
+        "decl": "export function getMyNotificationPreferences(): Promise<GetMyNotificationPreferencesResponse>;",
+        "verified": false
       },
       {
         "name": "getNotificationTopics",
         "kind": "function",
         "jsdoc": "/** List the available notification topics (id + displayName for labels) —\n *  GET /notifications/v1/preferences/topics. */",
-        "decl": "export function getNotificationTopics(): Promise<GetNotificationTopicsResponse>;"
+        "decl": "export function getNotificationTopics(): Promise<GetNotificationTopicsResponse>;",
+        "verified": false
       },
       {
         "name": "upsertMyNotificationPreferences",
         "kind": "function",
         "jsdoc": "/** Upsert one or more of the signed-in member's preferences —\n *  POST /notifications/v1/preferences-by-implicit-recipient, body\n *  { preferencesInfo }. Pass only the rows that changed. */",
-        "decl": "export function upsertMyNotificationPreferences(\n  preferencesInfo: PreferenceInfo[]\n): Promise<UpsertMyNotificationPreferencesResponse>;"
+        "decl": "export function upsertMyNotificationPreferences(\n  preferencesInfo: PreferenceInfo[]\n): Promise<UpsertMyNotificationPreferencesResponse>;",
+        "verified": false
       }
     ]
   },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/himalaya-cli",
-  "version": "0.942.0",
+  "version": "0.944.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": [
@@ -64,5 +64,5 @@
       "artifactId": "himalaya-cli"
     }
   },
-  "falconPackageHash": "8700bed97461c826fd04a33c50c3cc26d349fdeaad788594d2f598c1"
+  "falconPackageHash": "430cfb64da57b0b2bd12c6e873effe559a8b82eb6aaf60bfa1037748"
 }