@wireai/activation 0.14.3 → 0.16.0

package/dist/{currentSession-CUvTOchb.d.mts → currentSession-Bz7G6lno.d.mts}

@@ -81,33 +81,6 @@ type DeviceContext = {
  */
 declare const collectDeviceContext: () => DeviceContext;
 
-/**
- * reportClientEvent — forward DEVICE-ONLY onboarding events to the Wire AI analytics
- * backend (`POST {serverUrl}/v1/events`), completing the funnel for events the server
- * can't observe on its own.
- *
- * The backend already records the server-observable funnel during the A2A flow
- * (`session_started`, `screen_shown`, `answer_submitted`, `completed`, `llm_fallback`,
- * and even `screen_skipped` — it derives that from the kit's skip sentinel). The one
- * event no server request can capture is `dropped`: the user closing the app / unmounting
- * the flow without finishing. That's what this reporter is for.
- *
- * Contract (server: routers/onboarding.py → analytics/events.py):
- *   POST {serverUrl}/v1/events
- *   Authorization: Bearer {apiKey}
- *   { "events": [ { event_type, session_id, screen_index?, component?, question_key?,
- *                   latency_ms?, meta?, device?, user_context? } ] }
- * The server fills `app_id` + `environment` from the resolving key (never send app_id),
- * and silently skips malformed events — one bad payload never fails the batch.
- *
- * ⚠️ Correlation: `session_id` MUST equal the A2A `contextId` the server uses to key the
- * server-side events, or the funnel report (which groups by `session_id`) treats this as a
- * phantom session. See `makeSessionId` + WireOnboarding for how the kit seeds it.
- *
- * Fire-and-forget: this never throws into the UI and never awaits — analytics must never
- * be able to break onboarding.
- */
-
 /** Event types a CLIENT may report. The rest of the funnel is server-side; sending those
  *  here would double-count. `screen_skipped` is included for completeness, but the kit does
  *  NOT emit it — the backend already derives it from the skip sentinel (see OnboardingFlow).
@@ -669,10 +642,11 @@ type WireOnboardingProps = {
      * Build the value with the helper so the wire spelling is decided in one place:
      *
      * ```tsx
-     * <WireOnboarding userContext={activationJoinContext(deviceKey)} ... />
-     * // no device id of your own? pass `storage` and leave this prop alone — the kit injects its
-     * // own key, and only after it has confirmed the key actually persists (see `autoJoinKey`).
-     * <WireOnboarding config={{ ...config, storage }} ... />
+     * <WireOnboarding config={config} userContext={activationJoinContext(deviceKey)} ... />
+     * // no device id of your own? pass the `storage` PROP (it is a prop of this component, never a
+     * // field of `WireOnboardingConfig`) and leave this prop alone — the kit injects its own key,
+     * // and only after it has confirmed the key actually persists (see `autoJoinKey`).
+     * <WireOnboarding config={config} storage={storage} ... />
      * ```
      *
      * ⛔ Do NOT hand-build the auto key with `activationJoinContext(resolveAutoDeviceKey({...}))`.
@@ -685,8 +659,11 @@ type WireOnboardingProps = {
      *
      * SINCE 0.12.2, leaving it out no longer silently empties the funnel: when you pass `storage` and
      * this prop carries no `device_key`, the kit injects its OWN per-install key — the same one the
-     * analytics surfaces mint and persist — so the default wiring joins. Anything you DO pass wins
-     * verbatim and is never touched. See `autoJoinKey` for the opt-out and the two cases where the kit
+     * analytics surfaces mint and persist — so the default wiring joins. A `device_key` you DO pass
+     * wins verbatim and is never touched, provided it is a string with at least one non-whitespace
+     * character (`resolveIdentity`) — this map also accepts numbers and booleans, and a non-string or
+     * all-whitespace value is not a usable join key, so it is read as absent and the auto key is
+     * merged over it. See `autoJoinKey` for the opt-out and the two cases where the kit
      * still cannot fill the gap (no `storage`, or you opted out), which keep warning in dev.
      *
      * Never hand-write `userContext={{ deviceKey }}`: the server's device lookup reads `device_key`,
@@ -713,8 +690,11 @@ type WireOnboardingProps = {
      * `autoJoinKey={false}` if you genuinely want an UNLINKED onboarding session; that restores the
      * pre-0.12.2 behavior exactly (nothing injected) and the dev warning fires again.
      *
-     * Two things this flag does NOT do. It never overrides a `device_key` you passed — a host-supplied
-     * key always wins, whatever this is set to. And it cannot conjure a key without `storage`: with no
+     * Two things this flag does NOT do. It never overrides a `device_key` you actually supplied — a
+     * host-supplied key always wins, whatever this is set to, where "supplied" means a string with at
+     * least one non-whitespace character (`resolveIdentity`); a non-string or an all-whitespace value
+     * is read as absent and the auto key is merged over it. And it cannot conjure a key without
+     * `storage`: with no
      * persistence the kit's id is minted fresh every launch, and a per-launch key corrupts
      * `min_sessions` instead of merely leaving the join empty, so the kit declines to inject and warns
      * in dev instead.
@@ -1396,8 +1376,19 @@ declare const resolveAutoDeviceKey: (opts?: ResolveAutoDeviceKeyOptions) => stri
  * follows it. Only a caller that can afford one storage read should use this; the fire-and-forget
  * event paths must stay on the sync function.
  *
- * Never throws or rejects: a missing, hung, or rejecting adapter resolves to the in-memory id, and
- * with no `storage` it resolves immediately (there is nothing to hydrate from).
+ * Never throws or rejects: a missing or rejecting adapter resolves to the in-memory id, and with no
+ * `storage` it resolves immediately (there is nothing to hydrate from).
+ *
+ * ⛔ A HUNG ADAPTER IS THE ONE CASE IT DOES NOT COVER, and this line used to claim it did. The read
+ * underneath is a bare `storage.getItem` with no ceiling of its own, so an adapter that neither
+ * resolves nor rejects (a locked keychain, a wedged native bridge) leaves THIS PROMISE PENDING
+ * FOREVER — it does not fall back to the in-memory id, it simply never answers. Anything that gates
+ * a user-visible or metric-bearing action on the result must therefore race it against a ceiling of
+ * its own: `<WireOnboarding>` does (`AUTO_JOIN_HYDRATION_TIMEOUT_MS`), and so do the two lifecycle
+ * hooks (`session-analytics/useLifecycleEvents` + `useSessionStart`, through the shared
+ * `withTimeout` + `READ_TIMEOUT_MS` in `session/persistedSession`) — a hung read there had silently
+ * killed `app.session_started` and `app.first_open` for the whole process. Use the SYNC
+ * {@link resolveAutoDeviceKey} when you cannot afford to wait at all.
  *
  * ⚠️ IT RETURNS A BARE STRING, so it CANNOT say whether the id survives the launch — a degraded
  * adapter resolves to the in-memory mint and reads identically to a persisted one. No kit surface
@@ -1419,7 +1410,9 @@ declare const hydrateAutoDeviceKey: (opts?: ResolveAutoDeviceKeyOptions) => Prom
  *
  * 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.
+ * Never throws or rejects — but, exactly like {@link hydrateAutoDeviceKey} above, it can also never
+ * SETTLE on a hung adapter (the underlying `getItem` carries no ceiling), so every caller races it
+ * against one of its own. See the note there.
  */
 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. */
@@ -1432,7 +1425,10 @@ declare const resetAutoDeviceKeys: () => void;
 declare const setCurrentSessionId: (id: string | undefined) => void;
 /** The current per-open `session_id`, or `undefined` when no app-open has been registered yet. */
 declare const getCurrentSessionId: () => string | undefined;
-/** Test-only: forget the current session id so a unit test starts from a clean registry. */
+/** Test-only: forget the current session id so a unit test starts from a clean registry. Does NOT
+ *  clear the MINTED-id record (see `isMintedSessionId`), for the same reason the warn latch below is
+ *  not cleared: `makeSessionId()` never repeats, so a remembered fallback id can never again equal a
+ *  live one, and the record is overwritten by the next mint anyway. */
 declare const resetCurrentSessionId: () => void;
 /**
  * The current per-open `session_id`, MINTING and registering one when no app-open has been

package/dist/{currentSession-CW_5Mq4O.d.ts → currentSession-z-CZ55ad.d.ts}

@@ -81,33 +81,6 @@ type DeviceContext = {
  */
 declare const collectDeviceContext: () => DeviceContext;
 
-/**
- * reportClientEvent — forward DEVICE-ONLY onboarding events to the Wire AI analytics
- * backend (`POST {serverUrl}/v1/events`), completing the funnel for events the server
- * can't observe on its own.
- *
- * The backend already records the server-observable funnel during the A2A flow
- * (`session_started`, `screen_shown`, `answer_submitted`, `completed`, `llm_fallback`,
- * and even `screen_skipped` — it derives that from the kit's skip sentinel). The one
- * event no server request can capture is `dropped`: the user closing the app / unmounting
- * the flow without finishing. That's what this reporter is for.
- *
- * Contract (server: routers/onboarding.py → analytics/events.py):
- *   POST {serverUrl}/v1/events
- *   Authorization: Bearer {apiKey}
- *   { "events": [ { event_type, session_id, screen_index?, component?, question_key?,
- *                   latency_ms?, meta?, device?, user_context? } ] }
- * The server fills `app_id` + `environment` from the resolving key (never send app_id),
- * and silently skips malformed events — one bad payload never fails the batch.
- *
- * ⚠️ Correlation: `session_id` MUST equal the A2A `contextId` the server uses to key the
- * server-side events, or the funnel report (which groups by `session_id`) treats this as a
- * phantom session. See `makeSessionId` + WireOnboarding for how the kit seeds it.
- *
- * Fire-and-forget: this never throws into the UI and never awaits — analytics must never
- * be able to break onboarding.
- */
-
 /** Event types a CLIENT may report. The rest of the funnel is server-side; sending those
  *  here would double-count. `screen_skipped` is included for completeness, but the kit does
  *  NOT emit it — the backend already derives it from the skip sentinel (see OnboardingFlow).
@@ -669,10 +642,11 @@ type WireOnboardingProps = {
      * Build the value with the helper so the wire spelling is decided in one place:
      *
      * ```tsx
-     * <WireOnboarding userContext={activationJoinContext(deviceKey)} ... />
-     * // no device id of your own? pass `storage` and leave this prop alone — the kit injects its
-     * // own key, and only after it has confirmed the key actually persists (see `autoJoinKey`).
-     * <WireOnboarding config={{ ...config, storage }} ... />
+     * <WireOnboarding config={config} userContext={activationJoinContext(deviceKey)} ... />
+     * // no device id of your own? pass the `storage` PROP (it is a prop of this component, never a
+     * // field of `WireOnboardingConfig`) and leave this prop alone — the kit injects its own key,
+     * // and only after it has confirmed the key actually persists (see `autoJoinKey`).
+     * <WireOnboarding config={config} storage={storage} ... />
      * ```
      *
      * ⛔ Do NOT hand-build the auto key with `activationJoinContext(resolveAutoDeviceKey({...}))`.
@@ -685,8 +659,11 @@ type WireOnboardingProps = {
      *
      * SINCE 0.12.2, leaving it out no longer silently empties the funnel: when you pass `storage` and
      * this prop carries no `device_key`, the kit injects its OWN per-install key — the same one the
-     * analytics surfaces mint and persist — so the default wiring joins. Anything you DO pass wins
-     * verbatim and is never touched. See `autoJoinKey` for the opt-out and the two cases where the kit
+     * analytics surfaces mint and persist — so the default wiring joins. A `device_key` you DO pass
+     * wins verbatim and is never touched, provided it is a string with at least one non-whitespace
+     * character (`resolveIdentity`) — this map also accepts numbers and booleans, and a non-string or
+     * all-whitespace value is not a usable join key, so it is read as absent and the auto key is
+     * merged over it. See `autoJoinKey` for the opt-out and the two cases where the kit
      * still cannot fill the gap (no `storage`, or you opted out), which keep warning in dev.
      *
      * Never hand-write `userContext={{ deviceKey }}`: the server's device lookup reads `device_key`,
@@ -713,8 +690,11 @@ type WireOnboardingProps = {
      * `autoJoinKey={false}` if you genuinely want an UNLINKED onboarding session; that restores the
      * pre-0.12.2 behavior exactly (nothing injected) and the dev warning fires again.
      *
-     * Two things this flag does NOT do. It never overrides a `device_key` you passed — a host-supplied
-     * key always wins, whatever this is set to. And it cannot conjure a key without `storage`: with no
+     * Two things this flag does NOT do. It never overrides a `device_key` you actually supplied — a
+     * host-supplied key always wins, whatever this is set to, where "supplied" means a string with at
+     * least one non-whitespace character (`resolveIdentity`); a non-string or an all-whitespace value
+     * is read as absent and the auto key is merged over it. And it cannot conjure a key without
+     * `storage`: with no
      * persistence the kit's id is minted fresh every launch, and a per-launch key corrupts
      * `min_sessions` instead of merely leaving the join empty, so the kit declines to inject and warns
      * in dev instead.
@@ -1396,8 +1376,19 @@ declare const resolveAutoDeviceKey: (opts?: ResolveAutoDeviceKeyOptions) => stri
  * follows it. Only a caller that can afford one storage read should use this; the fire-and-forget
  * event paths must stay on the sync function.
  *
- * Never throws or rejects: a missing, hung, or rejecting adapter resolves to the in-memory id, and
- * with no `storage` it resolves immediately (there is nothing to hydrate from).
+ * Never throws or rejects: a missing or rejecting adapter resolves to the in-memory id, and with no
+ * `storage` it resolves immediately (there is nothing to hydrate from).
+ *
+ * ⛔ A HUNG ADAPTER IS THE ONE CASE IT DOES NOT COVER, and this line used to claim it did. The read
+ * underneath is a bare `storage.getItem` with no ceiling of its own, so an adapter that neither
+ * resolves nor rejects (a locked keychain, a wedged native bridge) leaves THIS PROMISE PENDING
+ * FOREVER — it does not fall back to the in-memory id, it simply never answers. Anything that gates
+ * a user-visible or metric-bearing action on the result must therefore race it against a ceiling of
+ * its own: `<WireOnboarding>` does (`AUTO_JOIN_HYDRATION_TIMEOUT_MS`), and so do the two lifecycle
+ * hooks (`session-analytics/useLifecycleEvents` + `useSessionStart`, through the shared
+ * `withTimeout` + `READ_TIMEOUT_MS` in `session/persistedSession`) — a hung read there had silently
+ * killed `app.session_started` and `app.first_open` for the whole process. Use the SYNC
+ * {@link resolveAutoDeviceKey} when you cannot afford to wait at all.
  *
  * ⚠️ IT RETURNS A BARE STRING, so it CANNOT say whether the id survives the launch — a degraded
  * adapter resolves to the in-memory mint and reads identically to a persisted one. No kit surface
@@ -1419,7 +1410,9 @@ declare const hydrateAutoDeviceKey: (opts?: ResolveAutoDeviceKeyOptions) => Prom
  *
  * 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.
+ * Never throws or rejects — but, exactly like {@link hydrateAutoDeviceKey} above, it can also never
+ * SETTLE on a hung adapter (the underlying `getItem` carries no ceiling), so every caller races it
+ * against one of its own. See the note there.
  */
 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. */
@@ -1432,7 +1425,10 @@ declare const resetAutoDeviceKeys: () => void;
 declare const setCurrentSessionId: (id: string | undefined) => void;
 /** The current per-open `session_id`, or `undefined` when no app-open has been registered yet. */
 declare const getCurrentSessionId: () => string | undefined;
-/** Test-only: forget the current session id so a unit test starts from a clean registry. */
+/** Test-only: forget the current session id so a unit test starts from a clean registry. Does NOT
+ *  clear the MINTED-id record (see `isMintedSessionId`), for the same reason the warn latch below is
+ *  not cleared: `makeSessionId()` never repeats, so a remembered fallback id can never again equal a
+ *  live one, and the record is overwritten by the next mint anyway. */
 declare const resetCurrentSessionId: () => void;
 /**
  * The current per-open `session_id`, MINTING and registering one when no app-open has been

package/dist/{decision-Bgo17oH7.d.mts → decision-3vWLuBlO.d.ts}

@@ -1,4 +1,4 @@
-import { c as ReviewDecision, j as ReviewSubmission, e as RatingRoute } from './types-Cju-1_jT.mjs';
+import { c as ReviewDecision, j as ReviewSubmission, e as RatingRoute } from './types-tdATL5z0.js';
 
 /**
  * decision.ts — the pure decision logic for the review gate.
@@ -65,7 +65,14 @@ declare const evaluateGate: (rules: GateRules, s: GateSignals) => ReviewDecision
  * never a button labeled "rate us 5 stars" (see the store-policy notes in the README).
  */
 declare const routeRating: (stars: number) => RatingRoute;
-/** Build the `POST /v1/reviews` body. Feedback text/contact belong ONLY here, never in events. */
+/**
+ * Build the `POST /v1/reviews` body. Feedback text/contact belong ONLY here, never in events.
+ *
+ * STILL PURE, deliberately: `idempotencyKey` and the `meta.device_key` the server scopes it to are
+ * both passed IN rather than resolved here. Reaching into the device-key registry from this function
+ * would make the gate logic untestable in isolation, and both values are scoped to an impression
+ * this function cannot see — see `reviews/idempotency.ts`.
+ */
 declare const buildReviewSubmission: (input: {
     stars: number;
     feedbackText?: string;
@@ -73,6 +80,8 @@ declare const buildReviewSubmission: (input: {
     contact?: string;
     sessionId?: string;
     source?: string;
+    /** The impression's idempotency key. Omitted → the server mints a row id and inserts, as before. */
+    idempotencyKey?: string;
     meta?: Record<string, unknown>;
 }) => ReviewSubmission;
 

package/dist/{decision-Bkh_LigV.d.ts → decision-yBj2AyPW.d.mts}

@@ -1,4 +1,4 @@
-import { c as ReviewDecision, j as ReviewSubmission, e as RatingRoute } from './types-h2BZvl1t.js';
+import { c as ReviewDecision, j as ReviewSubmission, e as RatingRoute } from './types-Byx306Kv.mjs';
 
 /**
  * decision.ts — the pure decision logic for the review gate.
@@ -65,7 +65,14 @@ declare const evaluateGate: (rules: GateRules, s: GateSignals) => ReviewDecision
  * never a button labeled "rate us 5 stars" (see the store-policy notes in the README).
  */
 declare const routeRating: (stars: number) => RatingRoute;
-/** Build the `POST /v1/reviews` body. Feedback text/contact belong ONLY here, never in events. */
+/**
+ * Build the `POST /v1/reviews` body. Feedback text/contact belong ONLY here, never in events.
+ *
+ * STILL PURE, deliberately: `idempotencyKey` and the `meta.device_key` the server scopes it to are
+ * both passed IN rather than resolved here. Reaching into the device-key registry from this function
+ * would make the gate logic untestable in isolation, and both values are scoped to an impression
+ * this function cannot see — see `reviews/idempotency.ts`.
+ */
 declare const buildReviewSubmission: (input: {
     stars: number;
     feedbackText?: string;
@@ -73,6 +80,8 @@ declare const buildReviewSubmission: (input: {
     contact?: string;
     sessionId?: string;
     source?: string;
+    /** The impression's idempotency key. Omitted → the server mints a row id and inserts, as before. */
+    idempotencyKey?: string;
     meta?: Record<string, unknown>;
 }) => ReviewSubmission;
 

package/dist/index.d.mts

@@ -1,7 +1,7 @@
 import * as React from 'react';
 import React__default, { ReactNode } from 'react';
-import { I as WireOnboardingProps, J as WireOnboardingConfig, O as OnboardingResult, K as WirePermissionStatus, P as PermissionStage, L as WirePermissionOutcome, S as StepValidator, M as OnboardingEvent, N as OnboardingCopy, C as ClientEventTarget, Q as DeviceContext, T as PermissionScreenConfig, W as WireUserContext, c as ClientEvent, U as PermissionPlacement, g as EnvelopeSource } from './currentSession-CUvTOchb.mjs';
-export { A as AUTO_DEVICE_ID_PREFIX, a as AnalyticsEvent, b as ClearUserContextOptions, d as ClientEventType, V as DEFAULT_PERMISSION_COPY, X as DeviceFormFactor, D as DeviceKeyStorage, Y as EXTRA_KEY_PREFIX, Z as GENERIC_PERMISSION_COPY, _ as IdentifyOnboardingBinding, $ as IdentifyOnboardingOptions, a0 as IdentityRecord, a1 as IdentitySource, a2 as IdentitySpace, a3 as NOTIFICATIONS_PERMISSION_COPY, a4 as OnboardingProgress, a5 as PermissionScreenCopy, R as ResolveAutoDeviceKeyOptions, a6 as ResolveUserContextOptions, a7 as ResolvedUserContext, a8 as USER_ID_MAX_LENGTH, i as WIRE_ONBOARDING_EVENTS, a9 as WIRE_PERMISSION_EVENTS, j as WireOnboardingEventName, aa as WirePermissionEventName, ab as WirePermissionKind, ac as activationJoinContext, k as analyticsUserIdStorageKey, m as clearPiiFromContext, n as clearUserContext, ad as collectDeviceContext, p as deviceIdStorageKey, q as ensureCurrentSessionId, r as getCurrentSessionId, ae as hashEmailFnv1a, af as hostIdentity, ag as hydrateAutoDeviceKey, ah as hydrateDeviceIdentity, ai as identifyOnboarding, aj as isWireScalar, s as looksLikeEmail, t as makeSessionId, ak as mintDeviceId, al as namespaceExtra, am as normalizePermissionStatus, an as permissionEventName, ao as permissionEventProps, u as reportClientEvent, v as reportClientEventAwait, w as reportClientEvents, x as reportClientEventsAwait, y as resetAutoDeviceKeys, z as resetCurrentSessionId, ap as resetIdentityProvenance, F as resolveAutoDeviceKey, aq as resolveIdentity, ar as resolvePermissionCopy, as as resolveUserContext, at as sanitizeUserId, G as setCurrentSessionId, H as toAnalyticsEvent } from './currentSession-CUvTOchb.mjs';
+import { I as WireOnboardingProps, J as WireOnboardingConfig, O as OnboardingResult, K as WirePermissionStatus, P as PermissionStage, L as WirePermissionOutcome, S as StepValidator, M as OnboardingEvent, N as OnboardingCopy, C as ClientEventTarget, Q as DeviceContext, T as PermissionScreenConfig, W as WireUserContext, c as ClientEvent, U as PermissionPlacement, g as EnvelopeSource } from './currentSession-Bz7G6lno.mjs';
+export { A as AUTO_DEVICE_ID_PREFIX, a as AnalyticsEvent, b as ClearUserContextOptions, d as ClientEventType, V as DEFAULT_PERMISSION_COPY, X as DeviceFormFactor, D as DeviceKeyStorage, Y as EXTRA_KEY_PREFIX, Z as GENERIC_PERMISSION_COPY, _ as IdentifyOnboardingBinding, $ as IdentifyOnboardingOptions, a0 as IdentityRecord, a1 as IdentitySource, a2 as IdentitySpace, a3 as NOTIFICATIONS_PERMISSION_COPY, a4 as OnboardingProgress, a5 as PermissionScreenCopy, R as ResolveAutoDeviceKeyOptions, a6 as ResolveUserContextOptions, a7 as ResolvedUserContext, a8 as USER_ID_MAX_LENGTH, i as WIRE_ONBOARDING_EVENTS, a9 as WIRE_PERMISSION_EVENTS, j as WireOnboardingEventName, aa as WirePermissionEventName, ab as WirePermissionKind, ac as activationJoinContext, k as analyticsUserIdStorageKey, m as clearPiiFromContext, n as clearUserContext, ad as collectDeviceContext, p as deviceIdStorageKey, q as ensureCurrentSessionId, r as getCurrentSessionId, ae as hashEmailFnv1a, af as hostIdentity, ag as hydrateAutoDeviceKey, ah as hydrateDeviceIdentity, ai as identifyOnboarding, aj as isWireScalar, s as looksLikeEmail, t as makeSessionId, ak as mintDeviceId, al as namespaceExtra, am as normalizePermissionStatus, an as permissionEventName, ao as permissionEventProps, u as reportClientEvent, v as reportClientEventAwait, w as reportClientEvents, x as reportClientEventsAwait, y as resetAutoDeviceKeys, z as resetCurrentSessionId, ap as resetIdentityProvenance, F as resolveAutoDeviceKey, aq as resolveIdentity, ar as resolvePermissionCopy, as as resolveUserContext, at as sanitizeUserId, G as setCurrentSessionId, H as toAnalyticsEvent } from './currentSession-Bz7G6lno.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';
@@ -1301,6 +1301,7 @@ declare const readProgress: (response?: WireAIResponse) => PartialProgress;
  */
 declare const fetchWireFeatures: (config?: WireFeaturesConfig) => Promise<WireFeatures>;
 
+/** The flags alone — the original hook, unchanged for every consumer that cannot act on `settled`. */
 declare const useWireFeatures: (config?: WireFeaturesConfig) => WireFeatures;
 
 /**
@@ -2165,6 +2166,8 @@ interface ReportFirstOpenOptions extends LifecycleEventInput {
  *   • Race guard: an in-memory latch is set SYNCHRONOUSLY before the async read, so two
  *     near-simultaneous calls fire at most once.
  *   • Without `storage`: degraded mode — fires once per PROCESS via the latch only (documented).
+ *   • WITHOUT A TRANSPORT: no-op, and — the point of the check — the once-ever flag is NOT spent.
+ *     See below.
  */
 declare const reportFirstOpen: (opts: ReportFirstOpenOptions) => void;
 /** Options for {@link wireLifecycleEvents}: the shared lifecycle inputs + first-open persistence. */

package/dist/index.d.ts

@@ -1,7 +1,7 @@
 import * as React from 'react';
 import React__default, { ReactNode } from 'react';
-import { I as WireOnboardingProps, J as WireOnboardingConfig, O as OnboardingResult, K as WirePermissionStatus, P as PermissionStage, L as WirePermissionOutcome, S as StepValidator, M as OnboardingEvent, N as OnboardingCopy, C as ClientEventTarget, Q as DeviceContext, T as PermissionScreenConfig, W as WireUserContext, c as ClientEvent, U as PermissionPlacement, g as EnvelopeSource } from './currentSession-CW_5Mq4O.js';
-export { A as AUTO_DEVICE_ID_PREFIX, a as AnalyticsEvent, b as ClearUserContextOptions, d as ClientEventType, V as DEFAULT_PERMISSION_COPY, X as DeviceFormFactor, D as DeviceKeyStorage, Y as EXTRA_KEY_PREFIX, Z as GENERIC_PERMISSION_COPY, _ as IdentifyOnboardingBinding, $ as IdentifyOnboardingOptions, a0 as IdentityRecord, a1 as IdentitySource, a2 as IdentitySpace, a3 as NOTIFICATIONS_PERMISSION_COPY, a4 as OnboardingProgress, a5 as PermissionScreenCopy, R as ResolveAutoDeviceKeyOptions, a6 as ResolveUserContextOptions, a7 as ResolvedUserContext, a8 as USER_ID_MAX_LENGTH, i as WIRE_ONBOARDING_EVENTS, a9 as WIRE_PERMISSION_EVENTS, j as WireOnboardingEventName, aa as WirePermissionEventName, ab as WirePermissionKind, ac as activationJoinContext, k as analyticsUserIdStorageKey, m as clearPiiFromContext, n as clearUserContext, ad as collectDeviceContext, p as deviceIdStorageKey, q as ensureCurrentSessionId, r as getCurrentSessionId, ae as hashEmailFnv1a, af as hostIdentity, ag as hydrateAutoDeviceKey, ah as hydrateDeviceIdentity, ai as identifyOnboarding, aj as isWireScalar, s as looksLikeEmail, t as makeSessionId, ak as mintDeviceId, al as namespaceExtra, am as normalizePermissionStatus, an as permissionEventName, ao as permissionEventProps, u as reportClientEvent, v as reportClientEventAwait, w as reportClientEvents, x as reportClientEventsAwait, y as resetAutoDeviceKeys, z as resetCurrentSessionId, ap as resetIdentityProvenance, F as resolveAutoDeviceKey, aq as resolveIdentity, ar as resolvePermissionCopy, as as resolveUserContext, at as sanitizeUserId, G as setCurrentSessionId, H as toAnalyticsEvent } from './currentSession-CW_5Mq4O.js';
+import { I as WireOnboardingProps, J as WireOnboardingConfig, O as OnboardingResult, K as WirePermissionStatus, P as PermissionStage, L as WirePermissionOutcome, S as StepValidator, M as OnboardingEvent, N as OnboardingCopy, C as ClientEventTarget, Q as DeviceContext, T as PermissionScreenConfig, W as WireUserContext, c as ClientEvent, U as PermissionPlacement, g as EnvelopeSource } from './currentSession-z-CZ55ad.js';
+export { A as AUTO_DEVICE_ID_PREFIX, a as AnalyticsEvent, b as ClearUserContextOptions, d as ClientEventType, V as DEFAULT_PERMISSION_COPY, X as DeviceFormFactor, D as DeviceKeyStorage, Y as EXTRA_KEY_PREFIX, Z as GENERIC_PERMISSION_COPY, _ as IdentifyOnboardingBinding, $ as IdentifyOnboardingOptions, a0 as IdentityRecord, a1 as IdentitySource, a2 as IdentitySpace, a3 as NOTIFICATIONS_PERMISSION_COPY, a4 as OnboardingProgress, a5 as PermissionScreenCopy, R as ResolveAutoDeviceKeyOptions, a6 as ResolveUserContextOptions, a7 as ResolvedUserContext, a8 as USER_ID_MAX_LENGTH, i as WIRE_ONBOARDING_EVENTS, a9 as WIRE_PERMISSION_EVENTS, j as WireOnboardingEventName, aa as WirePermissionEventName, ab as WirePermissionKind, ac as activationJoinContext, k as analyticsUserIdStorageKey, m as clearPiiFromContext, n as clearUserContext, ad as collectDeviceContext, p as deviceIdStorageKey, q as ensureCurrentSessionId, r as getCurrentSessionId, ae as hashEmailFnv1a, af as hostIdentity, ag as hydrateAutoDeviceKey, ah as hydrateDeviceIdentity, ai as identifyOnboarding, aj as isWireScalar, s as looksLikeEmail, t as makeSessionId, ak as mintDeviceId, al as namespaceExtra, am as normalizePermissionStatus, an as permissionEventName, ao as permissionEventProps, u as reportClientEvent, v as reportClientEventAwait, w as reportClientEvents, x as reportClientEventsAwait, y as resetAutoDeviceKeys, z as resetCurrentSessionId, ap as resetIdentityProvenance, F as resolveAutoDeviceKey, aq as resolveIdentity, ar as resolvePermissionCopy, as as resolveUserContext, at as sanitizeUserId, G as setCurrentSessionId, H as toAnalyticsEvent } from './currentSession-z-CZ55ad.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';
@@ -1301,6 +1301,7 @@ declare const readProgress: (response?: WireAIResponse) => PartialProgress;
  */
 declare const fetchWireFeatures: (config?: WireFeaturesConfig) => Promise<WireFeatures>;
 
+/** The flags alone — the original hook, unchanged for every consumer that cannot act on `settled`. */
 declare const useWireFeatures: (config?: WireFeaturesConfig) => WireFeatures;
 
 /**
@@ -2165,6 +2166,8 @@ interface ReportFirstOpenOptions extends LifecycleEventInput {
  *   • Race guard: an in-memory latch is set SYNCHRONOUSLY before the async read, so two
  *     near-simultaneous calls fire at most once.
  *   • Without `storage`: degraded mode — fires once per PROCESS via the latch only (documented).
+ *   • WITHOUT A TRANSPORT: no-op, and — the point of the check — the once-ever flag is NOT spent.
+ *     See below.
  */
 declare const reportFirstOpen: (opts: ReportFirstOpenOptions) => void;
 /** Options for {@link wireLifecycleEvents}: the shared lifecycle inputs + first-open persistence. */