@wireai/activation 0.8.0 → 0.9.0

package/src/session-analytics/lifecycle.ts

@@ -44,7 +44,7 @@ import { reportSessionStart, SESSION_STARTED_EVENT } from "./reportSessionStart"
  *  {@link SESSION_STARTED_EVENT}; a trigger keys off this exact string. */
 export const FIRST_OPEN_EVENT = "app.first_open" as const;
 
-/** Storage key for the once-ever first-open flag, e.g. `wireai:first_open:myelino`. Mirrors the
+/** Storage key for the once-ever first-open flag, e.g. `wireai:first_open:acme`. Mirrors the
  *  `wireai:<concern>:<appId>` namespacing of {@link sessionStorageKey}. */
 export const firstOpenStorageKey = (appId: string): string => `wireai:first_open:${appId}`;
 

package/src/session-analytics/useSessionStart.ts

@@ -1,7 +1,7 @@
 /**
  * useSessionStart — the optional convenience hook that fires {@link reportSessionStart} for you.
  *
- * Two firing moments, mirroring the Myelino/Morrow session-counter semantics:
+ * Two firing moments, mirroring the reference apps' session-counter semantics:
  *   • ON MOUNT — the app opened (cold start or the provider first rendered).
  *   • ON FOREGROUND after a real background — when AppState returns to `active` having been
  *     backgrounded for at least {@link BACKGROUND_SESSION_MS} (30 min), that's a NEW open, so a
@@ -10,7 +10,7 @@
  * Each firing mints its OWN per-open `session_id` (held in a ref so a re-render never re-fires),
  * so grouping over time is by `deviceKey`/`userId`, never by session_id (see reportSessionStart).
  *
- * The hook is OPTIONAL. A host that already owns a session counter (Myelino/Morrow do) can skip
+ * The hook is OPTIONAL. A host that already owns a session counter (most hosts do) can skip
  * the hook and call `reportSessionStart(...)` directly from its own "app opened" path — BOTH
  * paths are first-class. This hook is the batteries-included option for a host that has none.
  *

package/src/showcase/FeatureShowcase.tsx

@@ -135,7 +135,7 @@ const _FeatureShowcase: React.FC<FeatureShowcaseProps> = ({
   // Calm the large image/hero panel. The package's `background.primary` is a
   // SINGLE key that fills the primary button, the intro highlight AND this hero
   // panel — painting it `accent` (correct for the button) also flooded the first
-  // slide with the app color (Malik, Myelino, 0.3.1). The package exposes a
+  // slide with the app color (0.3.1). The package exposes a
   // `background` render prop that REPLACES that panel fill outright, so we keep
   // the button accent (via `colors`) and paint the panel a calm surface + faint
   // accent tint here. See showcasePanelBackground.

package/src/showcase/showcaseColors.ts

@@ -63,7 +63,7 @@ export const showcaseColorsFromTheme = (
  * Opacity of the accent tint layered over the theme surface for the showcase's
  * image hero panel. Kept in a calm 8–12% band so the panel reads as a subtle
  * brand wash — a hint of the accent, never the full-bleed flood that `accent`
- * as a solid fill produced (the 0.3.1 → 0.3.2 bug Malik saw in Myelino).
+ * as a solid fill produced (the 0.3.1 → 0.3.2 bug seen in a host app).
  */
 export const SHOWCASE_PANEL_TINT_OPACITY = 0.1;
 

package/src/theme/mergeThemeOver.ts

@@ -0,0 +1,27 @@
+/**
+ * mergeThemeOver — merge a partial theme over an ARBITRARY base theme.
+ *
+ * Sibling of `mergeTheme` (defaultTheme.ts), which merges over the DEFAULT theme only.
+ * Gates need the other shape: a `theme` prop merged over whatever the host's active
+ * ThemeContext currently is. That helper was copy-pasted verbatim into ReviewGate and
+ * QuestionnaireGate; it lives here once instead, so a new theme section can never be
+ * added to one gate and forgotten in the other.
+ *
+ * Two levels deep, matching `mergeTheme`: the theme is intentionally shallow, so each
+ * known sub-object is merged and scalars overwrite.
+ */
+import type { OnboardingTheme } from "./types";
+
+export const mergeThemeOver = (
+  base: OnboardingTheme,
+  override?: Partial<OnboardingTheme>,
+): OnboardingTheme => {
+  if (!override) return base;
+  return {
+    colors: { ...base.colors, ...override.colors },
+    fonts: { ...base.fonts, ...override.fonts },
+    radius: { ...base.radius, ...override.radius },
+    spacing: { ...base.spacing, ...override.spacing },
+    button: { ...base.button, ...override.button },
+  };
+};

package/src/types.ts

@@ -108,6 +108,14 @@ export type WireOnboardingProps = {
    * via `illustration`; the kit slots the matching node (keeping itself dependency-free).
    */
   illustrations?: Record<string, import("react").ReactNode>;
+  /**
+   * App-supplied ICON nodes, keyed by the semantic vocabulary name the AI emits (e.g.
+   * `{ instagram: <BrandIg/> }`). Checked FIRST, so a host can override any icon with its own
+   * brand mark, supply icons without installing `@expo/vector-icons`, or extend the vocabulary
+   * with names of its own. Anything not listed falls back to `@expo/vector-icons` when that
+   * optional peer is present, and to no icon at all when it isn't — never a crash.
+   */
+  icons?: Record<string, import("react").ReactNode>;
   /** Per-step validators keyed by base-question key, e.g. `{ username: checkUsername }`. */
   validators?: Record<string, StepValidator>;
   /** Fired once the flow reaches its terminal StatusCard. */

package/dist/transport-BeO_Brcu.d.mts

@@ -1,40 +0,0 @@
-import { j as ReviewTarget, i as ReviewSubmission } from './types-A6pTxIZV.mjs';
-
-/**
- * transport.ts — kit → Wire server requests for the review module, all fire-and-forget
- * (analytics/reviews must never break the app). Mirrors analytics/reportClientEvent: a
- * thin fetch wrapper, Bearer tenant key, swallow every error.
- *
- *   • submitReview        → POST {serverUrl}/v1/reviews   (the 1-4 feedback body)
- *   • reportAppEvent      → POST {serverUrl}/v1/events    (generic app.* namespace)
- *
- * `reportAppEvent` is the strategic extension: it lets a host report arbitrary in-app
- * events through the SAME transport (stored server-side as event_type='app_event',
- * question_key=<name>), which is what the backend review-firing rules evaluate on — and
- * it seeds the broader app-analytics stream. Keep payloads minimal + non-PII.
- */
-
-/**
- * POST a review (the 1-4 feedback path). Fire-and-forget: a missing target, a build error,
- * a missing `fetch`, or a network failure is swallowed and the call returns immediately.
- */
-declare const submitReview: (target: ReviewTarget | undefined, review: ReviewSubmission) => void;
-/** Options for a reported app event. `deviceKey` groups a device's sessions server-side. */
-interface ReportAppEventOptions {
-    /** The onboarding/session id to correlate with, when known. */
-    sessionId?: string;
-    /** A stable, non-PII device id — the review-decision endpoint reads it for min-sessions. */
-    deviceKey?: string;
-    /** Small non-PII extras. */
-    meta?: Record<string, unknown>;
-}
-/**
- * Report a generic in-app event through the existing events transport. Stored server-side
- * as `event_type='app_event'`, `question_key=<name>`. Fire-and-forget. Keep `name` a short
- * stable identifier and `meta` small + non-PII.
- *
- *   reportAppEvent(target, "content_share", { sessionId, deviceKey });
- */
-declare const reportAppEvent: (target: ReviewTarget | undefined, name: string, options?: ReportAppEventOptions) => void;
-
-export { type ReportAppEventOptions as R, reportAppEvent as r, submitReview as s };

package/dist/transport-DLpd1v5_.d.ts

@@ -1,40 +0,0 @@
-import { j as ReviewTarget, i as ReviewSubmission } from './types-BhpXJGlg.js';
-
-/**
- * transport.ts — kit → Wire server requests for the review module, all fire-and-forget
- * (analytics/reviews must never break the app). Mirrors analytics/reportClientEvent: a
- * thin fetch wrapper, Bearer tenant key, swallow every error.
- *
- *   • submitReview        → POST {serverUrl}/v1/reviews   (the 1-4 feedback body)
- *   • reportAppEvent      → POST {serverUrl}/v1/events    (generic app.* namespace)
- *
- * `reportAppEvent` is the strategic extension: it lets a host report arbitrary in-app
- * events through the SAME transport (stored server-side as event_type='app_event',
- * question_key=<name>), which is what the backend review-firing rules evaluate on — and
- * it seeds the broader app-analytics stream. Keep payloads minimal + non-PII.
- */
-
-/**
- * POST a review (the 1-4 feedback path). Fire-and-forget: a missing target, a build error,
- * a missing `fetch`, or a network failure is swallowed and the call returns immediately.
- */
-declare const submitReview: (target: ReviewTarget | undefined, review: ReviewSubmission) => void;
-/** Options for a reported app event. `deviceKey` groups a device's sessions server-side. */
-interface ReportAppEventOptions {
-    /** The onboarding/session id to correlate with, when known. */
-    sessionId?: string;
-    /** A stable, non-PII device id — the review-decision endpoint reads it for min-sessions. */
-    deviceKey?: string;
-    /** Small non-PII extras. */
-    meta?: Record<string, unknown>;
-}
-/**
- * Report a generic in-app event through the existing events transport. Stored server-side
- * as `event_type='app_event'`, `question_key=<name>`. Fire-and-forget. Keep `name` a short
- * stable identifier and `meta` small + non-PII.
- *
- *   reportAppEvent(target, "content_share", { sessionId, deviceKey });
- */
-declare const reportAppEvent: (target: ReviewTarget | undefined, name: string, options?: ReportAppEventOptions) => void;
-
-export { type ReportAppEventOptions as R, reportAppEvent as r, submitReview as s };