@wix/himalaya-cli 0.989.0 → 0.991.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/himalaya-cli",
-  "version": "0.989.0",
+  "version": "0.991.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": [
@@ -65,5 +65,5 @@
       "artifactId": "himalaya-cli"
     }
   },
-  "falconPackageHash": "67a573e97c057c3bf277ed30655a7855e28d5c899c59b41eac1f3c85"
+  "falconPackageHash": "ebb2d80b9a686fc18878c48955d691cd014019a04d2ed731b2a431dd"
 }

package/templates/beauty-salon-owner/tier5-src/_shared/aria-hot-path.ts

@@ -1,10 +1,10 @@
 // The Aria transcript's hot path — the rules it is written to, and the two
 // primitives that make them hold.
 //
-// Adapted from `native-apps/PERFORMANCE.md` in wix-private/aria-native-apps, which
+// Adapted from the performance guide of Aria's native app, which
 // states eleven rules, each "a class of shipped regression". Most of them govern
-// 30 Hz streaming, which this app does not do yet (#2612), and adopting all eleven
-// for a POLLED chat would be cargo-culting. These four apply now (#2623):
+// 30 Hz streaming, which this app does not do yet, and adopting all eleven
+// for a POLLED chat would be cargo-culting. These four apply now:
 //
 //  1. NEVER RE-DERIVE THE WHOLE TRANSCRIPT PER TICK. Every poll re-reads the full
 //     transcript, and turning a message into a bubble is the expensive step —
@@ -32,7 +32,7 @@
 //     a POSITION, and the moment anything before it is dropped (an empty
 //     placeholder, a hidden-only row, a windowed read) the same index names a
 //     different message. The bubble id is also the row's stable test id
-//     (`<screen>.msg_<id>`, invariant 27). `transcriptKeys`, `mintLocalId`.
+//     (`<screen>.msg_<id>`), which UI tests find it by. `transcriptKeys`, `mintLocalId`.
 //
 //  4. EVERY REPEATING CLOCK HAS AN OWNER AND STOPS ON EVERY EXIT PATH. The only
 //     clock here is the reply ladder, `_poll` id `aria-turn`, and its owner is
@@ -56,7 +56,7 @@
 // drivers) and the native app's device budgets (cold start, frame time, hangs)
 // are deliberately NOT adopted here: nothing in this repo measures them for
 // Aria, and a budget nobody measures is decoration. Each rule above is pinned by
-// a test instead — `core/dev-server/tests/aria-hot-path.test.ts`.
+// a test instead, one per rule, each asserting a count.
 //
 // Dependency-free on purpose: the tests import this file directly.
 

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

@@ -229,8 +229,13 @@ function total(m: WixAnalyticsMeasurement | undefined): number {
 function seriesOf(m: WixAnalyticsMeasurement | undefined): number[] {
   return (m?.values ?? []).map((v) => v.value || 0);
 }
+/**
+ * Counts go through the same grouped formatter as money, so "1,544" sits beside
+ * "7,290.53" rather than "1544". The note on `fmtMoney` explains why it
+ * is `formatNumber` and never `toLocaleString`.
+ */
 function fmtInt(n: number): string {
-  return String(Math.round(n));
+  return formatNumber(Math.round(n));
 }
 /**
  * NOT `toLocaleString`. That is ECMA-402, which QuickJS-ng — watchOS and Wear OS —

package/templates/beauty-salon-owner/tier5-src/himi-owner-lite-ask/catalog.ts

@@ -165,15 +165,14 @@ export function metricRowsFrom(
         // screens cannot disagree in the last digit about the same measure.
         // NO currency symbol, and that is not an omission. The Analytics
         // screen's fmtMoney is `formatNumber(round(n*100)/100)` with no symbol
-        // (himi-owner-lite-analytics/index.ts:241). Adding one here would make
+        // (`fmtMoney` in himi-owner-lite-analytics/index.ts). Adding one here would make
         // the two screens render the SAME number differently — breaking the
         // reconciliation this endpoint choice exists to guarantee — and would
         // show a euro sign to a USD, GBP or ILS site. Every other money value
         // in this bundle comes from the API's own formattedAmount for that
         // same reason.
-        value: m.money
-          ? formatNumber(Math.round(total * 100) / 100)
-          : String(Math.round(total)),
+        // Counts are grouped too, as the Analytics screen's fmtInt groups them.
+        value: formatNumber(m.money ? Math.round(total * 100) / 100 : Math.round(total)),
         // The same number unformatted, so orderBy:amount sorts numerically
         // rather than lexically ("9" > "1,240" as text).
         amount: String(total),

package/templates/community-club-owner/tier5-src/_shared/aria-hot-path.ts

@@ -1,10 +1,10 @@
 // The Aria transcript's hot path — the rules it is written to, and the two
 // primitives that make them hold.
 //
-// Adapted from `native-apps/PERFORMANCE.md` in wix-private/aria-native-apps, which
+// Adapted from the performance guide of Aria's native app, which
 // states eleven rules, each "a class of shipped regression". Most of them govern
-// 30 Hz streaming, which this app does not do yet (#2612), and adopting all eleven
-// for a POLLED chat would be cargo-culting. These four apply now (#2623):
+// 30 Hz streaming, which this app does not do yet, and adopting all eleven
+// for a POLLED chat would be cargo-culting. These four apply now:
 //
 //  1. NEVER RE-DERIVE THE WHOLE TRANSCRIPT PER TICK. Every poll re-reads the full
 //     transcript, and turning a message into a bubble is the expensive step —
@@ -32,7 +32,7 @@
 //     a POSITION, and the moment anything before it is dropped (an empty
 //     placeholder, a hidden-only row, a windowed read) the same index names a
 //     different message. The bubble id is also the row's stable test id
-//     (`<screen>.msg_<id>`, invariant 27). `transcriptKeys`, `mintLocalId`.
+//     (`<screen>.msg_<id>`), which UI tests find it by. `transcriptKeys`, `mintLocalId`.
 //
 //  4. EVERY REPEATING CLOCK HAS AN OWNER AND STOPS ON EVERY EXIT PATH. The only
 //     clock here is the reply ladder, `_poll` id `aria-turn`, and its owner is
@@ -56,7 +56,7 @@
 // drivers) and the native app's device budgets (cold start, frame time, hangs)
 // are deliberately NOT adopted here: nothing in this repo measures them for
 // Aria, and a budget nobody measures is decoration. Each rule above is pinned by
-// a test instead — `core/dev-server/tests/aria-hot-path.test.ts`.
+// a test instead, one per rule, each asserting a count.
 //
 // Dependency-free on purpose: the tests import this file directly.
 

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

@@ -229,8 +229,13 @@ function total(m: WixAnalyticsMeasurement | undefined): number {
 function seriesOf(m: WixAnalyticsMeasurement | undefined): number[] {
   return (m?.values ?? []).map((v) => v.value || 0);
 }
+/**
+ * Counts go through the same grouped formatter as money, so "1,544" sits beside
+ * "7,290.53" rather than "1544". The note on `fmtMoney` explains why it
+ * is `formatNumber` and never `toLocaleString`.
+ */
 function fmtInt(n: number): string {
-  return String(Math.round(n));
+  return formatNumber(Math.round(n));
 }
 /**
  * NOT `toLocaleString`. That is ECMA-402, which QuickJS-ng — watchOS and Wear OS —

package/templates/community-club-owner/tier5-src/himi-owner-lite-ask/catalog.ts

@@ -165,15 +165,14 @@ export function metricRowsFrom(
         // screens cannot disagree in the last digit about the same measure.
         // NO currency symbol, and that is not an omission. The Analytics
         // screen's fmtMoney is `formatNumber(round(n*100)/100)` with no symbol
-        // (himi-owner-lite-analytics/index.ts:241). Adding one here would make
+        // (`fmtMoney` in himi-owner-lite-analytics/index.ts). Adding one here would make
         // the two screens render the SAME number differently — breaking the
         // reconciliation this endpoint choice exists to guarantee — and would
         // show a euro sign to a USD, GBP or ILS site. Every other money value
         // in this bundle comes from the API's own formattedAmount for that
         // same reason.
-        value: m.money
-          ? formatNumber(Math.round(total * 100) / 100)
-          : String(Math.round(total)),
+        // Counts are grouped too, as the Analytics screen's fmtInt groups them.
+        value: formatNumber(m.money ? Math.round(total * 100) / 100 : Math.round(total)),
         // The same number unformatted, so orderBy:amount sorts numerically
         // rather than lexically ("9" > "1,240" as text).
         amount: String(total),

package/templates/events-meetups-owner/tier5-src/_shared/aria-hot-path.ts

@@ -1,10 +1,10 @@
 // The Aria transcript's hot path — the rules it is written to, and the two
 // primitives that make them hold.
 //
-// Adapted from `native-apps/PERFORMANCE.md` in wix-private/aria-native-apps, which
+// Adapted from the performance guide of Aria's native app, which
 // states eleven rules, each "a class of shipped regression". Most of them govern
-// 30 Hz streaming, which this app does not do yet (#2612), and adopting all eleven
-// for a POLLED chat would be cargo-culting. These four apply now (#2623):
+// 30 Hz streaming, which this app does not do yet, and adopting all eleven
+// for a POLLED chat would be cargo-culting. These four apply now:
 //
 //  1. NEVER RE-DERIVE THE WHOLE TRANSCRIPT PER TICK. Every poll re-reads the full
 //     transcript, and turning a message into a bubble is the expensive step —
@@ -32,7 +32,7 @@
 //     a POSITION, and the moment anything before it is dropped (an empty
 //     placeholder, a hidden-only row, a windowed read) the same index names a
 //     different message. The bubble id is also the row's stable test id
-//     (`<screen>.msg_<id>`, invariant 27). `transcriptKeys`, `mintLocalId`.
+//     (`<screen>.msg_<id>`), which UI tests find it by. `transcriptKeys`, `mintLocalId`.
 //
 //  4. EVERY REPEATING CLOCK HAS AN OWNER AND STOPS ON EVERY EXIT PATH. The only
 //     clock here is the reply ladder, `_poll` id `aria-turn`, and its owner is
@@ -56,7 +56,7 @@
 // drivers) and the native app's device budgets (cold start, frame time, hangs)
 // are deliberately NOT adopted here: nothing in this repo measures them for
 // Aria, and a budget nobody measures is decoration. Each rule above is pinned by
-// a test instead — `core/dev-server/tests/aria-hot-path.test.ts`.
+// a test instead, one per rule, each asserting a count.
 //
 // Dependency-free on purpose: the tests import this file directly.
 

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

@@ -229,8 +229,13 @@ function total(m: WixAnalyticsMeasurement | undefined): number {
 function seriesOf(m: WixAnalyticsMeasurement | undefined): number[] {
   return (m?.values ?? []).map((v) => v.value || 0);
 }
+/**
+ * Counts go through the same grouped formatter as money, so "1,544" sits beside
+ * "7,290.53" rather than "1544". The note on `fmtMoney` explains why it
+ * is `formatNumber` and never `toLocaleString`.
+ */
 function fmtInt(n: number): string {
-  return String(Math.round(n));
+  return formatNumber(Math.round(n));
 }
 /**
  * NOT `toLocaleString`. That is ECMA-402, which QuickJS-ng — watchOS and Wear OS —

package/templates/events-meetups-owner/tier5-src/himi-owner-lite-ask/catalog.ts

@@ -165,15 +165,14 @@ export function metricRowsFrom(
         // screens cannot disagree in the last digit about the same measure.
         // NO currency symbol, and that is not an omission. The Analytics
         // screen's fmtMoney is `formatNumber(round(n*100)/100)` with no symbol
-        // (himi-owner-lite-analytics/index.ts:241). Adding one here would make
+        // (`fmtMoney` in himi-owner-lite-analytics/index.ts). Adding one here would make
         // the two screens render the SAME number differently — breaking the
         // reconciliation this endpoint choice exists to guarantee — and would
         // show a euro sign to a USD, GBP or ILS site. Every other money value
         // in this bundle comes from the API's own formattedAmount for that
         // same reason.
-        value: m.money
-          ? formatNumber(Math.round(total * 100) / 100)
-          : String(Math.round(total)),
+        // Counts are grouped too, as the Analytics screen's fmtInt groups them.
+        value: formatNumber(m.money ? Math.round(total * 100) / 100 : Math.round(total)),
         // The same number unformatted, so orderBy:amount sorts numerically
         // rather than lexically ("9" > "1,240" as text).
         amount: String(total),

package/templates/gym-fitness-owner/tier5-src/_shared/aria-hot-path.ts

@@ -1,10 +1,10 @@
 // The Aria transcript's hot path — the rules it is written to, and the two
 // primitives that make them hold.
 //
-// Adapted from `native-apps/PERFORMANCE.md` in wix-private/aria-native-apps, which
+// Adapted from the performance guide of Aria's native app, which
 // states eleven rules, each "a class of shipped regression". Most of them govern
-// 30 Hz streaming, which this app does not do yet (#2612), and adopting all eleven
-// for a POLLED chat would be cargo-culting. These four apply now (#2623):
+// 30 Hz streaming, which this app does not do yet, and adopting all eleven
+// for a POLLED chat would be cargo-culting. These four apply now:
 //
 //  1. NEVER RE-DERIVE THE WHOLE TRANSCRIPT PER TICK. Every poll re-reads the full
 //     transcript, and turning a message into a bubble is the expensive step —
@@ -32,7 +32,7 @@
 //     a POSITION, and the moment anything before it is dropped (an empty
 //     placeholder, a hidden-only row, a windowed read) the same index names a
 //     different message. The bubble id is also the row's stable test id
-//     (`<screen>.msg_<id>`, invariant 27). `transcriptKeys`, `mintLocalId`.
+//     (`<screen>.msg_<id>`), which UI tests find it by. `transcriptKeys`, `mintLocalId`.
 //
 //  4. EVERY REPEATING CLOCK HAS AN OWNER AND STOPS ON EVERY EXIT PATH. The only
 //     clock here is the reply ladder, `_poll` id `aria-turn`, and its owner is
@@ -56,7 +56,7 @@
 // drivers) and the native app's device budgets (cold start, frame time, hangs)
 // are deliberately NOT adopted here: nothing in this repo measures them for
 // Aria, and a budget nobody measures is decoration. Each rule above is pinned by
-// a test instead — `core/dev-server/tests/aria-hot-path.test.ts`.
+// a test instead, one per rule, each asserting a count.
 //
 // Dependency-free on purpose: the tests import this file directly.
 

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

@@ -229,8 +229,13 @@ function total(m: WixAnalyticsMeasurement | undefined): number {
 function seriesOf(m: WixAnalyticsMeasurement | undefined): number[] {
   return (m?.values ?? []).map((v) => v.value || 0);
 }
+/**
+ * Counts go through the same grouped formatter as money, so "1,544" sits beside
+ * "7,290.53" rather than "1544". The note on `fmtMoney` explains why it
+ * is `formatNumber` and never `toLocaleString`.
+ */
 function fmtInt(n: number): string {
-  return String(Math.round(n));
+  return formatNumber(Math.round(n));
 }
 /**
  * NOT `toLocaleString`. That is ECMA-402, which QuickJS-ng — watchOS and Wear OS —

package/templates/gym-fitness-owner/tier5-src/himi-owner-lite-ask/catalog.ts

@@ -165,15 +165,14 @@ export function metricRowsFrom(
         // screens cannot disagree in the last digit about the same measure.
         // NO currency symbol, and that is not an omission. The Analytics
         // screen's fmtMoney is `formatNumber(round(n*100)/100)` with no symbol
-        // (himi-owner-lite-analytics/index.ts:241). Adding one here would make
+        // (`fmtMoney` in himi-owner-lite-analytics/index.ts). Adding one here would make
         // the two screens render the SAME number differently — breaking the
         // reconciliation this endpoint choice exists to guarantee — and would
         // show a euro sign to a USD, GBP or ILS site. Every other money value
         // in this bundle comes from the API's own formattedAmount for that
         // same reason.
-        value: m.money
-          ? formatNumber(Math.round(total * 100) / 100)
-          : String(Math.round(total)),
+        // Counts are grouped too, as the Analytics screen's fmtInt groups them.
+        value: formatNumber(m.money ? Math.round(total * 100) / 100 : Math.round(total)),
         // The same number unformatted, so orderBy:amount sorts numerically
         // rather than lexically ("9" > "1,240" as text).
         amount: String(total),

package/templates/nonprofit-cause-owner/tier5-src/_shared/aria-hot-path.ts

@@ -1,10 +1,10 @@
 // The Aria transcript's hot path — the rules it is written to, and the two
 // primitives that make them hold.
 //
-// Adapted from `native-apps/PERFORMANCE.md` in wix-private/aria-native-apps, which
+// Adapted from the performance guide of Aria's native app, which
 // states eleven rules, each "a class of shipped regression". Most of them govern
-// 30 Hz streaming, which this app does not do yet (#2612), and adopting all eleven
-// for a POLLED chat would be cargo-culting. These four apply now (#2623):
+// 30 Hz streaming, which this app does not do yet, and adopting all eleven
+// for a POLLED chat would be cargo-culting. These four apply now:
 //
 //  1. NEVER RE-DERIVE THE WHOLE TRANSCRIPT PER TICK. Every poll re-reads the full
 //     transcript, and turning a message into a bubble is the expensive step —
@@ -32,7 +32,7 @@
 //     a POSITION, and the moment anything before it is dropped (an empty
 //     placeholder, a hidden-only row, a windowed read) the same index names a
 //     different message. The bubble id is also the row's stable test id
-//     (`<screen>.msg_<id>`, invariant 27). `transcriptKeys`, `mintLocalId`.
+//     (`<screen>.msg_<id>`), which UI tests find it by. `transcriptKeys`, `mintLocalId`.
 //
 //  4. EVERY REPEATING CLOCK HAS AN OWNER AND STOPS ON EVERY EXIT PATH. The only
 //     clock here is the reply ladder, `_poll` id `aria-turn`, and its owner is
@@ -56,7 +56,7 @@
 // drivers) and the native app's device budgets (cold start, frame time, hangs)
 // are deliberately NOT adopted here: nothing in this repo measures them for
 // Aria, and a budget nobody measures is decoration. Each rule above is pinned by
-// a test instead — `core/dev-server/tests/aria-hot-path.test.ts`.
+// a test instead, one per rule, each asserting a count.
 //
 // Dependency-free on purpose: the tests import this file directly.
 

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

@@ -229,8 +229,13 @@ function total(m: WixAnalyticsMeasurement | undefined): number {
 function seriesOf(m: WixAnalyticsMeasurement | undefined): number[] {
   return (m?.values ?? []).map((v) => v.value || 0);
 }
+/**
+ * Counts go through the same grouped formatter as money, so "1,544" sits beside
+ * "7,290.53" rather than "1544". The note on `fmtMoney` explains why it
+ * is `formatNumber` and never `toLocaleString`.
+ */
 function fmtInt(n: number): string {
-  return String(Math.round(n));
+  return formatNumber(Math.round(n));
 }
 /**
  * NOT `toLocaleString`. That is ECMA-402, which QuickJS-ng — watchOS and Wear OS —

package/templates/nonprofit-cause-owner/tier5-src/himi-owner-lite-ask/catalog.ts

@@ -165,15 +165,14 @@ export function metricRowsFrom(
         // screens cannot disagree in the last digit about the same measure.
         // NO currency symbol, and that is not an omission. The Analytics
         // screen's fmtMoney is `formatNumber(round(n*100)/100)` with no symbol
-        // (himi-owner-lite-analytics/index.ts:241). Adding one here would make
+        // (`fmtMoney` in himi-owner-lite-analytics/index.ts). Adding one here would make
         // the two screens render the SAME number differently — breaking the
         // reconciliation this endpoint choice exists to guarantee — and would
         // show a euro sign to a USD, GBP or ILS site. Every other money value
         // in this bundle comes from the API's own formattedAmount for that
         // same reason.
-        value: m.money
-          ? formatNumber(Math.round(total * 100) / 100)
-          : String(Math.round(total)),
+        // Counts are grouped too, as the Analytics screen's fmtInt groups them.
+        value: formatNumber(m.money ? Math.round(total * 100) / 100 : Math.round(total)),
         // The same number unformatted, so orderBy:amount sorts numerically
         // rather than lexically ("9" > "1,240" as text).
         amount: String(total),

package/templates/owner-lite/tier5-src/_shared/aria-hot-path.ts

@@ -1,10 +1,10 @@
 // The Aria transcript's hot path — the rules it is written to, and the two
 // primitives that make them hold.
 //
-// Adapted from `native-apps/PERFORMANCE.md` in wix-private/aria-native-apps, which
+// Adapted from the performance guide of Aria's native app, which
 // states eleven rules, each "a class of shipped regression". Most of them govern
-// 30 Hz streaming, which this app does not do yet (#2612), and adopting all eleven
-// for a POLLED chat would be cargo-culting. These four apply now (#2623):
+// 30 Hz streaming, which this app does not do yet, and adopting all eleven
+// for a POLLED chat would be cargo-culting. These four apply now:
 //
 //  1. NEVER RE-DERIVE THE WHOLE TRANSCRIPT PER TICK. Every poll re-reads the full
 //     transcript, and turning a message into a bubble is the expensive step —
@@ -32,7 +32,7 @@
 //     a POSITION, and the moment anything before it is dropped (an empty
 //     placeholder, a hidden-only row, a windowed read) the same index names a
 //     different message. The bubble id is also the row's stable test id
-//     (`<screen>.msg_<id>`, invariant 27). `transcriptKeys`, `mintLocalId`.
+//     (`<screen>.msg_<id>`), which UI tests find it by. `transcriptKeys`, `mintLocalId`.
 //
 //  4. EVERY REPEATING CLOCK HAS AN OWNER AND STOPS ON EVERY EXIT PATH. The only
 //     clock here is the reply ladder, `_poll` id `aria-turn`, and its owner is
@@ -56,7 +56,7 @@
 // drivers) and the native app's device budgets (cold start, frame time, hangs)
 // are deliberately NOT adopted here: nothing in this repo measures them for
 // Aria, and a budget nobody measures is decoration. Each rule above is pinned by
-// a test instead — `core/dev-server/tests/aria-hot-path.test.ts`.
+// a test instead, one per rule, each asserting a count.
 //
 // Dependency-free on purpose: the tests import this file directly.
 

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

@@ -229,8 +229,13 @@ function total(m: WixAnalyticsMeasurement | undefined): number {
 function seriesOf(m: WixAnalyticsMeasurement | undefined): number[] {
   return (m?.values ?? []).map((v) => v.value || 0);
 }
+/**
+ * Counts go through the same grouped formatter as money, so "1,544" sits beside
+ * "7,290.53" rather than "1544". The note on `fmtMoney` explains why it
+ * is `formatNumber` and never `toLocaleString`.
+ */
 function fmtInt(n: number): string {
-  return String(Math.round(n));
+  return formatNumber(Math.round(n));
 }
 /**
  * NOT `toLocaleString`. That is ECMA-402, which QuickJS-ng — watchOS and Wear OS —

package/templates/owner-lite/tier5-src/himi-owner-lite-ask/catalog.ts

@@ -165,15 +165,14 @@ export function metricRowsFrom(
         // screens cannot disagree in the last digit about the same measure.
         // NO currency symbol, and that is not an omission. The Analytics
         // screen's fmtMoney is `formatNumber(round(n*100)/100)` with no symbol
-        // (himi-owner-lite-analytics/index.ts:241). Adding one here would make
+        // (`fmtMoney` in himi-owner-lite-analytics/index.ts). Adding one here would make
         // the two screens render the SAME number differently — breaking the
         // reconciliation this endpoint choice exists to guarantee — and would
         // show a euro sign to a USD, GBP or ILS site. Every other money value
         // in this bundle comes from the API's own formattedAmount for that
         // same reason.
-        value: m.money
-          ? formatNumber(Math.round(total * 100) / 100)
-          : String(Math.round(total)),
+        // Counts are grouped too, as the Analytics screen's fmtInt groups them.
+        value: formatNumber(m.money ? Math.round(total * 100) / 100 : Math.round(total)),
         // The same number unformatted, so orderBy:amount sorts numerically
         // rather than lexically ("9" > "1,240" as text).
         amount: String(total),

package/templates/podcast-creator-owner/tier5-src/_shared/aria-hot-path.ts

@@ -1,10 +1,10 @@
 // The Aria transcript's hot path — the rules it is written to, and the two
 // primitives that make them hold.
 //
-// Adapted from `native-apps/PERFORMANCE.md` in wix-private/aria-native-apps, which
+// Adapted from the performance guide of Aria's native app, which
 // states eleven rules, each "a class of shipped regression". Most of them govern
-// 30 Hz streaming, which this app does not do yet (#2612), and adopting all eleven
-// for a POLLED chat would be cargo-culting. These four apply now (#2623):
+// 30 Hz streaming, which this app does not do yet, and adopting all eleven
+// for a POLLED chat would be cargo-culting. These four apply now:
 //
 //  1. NEVER RE-DERIVE THE WHOLE TRANSCRIPT PER TICK. Every poll re-reads the full
 //     transcript, and turning a message into a bubble is the expensive step —
@@ -32,7 +32,7 @@
 //     a POSITION, and the moment anything before it is dropped (an empty
 //     placeholder, a hidden-only row, a windowed read) the same index names a
 //     different message. The bubble id is also the row's stable test id
-//     (`<screen>.msg_<id>`, invariant 27). `transcriptKeys`, `mintLocalId`.
+//     (`<screen>.msg_<id>`), which UI tests find it by. `transcriptKeys`, `mintLocalId`.
 //
 //  4. EVERY REPEATING CLOCK HAS AN OWNER AND STOPS ON EVERY EXIT PATH. The only
 //     clock here is the reply ladder, `_poll` id `aria-turn`, and its owner is
@@ -56,7 +56,7 @@
 // drivers) and the native app's device budgets (cold start, frame time, hangs)
 // are deliberately NOT adopted here: nothing in this repo measures them for
 // Aria, and a budget nobody measures is decoration. Each rule above is pinned by
-// a test instead — `core/dev-server/tests/aria-hot-path.test.ts`.
+// a test instead, one per rule, each asserting a count.
 //
 // Dependency-free on purpose: the tests import this file directly.
 

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

@@ -229,8 +229,13 @@ function total(m: WixAnalyticsMeasurement | undefined): number {
 function seriesOf(m: WixAnalyticsMeasurement | undefined): number[] {
   return (m?.values ?? []).map((v) => v.value || 0);
 }
+/**
+ * Counts go through the same grouped formatter as money, so "1,544" sits beside
+ * "7,290.53" rather than "1544". The note on `fmtMoney` explains why it
+ * is `formatNumber` and never `toLocaleString`.
+ */
 function fmtInt(n: number): string {
-  return String(Math.round(n));
+  return formatNumber(Math.round(n));
 }
 /**
  * NOT `toLocaleString`. That is ECMA-402, which QuickJS-ng — watchOS and Wear OS —

package/templates/podcast-creator-owner/tier5-src/himi-owner-lite-ask/catalog.ts

@@ -165,15 +165,14 @@ export function metricRowsFrom(
         // screens cannot disagree in the last digit about the same measure.
         // NO currency symbol, and that is not an omission. The Analytics
         // screen's fmtMoney is `formatNumber(round(n*100)/100)` with no symbol
-        // (himi-owner-lite-analytics/index.ts:241). Adding one here would make
+        // (`fmtMoney` in himi-owner-lite-analytics/index.ts). Adding one here would make
         // the two screens render the SAME number differently — breaking the
         // reconciliation this endpoint choice exists to guarantee — and would
         // show a euro sign to a USD, GBP or ILS site. Every other money value
         // in this bundle comes from the API's own formattedAmount for that
         // same reason.
-        value: m.money
-          ? formatNumber(Math.round(total * 100) / 100)
-          : String(Math.round(total)),
+        // Counts are grouped too, as the Analytics screen's fmtInt groups them.
+        value: formatNumber(m.money ? Math.round(total * 100) / 100 : Math.round(total)),
         // The same number unformatted, so orderBy:amount sorts numerically
         // rather than lexically ("9" > "1,240" as text).
         amount: String(total),

package/templates/portfolio-creative-owner/tier5-src/_shared/aria-hot-path.ts

@@ -1,10 +1,10 @@
 // The Aria transcript's hot path — the rules it is written to, and the two
 // primitives that make them hold.
 //
-// Adapted from `native-apps/PERFORMANCE.md` in wix-private/aria-native-apps, which
+// Adapted from the performance guide of Aria's native app, which
 // states eleven rules, each "a class of shipped regression". Most of them govern
-// 30 Hz streaming, which this app does not do yet (#2612), and adopting all eleven
-// for a POLLED chat would be cargo-culting. These four apply now (#2623):
+// 30 Hz streaming, which this app does not do yet, and adopting all eleven
+// for a POLLED chat would be cargo-culting. These four apply now:
 //
 //  1. NEVER RE-DERIVE THE WHOLE TRANSCRIPT PER TICK. Every poll re-reads the full
 //     transcript, and turning a message into a bubble is the expensive step —
@@ -32,7 +32,7 @@
 //     a POSITION, and the moment anything before it is dropped (an empty
 //     placeholder, a hidden-only row, a windowed read) the same index names a
 //     different message. The bubble id is also the row's stable test id
-//     (`<screen>.msg_<id>`, invariant 27). `transcriptKeys`, `mintLocalId`.
+//     (`<screen>.msg_<id>`), which UI tests find it by. `transcriptKeys`, `mintLocalId`.
 //
 //  4. EVERY REPEATING CLOCK HAS AN OWNER AND STOPS ON EVERY EXIT PATH. The only
 //     clock here is the reply ladder, `_poll` id `aria-turn`, and its owner is
@@ -56,7 +56,7 @@
 // drivers) and the native app's device budgets (cold start, frame time, hangs)
 // are deliberately NOT adopted here: nothing in this repo measures them for
 // Aria, and a budget nobody measures is decoration. Each rule above is pinned by
-// a test instead — `core/dev-server/tests/aria-hot-path.test.ts`.
+// a test instead, one per rule, each asserting a count.
 //
 // Dependency-free on purpose: the tests import this file directly.
 

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

@@ -229,8 +229,13 @@ function total(m: WixAnalyticsMeasurement | undefined): number {
 function seriesOf(m: WixAnalyticsMeasurement | undefined): number[] {
   return (m?.values ?? []).map((v) => v.value || 0);
 }
+/**
+ * Counts go through the same grouped formatter as money, so "1,544" sits beside
+ * "7,290.53" rather than "1544". The note on `fmtMoney` explains why it
+ * is `formatNumber` and never `toLocaleString`.
+ */
 function fmtInt(n: number): string {
-  return String(Math.round(n));
+  return formatNumber(Math.round(n));
 }
 /**
  * NOT `toLocaleString`. That is ECMA-402, which QuickJS-ng — watchOS and Wear OS —

package/templates/portfolio-creative-owner/tier5-src/himi-owner-lite-ask/catalog.ts

@@ -165,15 +165,14 @@ export function metricRowsFrom(
         // screens cannot disagree in the last digit about the same measure.
         // NO currency symbol, and that is not an omission. The Analytics
         // screen's fmtMoney is `formatNumber(round(n*100)/100)` with no symbol
-        // (himi-owner-lite-analytics/index.ts:241). Adding one here would make
+        // (`fmtMoney` in himi-owner-lite-analytics/index.ts). Adding one here would make
         // the two screens render the SAME number differently — breaking the
         // reconciliation this endpoint choice exists to guarantee — and would
         // show a euro sign to a USD, GBP or ILS site. Every other money value
         // in this bundle comes from the API's own formattedAmount for that
         // same reason.
-        value: m.money
-          ? formatNumber(Math.round(total * 100) / 100)
-          : String(Math.round(total)),
+        // Counts are grouped too, as the Analytics screen's fmtInt groups them.
+        value: formatNumber(m.money ? Math.round(total * 100) / 100 : Math.round(total)),
         // The same number unformatted, so orderBy:amount sorts numerically
         // rather than lexically ("9" > "1,240" as text).
         amount: String(total),

package/templates/restaurant-owner/tier5-src/_shared/aria-hot-path.ts

@@ -1,10 +1,10 @@
 // The Aria transcript's hot path — the rules it is written to, and the two
 // primitives that make them hold.
 //
-// Adapted from `native-apps/PERFORMANCE.md` in wix-private/aria-native-apps, which
+// Adapted from the performance guide of Aria's native app, which
 // states eleven rules, each "a class of shipped regression". Most of them govern
-// 30 Hz streaming, which this app does not do yet (#2612), and adopting all eleven
-// for a POLLED chat would be cargo-culting. These four apply now (#2623):
+// 30 Hz streaming, which this app does not do yet, and adopting all eleven
+// for a POLLED chat would be cargo-culting. These four apply now:
 //
 //  1. NEVER RE-DERIVE THE WHOLE TRANSCRIPT PER TICK. Every poll re-reads the full
 //     transcript, and turning a message into a bubble is the expensive step —
@@ -32,7 +32,7 @@
 //     a POSITION, and the moment anything before it is dropped (an empty
 //     placeholder, a hidden-only row, a windowed read) the same index names a
 //     different message. The bubble id is also the row's stable test id
-//     (`<screen>.msg_<id>`, invariant 27). `transcriptKeys`, `mintLocalId`.
+//     (`<screen>.msg_<id>`), which UI tests find it by. `transcriptKeys`, `mintLocalId`.
 //
 //  4. EVERY REPEATING CLOCK HAS AN OWNER AND STOPS ON EVERY EXIT PATH. The only
 //     clock here is the reply ladder, `_poll` id `aria-turn`, and its owner is
@@ -56,7 +56,7 @@
 // drivers) and the native app's device budgets (cold start, frame time, hangs)
 // are deliberately NOT adopted here: nothing in this repo measures them for
 // Aria, and a budget nobody measures is decoration. Each rule above is pinned by
-// a test instead — `core/dev-server/tests/aria-hot-path.test.ts`.
+// a test instead, one per rule, each asserting a count.
 //
 // Dependency-free on purpose: the tests import this file directly.
 

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

@@ -229,8 +229,13 @@ function total(m: WixAnalyticsMeasurement | undefined): number {
 function seriesOf(m: WixAnalyticsMeasurement | undefined): number[] {
   return (m?.values ?? []).map((v) => v.value || 0);
 }
+/**
+ * Counts go through the same grouped formatter as money, so "1,544" sits beside
+ * "7,290.53" rather than "1544". The note on `fmtMoney` explains why it
+ * is `formatNumber` and never `toLocaleString`.
+ */
 function fmtInt(n: number): string {
-  return String(Math.round(n));
+  return formatNumber(Math.round(n));
 }
 /**
  * NOT `toLocaleString`. That is ECMA-402, which QuickJS-ng — watchOS and Wear OS —

package/templates/restaurant-owner/tier5-src/himi-owner-lite-ask/catalog.ts

@@ -165,15 +165,14 @@ export function metricRowsFrom(
         // screens cannot disagree in the last digit about the same measure.
         // NO currency symbol, and that is not an omission. The Analytics
         // screen's fmtMoney is `formatNumber(round(n*100)/100)` with no symbol
-        // (himi-owner-lite-analytics/index.ts:241). Adding one here would make
+        // (`fmtMoney` in himi-owner-lite-analytics/index.ts). Adding one here would make
         // the two screens render the SAME number differently — breaking the
         // reconciliation this endpoint choice exists to guarantee — and would
         // show a euro sign to a USD, GBP or ILS site. Every other money value
         // in this bundle comes from the API's own formattedAmount for that
         // same reason.
-        value: m.money
-          ? formatNumber(Math.round(total * 100) / 100)
-          : String(Math.round(total)),
+        // Counts are grouped too, as the Analytics screen's fmtInt groups them.
+        value: formatNumber(m.money ? Math.round(total * 100) / 100 : Math.round(total)),
         // The same number unformatted, so orderBy:amount sorts numerically
         // rather than lexically ("9" > "1,240" as text).
         amount: String(total),

package/templates/retail-store-owner/tier5-src/_shared/aria-hot-path.ts

@@ -1,10 +1,10 @@
 // The Aria transcript's hot path — the rules it is written to, and the two
 // primitives that make them hold.
 //
-// Adapted from `native-apps/PERFORMANCE.md` in wix-private/aria-native-apps, which
+// Adapted from the performance guide of Aria's native app, which
 // states eleven rules, each "a class of shipped regression". Most of them govern
-// 30 Hz streaming, which this app does not do yet (#2612), and adopting all eleven
-// for a POLLED chat would be cargo-culting. These four apply now (#2623):
+// 30 Hz streaming, which this app does not do yet, and adopting all eleven
+// for a POLLED chat would be cargo-culting. These four apply now:
 //
 //  1. NEVER RE-DERIVE THE WHOLE TRANSCRIPT PER TICK. Every poll re-reads the full
 //     transcript, and turning a message into a bubble is the expensive step —
@@ -32,7 +32,7 @@
 //     a POSITION, and the moment anything before it is dropped (an empty
 //     placeholder, a hidden-only row, a windowed read) the same index names a
 //     different message. The bubble id is also the row's stable test id
-//     (`<screen>.msg_<id>`, invariant 27). `transcriptKeys`, `mintLocalId`.
+//     (`<screen>.msg_<id>`), which UI tests find it by. `transcriptKeys`, `mintLocalId`.
 //
 //  4. EVERY REPEATING CLOCK HAS AN OWNER AND STOPS ON EVERY EXIT PATH. The only
 //     clock here is the reply ladder, `_poll` id `aria-turn`, and its owner is
@@ -56,7 +56,7 @@
 // drivers) and the native app's device budgets (cold start, frame time, hangs)
 // are deliberately NOT adopted here: nothing in this repo measures them for
 // Aria, and a budget nobody measures is decoration. Each rule above is pinned by
-// a test instead — `core/dev-server/tests/aria-hot-path.test.ts`.
+// a test instead, one per rule, each asserting a count.
 //
 // Dependency-free on purpose: the tests import this file directly.
 

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

@@ -229,8 +229,13 @@ function total(m: WixAnalyticsMeasurement | undefined): number {
 function seriesOf(m: WixAnalyticsMeasurement | undefined): number[] {
   return (m?.values ?? []).map((v) => v.value || 0);
 }
+/**
+ * Counts go through the same grouped formatter as money, so "1,544" sits beside
+ * "7,290.53" rather than "1544". The note on `fmtMoney` explains why it
+ * is `formatNumber` and never `toLocaleString`.
+ */
 function fmtInt(n: number): string {
-  return String(Math.round(n));
+  return formatNumber(Math.round(n));
 }
 /**
  * NOT `toLocaleString`. That is ECMA-402, which QuickJS-ng — watchOS and Wear OS —

package/templates/retail-store-owner/tier5-src/himi-owner-lite-ask/catalog.ts

@@ -165,15 +165,14 @@ export function metricRowsFrom(
         // screens cannot disagree in the last digit about the same measure.
         // NO currency symbol, and that is not an omission. The Analytics
         // screen's fmtMoney is `formatNumber(round(n*100)/100)` with no symbol
-        // (himi-owner-lite-analytics/index.ts:241). Adding one here would make
+        // (`fmtMoney` in himi-owner-lite-analytics/index.ts). Adding one here would make
         // the two screens render the SAME number differently — breaking the
         // reconciliation this endpoint choice exists to guarantee — and would
         // show a euro sign to a USD, GBP or ILS site. Every other money value
         // in this bundle comes from the API's own formattedAmount for that
         // same reason.
-        value: m.money
-          ? formatNumber(Math.round(total * 100) / 100)
-          : String(Math.round(total)),
+        // Counts are grouped too, as the Analytics screen's fmtInt groups them.
+        value: formatNumber(m.money ? Math.round(total * 100) / 100 : Math.round(total)),
         // The same number unformatted, so orderBy:amount sorts numerically
         // rather than lexically ("9" > "1,240" as text).
         amount: String(total),

package/templates/yoga-studio-owner/tier5-src/_shared/aria-hot-path.ts

@@ -1,10 +1,10 @@
 // The Aria transcript's hot path — the rules it is written to, and the two
 // primitives that make them hold.
 //
-// Adapted from `native-apps/PERFORMANCE.md` in wix-private/aria-native-apps, which
+// Adapted from the performance guide of Aria's native app, which
 // states eleven rules, each "a class of shipped regression". Most of them govern
-// 30 Hz streaming, which this app does not do yet (#2612), and adopting all eleven
-// for a POLLED chat would be cargo-culting. These four apply now (#2623):
+// 30 Hz streaming, which this app does not do yet, and adopting all eleven
+// for a POLLED chat would be cargo-culting. These four apply now:
 //
 //  1. NEVER RE-DERIVE THE WHOLE TRANSCRIPT PER TICK. Every poll re-reads the full
 //     transcript, and turning a message into a bubble is the expensive step —
@@ -32,7 +32,7 @@
 //     a POSITION, and the moment anything before it is dropped (an empty
 //     placeholder, a hidden-only row, a windowed read) the same index names a
 //     different message. The bubble id is also the row's stable test id
-//     (`<screen>.msg_<id>`, invariant 27). `transcriptKeys`, `mintLocalId`.
+//     (`<screen>.msg_<id>`), which UI tests find it by. `transcriptKeys`, `mintLocalId`.
 //
 //  4. EVERY REPEATING CLOCK HAS AN OWNER AND STOPS ON EVERY EXIT PATH. The only
 //     clock here is the reply ladder, `_poll` id `aria-turn`, and its owner is
@@ -56,7 +56,7 @@
 // drivers) and the native app's device budgets (cold start, frame time, hangs)
 // are deliberately NOT adopted here: nothing in this repo measures them for
 // Aria, and a budget nobody measures is decoration. Each rule above is pinned by
-// a test instead — `core/dev-server/tests/aria-hot-path.test.ts`.
+// a test instead, one per rule, each asserting a count.
 //
 // Dependency-free on purpose: the tests import this file directly.
 

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

@@ -229,8 +229,13 @@ function total(m: WixAnalyticsMeasurement | undefined): number {
 function seriesOf(m: WixAnalyticsMeasurement | undefined): number[] {
   return (m?.values ?? []).map((v) => v.value || 0);
 }
+/**
+ * Counts go through the same grouped formatter as money, so "1,544" sits beside
+ * "7,290.53" rather than "1544". The note on `fmtMoney` explains why it
+ * is `formatNumber` and never `toLocaleString`.
+ */
 function fmtInt(n: number): string {
-  return String(Math.round(n));
+  return formatNumber(Math.round(n));
 }
 /**
  * NOT `toLocaleString`. That is ECMA-402, which QuickJS-ng — watchOS and Wear OS —

package/templates/yoga-studio-owner/tier5-src/himi-owner-lite-ask/catalog.ts

@@ -165,15 +165,14 @@ export function metricRowsFrom(
         // screens cannot disagree in the last digit about the same measure.
         // NO currency symbol, and that is not an omission. The Analytics
         // screen's fmtMoney is `formatNumber(round(n*100)/100)` with no symbol
-        // (himi-owner-lite-analytics/index.ts:241). Adding one here would make
+        // (`fmtMoney` in himi-owner-lite-analytics/index.ts). Adding one here would make
         // the two screens render the SAME number differently — breaking the
         // reconciliation this endpoint choice exists to guarantee — and would
         // show a euro sign to a USD, GBP or ILS site. Every other money value
         // in this bundle comes from the API's own formattedAmount for that
         // same reason.
-        value: m.money
-          ? formatNumber(Math.round(total * 100) / 100)
-          : String(Math.round(total)),
+        // Counts are grouped too, as the Analytics screen's fmtInt groups them.
+        value: formatNumber(m.money ? Math.round(total * 100) / 100 : Math.round(total)),
         // The same number unformatted, so orderBy:amount sorts numerically
         // rather than lexically ("9" > "1,240" as text).
         amount: String(total),