@wix/himalaya-cli 0.833.0 → 0.835.0

package/guides/headless-loop.md

@@ -194,7 +194,9 @@ closed. The loop to teach an agent: **build → test → close the top ledger ga
 Before calling a multi-screen app ready, run `himi ux audit --content . --strict` and fix the
 acceptance/evidence gaps it reports. After driving a native shell, record what actually happened
 with `himi ux record --content . --platform ios|android --status passed|failed|unavailable
---checks back,keyboard,…`; an unavailable platform needs its reason recorded, not guessed.
+[--checks back,keyboard,…]`. `--checks` is required for `passed`/`failed` and names what you
+actually drove; an unavailable platform drove nothing, so it takes no checks and needs its reason
+recorded, not guessed.
 
 Report v2 sharpens all of it: a worker throw carries `in tier5-src/<screen>/index.ts:<line>`
 (mapped through the bundle's sourcemap — fix it without grepping), the ledger lists worker

package/guides/himi-test.md

@@ -66,9 +66,15 @@ CLI orchestration: `tools/himi-cli/src/test.ts`.
 
 ## Typed form journeys
 
-The automatic form axis intentionally dispatches the descriptor's default (often empty)
-value. For a flow where the real proof is **typed value → submit → visible completion**,
-add a short screen-local journey to `himi-test.json`:
+The crawl types into a control **only when it can read a legal value off the app itself** — an id
+from the control's own `options`/`optionsPath` that is not the one selected, or a word from the
+booted worker's own seeded state that is not what the field already shows — and only for a control
+the payload contract names. A `Slider`, `Stepper`, `Toggle` or `DatePicker` has no such source, so
+those still dispatch with the descriptor's default (often empty) value, and the gap ledger says so
+per screen.
+
+For a flow where the real proof is **typed value → submit → visible completion** — several fields,
+in order, ending in a rendered result — add a short screen-local journey to `himi-test.json`:
 
 ```json
 {
@@ -111,6 +117,7 @@ Only **unambiguous** defects, so a green run stays worth trusting:
 | `refresh-not-idempotent` | **warning** | `refresh` from a fresh boot settles somewhere other than the boot did, on identical data — usually a refresh that appends instead of replacing. |
 | `list-shrank-on-load-more` | **warning** | A "load more" returned FEWER rows than before it ran: the new page replaced the list instead of extending it. |
 | `list-grew-on-filter` | **warning** | A filter, search or sort made a list longer. Narrowing can reorder or remove, never add. |
+| `typed-value-ignored` | **warning** | The crawl typed the value a control really carries — the payload key every renderer injects for that control — and the dispatch changed **nothing**: no state, no navigation, no request. The value is read off the app itself (an id from the control's own options, or a word from the worker's seeded state) and is always one the control is *not* already showing, so a reducer that ignores it cannot work on device. A warning because the input is the crawl's: a reducer that legitimately no-ops on a value is possible, and `himi-test.json` `skip[]` takes the invariant. |
 
 **Deliberately never reported:** an empty collection · an `error` state (often the correct
 answer to empty input) · a `null` optional · whether a nav target *exists* (approximating

package/guides/mobile-ux.md

@@ -131,8 +131,9 @@ Use `himi ux audit --content <app>` as the repeatable evidence check. It is advi
 existing templates migrate; `--strict` promotes an incomplete contract, remaining template
 copy, missing app fixtures, or unrecorded platform audit to a release blocker. After actually
 driving a native shell, record the result—not an assumption—with `himi ux record --content <app>
---platform ios|android --status passed|failed|unavailable --checks back,keyboard,...`; an
-unavailable platform needs a reason.
+--platform ios|android --status passed|failed|unavailable [--checks back,keyboard,...]`. `--checks`
+is required for `passed`/`failed` and names what you actually drove; an unavailable platform drove
+nothing, so it takes no checks and needs a `--reason` instead.
 
 ### Strict audit contract
 
@@ -140,15 +141,53 @@ unavailable platform needs a reason.
 rewrite that drops a required string is caught in the loop you are already running rather than at
 the end of it. `himi validate --strict` and `himi ux audit --strict` both promote that warning to a
 **release blocker**. Both read the same exact markers, and each gate **substring-matches** these
-phrases — so use them verbatim: a semantically equivalent rewrite ("each state exposes exactly one
-primary call to action") fails the same as omitting them:
+three phrases — so use them verbatim: a semantically equivalent rewrite ("each state exposes exactly
+one primary call to action") fails the same as omitting them:
 
 - The heading `## Implementation acceptance`.
 - The heading `## Evidence`.
 - The phrase `one primary CTA per state`.
-- A width-evidence sentence containing `compact (320/360)` followed later by `expanded`. The two
-  **may wrap across lines** — the check is not line-based — but `expanded` must follow within about
-  400 characters, so keep them in the same sentence or bullet rather than in separate sections.
+
+The fourth marker, **width evidence**, is graded by **content, not by phrase** — it is a
+fact about what you rendered rather than a string, so there is nothing to paste. Satisfy it either
+way:
+
+- Name two pixel widths spanning compact → wider, within about 400 characters of each other so
+  they read as one statement: one **below 600px** (compact) and one **at 600px or wider** (medium
+  or expanded). `Rendered 320, 390 and 834 (home-320.png, home-390.png, home-834.png)` satisfies it
+  — a single width does not. What this proves is that you rendered more than one size class, not
+  which wider one: 600px is the `medium` breakpoint and `expanded` begins at 840px, so 834 counts
+  as wider without being expanded. The two bands are contiguous, so every width you actually render
+  counts as one or the other: `pixel` (412) and `iphone-max` (430) from `himi render --device` are
+  compact.
+  Each number must read as a **width**: give it a unit (`834px`), put it in a screenshot filename
+  (`home-834.png`, `home-834-dark.png`, `home-834x1112.png`), or name it with the vocabulary of
+  widths — `width`, `wide`, `pixel`, `viewport`, `breakpoint`, `compact`, `expanded`, `column`,
+  `portrait`, `landscape`. One such word covers a whole list of widths from either end (`Rendered
+  320, 390 and 834 widths`, `Widths: 320, 390, 834` and `Rendered compact (320) and expanded (834)`
+  all work), and the list may wrap across lines — but it does not reach across another phrase or
+  into the next line unless that line continues the list: in `Rendered home at 834px; p95
+  250 ms` only `834` is a width, so that line names a single width and is still reported. In a
+  `390x844` pair the first number is the width and the second is the height, so one portrait
+  screenshot is one width — `home-390x844.png` on its own is not two. Bare
+  digits count for nothing, which keeps a latency budget, a price or an issue number from standing
+  in for the half you did not render. A number in the 1990-2099 range needs its **unit** to count
+  as a width: `2048px` is taken at its word, while a bare `2026` and a year-shaped filename
+  (`shot-2026.png`, `evidence-2026-09-18.png`) are not widths — `home-2048.png` cannot be told
+  apart from `shot-2026.png`, so spell the unit when your render really is that wide.
+  `render` is deliberately **not** one of the cues: an acceptance row says "renders in under
+  250 ms" far more often than it names a viewport. Neither is a pixel measurement of something
+  that is not a viewport — `Row height 320px`, `Font size: 512px` and `844 tall` are ignored,
+  because a unit says pixels, not width. Assets are judged by the SENTENCE they sit in rather than
+  by word order: a sentence naming an image, logo, banner, hero, icon, media or artwork is a record
+  of assets, so none of its numbers count — `Use 320px-wide mobile and 1024px-wide desktop hero
+  images` records no render. A screenshot **filename** is the exception and outranks the sentence
+  it appears in, because a file that was written is the strongest evidence this marker takes:
+  `Screenshots: hero-320.png and hero-834.png` counts.
+- Or keep the scaffold's own sentence, `compact (320/360)` followed later by `expanded`, which is
+  still accepted as-is. The two **may wrap across lines** — the check is not line-based — but
+  `expanded` must follow within about 400 characters, so keep them in the same sentence or bullet
+  rather than in separate sections.
 
 A `MOBILE-UX.md` that is **absent or empty** is not four missing markers. `himi ux audit` reports it
 once, as a missing contract; `himi validate` stays silent about it entirely. Asking for the document

package/guides/sdk-reference.json

@@ -7105,39 +7105,12 @@
         "decl": "export function updateService(serviceId: string, service: WixServiceWrite & { revision?: string }): Promise<WixUpdateServiceResponse>;",
         "http": "PATCH /bookings/v2/services/{…}"
       },
-      {
-        "name": "deleteService",
-        "kind": "function",
-        "jsdoc": "/** Delete a service — DELETE /bookings/v1/services/{id}. */",
-        "decl": "export function deleteService(serviceId: string): Promise<WixDeleteServiceResponse>;",
-        "http": "DELETE /bookings/v1/services/{…}"
-      },
-      {
-        "name": "WixListBookingsResponse",
-        "kind": "interface",
-        "jsdoc": "",
-        "decl": "export interface WixListBookingsResponse {\n  bookings: WixBooking[];\n}"
-      },
-      {
-        "name": "listBookings",
-        "kind": "function",
-        "jsdoc": "/** List bookings — GET /bookings/v1/bookings. */",
-        "decl": "export function listBookings(): Promise<WixListBookingsResponse>;",
-        "http": "GET /bookings/v1/bookings"
-      },
       {
         "name": "WixGetBookingResponse",
         "kind": "interface",
         "jsdoc": "",
         "decl": "export interface WixGetBookingResponse {\n  booking: WixBooking;\n}"
       },
-      {
-        "name": "getBooking",
-        "kind": "function",
-        "jsdoc": "/** Fetch a single booking by id — GET /bookings/v1/bookings/{id}. */",
-        "decl": "export function getBooking(bookingId: string): Promise<WixGetBookingResponse>;",
-        "http": "GET /bookings/v1/bookings/{…}"
-      },
       {
         "name": "WixBookingWrite",
         "kind": "interface",
@@ -7150,13 +7123,6 @@
         "jsdoc": "",
         "decl": "export interface WixCreateBookingResponse {\n  booking: WixBooking;\n}"
       },
-      {
-        "name": "createBooking",
-        "kind": "function",
-        "jsdoc": "/** Create a booking on behalf of a client — POST /bookings/v1/bookings. */",
-        "decl": "export function createBooking(booking: WixBookingWrite): Promise<WixCreateBookingResponse>;",
-        "http": "POST /bookings/v1/bookings"
-      },
       {
         "name": "WixUpdateBookingResponse",
         "kind": "interface",
@@ -7234,11 +7200,17 @@
         "jsdoc": "",
         "decl": "export interface WixQueryAvailabilityResponse { availabilityEntries?: WixAvailabilityEntry[] }"
       },
+      {
+        "name": "WixServiceAvailabilityOptions",
+        "kind": "interface",
+        "jsdoc": "/** How to bound an availability query. `bookable` is a `query.filter` member — the\n *  request's `query` has only `filter` and `sort`, so there is NO paging member and\n *  a `paging: { limit }` you add is silently dropped rather than honoured. */",
+        "decl": "export interface WixServiceAvailabilityOptions {\n  /** Bookable slots only. Defaults to `true`; pass `false` to get the unbookable\n   *  ones too (a greyed-out calendar), which is what the endpoint returns unfiltered. */\n  bookable?: boolean;\n}"
+      },
       {
         "name": "queryServiceAvailability",
         "kind": "function",
-        "jsdoc": "/** Query bookable slots for a service in a date window —\n *  POST /bookings/v1/availability/query. Verified live (571 entries). */",
-        "decl": "export function queryServiceAvailability(serviceId: string, startDate: string, endDate: string): Promise<WixQueryAvailabilityResponse>;",
+        "jsdoc": "/**\n * Query bookable slots for a service in a date window —\n * POST /bookings/v1/availability/query. Verified live (571 entries).\n *\n * BOUND IT. Unfiltered, this returns every slot in the window, bookable AND\n * unbookable — a two-week window on a busy calendar is hundreds of entries and a\n * response big enough to stall a worker. Two things bound it, and only one of them\n * is a parameter here:\n *\n *  - `bookable`, which this now defaults to `true`. Slots you cannot book are not\n *    what a booking screen is paging through.\n *  - THE WINDOW ITSELF. Ask for the days you are about to paint, not the month.\n *\n * What is NOT available is paging: the request's `query` carries only `filter` and\n * `sort`, so a `paging: { limit }` is an unknown field the server drops on the\n * floor — which is why \"it ignores its own paging.limit\" is a misreading. There was\n * never a paging member to ignore.\n *\n * A per-day cap (`slotsPerDay`) is deliberately NOT offered. This v1 Availability\n * Calendar endpoint is absent from the current published Wix reference (superseded\n * by Time Slots V2), and the two plausible spellings put it in different places — a\n * `query.filter` member, or a top-level sibling of `query`. An unknown field in\n * either position is dropped silently rather than rejected, so shipping the wrong\n * guess would hand callers a knob that does nothing while this comment promised it\n * worked. Narrow the window instead, until the level can be confirmed against a\n * schema or a live call.\n */",
+        "decl": "export function queryServiceAvailability(\n  serviceId: string,\n  startDate: string,\n  endDate: string,\n  options: WixServiceAvailabilityOptions = {},\n): Promise<WixQueryAvailabilityResponse>;",
         "http": "POST /bookings/v1/availability/query"
       },
       {
@@ -7342,7 +7314,7 @@
       {
         "name": "getBookingFull",
         "kind": "function",
-        "jsdoc": "/** Rich single-booking read — GET /bookings/v1/bookings/{id}. Returns the full\n *  booking (payment/intake/location/staff/attendance). The booking-detail data source. */",
+        "jsdoc": "/** Rich single-booking read — GET /bookings/v1/bookings/{id}. Returns the full\n *  booking (payment/intake/location/staff/attendance). The booking-detail data source.\n *  Owner-scoped: needs an owner/BO session; a visitor or member token gets 403. A\n *  member-facing screen reads its own bookings via `queryBookings` instead. */",
         "decl": "export function getBookingFull(bookingId: string): Promise<WixGetBookingFullResponse>;",
         "http": "GET /bookings/v1/bookings/{…}"
       },
@@ -20549,16 +20521,16 @@
       {
         "name": "queryStoreProducts",
         "kind": "function",
-        "jsdoc": "",
-        "decl": "export async function queryStoreProducts(limit = 50, cursor?: string): Promise<StoreProductsResponse>;",
+        "jsdoc": "/** List products from whichever catalog this site runs. `fields` is additive — it\n *  WIDENS the default v3 display fieldset rather than replacing it. */",
+        "decl": "export async function queryStoreProducts(\n  limit = 50,\n  cursor?: string,\n  fields?: readonly string[],\n): Promise<StoreProductsResponse>;",
         "http": "POST /stores/v3/products/query"
       },
       {
         "name": "getStoreProduct",
         "kind": "function",
-        "jsdoc": "",
-        "decl": "export async function getStoreProduct(productId: string): Promise<StoreGetProductResponse>;",
-        "http": "GET /stores/v3/products/{…}?fields={…}"
+        "jsdoc": "/** Read one product from whichever catalog this site runs. `fields` is additive —\n *  it WIDENS the default v3 display fieldset rather than replacing it. */",
+        "decl": "export async function getStoreProduct(\n  productId: string,\n  fields?: readonly string[],\n): Promise<StoreGetProductResponse>;",
+        "http": "GET /stores/v3/products/{…}?{…}"
       },
       {
         "name": "productPrice",
@@ -20806,7 +20778,7 @@
         "name": "StoreProduct",
         "kind": "interface",
         "jsdoc": "",
-        "decl": "export interface StoreProduct {\n  id?: string;\n  name?: string;\n  slug?: string;\n  description?: string;\n  plainDescription?: string;\n  media?: {\n    mainMedia?: WixMediaSlot;\n    main?: WixMediaSlot;\n    items?: WixMediaSlot[];\n  };\n  price?: { formatted?: { price?: string }; price?: number; currency?: string };\n  priceData?: { formatted?: { price?: string }; price?: number; currency?: string };\n  currency?: string;\n  actualPriceRange?: {\n    minValue?: { amount?: string; formattedAmount?: string; currency?: string };\n    maxValue?: { amount?: string; formattedAmount?: string; currency?: string };\n  };\n}"
+        "decl": "export interface StoreProduct {\n  id?: string;\n  name?: string;\n  slug?: string;\n  description?: string;\n  plainDescription?: string;\n  /** Both gallery layouts: V1 `mainMedia`/`items`, V3 `main`/`itemsInfo.items`. */\n  media?: {\n    mainMedia?: WixMediaSlot;\n    main?: WixMediaSlot;\n    items?: WixMediaSlot[];\n    itemsInfo?: { items?: WixMediaSlot[] };\n  };\n  price?: { formatted?: { price?: string }; price?: number; currency?: string };\n  priceData?: { formatted?: { price?: string }; price?: number; currency?: string };\n  currency?: string;\n  actualPriceRange?: {\n    minValue?: { amount?: string; formattedAmount?: string; currency?: string };\n    maxValue?: { amount?: string; formattedAmount?: string; currency?: string };\n  };\n}"
       },
       {
         "name": "StoreProductsResponse",
@@ -20824,7 +20796,7 @@
         "name": "StoreProductSearch",
         "kind": "interface",
         "jsdoc": "/** User-facing product discovery. V3 name search/sorting belong to Search\n * Products; Query Products deliberately does not support the name field.\n * V1 uses its documented JSON-string filter/sort dialect. */",
-        "decl": "export interface StoreProductSearch {\n  query?: string;\n  sort?: 'default' | 'az' | 'za';\n  ids?: string[];\n  limit?: number;\n  cursor?: string;\n}"
+        "decl": "export interface StoreProductSearch {\n  query?: string;\n  sort?: 'default' | 'az' | 'za';\n  ids?: string[];\n  limit?: number;\n  cursor?: string;\n  /** Extra v3 fieldsets. Additive — widens the default, never replaces it. */\n  fields?: readonly string[];\n}"
       },
       {
         "name": "searchStoreProducts",
@@ -20839,6 +20811,12 @@
         "jsdoc": "",
         "decl": "export {\n  wixMediaUrl,\n  isUnsizedWixMedia,\n  WIX_LIST_IMAGE,\n  WIX_DETAIL_IMAGE,\n  type WixImageSize,\n} from \"@himalaya/wix-media\";"
       },
+      {
+        "name": "productGallery",
+        "kind": "function",
+        "jsdoc": "/**\n * EVERY image on the product, sized, in wire order — the gallery a detail screen\n * pages through, not just the one tile `productImage` returns.\n *\n * It reads both catalog layouts (V1 `media.items`, V3 `media.itemsInfo.items`) and\n * falls back to the primary image when the product carries no gallery, so a caller\n * always gets a non-empty list for a product that has any image at all. Empty slots\n * and duplicates are dropped.\n *\n * Exported because the gallery union was being re-derived by hand in ~10 template\n * workers, each free to miss a layout — which is exactly how a V3 store silently\n * lost its thumbnails. Defaults to the LIST budget like `productImage`; pass\n * `WIX_DETAIL_IMAGE` for a full-bleed pager, or `null` for the stored originals.\n */",
+        "decl": "export function productGallery(p: StoreProduct, size: WixImageSize | null = WIX_LIST_IMAGE): string[];"
+      },
       {
         "name": "plainText",
         "kind": "function",

package/guides/testing-himi-apps.md

@@ -38,13 +38,14 @@ answers three questions:
 > himi test --content . --json
 > himi render home --content . --png home-light.png            # one scheme per invocation
 > himi render home --content . --scheme dark --png home-dark.png
-> himi ux record --content . --platform ios     --status unavailable --checks back,keyboard --reason "no simulator off-repo"
-> himi ux record --content . --platform android --status unavailable --checks back,keyboard --reason "no emulator off-repo"
+> himi ux record --content . --platform ios     --status unavailable --reason "no simulator off-repo"
+> himi ux record --content . --platform android --status unavailable --reason "no emulator off-repo"
 > himi ux audit  --content . --strict
 > ```
 >
-> Use `--status passed` and the checks you actually drove when you did drive a device;
-> `unavailable` requires a reason, which is the point — it records the gap rather than hiding it.
+> Use `--status passed` and `--checks` naming what you actually drove when you did drive a device.
+> An `unavailable` platform takes **no `--checks`** — nothing was driven, so there is nothing to
+> list — and requires a `--reason`, which is the point: it records the gap rather than hiding it.
 
 ---
 

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

@@ -334,7 +334,7 @@ happened — or, honestly, that it could not.
 ```
 himi ux audit --strict           # the gate that fails on a missing per-platform record
 himi ux record --content . --platform ios --status passed --checks back,keyboard,scroll
-himi ux record --content . --platform ios --status unavailable --checks back --reason "no simulator on this machine"
+himi ux record --content . --platform ios --status unavailable --reason "no simulator on this machine"
 ```
 
 For the full tier ladder — which test tier observes which kind of change, and what a

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/himalaya-cli",
-  "version": "0.833.0",
+  "version": "0.835.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": [
@@ -63,5 +63,5 @@
       "artifactId": "himalaya-cli"
     }
   },
-  "falconPackageHash": "a2c1ef13eceb008115d02b8e16b9dd82c4a1040e822600be9b93647c"
+  "falconPackageHash": "28f3f50cd02d76203d4daf19d83865ed5be46f5158dc74ca6e1764b1"
 }

package/templates/beauty-salon/tier5-src/himi-store-product/index.ts

@@ -3,7 +3,7 @@ import { defineService } from "@himalaya/state";
 import { share as shareSheet } from "@himalaya/share";
 import { addToCurrentCart, getCurrentCart } from "@himalaya/wix-ecom";
 import { get, upsert, enqueue, type DbEntity } from "@himalaya/local-db";
-import { getStoreProduct, plainText, productImage, productPrice, wixMediaUrl, mediaSlotUrl, WIX_DETAIL_IMAGE, type StoreProduct } from "../_shared/himi-store.js";
+import { getStoreProduct, plainText, productImage, productPrice, wixMediaUrl, productGallery as sdkProductGallery, WIX_DETAIL_IMAGE, type StoreProduct } from "../_shared/himi-store.js";
 import { cleanTitle } from "../_shared/himi-text.js";
 import { stashCopy, copyParam, copyTemplate } from "../_shared/himi-copy.js";
 import { isBridgeUnavailable } from "../_shared/owner-load-error.js";
@@ -96,11 +96,12 @@ export function productGallery(p: StoreProduct): GalleryItem[] {
   // entry goes through the same CDN transform — the primary AND the extra media
   // items, which would otherwise stay untouched 4000px originals.
   push(productImage(p, WIX_DETAIL_IMAGE));
-  for (const item of p.media?.items ?? []) {
-    // Same reader productImage uses — a slot may be the reference STRING rather than
-    // an object, and two private copies of that knowledge is how they drift.
-    push(mediaSlotUrl(item, WIX_DETAIL_IMAGE));
-  }
+  // The SDK helper reads BOTH gallery layouts — V1 `media.items` and Catalog V3
+  // `media.itemsInfo.items`. This loop used to walk `media.items` itself, which is
+  // the V1 spelling only, so a V3 product with a ten-image gallery rendered as one
+  // image no matter what the read asked for. One reader, not a private copy per
+  // worker — that is how the two layouts drifted apart in the first place.
+  for (const url of sdkProductGallery(p, WIX_DETAIL_IMAGE)) push(url);
   return urls.map((url) => ({ url }));
 }
 

package/templates/branded-lite/tier5-src/himi-store-product/index.ts

@@ -3,7 +3,7 @@ import { defineService } from "@himalaya/state";
 import { share as shareSheet } from "@himalaya/share";
 import { addToCurrentCart, getCurrentCart } from "@himalaya/wix-ecom";
 import { get, upsert, enqueue, type DbEntity } from "@himalaya/local-db";
-import { getStoreProduct, plainText, productImage, productPrice, wixMediaUrl, mediaSlotUrl, WIX_DETAIL_IMAGE, type StoreProduct } from "../_shared/himi-store.js";
+import { getStoreProduct, plainText, productImage, productPrice, wixMediaUrl, productGallery as sdkProductGallery, WIX_DETAIL_IMAGE, type StoreProduct } from "../_shared/himi-store.js";
 import { cleanTitle } from "../_shared/himi-text.js";
 import { stashCopy, copyParam, copyTemplate } from "../_shared/himi-copy.js";
 import { isBridgeUnavailable } from "../_shared/owner-load-error.js";
@@ -96,11 +96,12 @@ export function productGallery(p: StoreProduct): GalleryItem[] {
   // entry goes through the same CDN transform — the primary AND the extra media
   // items, which would otherwise stay untouched 4000px originals.
   push(productImage(p, WIX_DETAIL_IMAGE));
-  for (const item of p.media?.items ?? []) {
-    // Same reader productImage uses — a slot may be the reference STRING rather than
-    // an object, and two private copies of that knowledge is how they drift.
-    push(mediaSlotUrl(item, WIX_DETAIL_IMAGE));
-  }
+  // The SDK helper reads BOTH gallery layouts — V1 `media.items` and Catalog V3
+  // `media.itemsInfo.items`. This loop used to walk `media.items` itself, which is
+  // the V1 spelling only, so a V3 product with a ten-image gallery rendered as one
+  // image no matter what the read asked for. One reader, not a private copy per
+  // worker — that is how the two layouts drifted apart in the first place.
+  for (const url of sdkProductGallery(p, WIX_DETAIL_IMAGE)) push(url);
   return urls.map((url) => ({ url }));
 }
 

package/templates/gym-fitness/tier5-src/himi-store-product/index.ts

@@ -3,7 +3,7 @@ import { defineService } from "@himalaya/state";
 import { share as shareSheet } from "@himalaya/share";
 import { addToCurrentCart, getCurrentCart } from "@himalaya/wix-ecom";
 import { get, upsert, enqueue, type DbEntity } from "@himalaya/local-db";
-import { getStoreProduct, plainText, productImage, productPrice, wixMediaUrl, mediaSlotUrl, WIX_DETAIL_IMAGE, type StoreProduct } from "../_shared/himi-store.js";
+import { getStoreProduct, plainText, productImage, productPrice, wixMediaUrl, productGallery as sdkProductGallery, WIX_DETAIL_IMAGE, type StoreProduct } from "../_shared/himi-store.js";
 import { cleanTitle } from "../_shared/himi-text.js";
 import { stashCopy, copyParam, copyTemplate } from "../_shared/himi-copy.js";
 import { isBridgeUnavailable } from "../_shared/owner-load-error.js";
@@ -96,11 +96,12 @@ export function productGallery(p: StoreProduct): GalleryItem[] {
   // entry goes through the same CDN transform — the primary AND the extra media
   // items, which would otherwise stay untouched 4000px originals.
   push(productImage(p, WIX_DETAIL_IMAGE));
-  for (const item of p.media?.items ?? []) {
-    // Same reader productImage uses — a slot may be the reference STRING rather than
-    // an object, and two private copies of that knowledge is how they drift.
-    push(mediaSlotUrl(item, WIX_DETAIL_IMAGE));
-  }
+  // The SDK helper reads BOTH gallery layouts — V1 `media.items` and Catalog V3
+  // `media.itemsInfo.items`. This loop used to walk `media.items` itself, which is
+  // the V1 spelling only, so a V3 product with a ten-image gallery rendered as one
+  // image no matter what the read asked for. One reader, not a private copy per
+  // worker — that is how the two layouts drifted apart in the first place.
+  for (const url of sdkProductGallery(p, WIX_DETAIL_IMAGE)) push(url);
   return urls.map((url) => ({ url }));
 }
 

package/templates/himi-chat/dev/index.ts

@@ -1269,13 +1269,13 @@ const SCREENS = runtimeSetting({
                   "style": "primary",
                   "size": "sm",
                   "fullWidth": false,
-                  "accessibilityLabel": "Send",
                   "action": {
                     "actionId": "tier5.chat.send"
                   }
                 }
               },
               "modifiers": {
+                "accessibilityLabel": "Send",
                 "hiddenPath": "$service:chat.busy"
               }
             },
@@ -1291,13 +1291,13 @@ const SCREENS = runtimeSetting({
                   "style": "primary",
                   "size": "sm",
                   "fullWidth": false,
-                  "accessibilityLabel": "Stop",
                   "action": {
                     "actionId": "tier5.chat.stop"
                   }
                 }
               },
               "modifiers": {
+                "accessibilityLabel": "Stop",
                 "hiddenPath": "$service:chat.idle"
               }
             },

package/templates/portfolio-creative/tier5-src/himi-store-product/index.ts

@@ -3,7 +3,7 @@ import { defineService } from "@himalaya/state";
 import { share as shareSheet } from "@himalaya/share";
 import { addToCurrentCart, getCurrentCart } from "@himalaya/wix-ecom";
 import { get, upsert, enqueue, type DbEntity } from "@himalaya/local-db";
-import { getStoreProduct, plainText, productImage, productPrice, wixMediaUrl, mediaSlotUrl, WIX_DETAIL_IMAGE, type StoreProduct } from "../_shared/himi-store.js";
+import { getStoreProduct, plainText, productImage, productPrice, wixMediaUrl, productGallery as sdkProductGallery, WIX_DETAIL_IMAGE, type StoreProduct } from "../_shared/himi-store.js";
 import { cleanTitle } from "../_shared/himi-text.js";
 import { stashCopy, copyParam, copyTemplate } from "../_shared/himi-copy.js";
 import { isBridgeUnavailable } from "../_shared/owner-load-error.js";
@@ -96,11 +96,12 @@ export function productGallery(p: StoreProduct): GalleryItem[] {
   // entry goes through the same CDN transform — the primary AND the extra media
   // items, which would otherwise stay untouched 4000px originals.
   push(productImage(p, WIX_DETAIL_IMAGE));
-  for (const item of p.media?.items ?? []) {
-    // Same reader productImage uses — a slot may be the reference STRING rather than
-    // an object, and two private copies of that knowledge is how they drift.
-    push(mediaSlotUrl(item, WIX_DETAIL_IMAGE));
-  }
+  // The SDK helper reads BOTH gallery layouts — V1 `media.items` and Catalog V3
+  // `media.itemsInfo.items`. This loop used to walk `media.items` itself, which is
+  // the V1 spelling only, so a V3 product with a ten-image gallery rendered as one
+  // image no matter what the read asked for. One reader, not a private copy per
+  // worker — that is how the two layouts drifted apart in the first place.
+  for (const url of sdkProductGallery(p, WIX_DETAIL_IMAGE)) push(url);
   return urls.map((url) => ({ url }));
 }
 

package/templates/retail-store/tier5-src/himi-store-product/index.ts

@@ -3,7 +3,7 @@ import { defineService } from "@himalaya/state";
 import { share as shareSheet } from "@himalaya/share";
 import { addToCurrentCart, getCurrentCart } from "@himalaya/wix-ecom";
 import { get, upsert, enqueue, type DbEntity } from "@himalaya/local-db";
-import { getStoreProduct, plainText, productImage, productPrice, wixMediaUrl, mediaSlotUrl, WIX_DETAIL_IMAGE, type StoreProduct } from "../_shared/himi-store.js";
+import { getStoreProduct, plainText, productImage, productPrice, wixMediaUrl, productGallery as sdkProductGallery, WIX_DETAIL_IMAGE, type StoreProduct } from "../_shared/himi-store.js";
 import { cleanTitle } from "../_shared/himi-text.js";
 import { stashCopy, copyParam, copyTemplate } from "../_shared/himi-copy.js";
 import { isBridgeUnavailable } from "../_shared/owner-load-error.js";
@@ -96,11 +96,12 @@ export function productGallery(p: StoreProduct): GalleryItem[] {
   // entry goes through the same CDN transform — the primary AND the extra media
   // items, which would otherwise stay untouched 4000px originals.
   push(productImage(p, WIX_DETAIL_IMAGE));
-  for (const item of p.media?.items ?? []) {
-    // Same reader productImage uses — a slot may be the reference STRING rather than
-    // an object, and two private copies of that knowledge is how they drift.
-    push(mediaSlotUrl(item, WIX_DETAIL_IMAGE));
-  }
+  // The SDK helper reads BOTH gallery layouts — V1 `media.items` and Catalog V3
+  // `media.itemsInfo.items`. This loop used to walk `media.items` itself, which is
+  // the V1 spelling only, so a V3 product with a ten-image gallery rendered as one
+  // image no matter what the read asked for. One reader, not a private copy per
+  // worker — that is how the two layouts drifted apart in the first place.
+  for (const url of sdkProductGallery(p, WIX_DETAIL_IMAGE)) push(url);
   return urls.map((url) => ({ url }));
 }