@wireai/activation 0.12.1 → 0.13.0

package/dist/{currentSession-BxEB37xt.d.ts → currentSession-D7zabMXK.d.ts}

@@ -190,8 +190,17 @@ declare const reportClientEvent: (target: ClientEventTarget | undefined, event:
  * `/v1/events` path, but resolve only once the server has RESPONDED — so a decision re-fetch fired
  * immediately after is guaranteed to see the event in the session stream (this is the guarantee
  * `wire.track` needs before it triggers decision revalidation). Never throws: a missing/invalid
- * target, a missing `fetch`, a network error, or a non-2xx status all resolve to `false`. Resolves
- * `true` only on a 2xx response.
+ * target, a missing `fetch`, a network error, or a non-2xx status all resolve to `false`.
+ *
+ * ⚠️ 0.13.0: a 2xx is NO LONGER SUFFICIENT. The endpoint answers HTTP 200 with `{ ok, written,
+ * skipped }` and counts an event it refuses in `skipped`, so this used to resolve `true` for an event
+ * the server had thrown away — and `wire.track` then bumped decision revalidation, making every
+ * subscribed gate re-fetch against a stream the action never entered. It now reads the ack and
+ * resolves `false` when the server reports a positive `skipped`.
+ *
+ * BACKWARD COMPATIBLE BY CONSTRUCTION: only an explicit positive `skipped` demotes a 200. An old
+ * server that sends no such field, a body that cannot be parsed, or a response with no `.json` at all
+ * resolves `true` exactly as before — the change can produce no false negatives.
  */
 declare const reportClientEventsAwait: (target: ClientEventTarget | undefined, events: ClientEvent[]) => Promise<boolean>;
 /** Convenience single-event wrapper around {@link reportClientEventsAwait}. */
@@ -472,6 +481,20 @@ 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;
 };
@@ -638,6 +661,10 @@ type EventQueue = {
     /** Current pending (in-memory) count. */
     size(): number;
 };
+/** Test-only: forget every claimed queue key. A real RELAUNCH is a new process, so a test that
+ *  simulates one in-process must call this or its second queue reads as a concurrent sibling.
+ *  Exported from `@wireai/activation/analytics`, matching `resetAutoDeviceKeys` / `resetCurrentSessionId`. */
+declare const resetEventQueueKeys: () => void;
 /**
  * Create an offline-first event queue. Loads any persisted backlog on creation so a
  * killed-and-relaunched app resumes where it left off. Returns the {@link EventQueue} surface.
@@ -705,8 +732,6 @@ interface ResolvedUserContext {
     /** The `user_context` bucket (device_key, app_version, user_email[+ _hashed], custom.*). */
     userContext?: Record<string, string | number | boolean>;
 }
-/** Reserved `user_context` keys the kit itself writes; host `extra` is namespaced away from these. */
-declare const RESERVED_USER_CONTEXT_KEYS: readonly ["device_key", "app_version", "app_build", "network_type", "session_count", "returning", "platform", "user_email", "user_email_hashed"];
 /** The prefix applied to every host `extra` key so it can never collide with a reserved key. */
 declare const EXTRA_KEY_PREFIX: "custom.";
 /** A finite scalar the wire accepts. Non-finite numbers (NaN/Infinity) are NOT scalars here. */
@@ -831,17 +856,127 @@ type IdentifyOnboardingOptions = {
     appId?: string;
     /** Storage key override — pass the same `persistKey` you gave `<WireOnboarding>`, if any. */
     persistKey?: string;
+    /**
+     * OPT-IN LAST RESORT, default `false`. When no ONBOARDING session can be resolved (no `contextId`,
+     * nothing in `storage`), bind the user to the LIVE PER-OPEN app session instead and return
+     * `"app_session"`.
+     *
+     * ⚠️ These are two different id spaces sharing one wire field. An onboarding session id is the A2A
+     * `contextId`; a per-open id is what `app.session_started` registers. The server's onboarding funnel
+     * groups by `session_id`, so a per-open id posted here does not attach the user to their onboarding
+     * — it writes a row nothing in that funnel can join. Until 0.13.0 this happened SILENTLY and
+     * returned `true`, in exactly the documented post-completion case (completion clears the persisted
+     * session), so the funnel stayed unattributed while the host was told it had worked.
+     *
+     * Turn it on only if binding the id to *some* session the server saw is genuinely worth more to you
+     * than knowing the onboarding bind failed — and read the return value, which now says which it was.
+     */
+    allowAppSessionFallback?: boolean;
 };
+/**
+ * What {@link identifyOnboarding} bound, and to WHICH id space — because `true` could not say.
+ *
+ *   • `"onboarding"`  — bound to the A2A `contextId`. This is the one that attributes the funnel.
+ *   • `"app_session"` — bound to the live per-open app session, via `allowAppSessionFallback`. The
+ *                       server saw that session, but it is not this user's onboarding.
+ *   • `false`         — nothing was dispatched (no user id, no server url, no resolvable session).
+ *
+ * ⚠️ 0.13.0 widened this from `boolean`. `"onboarding"` is truthy, so an `if (await identify…)` still
+ * behaves identically; only an explicit `: boolean` annotation needs updating.
+ */
+type IdentifyOnboardingBinding = "onboarding" | "app_session" | false;
 /**
  * Attach a host user id to an onboarding session AFTER the fact (post-registration), by sending
  * an `identify` client event to `/v1/events`. Resolves the contextId from an explicit
  * `contextId` or, failing that, from the persisted session in the host `storage`.
  *
- * Fire-and-forget under the hood (never throws, never blocks onboarding). Resolves to `true`
- * when an identify event was dispatched, `false` when it couldn't (no user id, no server url,
- * or no resolvable contextId).
+ * Fire-and-forget under the hood (never throws, never blocks onboarding). Resolves to the
+ * {@link IdentifyOnboardingBinding} that says WHICH id space was bound, or `false` when nothing could
+ * be (no user id, no server url, or no resolvable session).
  */
-declare const identifyOnboarding: (opts: IdentifyOnboardingOptions) => Promise<boolean>;
+declare const identifyOnboarding: (opts: IdentifyOnboardingOptions) => Promise<IdentifyOnboardingBinding>;
+
+/**
+ * identityRecord — the ONE provenance-carrying shape for an id the kit puts on the wire.
+ *
+ * WHY IT EXISTS. `session_id` and `device_key` are bare `string`s minted independently by four
+ * subsystems, and nothing anywhere recorded WHERE a given id came from. Every id-layer defect this
+ * release fixes is a direct consequence of that one omission:
+ *
+ *   • a rejecting storage adapter's in-memory id was indistinguishable from a persisted one, so the
+ *     kit injected a fresh per-launch join key on every launch — nothing carried `durable`.
+ *   • an app-OPEN session id could be posted into a field that means the ONBOARDING session, and the
+ *     caller was told `true` — nothing carried `space`.
+ *   • an auto-minted `wdev_*` could be injected beside a device id the host demonstrably owns on
+ *     another surface, silently — nothing carried `source`.
+ *
+ * WHAT THIS IS, AND WHAT IT DELIBERATELY IS NOT. It is a small record plus a process-wide registry of
+ * the ids a HOST supplied. It is NOT a branded-type refactor (`OnboardingSessionId` / `AppSessionId` /
+ * `DeviceKey` across every signature) — that is real value and it is deferred, because it touches
+ * every file and is not what makes a number correct this week. Nothing here changes the wire.
+ *
+ * WHY A `Symbol.for` REGISTRY. Same reason as `analytics/currentSession` and `context/deviceId`: tsup
+ * inlines a separate copy of a module into each bundle (`.` and `./analytics`), so a plain module
+ * `let` would give every bundle its own registry and the cross-surface question this exists to answer
+ * ("did ANY surface in this process get a host-supplied device key?") would read `no` from the wrong
+ * copy. `Symbol.for` resolves to one slot on `globalThis` no matter how many copies exist.
+ */
+/**
+ * Which id space a value belongs to. These are NOT interchangeable, and the whole point of naming
+ * them is that a value from one space must never be posted into a field that means another:
+ *   • `onboarding-session` — the A2A `contextId` for ONE onboarding run.
+ *   • `app-session`        — the per-app-open session id (`app.session_started`).
+ *   • `device`             — the per-install `device_key`; the only cross-family join key.
+ */
+type IdentitySpace = "onboarding-session" | "app-session" | "device";
+/** Where the value came from: the host handed it over, or the kit minted it. */
+type IdentitySource = "host" | "auto";
+/** An id plus everything a consumer needs to decide whether it may use it. */
+type IdentityRecord = {
+    /** The id itself, trimmed. Never empty (a blank input yields no record at all). */
+    value: string;
+    /** Which id space {@link value} belongs to. */
+    space: IdentitySpace;
+    /** `host` = the integrator supplied it; `auto` = the kit minted it. */
+    source: IdentitySource;
+    /**
+     * Whether the value was actually PERSISTED (or adopted from persistence), as opposed to living
+     * only in this process's memory. A non-durable auto id is a DIFFERENT id on the next launch, which
+     * for a `device` value is worse than no value at all: the server counts `min_sessions` by distinct
+     * opens grouped on `device_key`, so a per-launch key corrupts the counter rather than leaving it
+     * empty. A host-supplied value is durable by definition — the host owns its lifetime.
+     */
+    durable: boolean;
+};
+/** Input to {@link resolveIdentity}. `value` is `unknown` so callers can pass a raw prop through. */
+type ResolveIdentityInput = {
+    value: unknown;
+    space: IdentitySpace;
+    source: IdentitySource;
+    /** Defaults to `true` for a host value (the host owns its lifetime) and `false` otherwise. */
+    durable?: boolean;
+    /** Tenant/app id — two tenants in one process never share a provenance entry. */
+    scope?: string;
+};
+/**
+ * Build an {@link IdentityRecord} from a candidate value, or `undefined` when there is nothing usable
+ * (a non-string, or blank after trimming) — so a caller can `if (record)`-gate instead of guessing
+ * whether an empty string means "none" or "not yet".
+ *
+ * SIDE EFFECT, deliberate and the reason this is a function and not an object literal: a `host`-sourced
+ * record is RECORDED on the process registry, so a later surface can ask {@link hostIdentity} whether
+ * this process demonstrably owns a host id in that space. That is what turns "the kit injected its own
+ * key" from a silent third id space into a warnable condition. Never throws.
+ */
+declare const resolveIdentity: (input: ResolveIdentityInput) => IdentityRecord | undefined;
+/**
+ * The HOST-supplied id this process has seen for a space, or `undefined` when every surface so far
+ * let the kit mint its own. Answers the cross-surface question no single mount can answer alone:
+ * "does this app own a device id that this particular mount was not given?"
+ */
+declare const hostIdentity: (space: IdentitySpace, scope?: string) => string | undefined;
+/** Test-only: forget every recorded host identity so a unit test starts from a clean registry. */
+declare const resetIdentityProvenance: () => void;
 
 /**
  * deviceId — mint a stable, NON-PII, per-install device id the kit owns when the host supplies
@@ -862,6 +997,7 @@ declare const identifyOnboarding: (opts: IdentifyOnboardingOptions) => Promise<b
  * A host that wants its OWN device id still wins: pass `WireUserContext.deviceKey` and the kit uses
  * that verbatim and never mints/persists an auto id.
  */
+
 /** Prefix so an auto-minted id is visibly the kit's (distinguishable from a host-supplied `deviceKey`). */
 declare const AUTO_DEVICE_ID_PREFIX = "wdev_";
 /** The storage key the façade persists the auto-minted id under (namespaced per `appId`). */
@@ -917,6 +1053,22 @@ declare const resolveAutoDeviceKey: (opts?: ResolveAutoDeviceKeyOptions) => stri
  * with no `storage` it resolves immediately (there is nothing to hydrate from).
  */
 declare const hydrateAutoDeviceKey: (opts?: ResolveAutoDeviceKeyOptions) => Promise<string>;
+/**
+ * The PROVENANCE-CARRYING sibling of {@link hydrateAutoDeviceKey}: the same awaited read, but it
+ * answers "is this id one this install will KEEP?" instead of only "what is the id?".
+ *
+ * WHY IT EXISTS (K1). `<WireOnboarding>` gated auto-injection on `Boolean(storage)` — the presence of
+ * the prop — because a string carries no provenance and there was nothing better to gate on. A
+ * REJECTING adapter therefore injected a fresh `wdev_*` on every launch: strictly worse than
+ * injecting nothing, since the server counts `min_sessions` by distinct opens grouped on `device_key`,
+ * so a per-launch key corrupts that counter AND inflates distinct-device counts. Callers that write a
+ * key onto the wire as a cross-launch join must read `durable` and refuse a `false`.
+ *
+ * Resolves `undefined` only when there is no usable id at all. With no `storage` it resolves
+ * immediately with `durable: false` — a process-scoped id is exactly what "no persistence" means.
+ * Never throws or rejects.
+ */
+declare const hydrateDeviceIdentity: (opts?: ResolveAutoDeviceKeyOptions) => Promise<IdentityRecord | undefined>;
 /** Test-only: forget every auto id + hydration flag so a unit test starts from a clean registry. */
 declare const resetAutoDeviceKeys: () => void;
 
@@ -948,4 +1100,4 @@ declare const resetCurrentSessionId: () => void;
  */
 declare const ensureCurrentSessionId: () => string;
 
-export { hydrateAutoDeviceKey as $, AUTO_DEVICE_ID_PREFIX as A, resolveAutoDeviceKey as B, type ClearUserContextOptions as C, type DeviceKeyStorage as D, type EventQueueOptions as E, setCurrentSessionId as F, toAnalyticsEvent as G, type WireOnboardingProps as H, type WireOnboardingConfig as I, type OnboardingEvent as J, type OnboardingCopy as K, type DeviceContext as L, type DeviceFormFactor as M, EXTRA_KEY_PREFIX as N, type OnboardingResult as O, type IdentifyOnboardingOptions as P, type OnboardingProgress as Q, type ResolveAutoDeviceKeyOptions as R, type StepValidator as S, RESERVED_USER_CONTEXT_KEYS as T, type ResolveUserContextOptions as U, type ResolvedUserContext as V, type WireUserContext as W, USER_ID_MAX_LENGTH as X, activationJoinContext as Y, collectDeviceContext as Z, hashEmailFnv1a as _, type AnalyticsEvent as a, identifyOnboarding as a0, isWireScalar as a1, mintDeviceId as a2, namespaceExtra as a3, resolveUserContext as a4, sanitizeUserId as a5, type ClientEvent as b, type ClientEventTarget as c, type ClientEventType as d, type ContextEnvelope as e, type ContextEnvelopeInput as f, type EnvelopeSource as g, type EventQueue as h, WIRE_ONBOARDING_EVENTS as i, type WireOnboardingEventName as j, analyticsUserIdStorageKey as k, buildContextEnvelope as l, clearPiiFromContext as m, clearUserContext as n, createEventQueue as o, deviceIdStorageKey as p, ensureCurrentSessionId as q, getCurrentSessionId as r, looksLikeEmail as s, makeSessionId as t, reportClientEvent as u, reportClientEventAwait as v, reportClientEvents as w, reportClientEventsAwait as x, resetAutoDeviceKeys as y, resetCurrentSessionId as z };
+export { USER_ID_MAX_LENGTH as $, AUTO_DEVICE_ID_PREFIX as A, resetEventQueueKeys as B, type ClearUserContextOptions as C, type DeviceKeyStorage as D, type EventQueueOptions as E, resolveAutoDeviceKey as F, setCurrentSessionId as G, toAnalyticsEvent as H, type WireOnboardingProps as I, type WireOnboardingConfig as J, type OnboardingEvent as K, type OnboardingCopy as L, type DeviceContext as M, type DeviceFormFactor as N, type OnboardingResult as O, EXTRA_KEY_PREFIX as P, type IdentifyOnboardingBinding as Q, type ResolveAutoDeviceKeyOptions as R, type StepValidator as S, type IdentifyOnboardingOptions as T, type IdentityRecord as U, type IdentitySource as V, type WireUserContext as W, type IdentitySpace as X, type OnboardingProgress as Y, type ResolveUserContextOptions as Z, type ResolvedUserContext as _, type AnalyticsEvent as a, activationJoinContext as a0, collectDeviceContext as a1, hashEmailFnv1a as a2, hostIdentity as a3, hydrateAutoDeviceKey as a4, hydrateDeviceIdentity as a5, identifyOnboarding as a6, isWireScalar as a7, mintDeviceId as a8, namespaceExtra as a9, resetIdentityProvenance as aa, resolveIdentity as ab, resolveUserContext as ac, sanitizeUserId as ad, type ClientEvent as b, type ClientEventTarget as c, type ClientEventType as d, type ContextEnvelope as e, type ContextEnvelopeInput as f, type EnvelopeSource as g, type EventQueue as h, WIRE_ONBOARDING_EVENTS as i, type WireOnboardingEventName as j, analyticsUserIdStorageKey as k, buildContextEnvelope as l, clearPiiFromContext as m, clearUserContext as n, createEventQueue as o, deviceIdStorageKey as p, ensureCurrentSessionId as q, getCurrentSessionId as r, looksLikeEmail as s, makeSessionId as t, reportClientEvent as u, reportClientEventAwait as v, reportClientEvents as w, reportClientEventsAwait as x, resetAutoDeviceKeys as y, resetCurrentSessionId as z };

package/dist/{currentSession-BlCeDP0f.d.mts → currentSession-_GynvhzT.d.mts}

@@ -190,8 +190,17 @@ declare const reportClientEvent: (target: ClientEventTarget | undefined, event:
  * `/v1/events` path, but resolve only once the server has RESPONDED — so a decision re-fetch fired
  * immediately after is guaranteed to see the event in the session stream (this is the guarantee
  * `wire.track` needs before it triggers decision revalidation). Never throws: a missing/invalid
- * target, a missing `fetch`, a network error, or a non-2xx status all resolve to `false`. Resolves
- * `true` only on a 2xx response.
+ * target, a missing `fetch`, a network error, or a non-2xx status all resolve to `false`.
+ *
+ * ⚠️ 0.13.0: a 2xx is NO LONGER SUFFICIENT. The endpoint answers HTTP 200 with `{ ok, written,
+ * skipped }` and counts an event it refuses in `skipped`, so this used to resolve `true` for an event
+ * the server had thrown away — and `wire.track` then bumped decision revalidation, making every
+ * subscribed gate re-fetch against a stream the action never entered. It now reads the ack and
+ * resolves `false` when the server reports a positive `skipped`.
+ *
+ * BACKWARD COMPATIBLE BY CONSTRUCTION: only an explicit positive `skipped` demotes a 200. An old
+ * server that sends no such field, a body that cannot be parsed, or a response with no `.json` at all
+ * resolves `true` exactly as before — the change can produce no false negatives.
  */
 declare const reportClientEventsAwait: (target: ClientEventTarget | undefined, events: ClientEvent[]) => Promise<boolean>;
 /** Convenience single-event wrapper around {@link reportClientEventsAwait}. */
@@ -472,6 +481,20 @@ 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;
 };
@@ -638,6 +661,10 @@ type EventQueue = {
     /** Current pending (in-memory) count. */
     size(): number;
 };
+/** Test-only: forget every claimed queue key. A real RELAUNCH is a new process, so a test that
+ *  simulates one in-process must call this or its second queue reads as a concurrent sibling.
+ *  Exported from `@wireai/activation/analytics`, matching `resetAutoDeviceKeys` / `resetCurrentSessionId`. */
+declare const resetEventQueueKeys: () => void;
 /**
  * Create an offline-first event queue. Loads any persisted backlog on creation so a
  * killed-and-relaunched app resumes where it left off. Returns the {@link EventQueue} surface.
@@ -705,8 +732,6 @@ interface ResolvedUserContext {
     /** The `user_context` bucket (device_key, app_version, user_email[+ _hashed], custom.*). */
     userContext?: Record<string, string | number | boolean>;
 }
-/** Reserved `user_context` keys the kit itself writes; host `extra` is namespaced away from these. */
-declare const RESERVED_USER_CONTEXT_KEYS: readonly ["device_key", "app_version", "app_build", "network_type", "session_count", "returning", "platform", "user_email", "user_email_hashed"];
 /** The prefix applied to every host `extra` key so it can never collide with a reserved key. */
 declare const EXTRA_KEY_PREFIX: "custom.";
 /** A finite scalar the wire accepts. Non-finite numbers (NaN/Infinity) are NOT scalars here. */
@@ -831,17 +856,127 @@ type IdentifyOnboardingOptions = {
     appId?: string;
     /** Storage key override — pass the same `persistKey` you gave `<WireOnboarding>`, if any. */
     persistKey?: string;
+    /**
+     * OPT-IN LAST RESORT, default `false`. When no ONBOARDING session can be resolved (no `contextId`,
+     * nothing in `storage`), bind the user to the LIVE PER-OPEN app session instead and return
+     * `"app_session"`.
+     *
+     * ⚠️ These are two different id spaces sharing one wire field. An onboarding session id is the A2A
+     * `contextId`; a per-open id is what `app.session_started` registers. The server's onboarding funnel
+     * groups by `session_id`, so a per-open id posted here does not attach the user to their onboarding
+     * — it writes a row nothing in that funnel can join. Until 0.13.0 this happened SILENTLY and
+     * returned `true`, in exactly the documented post-completion case (completion clears the persisted
+     * session), so the funnel stayed unattributed while the host was told it had worked.
+     *
+     * Turn it on only if binding the id to *some* session the server saw is genuinely worth more to you
+     * than knowing the onboarding bind failed — and read the return value, which now says which it was.
+     */
+    allowAppSessionFallback?: boolean;
 };
+/**
+ * What {@link identifyOnboarding} bound, and to WHICH id space — because `true` could not say.
+ *
+ *   • `"onboarding"`  — bound to the A2A `contextId`. This is the one that attributes the funnel.
+ *   • `"app_session"` — bound to the live per-open app session, via `allowAppSessionFallback`. The
+ *                       server saw that session, but it is not this user's onboarding.
+ *   • `false`         — nothing was dispatched (no user id, no server url, no resolvable session).
+ *
+ * ⚠️ 0.13.0 widened this from `boolean`. `"onboarding"` is truthy, so an `if (await identify…)` still
+ * behaves identically; only an explicit `: boolean` annotation needs updating.
+ */
+type IdentifyOnboardingBinding = "onboarding" | "app_session" | false;
 /**
  * Attach a host user id to an onboarding session AFTER the fact (post-registration), by sending
  * an `identify` client event to `/v1/events`. Resolves the contextId from an explicit
  * `contextId` or, failing that, from the persisted session in the host `storage`.
  *
- * Fire-and-forget under the hood (never throws, never blocks onboarding). Resolves to `true`
- * when an identify event was dispatched, `false` when it couldn't (no user id, no server url,
- * or no resolvable contextId).
+ * Fire-and-forget under the hood (never throws, never blocks onboarding). Resolves to the
+ * {@link IdentifyOnboardingBinding} that says WHICH id space was bound, or `false` when nothing could
+ * be (no user id, no server url, or no resolvable session).
  */
-declare const identifyOnboarding: (opts: IdentifyOnboardingOptions) => Promise<boolean>;
+declare const identifyOnboarding: (opts: IdentifyOnboardingOptions) => Promise<IdentifyOnboardingBinding>;
+
+/**
+ * identityRecord — the ONE provenance-carrying shape for an id the kit puts on the wire.
+ *
+ * WHY IT EXISTS. `session_id` and `device_key` are bare `string`s minted independently by four
+ * subsystems, and nothing anywhere recorded WHERE a given id came from. Every id-layer defect this
+ * release fixes is a direct consequence of that one omission:
+ *
+ *   • a rejecting storage adapter's in-memory id was indistinguishable from a persisted one, so the
+ *     kit injected a fresh per-launch join key on every launch — nothing carried `durable`.
+ *   • an app-OPEN session id could be posted into a field that means the ONBOARDING session, and the
+ *     caller was told `true` — nothing carried `space`.
+ *   • an auto-minted `wdev_*` could be injected beside a device id the host demonstrably owns on
+ *     another surface, silently — nothing carried `source`.
+ *
+ * WHAT THIS IS, AND WHAT IT DELIBERATELY IS NOT. It is a small record plus a process-wide registry of
+ * the ids a HOST supplied. It is NOT a branded-type refactor (`OnboardingSessionId` / `AppSessionId` /
+ * `DeviceKey` across every signature) — that is real value and it is deferred, because it touches
+ * every file and is not what makes a number correct this week. Nothing here changes the wire.
+ *
+ * WHY A `Symbol.for` REGISTRY. Same reason as `analytics/currentSession` and `context/deviceId`: tsup
+ * inlines a separate copy of a module into each bundle (`.` and `./analytics`), so a plain module
+ * `let` would give every bundle its own registry and the cross-surface question this exists to answer
+ * ("did ANY surface in this process get a host-supplied device key?") would read `no` from the wrong
+ * copy. `Symbol.for` resolves to one slot on `globalThis` no matter how many copies exist.
+ */
+/**
+ * Which id space a value belongs to. These are NOT interchangeable, and the whole point of naming
+ * them is that a value from one space must never be posted into a field that means another:
+ *   • `onboarding-session` — the A2A `contextId` for ONE onboarding run.
+ *   • `app-session`        — the per-app-open session id (`app.session_started`).
+ *   • `device`             — the per-install `device_key`; the only cross-family join key.
+ */
+type IdentitySpace = "onboarding-session" | "app-session" | "device";
+/** Where the value came from: the host handed it over, or the kit minted it. */
+type IdentitySource = "host" | "auto";
+/** An id plus everything a consumer needs to decide whether it may use it. */
+type IdentityRecord = {
+    /** The id itself, trimmed. Never empty (a blank input yields no record at all). */
+    value: string;
+    /** Which id space {@link value} belongs to. */
+    space: IdentitySpace;
+    /** `host` = the integrator supplied it; `auto` = the kit minted it. */
+    source: IdentitySource;
+    /**
+     * Whether the value was actually PERSISTED (or adopted from persistence), as opposed to living
+     * only in this process's memory. A non-durable auto id is a DIFFERENT id on the next launch, which
+     * for a `device` value is worse than no value at all: the server counts `min_sessions` by distinct
+     * opens grouped on `device_key`, so a per-launch key corrupts the counter rather than leaving it
+     * empty. A host-supplied value is durable by definition — the host owns its lifetime.
+     */
+    durable: boolean;
+};
+/** Input to {@link resolveIdentity}. `value` is `unknown` so callers can pass a raw prop through. */
+type ResolveIdentityInput = {
+    value: unknown;
+    space: IdentitySpace;
+    source: IdentitySource;
+    /** Defaults to `true` for a host value (the host owns its lifetime) and `false` otherwise. */
+    durable?: boolean;
+    /** Tenant/app id — two tenants in one process never share a provenance entry. */
+    scope?: string;
+};
+/**
+ * Build an {@link IdentityRecord} from a candidate value, or `undefined` when there is nothing usable
+ * (a non-string, or blank after trimming) — so a caller can `if (record)`-gate instead of guessing
+ * whether an empty string means "none" or "not yet".
+ *
+ * SIDE EFFECT, deliberate and the reason this is a function and not an object literal: a `host`-sourced
+ * record is RECORDED on the process registry, so a later surface can ask {@link hostIdentity} whether
+ * this process demonstrably owns a host id in that space. That is what turns "the kit injected its own
+ * key" from a silent third id space into a warnable condition. Never throws.
+ */
+declare const resolveIdentity: (input: ResolveIdentityInput) => IdentityRecord | undefined;
+/**
+ * The HOST-supplied id this process has seen for a space, or `undefined` when every surface so far
+ * let the kit mint its own. Answers the cross-surface question no single mount can answer alone:
+ * "does this app own a device id that this particular mount was not given?"
+ */
+declare const hostIdentity: (space: IdentitySpace, scope?: string) => string | undefined;
+/** Test-only: forget every recorded host identity so a unit test starts from a clean registry. */
+declare const resetIdentityProvenance: () => void;
 
 /**
  * deviceId — mint a stable, NON-PII, per-install device id the kit owns when the host supplies
@@ -862,6 +997,7 @@ declare const identifyOnboarding: (opts: IdentifyOnboardingOptions) => Promise<b
  * A host that wants its OWN device id still wins: pass `WireUserContext.deviceKey` and the kit uses
  * that verbatim and never mints/persists an auto id.
  */
+
 /** Prefix so an auto-minted id is visibly the kit's (distinguishable from a host-supplied `deviceKey`). */
 declare const AUTO_DEVICE_ID_PREFIX = "wdev_";
 /** The storage key the façade persists the auto-minted id under (namespaced per `appId`). */
@@ -917,6 +1053,22 @@ declare const resolveAutoDeviceKey: (opts?: ResolveAutoDeviceKeyOptions) => stri
  * with no `storage` it resolves immediately (there is nothing to hydrate from).
  */
 declare const hydrateAutoDeviceKey: (opts?: ResolveAutoDeviceKeyOptions) => Promise<string>;
+/**
+ * The PROVENANCE-CARRYING sibling of {@link hydrateAutoDeviceKey}: the same awaited read, but it
+ * answers "is this id one this install will KEEP?" instead of only "what is the id?".
+ *
+ * WHY IT EXISTS (K1). `<WireOnboarding>` gated auto-injection on `Boolean(storage)` — the presence of
+ * the prop — because a string carries no provenance and there was nothing better to gate on. A
+ * REJECTING adapter therefore injected a fresh `wdev_*` on every launch: strictly worse than
+ * injecting nothing, since the server counts `min_sessions` by distinct opens grouped on `device_key`,
+ * so a per-launch key corrupts that counter AND inflates distinct-device counts. Callers that write a
+ * key onto the wire as a cross-launch join must read `durable` and refuse a `false`.
+ *
+ * Resolves `undefined` only when there is no usable id at all. With no `storage` it resolves
+ * immediately with `durable: false` — a process-scoped id is exactly what "no persistence" means.
+ * Never throws or rejects.
+ */
+declare const hydrateDeviceIdentity: (opts?: ResolveAutoDeviceKeyOptions) => Promise<IdentityRecord | undefined>;
 /** Test-only: forget every auto id + hydration flag so a unit test starts from a clean registry. */
 declare const resetAutoDeviceKeys: () => void;
 
@@ -948,4 +1100,4 @@ declare const resetCurrentSessionId: () => void;
  */
 declare const ensureCurrentSessionId: () => string;
 
-export { hydrateAutoDeviceKey as $, AUTO_DEVICE_ID_PREFIX as A, resolveAutoDeviceKey as B, type ClearUserContextOptions as C, type DeviceKeyStorage as D, type EventQueueOptions as E, setCurrentSessionId as F, toAnalyticsEvent as G, type WireOnboardingProps as H, type WireOnboardingConfig as I, type OnboardingEvent as J, type OnboardingCopy as K, type DeviceContext as L, type DeviceFormFactor as M, EXTRA_KEY_PREFIX as N, type OnboardingResult as O, type IdentifyOnboardingOptions as P, type OnboardingProgress as Q, type ResolveAutoDeviceKeyOptions as R, type StepValidator as S, RESERVED_USER_CONTEXT_KEYS as T, type ResolveUserContextOptions as U, type ResolvedUserContext as V, type WireUserContext as W, USER_ID_MAX_LENGTH as X, activationJoinContext as Y, collectDeviceContext as Z, hashEmailFnv1a as _, type AnalyticsEvent as a, identifyOnboarding as a0, isWireScalar as a1, mintDeviceId as a2, namespaceExtra as a3, resolveUserContext as a4, sanitizeUserId as a5, type ClientEvent as b, type ClientEventTarget as c, type ClientEventType as d, type ContextEnvelope as e, type ContextEnvelopeInput as f, type EnvelopeSource as g, type EventQueue as h, WIRE_ONBOARDING_EVENTS as i, type WireOnboardingEventName as j, analyticsUserIdStorageKey as k, buildContextEnvelope as l, clearPiiFromContext as m, clearUserContext as n, createEventQueue as o, deviceIdStorageKey as p, ensureCurrentSessionId as q, getCurrentSessionId as r, looksLikeEmail as s, makeSessionId as t, reportClientEvent as u, reportClientEventAwait as v, reportClientEvents as w, reportClientEventsAwait as x, resetAutoDeviceKeys as y, resetCurrentSessionId as z };
+export { USER_ID_MAX_LENGTH as $, AUTO_DEVICE_ID_PREFIX as A, resetEventQueueKeys as B, type ClearUserContextOptions as C, type DeviceKeyStorage as D, type EventQueueOptions as E, resolveAutoDeviceKey as F, setCurrentSessionId as G, toAnalyticsEvent as H, type WireOnboardingProps as I, type WireOnboardingConfig as J, type OnboardingEvent as K, type OnboardingCopy as L, type DeviceContext as M, type DeviceFormFactor as N, type OnboardingResult as O, EXTRA_KEY_PREFIX as P, type IdentifyOnboardingBinding as Q, type ResolveAutoDeviceKeyOptions as R, type StepValidator as S, type IdentifyOnboardingOptions as T, type IdentityRecord as U, type IdentitySource as V, type WireUserContext as W, type IdentitySpace as X, type OnboardingProgress as Y, type ResolveUserContextOptions as Z, type ResolvedUserContext as _, type AnalyticsEvent as a, activationJoinContext as a0, collectDeviceContext as a1, hashEmailFnv1a as a2, hostIdentity as a3, hydrateAutoDeviceKey as a4, hydrateDeviceIdentity as a5, identifyOnboarding as a6, isWireScalar as a7, mintDeviceId as a8, namespaceExtra as a9, resetIdentityProvenance as aa, resolveIdentity as ab, resolveUserContext as ac, sanitizeUserId as ad, type ClientEvent as b, type ClientEventTarget as c, type ClientEventType as d, type ContextEnvelope as e, type ContextEnvelopeInput as f, type EnvelopeSource as g, type EventQueue as h, WIRE_ONBOARDING_EVENTS as i, type WireOnboardingEventName as j, analyticsUserIdStorageKey as k, buildContextEnvelope as l, clearPiiFromContext as m, clearUserContext as n, createEventQueue as o, deviceIdStorageKey as p, ensureCurrentSessionId as q, getCurrentSessionId as r, looksLikeEmail as s, makeSessionId as t, reportClientEvent as u, reportClientEventAwait as v, reportClientEvents as w, reportClientEventsAwait as x, resetAutoDeviceKeys as y, resetCurrentSessionId as z };

package/dist/index.d.mts

@@ -1,7 +1,7 @@
 import * as React from 'react';
 import React__default, { ReactNode } from 'react';
-import { H as WireOnboardingProps, I as WireOnboardingConfig, O as OnboardingResult, S as StepValidator, J as OnboardingEvent, K as OnboardingCopy, c as ClientEventTarget, L as DeviceContext, W as WireUserContext, b as ClientEvent, g as EnvelopeSource } from './currentSession-BlCeDP0f.mjs';
-export { A as AUTO_DEVICE_ID_PREFIX, a as AnalyticsEvent, C as ClearUserContextOptions, d as ClientEventType, M as DeviceFormFactor, D as DeviceKeyStorage, N as EXTRA_KEY_PREFIX, P as IdentifyOnboardingOptions, Q as OnboardingProgress, T as RESERVED_USER_CONTEXT_KEYS, R as ResolveAutoDeviceKeyOptions, U as ResolveUserContextOptions, V as ResolvedUserContext, X as USER_ID_MAX_LENGTH, i as WIRE_ONBOARDING_EVENTS, j as WireOnboardingEventName, Y as activationJoinContext, k as analyticsUserIdStorageKey, m as clearPiiFromContext, n as clearUserContext, Z as collectDeviceContext, p as deviceIdStorageKey, q as ensureCurrentSessionId, r as getCurrentSessionId, _ as hashEmailFnv1a, $ as hydrateAutoDeviceKey, a0 as identifyOnboarding, a1 as isWireScalar, s as looksLikeEmail, t as makeSessionId, a2 as mintDeviceId, a3 as namespaceExtra, u as reportClientEvent, v as reportClientEventAwait, w as reportClientEvents, x as reportClientEventsAwait, y as resetAutoDeviceKeys, z as resetCurrentSessionId, B as resolveAutoDeviceKey, a4 as resolveUserContext, a5 as sanitizeUserId, F as setCurrentSessionId, G as toAnalyticsEvent } from './currentSession-BlCeDP0f.mjs';
+import { I as WireOnboardingProps, J as WireOnboardingConfig, O as OnboardingResult, S as StepValidator, K as OnboardingEvent, L as OnboardingCopy, c as ClientEventTarget, M as DeviceContext, W as WireUserContext, b as ClientEvent, g as EnvelopeSource } from './currentSession-_GynvhzT.mjs';
+export { A as AUTO_DEVICE_ID_PREFIX, a as AnalyticsEvent, C as ClearUserContextOptions, d as ClientEventType, N as DeviceFormFactor, D as DeviceKeyStorage, P as EXTRA_KEY_PREFIX, Q as IdentifyOnboardingBinding, T as IdentifyOnboardingOptions, U as IdentityRecord, V as IdentitySource, X as IdentitySpace, Y as OnboardingProgress, R as ResolveAutoDeviceKeyOptions, Z as ResolveUserContextOptions, _ as ResolvedUserContext, $ as USER_ID_MAX_LENGTH, i as WIRE_ONBOARDING_EVENTS, j as WireOnboardingEventName, a0 as activationJoinContext, k as analyticsUserIdStorageKey, m as clearPiiFromContext, n as clearUserContext, a1 as collectDeviceContext, p as deviceIdStorageKey, q as ensureCurrentSessionId, r as getCurrentSessionId, a2 as hashEmailFnv1a, a3 as hostIdentity, a4 as hydrateAutoDeviceKey, a5 as hydrateDeviceIdentity, a6 as identifyOnboarding, a7 as isWireScalar, s as looksLikeEmail, t as makeSessionId, a8 as mintDeviceId, a9 as namespaceExtra, u as reportClientEvent, v as reportClientEventAwait, w as reportClientEvents, x as reportClientEventsAwait, y as resetAutoDeviceKeys, z as resetCurrentSessionId, aa as resetIdentityProvenance, F as resolveAutoDeviceKey, ab as resolveIdentity, ac as resolveUserContext, ad as sanitizeUserId, G as setCurrentSessionId, H as toAnalyticsEvent } from './currentSession-_GynvhzT.mjs';
 import { O as OnboardingTheme } from './types-BKfpdZzX.mjs';
 export { a as OnboardingButtonStyle, b as OnboardingColors, c as OnboardingFonts, d as OnboardingRadius, e as OnboardingSpacing } from './types-BKfpdZzX.mjs';
 export { C as CenteredModal, a as CenteredModalHandle, b as CenteredModalProps } from './CenteredModal-C3qQBHsA.mjs';
@@ -231,18 +231,6 @@ type ErrorBlockProps = {
 };
 declare const ErrorBlock: React__default.NamedExoticComponent<ErrorBlockProps>;
 
-/**
- * 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).
- */
-
-type DoneBlockProps = {
-    title?: string;
-    message?: string;
-};
-declare const DoneBlock: React__default.NamedExoticComponent<DoneBlockProps>;
-
 /**
  * CompletionView — the terminal "you're all set" screen, shown when the flow
  * reaches its final StatusCard. It surfaces the backend's recap (what the app
@@ -1163,6 +1151,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;
 };
 declare const readProgress: (response?: WireAIResponse) => PartialProgress;
@@ -1996,4 +1986,4 @@ interface UseLifecycleEventsOptions {
  */
 declare const useLifecycleEvents: (config: LifecycleConfig | undefined, options?: UseLifecycleEventsOptions) => void;
 
-export { AnimatedSparkle, BACKGROUND_SESSION_MS, type CachedFeatures, CardGridSelectCard, CardHandoff, type CardHandoffProps, type CardHandoffVariant, type CardOption, ChipSelectCard, ClientEvent, ClientEventTarget, CompletionView, DEFAULT_FEATURES_TTL_MS, DemoOnboarding, type DemoOnboardingProps, DeviceContext, DoneBlock, ErrorBlock, FIRST_OPEN_EVENT, IconRegistryProvider, IllustrationProvider, type IllustrationRegistry, InterstitialCard, type LifecycleConfig, type LifecycleEventInput, LoadingBlock, LoadingScreen, NumberStepperCard, type OnboardingAttribution, Button as OnboardingButton, OnboardingCopy, OnboardingEvent, type OnboardingFlagOptions, OnboardingFlow, OnboardingResult, OnboardingScaffold, OnboardingTheme, OnboardingThemeProvider, PLAN_TIER_CONTEXT_KEY, type PlanTier, type PurchaseProps, type ReportFirstOpenOptions, type ReportSessionStartOptions, type ResolveFeaturesOptions, type RevenueCatBridge, type RevenueCatBridgeConfig, type RevenueCatCustomerInfoLike, type RevenueCatEntitlementLike, type RevenueCatErrorLike, type RevenueCatOfferingLike, type RevenueCatPackageLike, type RevenueCatProductLike, type RevenueCatSink, SESSION_STARTED_EVENT, SelectionCard, type SessionStartConfig, StatusCard, StepProgress, StepValidator, TextInputCard, type ThemeFromBrandInput, type UseLifecycleEventsOptions, type UseSessionStartOptions, type UseWireActivation, WIRE_ENV_VARS, WIRE_ICON_GLYPHS, WIRE_ICON_NAMES, WIRE_PURCHASE_EVENTS, type WireActivation, type WireActivationConfig, type WireConfigOverrides, WireFeatures, WireFeaturesConfig, WireFeaturesProvider, type WireFeaturesProviderProps, WireIcon, type WireIconFamily, type WireIconGlyph, type WireIconName, type WireIconProps, type WireIconRegistry, type WireLifecycleOptions, WireOnboarding, WireOnboardingConfig, WireOnboardingProps, WireOnboardingStorage, type WirePurchaseEventName, WireUserContext, activeEntitlement, attributionMetadata, bumpActivationRevalidation, createRevenueCatBridge, createWireActivation, defaultIllustrations, defaultOnboardingTheme, defaultWireFeatures, deriveAnswers, describeEntitlement, describeFailure, describePackage, detectAppVersion, detectNativeModel, featuresCacheKey, featuresEqual, fetchWireFeatures, firstOpenStorageKey, getActivationRevalidationVersion, isFeaturesFresh, isOnboardingEnabled, isUserCancelled, lookupIconGlyph, mergeTheme, motionSpec, onboardingComponents, parseWireFeatures, readCachedFeatures, readProgress, reportFirstOpen, reportSessionStart, resetActivationRevalidation, resetFirstOpenLatch, resetSessionStartGuard, resolvePlanTier, subscribeActivationRevalidation, themeFromBrand, useActivationRevalidation, useHostIcon, useIllustration, useLifecycleEvents, useOnboardingTheme, useReducedMotion, useResolvedFeatures, useSessionStart, useWireActivation, useWireFeatures, useWireFeaturesContext, wireConfigFromEnv, wireLifecycleEvents, writeCachedFeatures };
+export { AnimatedSparkle, BACKGROUND_SESSION_MS, type CachedFeatures, CardGridSelectCard, CardHandoff, type CardHandoffProps, type CardHandoffVariant, type CardOption, ChipSelectCard, ClientEvent, ClientEventTarget, CompletionView, DEFAULT_FEATURES_TTL_MS, DemoOnboarding, type DemoOnboardingProps, DeviceContext, ErrorBlock, FIRST_OPEN_EVENT, IconRegistryProvider, IllustrationProvider, type IllustrationRegistry, InterstitialCard, type LifecycleConfig, type LifecycleEventInput, LoadingBlock, LoadingScreen, NumberStepperCard, type OnboardingAttribution, Button as OnboardingButton, OnboardingCopy, OnboardingEvent, type OnboardingFlagOptions, OnboardingFlow, OnboardingResult, OnboardingScaffold, OnboardingTheme, OnboardingThemeProvider, PLAN_TIER_CONTEXT_KEY, type PlanTier, type PurchaseProps, type ReportFirstOpenOptions, type ReportSessionStartOptions, type ResolveFeaturesOptions, type RevenueCatBridge, type RevenueCatBridgeConfig, type RevenueCatCustomerInfoLike, type RevenueCatEntitlementLike, type RevenueCatErrorLike, type RevenueCatOfferingLike, type RevenueCatPackageLike, type RevenueCatProductLike, type RevenueCatSink, SESSION_STARTED_EVENT, SelectionCard, type SessionStartConfig, StatusCard, StepProgress, StepValidator, TextInputCard, type ThemeFromBrandInput, type UseLifecycleEventsOptions, type UseSessionStartOptions, type UseWireActivation, WIRE_ENV_VARS, WIRE_ICON_GLYPHS, WIRE_ICON_NAMES, WIRE_PURCHASE_EVENTS, type WireActivation, type WireActivationConfig, type WireConfigOverrides, WireFeatures, WireFeaturesConfig, WireFeaturesProvider, type WireFeaturesProviderProps, WireIcon, type WireIconFamily, type WireIconGlyph, type WireIconName, type WireIconProps, type WireIconRegistry, type WireLifecycleOptions, WireOnboarding, WireOnboardingConfig, WireOnboardingProps, WireOnboardingStorage, type WirePurchaseEventName, WireUserContext, activeEntitlement, attributionMetadata, bumpActivationRevalidation, createRevenueCatBridge, createWireActivation, defaultIllustrations, defaultOnboardingTheme, defaultWireFeatures, deriveAnswers, describeEntitlement, describeFailure, describePackage, detectAppVersion, detectNativeModel, featuresCacheKey, featuresEqual, fetchWireFeatures, firstOpenStorageKey, getActivationRevalidationVersion, isFeaturesFresh, isOnboardingEnabled, isUserCancelled, lookupIconGlyph, mergeTheme, motionSpec, onboardingComponents, parseWireFeatures, readCachedFeatures, readProgress, reportFirstOpen, reportSessionStart, resetActivationRevalidation, resetFirstOpenLatch, resetSessionStartGuard, resolvePlanTier, subscribeActivationRevalidation, themeFromBrand, useActivationRevalidation, useHostIcon, useIllustration, useLifecycleEvents, useOnboardingTheme, useReducedMotion, useResolvedFeatures, useSessionStart, useWireActivation, useWireFeatures, useWireFeaturesContext, wireConfigFromEnv, wireLifecycleEvents, writeCachedFeatures };

package/dist/index.d.ts

@@ -1,7 +1,7 @@
 import * as React from 'react';
 import React__default, { ReactNode } from 'react';
-import { H as WireOnboardingProps, I as WireOnboardingConfig, O as OnboardingResult, S as StepValidator, J as OnboardingEvent, K as OnboardingCopy, c as ClientEventTarget, L as DeviceContext, W as WireUserContext, b as ClientEvent, g as EnvelopeSource } from './currentSession-BxEB37xt.js';
-export { A as AUTO_DEVICE_ID_PREFIX, a as AnalyticsEvent, C as ClearUserContextOptions, d as ClientEventType, M as DeviceFormFactor, D as DeviceKeyStorage, N as EXTRA_KEY_PREFIX, P as IdentifyOnboardingOptions, Q as OnboardingProgress, T as RESERVED_USER_CONTEXT_KEYS, R as ResolveAutoDeviceKeyOptions, U as ResolveUserContextOptions, V as ResolvedUserContext, X as USER_ID_MAX_LENGTH, i as WIRE_ONBOARDING_EVENTS, j as WireOnboardingEventName, Y as activationJoinContext, k as analyticsUserIdStorageKey, m as clearPiiFromContext, n as clearUserContext, Z as collectDeviceContext, p as deviceIdStorageKey, q as ensureCurrentSessionId, r as getCurrentSessionId, _ as hashEmailFnv1a, $ as hydrateAutoDeviceKey, a0 as identifyOnboarding, a1 as isWireScalar, s as looksLikeEmail, t as makeSessionId, a2 as mintDeviceId, a3 as namespaceExtra, u as reportClientEvent, v as reportClientEventAwait, w as reportClientEvents, x as reportClientEventsAwait, y as resetAutoDeviceKeys, z as resetCurrentSessionId, B as resolveAutoDeviceKey, a4 as resolveUserContext, a5 as sanitizeUserId, F as setCurrentSessionId, G as toAnalyticsEvent } from './currentSession-BxEB37xt.js';
+import { I as WireOnboardingProps, J as WireOnboardingConfig, O as OnboardingResult, S as StepValidator, K as OnboardingEvent, L as OnboardingCopy, c as ClientEventTarget, M as DeviceContext, W as WireUserContext, b as ClientEvent, g as EnvelopeSource } from './currentSession-D7zabMXK.js';
+export { A as AUTO_DEVICE_ID_PREFIX, a as AnalyticsEvent, C as ClearUserContextOptions, d as ClientEventType, N as DeviceFormFactor, D as DeviceKeyStorage, P as EXTRA_KEY_PREFIX, Q as IdentifyOnboardingBinding, T as IdentifyOnboardingOptions, U as IdentityRecord, V as IdentitySource, X as IdentitySpace, Y as OnboardingProgress, R as ResolveAutoDeviceKeyOptions, Z as ResolveUserContextOptions, _ as ResolvedUserContext, $ as USER_ID_MAX_LENGTH, i as WIRE_ONBOARDING_EVENTS, j as WireOnboardingEventName, a0 as activationJoinContext, k as analyticsUserIdStorageKey, m as clearPiiFromContext, n as clearUserContext, a1 as collectDeviceContext, p as deviceIdStorageKey, q as ensureCurrentSessionId, r as getCurrentSessionId, a2 as hashEmailFnv1a, a3 as hostIdentity, a4 as hydrateAutoDeviceKey, a5 as hydrateDeviceIdentity, a6 as identifyOnboarding, a7 as isWireScalar, s as looksLikeEmail, t as makeSessionId, a8 as mintDeviceId, a9 as namespaceExtra, u as reportClientEvent, v as reportClientEventAwait, w as reportClientEvents, x as reportClientEventsAwait, y as resetAutoDeviceKeys, z as resetCurrentSessionId, aa as resetIdentityProvenance, F as resolveAutoDeviceKey, ab as resolveIdentity, ac as resolveUserContext, ad as sanitizeUserId, G as setCurrentSessionId, H as toAnalyticsEvent } from './currentSession-D7zabMXK.js';
 import { O as OnboardingTheme } from './types-BKfpdZzX.js';
 export { a as OnboardingButtonStyle, b as OnboardingColors, c as OnboardingFonts, d as OnboardingRadius, e as OnboardingSpacing } from './types-BKfpdZzX.js';
 export { C as CenteredModal, a as CenteredModalHandle, b as CenteredModalProps } from './CenteredModal-Cdgns6--.js';
@@ -231,18 +231,6 @@ type ErrorBlockProps = {
 };
 declare const ErrorBlock: React__default.NamedExoticComponent<ErrorBlockProps>;
 
-/**
- * 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).
- */
-
-type DoneBlockProps = {
-    title?: string;
-    message?: string;
-};
-declare const DoneBlock: React__default.NamedExoticComponent<DoneBlockProps>;
-
 /**
  * CompletionView — the terminal "you're all set" screen, shown when the flow
  * reaches its final StatusCard. It surfaces the backend's recap (what the app
@@ -1163,6 +1151,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;
 };
 declare const readProgress: (response?: WireAIResponse) => PartialProgress;
@@ -1996,4 +1986,4 @@ interface UseLifecycleEventsOptions {
  */
 declare const useLifecycleEvents: (config: LifecycleConfig | undefined, options?: UseLifecycleEventsOptions) => void;
 
-export { AnimatedSparkle, BACKGROUND_SESSION_MS, type CachedFeatures, CardGridSelectCard, CardHandoff, type CardHandoffProps, type CardHandoffVariant, type CardOption, ChipSelectCard, ClientEvent, ClientEventTarget, CompletionView, DEFAULT_FEATURES_TTL_MS, DemoOnboarding, type DemoOnboardingProps, DeviceContext, DoneBlock, ErrorBlock, FIRST_OPEN_EVENT, IconRegistryProvider, IllustrationProvider, type IllustrationRegistry, InterstitialCard, type LifecycleConfig, type LifecycleEventInput, LoadingBlock, LoadingScreen, NumberStepperCard, type OnboardingAttribution, Button as OnboardingButton, OnboardingCopy, OnboardingEvent, type OnboardingFlagOptions, OnboardingFlow, OnboardingResult, OnboardingScaffold, OnboardingTheme, OnboardingThemeProvider, PLAN_TIER_CONTEXT_KEY, type PlanTier, type PurchaseProps, type ReportFirstOpenOptions, type ReportSessionStartOptions, type ResolveFeaturesOptions, type RevenueCatBridge, type RevenueCatBridgeConfig, type RevenueCatCustomerInfoLike, type RevenueCatEntitlementLike, type RevenueCatErrorLike, type RevenueCatOfferingLike, type RevenueCatPackageLike, type RevenueCatProductLike, type RevenueCatSink, SESSION_STARTED_EVENT, SelectionCard, type SessionStartConfig, StatusCard, StepProgress, StepValidator, TextInputCard, type ThemeFromBrandInput, type UseLifecycleEventsOptions, type UseSessionStartOptions, type UseWireActivation, WIRE_ENV_VARS, WIRE_ICON_GLYPHS, WIRE_ICON_NAMES, WIRE_PURCHASE_EVENTS, type WireActivation, type WireActivationConfig, type WireConfigOverrides, WireFeatures, WireFeaturesConfig, WireFeaturesProvider, type WireFeaturesProviderProps, WireIcon, type WireIconFamily, type WireIconGlyph, type WireIconName, type WireIconProps, type WireIconRegistry, type WireLifecycleOptions, WireOnboarding, WireOnboardingConfig, WireOnboardingProps, WireOnboardingStorage, type WirePurchaseEventName, WireUserContext, activeEntitlement, attributionMetadata, bumpActivationRevalidation, createRevenueCatBridge, createWireActivation, defaultIllustrations, defaultOnboardingTheme, defaultWireFeatures, deriveAnswers, describeEntitlement, describeFailure, describePackage, detectAppVersion, detectNativeModel, featuresCacheKey, featuresEqual, fetchWireFeatures, firstOpenStorageKey, getActivationRevalidationVersion, isFeaturesFresh, isOnboardingEnabled, isUserCancelled, lookupIconGlyph, mergeTheme, motionSpec, onboardingComponents, parseWireFeatures, readCachedFeatures, readProgress, reportFirstOpen, reportSessionStart, resetActivationRevalidation, resetFirstOpenLatch, resetSessionStartGuard, resolvePlanTier, subscribeActivationRevalidation, themeFromBrand, useActivationRevalidation, useHostIcon, useIllustration, useLifecycleEvents, useOnboardingTheme, useReducedMotion, useResolvedFeatures, useSessionStart, useWireActivation, useWireFeatures, useWireFeaturesContext, wireConfigFromEnv, wireLifecycleEvents, writeCachedFeatures };
+export { AnimatedSparkle, BACKGROUND_SESSION_MS, type CachedFeatures, CardGridSelectCard, CardHandoff, type CardHandoffProps, type CardHandoffVariant, type CardOption, ChipSelectCard, ClientEvent, ClientEventTarget, CompletionView, DEFAULT_FEATURES_TTL_MS, DemoOnboarding, type DemoOnboardingProps, DeviceContext, ErrorBlock, FIRST_OPEN_EVENT, IconRegistryProvider, IllustrationProvider, type IllustrationRegistry, InterstitialCard, type LifecycleConfig, type LifecycleEventInput, LoadingBlock, LoadingScreen, NumberStepperCard, type OnboardingAttribution, Button as OnboardingButton, OnboardingCopy, OnboardingEvent, type OnboardingFlagOptions, OnboardingFlow, OnboardingResult, OnboardingScaffold, OnboardingTheme, OnboardingThemeProvider, PLAN_TIER_CONTEXT_KEY, type PlanTier, type PurchaseProps, type ReportFirstOpenOptions, type ReportSessionStartOptions, type ResolveFeaturesOptions, type RevenueCatBridge, type RevenueCatBridgeConfig, type RevenueCatCustomerInfoLike, type RevenueCatEntitlementLike, type RevenueCatErrorLike, type RevenueCatOfferingLike, type RevenueCatPackageLike, type RevenueCatProductLike, type RevenueCatSink, SESSION_STARTED_EVENT, SelectionCard, type SessionStartConfig, StatusCard, StepProgress, StepValidator, TextInputCard, type ThemeFromBrandInput, type UseLifecycleEventsOptions, type UseSessionStartOptions, type UseWireActivation, WIRE_ENV_VARS, WIRE_ICON_GLYPHS, WIRE_ICON_NAMES, WIRE_PURCHASE_EVENTS, type WireActivation, type WireActivationConfig, type WireConfigOverrides, WireFeatures, WireFeaturesConfig, WireFeaturesProvider, type WireFeaturesProviderProps, WireIcon, type WireIconFamily, type WireIconGlyph, type WireIconName, type WireIconProps, type WireIconRegistry, type WireLifecycleOptions, WireOnboarding, WireOnboardingConfig, WireOnboardingProps, WireOnboardingStorage, type WirePurchaseEventName, WireUserContext, activeEntitlement, attributionMetadata, bumpActivationRevalidation, createRevenueCatBridge, createWireActivation, defaultIllustrations, defaultOnboardingTheme, defaultWireFeatures, deriveAnswers, describeEntitlement, describeFailure, describePackage, detectAppVersion, detectNativeModel, featuresCacheKey, featuresEqual, fetchWireFeatures, firstOpenStorageKey, getActivationRevalidationVersion, isFeaturesFresh, isOnboardingEnabled, isUserCancelled, lookupIconGlyph, mergeTheme, motionSpec, onboardingComponents, parseWireFeatures, readCachedFeatures, readProgress, reportFirstOpen, reportSessionStart, resetActivationRevalidation, resetFirstOpenLatch, resetSessionStartGuard, resolvePlanTier, subscribeActivationRevalidation, themeFromBrand, useActivationRevalidation, useHostIcon, useIllustration, useLifecycleEvents, useOnboardingTheme, useReducedMotion, useResolvedFeatures, useSessionStart, useWireActivation, useWireFeatures, useWireFeaturesContext, wireConfigFromEnv, wireLifecycleEvents, writeCachedFeatures };