@wireai/activation 0.12.2 → 0.13.0

package/src/types.ts

@@ -272,6 +272,20 @@ export type OnboardingProgress = {
   total: number;
   /** Base-question key for the CURRENT screen, when known (used to pick a validator). */
   key?: string;
+  /**
+   * STABLE per-slot identity for the CURRENT screen, when the backend sends one. Preferred over
+   * {@link key} for both the answer key and the validator lookup.
+   *
+   * WHY IT EXISTS: `key` is authored from the question's prompt text (the tenant flows slugify it and
+   * cut at 32 chars), so re-wording a question mints a NEW key — the answer a host reads as
+   * `answers.interests` silently becomes `answers.what_are_you_into_v2`, with no error anywhere. A
+   * slot is the question's identity independent of its wording.
+   *
+   * FULLY ADDITIVE AND CURRENTLY INERT: no server emits it yet. Every fallback is PER-CARD, so a
+   * thread that mixes slotted and unslotted cards (the real shape during a rollout) keys each one
+   * correctly, and a backend that never sends it produces byte-identical behaviour to 0.12.2.
+   */
+  slot_id?: string;
   /** Whether the CURRENT screen may be skipped (backend-marked; default false → no Skip shown). */
   skippable?: boolean;
 };

package/src/utils/deriveAnswers.ts

@@ -29,10 +29,14 @@ export const deriveAnswers = (messages: Message[]): Record<string, unknown> => {
     if (!m || m.role !== "assistant" || !r || r.action !== "render") continue;
 
     const props = (r.props ?? {}) as Record<string, unknown>;
-    const progress = props.progress as { key?: string } | undefined;
+    const progress = props.progress as { key?: string; slot_id?: string } | undefined;
     const questionText =
       (props.title as string) ?? (props.label as string) ?? (props.question as string);
-    const key = progress?.key || questionText;
+    // slot_id > key > question text, decided PER CARD. A thread that mixes slotted and unslotted
+    // cards is the real shape during a server rollout, so caching a "this backend does slots" verdict
+    // off the first card would mis-key every later one. Against a backend that sends no `slot_id`
+    // this is byte-identical to 0.12.2.
+    const key = progress?.slot_id || progress?.key || questionText;
 
     const reply = messages[i + 1];
     if (key && reply?.role === "user") {

package/src/utils/readProgress.ts

@@ -15,6 +15,8 @@ type PartialProgress = {
   step?: number;
   total?: number;
   key?: string;
+  /** The stable per-slot identity, when the backend sends one. See `OnboardingProgress.slot_id`. */
+  slot_id?: string;
   skippable?: boolean;
 };
 
@@ -28,6 +30,8 @@ export const readProgress = (response?: WireAIResponse): PartialProgress => {
     step: typeof p.step === "number" ? p.step : undefined,
     total: typeof p.total === "number" ? p.total : undefined,
     key: typeof p.key === "string" ? p.key : undefined,
+    // Whitelisted the same way as every other field: an old backend simply omits it.
+    slot_id: typeof p.slot_id === "string" ? p.slot_id : undefined,
     skippable: typeof p.skippable === "boolean" ? p.skippable : undefined,
   };
 };

package/src/utils/warnInDev.ts

@@ -0,0 +1,33 @@
+/**
+ * warnInDev — the ONE developer-warning primitive.
+ *
+ * The kit warns a developer in four places (the onboarding host, the env-config helper, the analytics
+ * façade, the current-session registry) and until 0.13.0 each carried its own copy of the same five
+ * lines. Three were byte-identical; the fourth differed only by returning whether it actually warned.
+ * Four copies of a guard is four chances for one of them to drift out of the `__DEV__` gate, which is
+ * the failure that matters: a warning that runs in production is a string built for nobody.
+ *
+ * ON THE TREE-SHAKING NOTE THIS REPLACES: `analytics/currentSession` used to justify its copy as
+ * keeping the module import-free for the tree-shaken `./analytics` bundle. That rationale had already
+ * lapsed — the module imports `makeSessionId` from `./reportClientEvent` — and this module has no
+ * imports of its own, so it adds one leaf to the graph and nothing to the bundle. The `treeShake`
+ * canary still holds the real guarantee (the analytics graph reaches no UI module).
+ */
+
+/** RN sets this global; absent under node/SSR. Read defensively, never assumed. */
+declare const __DEV__: boolean | undefined;
+
+/**
+ * Emit a one-line developer warning, but ONLY in a dev build (RN `__DEV__`). No-op in prod/tests.
+ *
+ * Returns whether it ACTUALLY warned, which a caller holding a once-flag must honour: marking
+ * "already warned" after a no-op would burn the single warning in production, and the one dev build
+ * that needed it would then run silent.
+ */
+export const warnInDev = (message: string): boolean => {
+  if (typeof __DEV__ !== "undefined" && __DEV__ && typeof console !== "undefined" && console.warn) {
+    console.warn(message);
+    return true;
+  }
+  return false;
+};

package/src/components/DoneBlock.tsx

@@ -1,37 +0,0 @@
-/**
- * DoneBlock — a brief themed "all set" state shown when the flow completes, while
- * the host persists results and navigates away. Purely cosmetic; the real
- * terminal signal is the SDK's StatusCard (handled in OnboardingFlow).
- */
-import React from "react";
-import { StyleSheet, Text, View } from "react-native";
-import { useOnboardingTheme } from "../theme/ThemeContext";
-import { bodyStyle, headingStyle } from "../theme/typography";
-
-export type DoneBlockProps = {
-  title?: string;
-  message?: string;
-};
-
-const _DoneBlock: React.FC<DoneBlockProps> = ({
-  title = "You're all set",
-  message = "Personalizing your experience…",
-}) => {
-  const t = useOnboardingTheme();
-  return (
-    <View style={[styles.center, { gap: t.spacing.sm, padding: t.spacing.lg }]}>
-      <Text style={[headingStyle(t.fonts), { color: t.colors.success, textAlign: "center" }]}>
-        {title}
-      </Text>
-      <Text style={[bodyStyle(t.fonts), { color: t.colors.textMuted, textAlign: "center" }]}>
-        {message}
-      </Text>
-    </View>
-  );
-};
-
-export const DoneBlock = React.memo(_DoneBlock);
-
-const styles = StyleSheet.create({
-  center: { flex: 1, alignItems: "center", justifyContent: "center" },
-});