fix(cross-sell): pin outcome value grouping to en-IN (deterministic INR)

The observed-outcome value used a bare toLocaleString(), so its grouping
followed the host's default locale — 1,25,000 on an Indian-locale box,
125,000 on a US-locale runner. That made the integration assertion
environment-dependent (it expected US grouping and failed on this box).
This is Indian BFSI money (INR); pin en-IN so it always reads 1,25,000,
and assert the true artifact. Verified green under both en-IN and en-US.

Author: alichherawalla

src/components/app-use/CrossSellCustomerJourney.tsx

@@ -208,7 +208,10 @@ export function CrossSellCustomerJourney({
                         <p className="mt-1 text-xs text-muted-foreground">
                           {formatDate(outcome.observedAt)}
                           {outcome.value !== null && outcome.currency
-                            ? ` · ${outcome.currency} ${outcome.value.toLocaleString()}`
+                            ? // Pin the grouping locale: this is Indian BFSI money (INR), so it
+                              // must read 1,25,000 — and a bare toLocaleString() would otherwise
+                              // follow the host's default locale, making the output non-deterministic.
+                              ` · ${outcome.currency} ${outcome.value.toLocaleString('en-IN')}`
                             : ''}
                         </p>
                         <p className="mt-1 break-all font-mono text-[10px] text-muted-foreground">

test/cross-sell-rm-experience.integration.test.ts

@@ -215,7 +215,7 @@ test('an observed response stays separate from CRM completion and suggests conve
   assert.match(html, /value="converted" selected=""/);
   assert.match(html, /Observed customer results/);
   assert.match(html, /accepted/);
-  assert.match(html, /INR 125,000/);
+  assert.match(html, /INR 1,25,000/);
   assert.match(html, /CRM completion confirms the system change/);
 });