@wix/himalaya-cli 0.839.0 → 0.841.0

package/dist/authoring-runtime/node_modules/@wix/himalaya/dist/_types/core/ts/src/schema.d.ts

@@ -500,13 +500,29 @@ export type TextContent = {
     text: string;
 } | {
     template: InterpolatedText;
+} | {
+    timeRef: WidgetTimeRef;
 };
+/** Lever D (RFC 0002 OS-widget reactive leaf) — a sanctioned DECLARATIVE live time the OS
+ *  ticks with NO worker and NO refresh, so it is a frozen literal rather than a
+ *  `$service:`/`$item.` binding. `at` is epoch SECONDS. Mirrors iOS `WidgetTimeRef` and
+ *  Android `WidgetTimeRef`; `core/ts/src/validator.ts` pins the same `{ at, style? }` shape
+ *  and style set for widget snapshots. */
+export interface WidgetTimeRef {
+    /** Epoch seconds the style counts from/to. */
+    at: number;
+    /** SwiftUI `Text.DateStyle` / Android time style (default "timer"). */
+    style?: "timer" | "relative" | "date" | "time" | "offset";
+}
 export type TextProps = TextContent & {
     style?: TokenName;
     /** Foreground color token (default "textPrimary"). */
     color?: TokenName;
     /** Tail-truncate after N lines (absent = unlimited). */
     maxLines?: number;
+    /** Lever D — a live time value (countdown/relative) the OS ticks with no refresh.
+     *  When present it OVERRIDES `text`. Widget-safe render only. */
+    timeRef?: WidgetTimeRef;
     /** RFC 0009 — render `text` as a constrained Markdown subset. */
     markdown?: boolean;
     /** RFC 0034 — capability enrichments. */
@@ -730,6 +746,9 @@ export interface AvatarStripProps {
     caption?: string;
     /** Fired when tapping any avatar. */
     onTap?: Action;
+    /** Gradient token painted as a ring around each avatar — the "story" ring.
+     *  Resolved through the gradient tokens, not the colour ones. */
+    ringGradient?: TokenName;
 }
 export interface BadgeProps {
     /** Badge text — binding-aware ("$item."/"$service:") on web, iOS and Android. */
@@ -1215,6 +1234,14 @@ export interface TableProps {
     rows?: TableRow[];
     rowsPath?: string;
 }
+/** One ring of a concentric multi-ring Gauge (Apple-Fitness style). */
+export interface GaugeRing {
+    /** Fraction 0..1 for this ring. */
+    value?: number;
+    /** `$service:`/`$item.` binding → a live number (overrides `value`). */
+    valuePath?: string;
+    tint?: TokenName;
+}
 export interface GaugeProps {
     value?: number;
     /** `$service:`/`$item.` binding → a live number (overrides `value`). */
@@ -1224,6 +1251,9 @@ export interface GaugeProps {
     label?: string;
     kind?: "radial" | "linear";
     tint?: TokenName;
+    /** Concentric multi-ring gauge, drawn outer→inner. When present it overrides the
+     *  single `value`/`valuePath` radial. */
+    rings?: GaugeRing[];
     /** Motion grammar (Batch 1, item 4) — tween the fill on value change instead of
      *  snapping; gated by reduced motion. Mirror of ProgressBarProps.animated. */
     animated?: boolean;

package/dist/cli.mjs

@@ -5926,7 +5926,6 @@ __export(validate_descriptor_core_exports, {
   NATIVE_MODIFIERS_CLASS: () => NATIVE_MODIFIERS_CLASS,
   NATIVE_NESTED_CLASSES: () => NATIVE_NESTED_CLASSES,
   NATIVE_NESTED_PROPS: () => NATIVE_NESTED_PROPS,
-  NATIVE_ONLY_PROPS: () => NATIVE_ONLY_PROPS,
   NATIVE_PROP_ENUMS: () => NATIVE_PROP_ENUMS,
   NATIVE_REQUIRED_PROPS: () => NATIVE_REQUIRED_PROPS,
   SERVICE_ONLY_BINDING_PROPS: () => SERVICE_ONLY_BINDING_PROPS,
@@ -6717,14 +6716,14 @@ function componentPropFindings(descriptor) {
         const base = at ? `${at}.body.props` : "body.props";
         for (const name of Object.keys(bag)) {
           const path = `${base}.${name}`;
-          const kind = own(declared, name) ?? own(own(NATIVE_ONLY_PROPS, type) ?? {}, name);
+          const kind = own(declared, name);
           if (kind === void 0) {
             if (LEGACY_UNSCORED_KEYS.has(`${type}.${name}`)) continue;
             const hint = MODIFIER_KEYS.has(name) ? ` \u2014 \`${name}\` is a MODIFIER, not a prop: move it out of \`props\` and into the node's \`modifiers\` bag (\`{ id, body, modifiers: { ${name}: \u2026 } }\`)` : "";
             out.push({
               path,
               kind: "hygiene",
-              message: `${type} has no prop \`${name}\` \u2014 the native decoders are built with \`ignoreUnknownKeys = true\`, so this key is SILENTLY DROPPED on iOS and Android and the value never reaches the screen (web, whose props are \`any\`, may still show it). Declared props: ${[...Object.keys(declared), ...Object.keys(own(NATIVE_ONLY_PROPS, type) ?? {})].sort().join(", ") || "(none)"}${hint}`
+              message: `${type} has no prop \`${name}\` \u2014 the native decoders are built with \`ignoreUnknownKeys = true\`, so this key is SILENTLY DROPPED on iOS and Android and the value never reaches the screen (web, whose props are \`any\`, may still show it). Declared props: ${Object.keys(declared).sort().join(", ") || "(none)"}${hint}`
             });
             continue;
           }
@@ -7608,7 +7607,7 @@ function validateScreenDescriptor(screenId, descriptor, opts = {}) {
     services: Object.keys(services)
   };
 }
-var CRAWL_BLOCKING_PASSES, BOOT_EVAL_TIMEOUT_MS, DEVICE_PARITY_WITHHELD, defaultEvaluator, bootEvaluator, actionEvaluator, NATIVE_PROP_ENUMS, KNOWN_PROPS, INTEGER_PROPS, NATIVE_REQUIRED_PROPS, bareNestedClass, NATIVE_NESTED_CLASSES, NATIVE_MODIFIERS_CLASS, NATIVE_DESCRIPTOR_CLASS, NATIVE_DESCRIPTOR_NESTED, NATIVE_NESTED_PROPS, MODIFIER_KEYS, INTEGER_MODIFIERS, MODIFIER_KINDS, SCHEMA_SCORED_NODES, CORE_PACKAGES, NATIVE_ONLY_PROPS, LEGACY_UNSCORED_KEYS, DYNAMIC_PLACEHOLDER, LITERAL_ONLY_PROPS, SERVICE_ONLY_BINDING_PROPS, WHOLE_VALUE_BINDING, EMBEDDED_BINDING, OPTIONS_BINDING_PROPS;
+var CRAWL_BLOCKING_PASSES, BOOT_EVAL_TIMEOUT_MS, DEVICE_PARITY_WITHHELD, defaultEvaluator, bootEvaluator, actionEvaluator, NATIVE_PROP_ENUMS, KNOWN_PROPS, INTEGER_PROPS, NATIVE_REQUIRED_PROPS, bareNestedClass, NATIVE_NESTED_CLASSES, NATIVE_MODIFIERS_CLASS, NATIVE_DESCRIPTOR_CLASS, NATIVE_DESCRIPTOR_NESTED, NATIVE_NESTED_PROPS, MODIFIER_KEYS, INTEGER_MODIFIERS, MODIFIER_KINDS, SCHEMA_SCORED_NODES, CORE_PACKAGES, LEGACY_UNSCORED_KEYS, DYNAMIC_PLACEHOLDER, LITERAL_ONLY_PROPS, SERVICE_ONLY_BINDING_PROPS, WHOLE_VALUE_BINDING, EMBEDDED_BINDING, OPTIONS_BINDING_PROPS;
 var init_validate_descriptor_core = __esm({
   "../../core/dev-server/src/validate-descriptor.core.ts"() {
     init_validator();
@@ -7682,6 +7681,7 @@ var init_validate_descriptor_core = __esm({
         onTap: "any",
         overflowCount: "number",
         overlapRatio: "number",
+        ringGradient: "string",
         showOverflow: "boolean",
         size: "number"
       },
@@ -7849,6 +7849,7 @@ var init_validate_descriptor_core = __esm({
         label: "string",
         max: "number",
         min: "number",
+        rings: "array",
         tint: "string",
         tintPath: "string",
         value: "number",
@@ -8131,7 +8132,8 @@ var init_validate_descriptor_core = __esm({
         template: "any",
         text: "string",
         textAlign: "string",
-        textDirection: "string"
+        textDirection: "string",
+        timeRef: "any"
       },
       TextField: {
         autoCapitalization: "string",
@@ -8475,16 +8477,6 @@ var init_validate_descriptor_core = __esm({
     CORE_PACKAGES = new Set(
       [...CORE_COMPONENTS].map((key2) => key2.slice(0, key2.indexOf(".")))
     );
-    NATIVE_ONLY_PROPS = {
-      // Schema.kt:1970 — `String?`, a gradient token → a per-avatar "story" ring.
-      AvatarStrip: { ringGradient: "string" },
-      // Schema.kt:2362 — `List<GaugeRing>?`, a concentric multi-ring gauge (overrides the value).
-      Gauge: { rings: "array" },
-      // Schema.kt:944 — `WidgetTimeRef?`, a widget-safe live clock; on a widget it overrides `text`.
-      // A serializable, so `any`: `NATIVE_NESTED_PROPS` owns what is INSIDE it, exactly as it does
-      // for every other object-valued prop.
-      Text: { timeRef: "any" }
-    };
     LEGACY_UNSCORED_KEYS = /* @__PURE__ */ new Set([
       // 297 sites / 8 packages. Meant `leadingIcon` (or `trailingIcon`).
       "Button.icon",
@@ -36843,7 +36835,6 @@ __export(validate_descriptor_exports, {
   NATIVE_MODIFIERS_CLASS: () => NATIVE_MODIFIERS_CLASS,
   NATIVE_NESTED_CLASSES: () => NATIVE_NESTED_CLASSES,
   NATIVE_NESTED_PROPS: () => NATIVE_NESTED_PROPS,
-  NATIVE_ONLY_PROPS: () => NATIVE_ONLY_PROPS,
   NATIVE_PROP_ENUMS: () => NATIVE_PROP_ENUMS,
   NATIVE_REQUIRED_PROPS: () => NATIVE_REQUIRED_PROPS,
   SERVICE_ONLY_BINDING_PROPS: () => SERVICE_ONLY_BINDING_PROPS,
@@ -63114,7 +63105,8 @@ default (no --glyph): ${DEFAULT_GLYPH2} \u2014 a mark that claims nothing, so th
           ...surfaceIssues(dir, outcome.surfaceNav, strict),
           ...tokenColorIssues(dir),
           ...await iconIssues(dir, strict),
-          ...fontIssues(dir, strict)
+          ...fontIssues(dir, strict),
+          ...storesV1Issues(dir, strict)
         ]);
         if (hasErrors && !force) {
           print({ ...report, pushed: false, hint: "lint found errors \u2014 fix them, or re-run `himi push --force` to publish anyway" });
@@ -63468,8 +63460,10 @@ default (no --glyph): ${DEFAULT_GLYPH2} \u2014 a mark that claims nothing, so th
         const { report, hasErrors } = summarizeLint(app, bres, outcome, strict, [
           ...await cmsIssues(dir, app, strict, { local: true }),
           ...surfaceIssues(dir, outcome.surfaceNav, strict),
+          ...tokenColorIssues(dir),
           ...await iconIssues(dir, strict),
-          ...fontIssues(dir, strict)
+          ...fontIssues(dir, strict),
+          ...storesV1Issues(dir, strict)
         ]);
         if (hasErrors && !force) {
           rmSync9(built, { recursive: true, force: true });

package/guides/component-reference.json

@@ -101,7 +101,7 @@
       "bindings": [
         "text"
       ],
-      "propsSource": "export type TextProps = TextContent & {\n  style?: TokenName;\n  /** Foreground color token (default \"textPrimary\"). */\n  color?: TokenName;\n  /** Tail-truncate after N lines (absent = unlimited). */\n  maxLines?: number;\n  /** Render `text` as a constrained Markdown subset. */\n  markdown?: boolean;\n  /** Capability enrichments. */\n  textAlign?: \"leading\" | \"center\" | \"trailing\" | \"justify\";\n  /** Base writing direction. \"auto\" (or \"rtl\") makes a bidi paragraph resolve +\n   *  align by its own strong-directional content (Hebrew/Arabic → right-aligned,\n   *  RTL layout), matching per-message direction in chat bubbles. Absent/\"ltr\" =\n   *  the current left-to-right behavior. Both renderers honor it (parity). */\n  textDirection?: \"auto\" | \"ltr\" | \"rtl\";\n  decoration?: \"underline\" | \"strikethrough\";\n  lineSpacing?: number;\n  /** Per-item gate (usually an `$item.` field pre-substituted per row): when it\n   *  resolves empty, the text collapses to zero size instead of taking layout. */\n  collapseWhenEmpty?: boolean;\n  /** Motion grammar (Batch 1, item 4) — count-up tween for a numeric value on\n   *  change; non-numeric values render instantly. Gated by reduced motion. */\n  animateValue?: boolean;\n  /** Motion grammar — reveal the (post-substitution literal) text word-by-word,\n   *  once per distinct content, like a chat assistant \"typing\" its reply. Each\n   *  content animates a single time (progress is remembered), so list re-renders\n   *  and scrolls don't restart it. Gated by reduced motion (snaps to full).\n   *  Both renderers honor it (parity). Default nil/false. */\n  animateReveal?: boolean;\n};"
+      "propsSource": "export type TextProps = TextContent & {\n  style?: TokenName;\n  /** Foreground color token (default \"textPrimary\"). */\n  color?: TokenName;\n  /** Tail-truncate after N lines (absent = unlimited). */\n  maxLines?: number;\n  /** Lever D — a live time value (countdown/relative) the OS ticks with no refresh.\n   *  When present it OVERRIDES `text`. Widget-safe render only. */\n  timeRef?: WidgetTimeRef;\n  /** Render `text` as a constrained Markdown subset. */\n  markdown?: boolean;\n  /** Capability enrichments. */\n  textAlign?: \"leading\" | \"center\" | \"trailing\" | \"justify\";\n  /** Base writing direction. \"auto\" (or \"rtl\") makes a bidi paragraph resolve +\n   *  align by its own strong-directional content (Hebrew/Arabic → right-aligned,\n   *  RTL layout), matching per-message direction in chat bubbles. Absent/\"ltr\" =\n   *  the current left-to-right behavior. Both renderers honor it (parity). */\n  textDirection?: \"auto\" | \"ltr\" | \"rtl\";\n  decoration?: \"underline\" | \"strikethrough\";\n  lineSpacing?: number;\n  /** Per-item gate (usually an `$item.` field pre-substituted per row): when it\n   *  resolves empty, the text collapses to zero size instead of taking layout. */\n  collapseWhenEmpty?: boolean;\n  /** Motion grammar (Batch 1, item 4) — count-up tween for a numeric value on\n   *  change; non-numeric values render instantly. Gated by reduced motion. */\n  animateValue?: boolean;\n  /** Motion grammar — reveal the (post-substitution literal) text word-by-word,\n   *  once per distinct content, like a chat assistant \"typing\" its reply. Each\n   *  content animates a single time (progress is remembered), so list re-renders\n   *  and scrolls don't restart it. Gated by reduced motion (snaps to full).\n   *  Both renderers honor it (parity). Default nil/false. */\n  animateReveal?: boolean;\n};"
     },
     {
       "name": "Image",
@@ -388,7 +388,7 @@
       "bindings": [
         "avatarsPath"
       ],
-      "propsSource": "export interface AvatarStripProps {\n  /** `$service:` binding → a live array of `{imageUrl, initials}` (overrides `avatars`). */\n  avatarsPath?: string;\n  /** Literal fallback (Tier 0–4); ignored if `avatarsPath` resolves. */\n  avatars?: AvatarStripAvatar[];\n  /** Diameter in points (default 40). */\n  size?: number;\n  /** 0..1; shift = size * (1 - overlapRatio) (default 0.67). */\n  overlapRatio?: number;\n  /** Max avatars before overflow (default 4). */\n  maxVisible?: number;\n  /** Default true. */\n  showOverflow?: boolean;\n  /** Explicit overflow; if 0/absent computed from total. */\n  overflowCount?: number;\n  /** Literal caption (or `$service:` upstream-resolved). */\n  caption?: string;\n  /** Fired when tapping any avatar. */\n  onTap?: Action;\n}"
+      "propsSource": "export interface AvatarStripProps {\n  /** `$service:` binding → a live array of `{imageUrl, initials}` (overrides `avatars`). */\n  avatarsPath?: string;\n  /** Literal fallback (Tier 0–4); ignored if `avatarsPath` resolves. */\n  avatars?: AvatarStripAvatar[];\n  /** Diameter in points (default 40). */\n  size?: number;\n  /** 0..1; shift = size * (1 - overlapRatio) (default 0.67). */\n  overlapRatio?: number;\n  /** Max avatars before overflow (default 4). */\n  maxVisible?: number;\n  /** Default true. */\n  showOverflow?: boolean;\n  /** Explicit overflow; if 0/absent computed from total. */\n  overflowCount?: number;\n  /** Literal caption (or `$service:` upstream-resolved). */\n  caption?: string;\n  /** Fired when tapping any avatar. */\n  onTap?: Action;\n  /** Gradient token painted as a ring around each avatar — the \"story\" ring.\n   *  Resolved through the gradient tokens, not the colour ones. */\n  ringGradient?: TokenName;\n}"
     },
     {
       "name": "Banner",
@@ -651,7 +651,7 @@
         "valuePath",
         "tintPath"
       ],
-      "propsSource": "export interface GaugeProps {\n  value?: number;\n  /** `$service:`/`$item.` binding → a live number (overrides `value`). */\n  valuePath?: string;\n  min?: number;\n  max?: number;\n  label?: string;\n  kind?: \"radial\" | \"linear\";\n  tint?: TokenName;\n  /** Motion grammar (Batch 1, item 4) — tween the fill on value change instead of\n   *  snapping; gated by reduced motion. Mirror of ProgressBarProps.animated. */\n  animated?: boolean;\n  /** #1055 — `$service:`/`$item.` binding resolving to a tint TOKEN NAME (overrides `tint`). Binding-aware. */\n  tintPath?: string;\n}"
+      "propsSource": "export interface GaugeProps {\n  value?: number;\n  /** `$service:`/`$item.` binding → a live number (overrides `value`). */\n  valuePath?: string;\n  min?: number;\n  max?: number;\n  label?: string;\n  kind?: \"radial\" | \"linear\";\n  tint?: TokenName;\n  /** Concentric multi-ring gauge, drawn outer→inner. When present it overrides the\n   *  single `value`/`valuePath` radial. */\n  rings?: GaugeRing[];\n  /** Motion grammar (Batch 1, item 4) — tween the fill on value change instead of\n   *  snapping; gated by reduced motion. Mirror of ProgressBarProps.animated. */\n  animated?: boolean;\n  /** #1055 — `$service:`/`$item.` binding resolving to a tint TOKEN NAME (overrides `tint`). Binding-aware. */\n  tintPath?: string;\n}"
     },
     {
       "name": "Rating",
@@ -887,6 +887,8 @@
     "Presentation": "export type Presentation =\n  | \"push\"\n  | \"sheet\"\n  | \"replace\"\n  | \"dismiss\"\n  | \"back\"\n  | \"full_screen\"\n  | \"alert\"\n  | \"snackbar\";",
     "FilterChip": "export interface FilterChip {\n  id: string;\n  label: string;\n  leadingIcon?: IconRef;\n  count?: number;\n}",
     "TabItem": "export interface TabItem {\n  id: string;\n  label: string;\n  badge?: string;\n}",
+    "GaugeRing": "export interface GaugeRing {\n  /** Fraction 0..1 for this ring. */\n  value?: number;\n  /** `$service:`/`$item.` binding → a live number (overrides `value`). */\n  valuePath?: string;\n  tint?: TokenName;\n}",
+    "WidgetTimeRef": "export interface WidgetTimeRef {\n  /** Epoch seconds the style counts from/to. */\n  at: number;\n  /** SwiftUI `Text.DateStyle` / Android time style (default \"timer\"). */\n  style?: \"timer\" | \"relative\" | \"date\" | \"time\" | \"offset\";\n}",
     "Border": "export interface Border {\n  width: number;\n  color: TokenRef;\n}"
   }
 }

package/guides/component-reference.md

@@ -167,7 +167,7 @@ So `border` nests an object and `boxShadow`/`backgroundGradient` nest strings. R
 element interface (printed below) rather than extrapolating from the level.
 
 - Modifier-level (`TokenRef` object): `modifiers.background`, `modifiers.shadow`, `modifiers.backgroundGradient`, `modifiers.appear`, `modifiers.material`, `modifiers.pressMotion`, `modifiers.border.color`.
-- Component-prop-level (bare `TokenName` string): `Card.background`, `Text.style`, `Text.color`, `Image.placeholder`, `Image.tint`, `Icon.tint`, `Toggle.trackOn`, `Toggle.trackOff`, `Toggle.thumb`, `Badge.token`, `Tag.token`, `ProgressBar.tint`, `ProgressBar.trackColor`, `ListItem.titleStyle`, `ListItem.subtitleStyle`, `ListItem.titleColor`, `ListItem.subtitleColor`, `ListItem.overlineColor`, `Slider.tint`, `ActivityIndicator.tint`, `Chip.token`, `Label.style`, `Label.color`, `Gauge.tint`, `Rating.color`, `Chart.color`, `DonutChart.color`, `VoiceNote.tint`, `Marquee.style`, `Marquee.color`, `Fab.tint`.
+- Component-prop-level (bare `TokenName` string): `Card.background`, `Text.style`, `Text.color`, `Image.placeholder`, `Image.tint`, `Icon.tint`, `Toggle.trackOn`, `Toggle.trackOff`, `Toggle.thumb`, `Badge.token`, `Tag.token`, `ProgressBar.tint`, `ProgressBar.trackColor`, `AvatarStrip.ringGradient`, `ListItem.titleStyle`, `ListItem.subtitleStyle`, `ListItem.titleColor`, `ListItem.subtitleColor`, `ListItem.overlineColor`, `Slider.tint`, `ActivityIndicator.tint`, `Chip.token`, `Label.style`, `Label.color`, `Gauge.tint`, `Rating.color`, `Chart.color`, `DonutChart.color`, `VoiceNote.tint`, `Marquee.style`, `Marquee.color`, `Fab.tint`.
 
 There is **no `modifiers.color` and no `modifiers.tint`** — a `tint` is always a component
 prop. Of the two nested slots spelled `color`, `modifiers.border.color` is a `TokenRef`
@@ -366,6 +366,9 @@ export type TextProps = TextContent & {
   color?: TokenName;
   /** Tail-truncate after N lines (absent = unlimited). */
   maxLines?: number;
+  /** Lever D — a live time value (countdown/relative) the OS ticks with no refresh.
+   *  When present it OVERRIDES `text`. Widget-safe render only. */
+  timeRef?: WidgetTimeRef;
   /** Render `text` as a constrained Markdown subset. */
   markdown?: boolean;
   /** Capability enrichments. */
@@ -915,6 +918,9 @@ export interface AvatarStripProps {
   caption?: string;
   /** Fired when tapping any avatar. */
   onTap?: Action;
+  /** Gradient token painted as a ring around each avatar — the "story" ring.
+   *  Resolved through the gradient tokens, not the colour ones. */
+  ringGradient?: TokenName;
 }
 ```
 
@@ -1265,6 +1271,9 @@ export interface GaugeProps {
   label?: string;
   kind?: "radial" | "linear";
   tint?: TokenName;
+  /** Concentric multi-ring gauge, drawn outer→inner. When present it overrides the
+   *  single `value`/`valuePath` radial. */
+  rings?: GaugeRing[];
   /** Motion grammar (Batch 1, item 4) — tween the fill on value change instead of
    *  snapping; gated by reduced motion. Mirror of ProgressBarProps.animated. */
   animated?: boolean;
@@ -1913,12 +1922,15 @@ export interface LogicBundleRef {
 }
 ```
 
-## Element shapes (list & tab items)
+## Element shapes (list & tab items, and other typed prop objects)
 
-A few props take an array of typed **element objects** rather than nested components:
-`FilterChips.chips` is a `FilterChip[]`, and `SegmentedControl.options` / `Tabs.tabs` are a
-`TabItem[]`. The prop blocks above name those arrays; here are the element interfaces themselves
-(each item's own fields — `id` is what an `onChange` reports back).
+A few props take a typed **object** rather than nested components. Some are arrays of them:
+`FilterChips.chips` is a `FilterChip[]`, `SegmentedControl.options` / `Tabs.tabs` are a
+`TabItem[]`, and `Gauge.rings` is a `GaugeRing[]` (concentric rings, drawn outer→inner).
+One is a single object: `Text.timeRef` is a `WidgetTimeRef`, the widget-safe live clock —
+note its `at` is REQUIRED and is in epoch SECONDS. The prop blocks above name these types;
+here are the interfaces themselves (for the arrays, each item's own fields — `id` is what an
+`onChange` reports back).
 
 ```ts
 export interface FilterChip {
@@ -1933,6 +1945,21 @@ export interface TabItem {
   label: string;
   badge?: string;
 }
+
+export interface GaugeRing {
+  /** Fraction 0..1 for this ring. */
+  value?: number;
+  /** `$service:`/`$item.` binding → a live number (overrides `value`). */
+  valuePath?: string;
+  tint?: TokenName;
+}
+
+export interface WidgetTimeRef {
+  /** Epoch seconds the style counts from/to. */
+  at: number;
+  /** SwiftUI `Text.DateStyle` / Android time style (default "timer"). */
+  style?: "timer" | "relative" | "date" | "time" | "offset";
+}
 ```
 
 ## Modifiers

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/himalaya-cli",
-  "version": "0.839.0",
+  "version": "0.841.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": "5de4fef57d6c6e87d57791a1f1af4e7bd241ef8902a4fbb3292442a0"
+  "falconPackageHash": "60bd923f4e7d6bcb8c585e19b160bbc63f2db7758a553bd612e945ad"
 }

package/templates/beauty-salon-owner/tier5-src/himi-owner-lite-aria/index.ts

@@ -186,5 +186,33 @@ const svc = defineService<AriaChatState, {
   },
 });
 
-svc.load();
+// NO module-scope `svc.load()`, deliberately — the descriptor's `onAppear` is the
+// only entry point, and on Android the self-kick did not merely duplicate it, it
+// DISABLED the screen.
+//
+// `load` opens by creating a conversation, so a self-kick puts a `wixApi.call`
+// inside the bundle's own evaluation — and a bridge call made during
+// `worker.boot(bundle)` stalls on the Android WebView. The host completes it
+// (`bridge_wix_call … ok=true` is logged between `bundle eval done` and
+// `services=[…]`) but the JS promise never settles. `createOnce` then caches that
+// promise as the per-site create latch, so the `onAppear` load — dispatched
+// correctly, and fine on its own — awaits the same dead promise and never returns
+// either. Result on Android: no greeting, no prompt chips, no conversation, and a
+// Send that does nothing, for the life of the screen. Nothing reports it, because
+// a pending dispatch has no timeout: an action that never settles is
+// indistinguishable from one still running (#2518).
+//
+// That stall is a known Android defect, not a new one. `WebViewJSWorker` already
+// prepends per-screen input into the bundle's own evaluate rather than assigning it
+// separately, and says why: "the bundle's first wixApi.call could stall". Aria is
+// simply the first owner-lite screen to call the network at module scope and so the
+// first to meet it head-on. Fixing the stall is a core-runtime change tracked
+// separately; not calling the network before the screen exists is right regardless.
+//
+// The self-kick was never load-bearing. Both hosts queue a `tier5.*` action
+// dispatched before the worker is up — `Tier5WorkerSession.invoke` on Android and
+// `HimalayaScreenHost.dispatch` on iOS — and both say in as many words that the
+// self-kick is what made `onAppear` only LOOK like it worked. It also cost a
+// second conversation-create attempt per open and minted the greeting with
+// fallback copy, since the copy pack only arrives with the onAppear params.
 export { svc };

package/templates/beauty-salon-owner/tier5-src/himi-owner-lite-aria-history/index.ts

@@ -38,5 +38,14 @@ const svc = defineService<AriaHistoryState, {
   },
 });
 
-svc.load();
+// NO module-scope `svc.load()` — same reason as the chat adapter next door, which
+// carries the full explanation. This `load` opens with `getConversations`, so a
+// self-kick makes a bridge call inside the bundle's own evaluation, and such a call
+// stalls on the Android WebView (#2518).
+//
+// It is less damaging here than on the chat screen: this load has no create latch
+// for a dead promise to poison, so the `onAppear` load issues its own request and
+// the list still fills. What the self-kick leaves behind is a dispatch that never
+// settles — `pendingDispatches` has no timeout, so it is held for the life of the
+// worker, on every open. Not worth keeping for a call whose result nothing reads.
 export { svc };

package/templates/community-club-owner/tier5-src/himi-owner-lite-aria/index.ts

@@ -186,5 +186,33 @@ const svc = defineService<AriaChatState, {
   },
 });
 
-svc.load();
+// NO module-scope `svc.load()`, deliberately — the descriptor's `onAppear` is the
+// only entry point, and on Android the self-kick did not merely duplicate it, it
+// DISABLED the screen.
+//
+// `load` opens by creating a conversation, so a self-kick puts a `wixApi.call`
+// inside the bundle's own evaluation — and a bridge call made during
+// `worker.boot(bundle)` stalls on the Android WebView. The host completes it
+// (`bridge_wix_call … ok=true` is logged between `bundle eval done` and
+// `services=[…]`) but the JS promise never settles. `createOnce` then caches that
+// promise as the per-site create latch, so the `onAppear` load — dispatched
+// correctly, and fine on its own — awaits the same dead promise and never returns
+// either. Result on Android: no greeting, no prompt chips, no conversation, and a
+// Send that does nothing, for the life of the screen. Nothing reports it, because
+// a pending dispatch has no timeout: an action that never settles is
+// indistinguishable from one still running (#2518).
+//
+// That stall is a known Android defect, not a new one. `WebViewJSWorker` already
+// prepends per-screen input into the bundle's own evaluate rather than assigning it
+// separately, and says why: "the bundle's first wixApi.call could stall". Aria is
+// simply the first owner-lite screen to call the network at module scope and so the
+// first to meet it head-on. Fixing the stall is a core-runtime change tracked
+// separately; not calling the network before the screen exists is right regardless.
+//
+// The self-kick was never load-bearing. Both hosts queue a `tier5.*` action
+// dispatched before the worker is up — `Tier5WorkerSession.invoke` on Android and
+// `HimalayaScreenHost.dispatch` on iOS — and both say in as many words that the
+// self-kick is what made `onAppear` only LOOK like it worked. It also cost a
+// second conversation-create attempt per open and minted the greeting with
+// fallback copy, since the copy pack only arrives with the onAppear params.
 export { svc };

package/templates/community-club-owner/tier5-src/himi-owner-lite-aria-history/index.ts

@@ -38,5 +38,14 @@ const svc = defineService<AriaHistoryState, {
   },
 });
 
-svc.load();
+// NO module-scope `svc.load()` — same reason as the chat adapter next door, which
+// carries the full explanation. This `load` opens with `getConversations`, so a
+// self-kick makes a bridge call inside the bundle's own evaluation, and such a call
+// stalls on the Android WebView (#2518).
+//
+// It is less damaging here than on the chat screen: this load has no create latch
+// for a dead promise to poison, so the `onAppear` load issues its own request and
+// the list still fills. What the self-kick leaves behind is a dispatch that never
+// settles — `pendingDispatches` has no timeout, so it is held for the life of the
+// worker, on every open. Not worth keeping for a call whose result nothing reads.
 export { svc };

package/templates/events-meetups-owner/tier5-src/himi-owner-lite-aria/index.ts

@@ -186,5 +186,33 @@ const svc = defineService<AriaChatState, {
   },
 });
 
-svc.load();
+// NO module-scope `svc.load()`, deliberately — the descriptor's `onAppear` is the
+// only entry point, and on Android the self-kick did not merely duplicate it, it
+// DISABLED the screen.
+//
+// `load` opens by creating a conversation, so a self-kick puts a `wixApi.call`
+// inside the bundle's own evaluation — and a bridge call made during
+// `worker.boot(bundle)` stalls on the Android WebView. The host completes it
+// (`bridge_wix_call … ok=true` is logged between `bundle eval done` and
+// `services=[…]`) but the JS promise never settles. `createOnce` then caches that
+// promise as the per-site create latch, so the `onAppear` load — dispatched
+// correctly, and fine on its own — awaits the same dead promise and never returns
+// either. Result on Android: no greeting, no prompt chips, no conversation, and a
+// Send that does nothing, for the life of the screen. Nothing reports it, because
+// a pending dispatch has no timeout: an action that never settles is
+// indistinguishable from one still running (#2518).
+//
+// That stall is a known Android defect, not a new one. `WebViewJSWorker` already
+// prepends per-screen input into the bundle's own evaluate rather than assigning it
+// separately, and says why: "the bundle's first wixApi.call could stall". Aria is
+// simply the first owner-lite screen to call the network at module scope and so the
+// first to meet it head-on. Fixing the stall is a core-runtime change tracked
+// separately; not calling the network before the screen exists is right regardless.
+//
+// The self-kick was never load-bearing. Both hosts queue a `tier5.*` action
+// dispatched before the worker is up — `Tier5WorkerSession.invoke` on Android and
+// `HimalayaScreenHost.dispatch` on iOS — and both say in as many words that the
+// self-kick is what made `onAppear` only LOOK like it worked. It also cost a
+// second conversation-create attempt per open and minted the greeting with
+// fallback copy, since the copy pack only arrives with the onAppear params.
 export { svc };

package/templates/events-meetups-owner/tier5-src/himi-owner-lite-aria-history/index.ts

@@ -38,5 +38,14 @@ const svc = defineService<AriaHistoryState, {
   },
 });
 
-svc.load();
+// NO module-scope `svc.load()` — same reason as the chat adapter next door, which
+// carries the full explanation. This `load` opens with `getConversations`, so a
+// self-kick makes a bridge call inside the bundle's own evaluation, and such a call
+// stalls on the Android WebView (#2518).
+//
+// It is less damaging here than on the chat screen: this load has no create latch
+// for a dead promise to poison, so the `onAppear` load issues its own request and
+// the list still fills. What the self-kick leaves behind is a dispatch that never
+// settles — `pendingDispatches` has no timeout, so it is held for the life of the
+// worker, on every open. Not worth keeping for a call whose result nothing reads.
 export { svc };

package/templates/gym-fitness-owner/tier5-src/himi-owner-lite-aria/index.ts

@@ -186,5 +186,33 @@ const svc = defineService<AriaChatState, {
   },
 });
 
-svc.load();
+// NO module-scope `svc.load()`, deliberately — the descriptor's `onAppear` is the
+// only entry point, and on Android the self-kick did not merely duplicate it, it
+// DISABLED the screen.
+//
+// `load` opens by creating a conversation, so a self-kick puts a `wixApi.call`
+// inside the bundle's own evaluation — and a bridge call made during
+// `worker.boot(bundle)` stalls on the Android WebView. The host completes it
+// (`bridge_wix_call … ok=true` is logged between `bundle eval done` and
+// `services=[…]`) but the JS promise never settles. `createOnce` then caches that
+// promise as the per-site create latch, so the `onAppear` load — dispatched
+// correctly, and fine on its own — awaits the same dead promise and never returns
+// either. Result on Android: no greeting, no prompt chips, no conversation, and a
+// Send that does nothing, for the life of the screen. Nothing reports it, because
+// a pending dispatch has no timeout: an action that never settles is
+// indistinguishable from one still running (#2518).
+//
+// That stall is a known Android defect, not a new one. `WebViewJSWorker` already
+// prepends per-screen input into the bundle's own evaluate rather than assigning it
+// separately, and says why: "the bundle's first wixApi.call could stall". Aria is
+// simply the first owner-lite screen to call the network at module scope and so the
+// first to meet it head-on. Fixing the stall is a core-runtime change tracked
+// separately; not calling the network before the screen exists is right regardless.
+//
+// The self-kick was never load-bearing. Both hosts queue a `tier5.*` action
+// dispatched before the worker is up — `Tier5WorkerSession.invoke` on Android and
+// `HimalayaScreenHost.dispatch` on iOS — and both say in as many words that the
+// self-kick is what made `onAppear` only LOOK like it worked. It also cost a
+// second conversation-create attempt per open and minted the greeting with
+// fallback copy, since the copy pack only arrives with the onAppear params.
 export { svc };

package/templates/gym-fitness-owner/tier5-src/himi-owner-lite-aria-history/index.ts

@@ -38,5 +38,14 @@ const svc = defineService<AriaHistoryState, {
   },
 });
 
-svc.load();
+// NO module-scope `svc.load()` — same reason as the chat adapter next door, which
+// carries the full explanation. This `load` opens with `getConversations`, so a
+// self-kick makes a bridge call inside the bundle's own evaluation, and such a call
+// stalls on the Android WebView (#2518).
+//
+// It is less damaging here than on the chat screen: this load has no create latch
+// for a dead promise to poison, so the `onAppear` load issues its own request and
+// the list still fills. What the self-kick leaves behind is a dispatch that never
+// settles — `pendingDispatches` has no timeout, so it is held for the life of the
+// worker, on every open. Not worth keeping for a call whose result nothing reads.
 export { svc };

package/templates/nonprofit-cause-owner/tier5-src/himi-owner-lite-aria/index.ts

@@ -186,5 +186,33 @@ const svc = defineService<AriaChatState, {
   },
 });
 
-svc.load();
+// NO module-scope `svc.load()`, deliberately — the descriptor's `onAppear` is the
+// only entry point, and on Android the self-kick did not merely duplicate it, it
+// DISABLED the screen.
+//
+// `load` opens by creating a conversation, so a self-kick puts a `wixApi.call`
+// inside the bundle's own evaluation — and a bridge call made during
+// `worker.boot(bundle)` stalls on the Android WebView. The host completes it
+// (`bridge_wix_call … ok=true` is logged between `bundle eval done` and
+// `services=[…]`) but the JS promise never settles. `createOnce` then caches that
+// promise as the per-site create latch, so the `onAppear` load — dispatched
+// correctly, and fine on its own — awaits the same dead promise and never returns
+// either. Result on Android: no greeting, no prompt chips, no conversation, and a
+// Send that does nothing, for the life of the screen. Nothing reports it, because
+// a pending dispatch has no timeout: an action that never settles is
+// indistinguishable from one still running (#2518).
+//
+// That stall is a known Android defect, not a new one. `WebViewJSWorker` already
+// prepends per-screen input into the bundle's own evaluate rather than assigning it
+// separately, and says why: "the bundle's first wixApi.call could stall". Aria is
+// simply the first owner-lite screen to call the network at module scope and so the
+// first to meet it head-on. Fixing the stall is a core-runtime change tracked
+// separately; not calling the network before the screen exists is right regardless.
+//
+// The self-kick was never load-bearing. Both hosts queue a `tier5.*` action
+// dispatched before the worker is up — `Tier5WorkerSession.invoke` on Android and
+// `HimalayaScreenHost.dispatch` on iOS — and both say in as many words that the
+// self-kick is what made `onAppear` only LOOK like it worked. It also cost a
+// second conversation-create attempt per open and minted the greeting with
+// fallback copy, since the copy pack only arrives with the onAppear params.
 export { svc };

package/templates/nonprofit-cause-owner/tier5-src/himi-owner-lite-aria-history/index.ts

@@ -38,5 +38,14 @@ const svc = defineService<AriaHistoryState, {
   },
 });
 
-svc.load();
+// NO module-scope `svc.load()` — same reason as the chat adapter next door, which
+// carries the full explanation. This `load` opens with `getConversations`, so a
+// self-kick makes a bridge call inside the bundle's own evaluation, and such a call
+// stalls on the Android WebView (#2518).
+//
+// It is less damaging here than on the chat screen: this load has no create latch
+// for a dead promise to poison, so the `onAppear` load issues its own request and
+// the list still fills. What the self-kick leaves behind is a dispatch that never
+// settles — `pendingDispatches` has no timeout, so it is held for the life of the
+// worker, on every open. Not worth keeping for a call whose result nothing reads.
 export { svc };

package/templates/owner-lite/tier5-src/himi-owner-lite-aria/index.ts

@@ -186,5 +186,33 @@ const svc = defineService<AriaChatState, {
   },
 });
 
-svc.load();
+// NO module-scope `svc.load()`, deliberately — the descriptor's `onAppear` is the
+// only entry point, and on Android the self-kick did not merely duplicate it, it
+// DISABLED the screen.
+//
+// `load` opens by creating a conversation, so a self-kick puts a `wixApi.call`
+// inside the bundle's own evaluation — and a bridge call made during
+// `worker.boot(bundle)` stalls on the Android WebView. The host completes it
+// (`bridge_wix_call … ok=true` is logged between `bundle eval done` and
+// `services=[…]`) but the JS promise never settles. `createOnce` then caches that
+// promise as the per-site create latch, so the `onAppear` load — dispatched
+// correctly, and fine on its own — awaits the same dead promise and never returns
+// either. Result on Android: no greeting, no prompt chips, no conversation, and a
+// Send that does nothing, for the life of the screen. Nothing reports it, because
+// a pending dispatch has no timeout: an action that never settles is
+// indistinguishable from one still running (#2518).
+//
+// That stall is a known Android defect, not a new one. `WebViewJSWorker` already
+// prepends per-screen input into the bundle's own evaluate rather than assigning it
+// separately, and says why: "the bundle's first wixApi.call could stall". Aria is
+// simply the first owner-lite screen to call the network at module scope and so the
+// first to meet it head-on. Fixing the stall is a core-runtime change tracked
+// separately; not calling the network before the screen exists is right regardless.
+//
+// The self-kick was never load-bearing. Both hosts queue a `tier5.*` action
+// dispatched before the worker is up — `Tier5WorkerSession.invoke` on Android and
+// `HimalayaScreenHost.dispatch` on iOS — and both say in as many words that the
+// self-kick is what made `onAppear` only LOOK like it worked. It also cost a
+// second conversation-create attempt per open and minted the greeting with
+// fallback copy, since the copy pack only arrives with the onAppear params.
 export { svc };

package/templates/owner-lite/tier5-src/himi-owner-lite-aria-history/index.ts

@@ -38,5 +38,14 @@ const svc = defineService<AriaHistoryState, {
   },
 });
 
-svc.load();
+// NO module-scope `svc.load()` — same reason as the chat adapter next door, which
+// carries the full explanation. This `load` opens with `getConversations`, so a
+// self-kick makes a bridge call inside the bundle's own evaluation, and such a call
+// stalls on the Android WebView (#2518).
+//
+// It is less damaging here than on the chat screen: this load has no create latch
+// for a dead promise to poison, so the `onAppear` load issues its own request and
+// the list still fills. What the self-kick leaves behind is a dispatch that never
+// settles — `pendingDispatches` has no timeout, so it is held for the life of the
+// worker, on every open. Not worth keeping for a call whose result nothing reads.
 export { svc };

package/templates/podcast-creator-owner/tier5-src/himi-owner-lite-aria/index.ts

@@ -186,5 +186,33 @@ const svc = defineService<AriaChatState, {
   },
 });
 
-svc.load();
+// NO module-scope `svc.load()`, deliberately — the descriptor's `onAppear` is the
+// only entry point, and on Android the self-kick did not merely duplicate it, it
+// DISABLED the screen.
+//
+// `load` opens by creating a conversation, so a self-kick puts a `wixApi.call`
+// inside the bundle's own evaluation — and a bridge call made during
+// `worker.boot(bundle)` stalls on the Android WebView. The host completes it
+// (`bridge_wix_call … ok=true` is logged between `bundle eval done` and
+// `services=[…]`) but the JS promise never settles. `createOnce` then caches that
+// promise as the per-site create latch, so the `onAppear` load — dispatched
+// correctly, and fine on its own — awaits the same dead promise and never returns
+// either. Result on Android: no greeting, no prompt chips, no conversation, and a
+// Send that does nothing, for the life of the screen. Nothing reports it, because
+// a pending dispatch has no timeout: an action that never settles is
+// indistinguishable from one still running (#2518).
+//
+// That stall is a known Android defect, not a new one. `WebViewJSWorker` already
+// prepends per-screen input into the bundle's own evaluate rather than assigning it
+// separately, and says why: "the bundle's first wixApi.call could stall". Aria is
+// simply the first owner-lite screen to call the network at module scope and so the
+// first to meet it head-on. Fixing the stall is a core-runtime change tracked
+// separately; not calling the network before the screen exists is right regardless.
+//
+// The self-kick was never load-bearing. Both hosts queue a `tier5.*` action
+// dispatched before the worker is up — `Tier5WorkerSession.invoke` on Android and
+// `HimalayaScreenHost.dispatch` on iOS — and both say in as many words that the
+// self-kick is what made `onAppear` only LOOK like it worked. It also cost a
+// second conversation-create attempt per open and minted the greeting with
+// fallback copy, since the copy pack only arrives with the onAppear params.
 export { svc };

package/templates/podcast-creator-owner/tier5-src/himi-owner-lite-aria-history/index.ts

@@ -38,5 +38,14 @@ const svc = defineService<AriaHistoryState, {
   },
 });
 
-svc.load();
+// NO module-scope `svc.load()` — same reason as the chat adapter next door, which
+// carries the full explanation. This `load` opens with `getConversations`, so a
+// self-kick makes a bridge call inside the bundle's own evaluation, and such a call
+// stalls on the Android WebView (#2518).
+//
+// It is less damaging here than on the chat screen: this load has no create latch
+// for a dead promise to poison, so the `onAppear` load issues its own request and
+// the list still fills. What the self-kick leaves behind is a dispatch that never
+// settles — `pendingDispatches` has no timeout, so it is held for the life of the
+// worker, on every open. Not worth keeping for a call whose result nothing reads.
 export { svc };

package/templates/portfolio-creative-owner/tier5-src/himi-owner-lite-aria/index.ts

@@ -186,5 +186,33 @@ const svc = defineService<AriaChatState, {
   },
 });
 
-svc.load();
+// NO module-scope `svc.load()`, deliberately — the descriptor's `onAppear` is the
+// only entry point, and on Android the self-kick did not merely duplicate it, it
+// DISABLED the screen.
+//
+// `load` opens by creating a conversation, so a self-kick puts a `wixApi.call`
+// inside the bundle's own evaluation — and a bridge call made during
+// `worker.boot(bundle)` stalls on the Android WebView. The host completes it
+// (`bridge_wix_call … ok=true` is logged between `bundle eval done` and
+// `services=[…]`) but the JS promise never settles. `createOnce` then caches that
+// promise as the per-site create latch, so the `onAppear` load — dispatched
+// correctly, and fine on its own — awaits the same dead promise and never returns
+// either. Result on Android: no greeting, no prompt chips, no conversation, and a
+// Send that does nothing, for the life of the screen. Nothing reports it, because
+// a pending dispatch has no timeout: an action that never settles is
+// indistinguishable from one still running (#2518).
+//
+// That stall is a known Android defect, not a new one. `WebViewJSWorker` already
+// prepends per-screen input into the bundle's own evaluate rather than assigning it
+// separately, and says why: "the bundle's first wixApi.call could stall". Aria is
+// simply the first owner-lite screen to call the network at module scope and so the
+// first to meet it head-on. Fixing the stall is a core-runtime change tracked
+// separately; not calling the network before the screen exists is right regardless.
+//
+// The self-kick was never load-bearing. Both hosts queue a `tier5.*` action
+// dispatched before the worker is up — `Tier5WorkerSession.invoke` on Android and
+// `HimalayaScreenHost.dispatch` on iOS — and both say in as many words that the
+// self-kick is what made `onAppear` only LOOK like it worked. It also cost a
+// second conversation-create attempt per open and minted the greeting with
+// fallback copy, since the copy pack only arrives with the onAppear params.
 export { svc };

package/templates/portfolio-creative-owner/tier5-src/himi-owner-lite-aria-history/index.ts

@@ -38,5 +38,14 @@ const svc = defineService<AriaHistoryState, {
   },
 });
 
-svc.load();
+// NO module-scope `svc.load()` — same reason as the chat adapter next door, which
+// carries the full explanation. This `load` opens with `getConversations`, so a
+// self-kick makes a bridge call inside the bundle's own evaluation, and such a call
+// stalls on the Android WebView (#2518).
+//
+// It is less damaging here than on the chat screen: this load has no create latch
+// for a dead promise to poison, so the `onAppear` load issues its own request and
+// the list still fills. What the self-kick leaves behind is a dispatch that never
+// settles — `pendingDispatches` has no timeout, so it is held for the life of the
+// worker, on every open. Not worth keeping for a call whose result nothing reads.
 export { svc };

package/templates/restaurant-owner/tier5-src/himi-owner-lite-aria/index.ts

@@ -186,5 +186,33 @@ const svc = defineService<AriaChatState, {
   },
 });
 
-svc.load();
+// NO module-scope `svc.load()`, deliberately — the descriptor's `onAppear` is the
+// only entry point, and on Android the self-kick did not merely duplicate it, it
+// DISABLED the screen.
+//
+// `load` opens by creating a conversation, so a self-kick puts a `wixApi.call`
+// inside the bundle's own evaluation — and a bridge call made during
+// `worker.boot(bundle)` stalls on the Android WebView. The host completes it
+// (`bridge_wix_call … ok=true` is logged between `bundle eval done` and
+// `services=[…]`) but the JS promise never settles. `createOnce` then caches that
+// promise as the per-site create latch, so the `onAppear` load — dispatched
+// correctly, and fine on its own — awaits the same dead promise and never returns
+// either. Result on Android: no greeting, no prompt chips, no conversation, and a
+// Send that does nothing, for the life of the screen. Nothing reports it, because
+// a pending dispatch has no timeout: an action that never settles is
+// indistinguishable from one still running (#2518).
+//
+// That stall is a known Android defect, not a new one. `WebViewJSWorker` already
+// prepends per-screen input into the bundle's own evaluate rather than assigning it
+// separately, and says why: "the bundle's first wixApi.call could stall". Aria is
+// simply the first owner-lite screen to call the network at module scope and so the
+// first to meet it head-on. Fixing the stall is a core-runtime change tracked
+// separately; not calling the network before the screen exists is right regardless.
+//
+// The self-kick was never load-bearing. Both hosts queue a `tier5.*` action
+// dispatched before the worker is up — `Tier5WorkerSession.invoke` on Android and
+// `HimalayaScreenHost.dispatch` on iOS — and both say in as many words that the
+// self-kick is what made `onAppear` only LOOK like it worked. It also cost a
+// second conversation-create attempt per open and minted the greeting with
+// fallback copy, since the copy pack only arrives with the onAppear params.
 export { svc };

package/templates/restaurant-owner/tier5-src/himi-owner-lite-aria-history/index.ts

@@ -38,5 +38,14 @@ const svc = defineService<AriaHistoryState, {
   },
 });
 
-svc.load();
+// NO module-scope `svc.load()` — same reason as the chat adapter next door, which
+// carries the full explanation. This `load` opens with `getConversations`, so a
+// self-kick makes a bridge call inside the bundle's own evaluation, and such a call
+// stalls on the Android WebView (#2518).
+//
+// It is less damaging here than on the chat screen: this load has no create latch
+// for a dead promise to poison, so the `onAppear` load issues its own request and
+// the list still fills. What the self-kick leaves behind is a dispatch that never
+// settles — `pendingDispatches` has no timeout, so it is held for the life of the
+// worker, on every open. Not worth keeping for a call whose result nothing reads.
 export { svc };

package/templates/retail-store-owner/tier5-src/himi-owner-lite-aria/index.ts

@@ -186,5 +186,33 @@ const svc = defineService<AriaChatState, {
   },
 });
 
-svc.load();
+// NO module-scope `svc.load()`, deliberately — the descriptor's `onAppear` is the
+// only entry point, and on Android the self-kick did not merely duplicate it, it
+// DISABLED the screen.
+//
+// `load` opens by creating a conversation, so a self-kick puts a `wixApi.call`
+// inside the bundle's own evaluation — and a bridge call made during
+// `worker.boot(bundle)` stalls on the Android WebView. The host completes it
+// (`bridge_wix_call … ok=true` is logged between `bundle eval done` and
+// `services=[…]`) but the JS promise never settles. `createOnce` then caches that
+// promise as the per-site create latch, so the `onAppear` load — dispatched
+// correctly, and fine on its own — awaits the same dead promise and never returns
+// either. Result on Android: no greeting, no prompt chips, no conversation, and a
+// Send that does nothing, for the life of the screen. Nothing reports it, because
+// a pending dispatch has no timeout: an action that never settles is
+// indistinguishable from one still running (#2518).
+//
+// That stall is a known Android defect, not a new one. `WebViewJSWorker` already
+// prepends per-screen input into the bundle's own evaluate rather than assigning it
+// separately, and says why: "the bundle's first wixApi.call could stall". Aria is
+// simply the first owner-lite screen to call the network at module scope and so the
+// first to meet it head-on. Fixing the stall is a core-runtime change tracked
+// separately; not calling the network before the screen exists is right regardless.
+//
+// The self-kick was never load-bearing. Both hosts queue a `tier5.*` action
+// dispatched before the worker is up — `Tier5WorkerSession.invoke` on Android and
+// `HimalayaScreenHost.dispatch` on iOS — and both say in as many words that the
+// self-kick is what made `onAppear` only LOOK like it worked. It also cost a
+// second conversation-create attempt per open and minted the greeting with
+// fallback copy, since the copy pack only arrives with the onAppear params.
 export { svc };

package/templates/retail-store-owner/tier5-src/himi-owner-lite-aria-history/index.ts

@@ -38,5 +38,14 @@ const svc = defineService<AriaHistoryState, {
   },
 });
 
-svc.load();
+// NO module-scope `svc.load()` — same reason as the chat adapter next door, which
+// carries the full explanation. This `load` opens with `getConversations`, so a
+// self-kick makes a bridge call inside the bundle's own evaluation, and such a call
+// stalls on the Android WebView (#2518).
+//
+// It is less damaging here than on the chat screen: this load has no create latch
+// for a dead promise to poison, so the `onAppear` load issues its own request and
+// the list still fills. What the self-kick leaves behind is a dispatch that never
+// settles — `pendingDispatches` has no timeout, so it is held for the life of the
+// worker, on every open. Not worth keeping for a call whose result nothing reads.
 export { svc };

package/templates/yoga-studio-owner/tier5-src/himi-owner-lite-aria/index.ts

@@ -186,5 +186,33 @@ const svc = defineService<AriaChatState, {
   },
 });
 
-svc.load();
+// NO module-scope `svc.load()`, deliberately — the descriptor's `onAppear` is the
+// only entry point, and on Android the self-kick did not merely duplicate it, it
+// DISABLED the screen.
+//
+// `load` opens by creating a conversation, so a self-kick puts a `wixApi.call`
+// inside the bundle's own evaluation — and a bridge call made during
+// `worker.boot(bundle)` stalls on the Android WebView. The host completes it
+// (`bridge_wix_call … ok=true` is logged between `bundle eval done` and
+// `services=[…]`) but the JS promise never settles. `createOnce` then caches that
+// promise as the per-site create latch, so the `onAppear` load — dispatched
+// correctly, and fine on its own — awaits the same dead promise and never returns
+// either. Result on Android: no greeting, no prompt chips, no conversation, and a
+// Send that does nothing, for the life of the screen. Nothing reports it, because
+// a pending dispatch has no timeout: an action that never settles is
+// indistinguishable from one still running (#2518).
+//
+// That stall is a known Android defect, not a new one. `WebViewJSWorker` already
+// prepends per-screen input into the bundle's own evaluate rather than assigning it
+// separately, and says why: "the bundle's first wixApi.call could stall". Aria is
+// simply the first owner-lite screen to call the network at module scope and so the
+// first to meet it head-on. Fixing the stall is a core-runtime change tracked
+// separately; not calling the network before the screen exists is right regardless.
+//
+// The self-kick was never load-bearing. Both hosts queue a `tier5.*` action
+// dispatched before the worker is up — `Tier5WorkerSession.invoke` on Android and
+// `HimalayaScreenHost.dispatch` on iOS — and both say in as many words that the
+// self-kick is what made `onAppear` only LOOK like it worked. It also cost a
+// second conversation-create attempt per open and minted the greeting with
+// fallback copy, since the copy pack only arrives with the onAppear params.
 export { svc };

package/templates/yoga-studio-owner/tier5-src/himi-owner-lite-aria-history/index.ts

@@ -38,5 +38,14 @@ const svc = defineService<AriaHistoryState, {
   },
 });
 
-svc.load();
+// NO module-scope `svc.load()` — same reason as the chat adapter next door, which
+// carries the full explanation. This `load` opens with `getConversations`, so a
+// self-kick makes a bridge call inside the bundle's own evaluation, and such a call
+// stalls on the Android WebView (#2518).
+//
+// It is less damaging here than on the chat screen: this load has no create latch
+// for a dead promise to poison, so the `onAppear` load issues its own request and
+// the list still fills. What the self-kick leaves behind is a dispatch that never
+// settles — `pendingDispatches` has no timeout, so it is held for the life of the
+// worker, on every open. Not worth keeping for a call whose result nothing reads.
 export { svc };