@wireai/activation 0.13.5 → 0.13.6-next.0

package/README.md

@@ -1363,6 +1363,137 @@ generation context). For the full
 scaffold-the-screen integration job, the [`wire-rn-integration`](./INTEGRATION_PROMPT.md)
 skill drives it end to end.
 
+## EU AI Act: acceptable use and our position
+
+**Position as of 2026-08-06, against Regulation (EU) 2024/1689 as amended by Regulation (EU) 2026/1744.**
+
+This is our own reading of where this kit sits inside the regulation, written down so an integrator
+can see the reasoning and disagree with it. It is not legal advice. Nobody has audited this kit
+against the regulation, and a review by a qualified lawyer is pending. Where that review says we
+read something wrong, this section gets corrected and re-dated.
+
+### Who is who
+
+The app that ships a Wire-powered surface is the **deployer** of that surface. You choose the flow,
+the audience, the questions, and what the answers are used for.
+
+Wire is the provider of a limited-risk component inside that: a card renderer, plus a backend that
+selects and fills cards from a fixed vocabulary you configure.
+
+### Not for high-risk use
+
+**This system is not intended to be put into service as, or changed into, a high-risk AI system.**
+
+Do not deploy Wire-powered surfaces in an Annex III high-risk area:
+
+1. Biometrics
+2. Critical infrastructure
+3. Education and vocational training
+4. Employment, workers management and access to self-employment
+5. Access to essential private and public services and benefits
+6. Law enforcement
+7. Migration, asylum and border control
+8. Administration of justice and democratic processes
+
+Obligations for Annex III systems apply from 2 December 2027, which is not a countdown to when this
+becomes usable there. It is not what this kit is built for, at any date.
+
+Two prohibitions in Article 5(1) have been live since 2 February 2025 and were left untouched by the
+Omnibus. Do not use these surfaces for subliminal, manipulative or deceptive techniques that
+materially distort behaviour, and do not use them to exploit vulnerabilities due to age, disability,
+or a specific social or economic situation.
+
+That second one deserves saying out loud, because an onboarding flow that adapts per user is an easy
+place to cross it without meaning to. A flow that adapts because it learned what a user responds to
+is one short step from a flow that adapts because it learned what a user cannot resist. Optimise for
+the user finishing something they came to do.
+
+### Article 50(1): telling people they are talking to an AI
+
+Article 50(1) applies since 2 August 2026. There is no legacy grace period for it.
+
+It requires that AI systems intended to interact directly with natural persons are designed so those
+persons are informed they are interacting with an AI system, unless that is obvious from the point of
+view of a reasonably well-informed, observant and circumspect natural person.
+
+Our reading of the generated-UI case: generated onboarding UI is not a conversational agent. Cards,
+buttons, pickers and form fields do not present themselves as a person, and someone tapping through a
+signup flow is not being led to believe there is a human on the other end. A form is obvious.
+
+Where that reading stops: if you build a chat-like or free-text-responding surface, one that answers
+a user in free prose the way a person would, that is the case Article 50(1) was written for. If you
+build that, **your app owns the disclosure**, not the kit.
+
+We cannot place it for you. We do not control your screen, your copy, or your first-run experience.
+Put it where the user meets the surface, not buried in a settings page nobody opens.
+
+The honest edge in between: `TextInputCard` takes free text, and the copy on the next card is
+generated from what the user typed. We read that as a form that adapts rather than a conversation,
+because the system does not answer as an interlocutor and the interaction stays inside the card
+vocabulary you configured. If that reading does not hold for the flow you built, disclose. Nothing in
+the kit stops you.
+
+### Article 50(2): marking generated content
+
+Article 50(2) covers providers of AI systems that generate synthetic audio, image, video or text, and
+requires the outputs to be marked in a machine-readable format as artificially generated or
+manipulated. Its legacy grace period runs to 2 December 2026, and only for providers of those
+generators.
+
+Our reading has two parts.
+
+The first is that Wire does not provide the generative model. The card copy a user reads was produced
+by a third-party model. Provider-level marking of a model's output sits upstream, with the provider
+of that model.
+
+The second is that for the layer we do provide, the carve-out written into the article is the one we
+rely on. It "shall not apply to the extent the AI systems perform an assistive function for standard
+editing or do not substantially alter the input data provided by the deployer or the semantics
+thereof." You supply the app description, the first question, the allowed components and the copy
+constraints. The system selects and fills cards inside that. We read it as assistive rather than as
+generating a work of synthetic content.
+
+Where that reading stops: if you use this kit as the delivery surface for a general content
+generator, handing a model's free-form output to a user as content, our reading does not carry over
+to your app. Look at Article 50(2) for yourself in that case.
+
+### Article 50(3): emotion recognition
+
+We do not read Article 50(3) as engaged by anything this kit does today.
+
+Article 3(39) defines an emotion recognition system as one inferring emotions or intentions **on the
+basis of biometric data**, and recital 18 confines that to biometric signals like face, gesture and
+voice. This kit reads typed and tapped answers, and text is not biometric data. No camera, no
+microphone, no biometric processing anywhere in the flow.
+
+### Article 25: the specification, and why we are not standing behind a licence
+
+Article 25(2) closes with an express carve-out. The provider flip does not apply "in cases where the
+initial provider has clearly specified that its AI system is not to be changed into a high-risk AI
+system."
+
+The sentence in bold under **Not for high-risk use** is that specification. It is written
+deliberately, and it is why this section exists in the README rather than in a lawyer's drawer.
+
+Article 25(4) ends by exempting third parties who make tools, services, processes or components
+(other than general-purpose AI models) publicly available "under a free and open-source licence" from
+the written-agreement duty. `@wireai/activation` is published on npm under the MIT licence, so on the
+face of it that sentence reaches it, though the source repository is private and that is a difference
+worth stating rather than glossing over.
+
+We would rather not stand on that carve-out. Unlike the open-source SDK underneath this kit, we
+usually know who integrates this one and we have a direct channel to them. So if you integrate the
+kit and need information about it to meet your own obligations as a deployer, ask, and you get it in
+writing. That is a commitment about how we behave, not a claim about our legal position.
+
+### What this section is not
+
+Nobody has reviewed or audited this kit against the regulation. This is not a statement that it meets
+a legal standard, and it is not a badge for a landing page.
+
+It is what we think the regulation asks of a component like this one, what we did about it, and which
+parts sit on your side of the line rather than ours. Your app, your users, your assessment.
+
 ## More from Code Meet AI
 
 **Open source:** [wireai-rn](https://github.com/chohra-med/wireai-rn) · [expo_boilerplate](https://github.com/chohra-med/expo_boilerplate) · [colorway-c-brand](https://github.com/chohra-med/colorway-c-brand) · [claude_design_skill](https://github.com/chohra-med/claude_design_skill)

package/dist/analytics/index.d.mts

@@ -1,6 +1,6 @@
 export { R as ReportAppEventOptions, r as reportAppEvent } from '../transport-j5gFfJhK.mjs';
-import { C as ClientEventTarget, W as WireUserContext, E as EventQueueOptions } from '../currentSession-DgJf0fRz.mjs';
-export { A as AUTO_DEVICE_ID_PREFIX, a as AnalyticsEvent, b as ClearUserContextOptions, c as ClientEvent, d as ClientEventType, e as ContextEnvelope, f as ContextEnvelopeInput, D as DeviceKeyStorage, g as EnvelopeSource, h as EventQueue, R as ResolveAutoDeviceKeyOptions, i as WIRE_ONBOARDING_EVENTS, j as WireOnboardingEventName, k as analyticsUserIdStorageKey, l as buildContextEnvelope, m as clearPiiFromContext, n as clearUserContext, o as createEventQueue, p as deviceIdStorageKey, q as ensureCurrentSessionId, r as getCurrentSessionId, s as looksLikeEmail, t as makeSessionId, u as reportClientEvent, v as reportClientEventAwait, w as reportClientEvents, x as reportClientEventsAwait, y as resetAutoDeviceKeys, z as resetCurrentSessionId, B as resetEventQueueKeys, F as resolveAutoDeviceKey, G as setCurrentSessionId, H as toAnalyticsEvent } from '../currentSession-DgJf0fRz.mjs';
+import { C as ClientEventTarget, W as WireUserContext, E as EventQueueOptions } from '../currentSession-Cs3lweFZ.mjs';
+export { A as AUTO_DEVICE_ID_PREFIX, a as AnalyticsEvent, b as ClearUserContextOptions, c as ClientEvent, d as ClientEventType, e as ContextEnvelope, f as ContextEnvelopeInput, D as DeviceKeyStorage, g as EnvelopeSource, h as EventQueue, R as ResolveAutoDeviceKeyOptions, i as WIRE_ONBOARDING_EVENTS, j as WireOnboardingEventName, k as analyticsUserIdStorageKey, l as buildContextEnvelope, m as clearPiiFromContext, n as clearUserContext, o as createEventQueue, p as deviceIdStorageKey, q as ensureCurrentSessionId, r as getCurrentSessionId, s as looksLikeEmail, t as makeSessionId, u as reportClientEvent, v as reportClientEventAwait, w as reportClientEvents, x as reportClientEventsAwait, y as resetAutoDeviceKeys, z as resetCurrentSessionId, B as resetEventQueueKeys, F as resolveAutoDeviceKey, G as setCurrentSessionId, H as toAnalyticsEvent } from '../currentSession-Cs3lweFZ.mjs';
 import { W as WireOnboardingStorage } from '../types-BpwiRpA8.mjs';
 import '../types-Cju-1_jT.mjs';
 import '../types-BKfpdZzX.mjs';

package/dist/analytics/index.d.ts

@@ -1,6 +1,6 @@
 export { R as ReportAppEventOptions, r as reportAppEvent } from '../transport-B_0SgCBe.js';
-import { C as ClientEventTarget, W as WireUserContext, E as EventQueueOptions } from '../currentSession-EOHU64QD.js';
-export { A as AUTO_DEVICE_ID_PREFIX, a as AnalyticsEvent, b as ClearUserContextOptions, c as ClientEvent, d as ClientEventType, e as ContextEnvelope, f as ContextEnvelopeInput, D as DeviceKeyStorage, g as EnvelopeSource, h as EventQueue, R as ResolveAutoDeviceKeyOptions, i as WIRE_ONBOARDING_EVENTS, j as WireOnboardingEventName, k as analyticsUserIdStorageKey, l as buildContextEnvelope, m as clearPiiFromContext, n as clearUserContext, o as createEventQueue, p as deviceIdStorageKey, q as ensureCurrentSessionId, r as getCurrentSessionId, s as looksLikeEmail, t as makeSessionId, u as reportClientEvent, v as reportClientEventAwait, w as reportClientEvents, x as reportClientEventsAwait, y as resetAutoDeviceKeys, z as resetCurrentSessionId, B as resetEventQueueKeys, F as resolveAutoDeviceKey, G as setCurrentSessionId, H as toAnalyticsEvent } from '../currentSession-EOHU64QD.js';
+import { C as ClientEventTarget, W as WireUserContext, E as EventQueueOptions } from '../currentSession-DD6dKB0i.js';
+export { A as AUTO_DEVICE_ID_PREFIX, a as AnalyticsEvent, b as ClearUserContextOptions, c as ClientEvent, d as ClientEventType, e as ContextEnvelope, f as ContextEnvelopeInput, D as DeviceKeyStorage, g as EnvelopeSource, h as EventQueue, R as ResolveAutoDeviceKeyOptions, i as WIRE_ONBOARDING_EVENTS, j as WireOnboardingEventName, k as analyticsUserIdStorageKey, l as buildContextEnvelope, m as clearPiiFromContext, n as clearUserContext, o as createEventQueue, p as deviceIdStorageKey, q as ensureCurrentSessionId, r as getCurrentSessionId, s as looksLikeEmail, t as makeSessionId, u as reportClientEvent, v as reportClientEventAwait, w as reportClientEvents, x as reportClientEventsAwait, y as resetAutoDeviceKeys, z as resetCurrentSessionId, B as resetEventQueueKeys, F as resolveAutoDeviceKey, G as setCurrentSessionId, H as toAnalyticsEvent } from '../currentSession-DD6dKB0i.js';
 import { W as WireOnboardingStorage } from '../types-BpwiRpA8.js';
 import '../types-h2BZvl1t.js';
 import '../types-BKfpdZzX.js';

package/dist/{currentSession-DgJf0fRz.d.mts → currentSession-Cs3lweFZ.d.mts}

@@ -471,6 +471,19 @@ type OnboardingResult = {
     answers: Record<string, unknown>;
     /** The raw message thread, for custom downstream parsing. */
     raw: Message[];
+    /**
+     * The backend's onboarding plan, when it sent one. Present ONLY on the AI path: a tenant running
+     * the static flow, or any run the server finished without a plan, leaves this `undefined` AND
+     * leaves the key off the result object entirely — so a host written before plans existed sees
+     * byte-identically what it always saw.
+     *
+     * ⚠️ The kit does NOT interpret this and does NOT validate it. It checks one structural fact (a
+     * plan is an object) and hands the payload straight through, unread, unlogged, and never attached
+     * to an analytics event. THE HOST MUST VALIDATE IT before applying it: the fields are
+     * backend-authored, they may gain new ones without a kit release, and what any of them mean is
+     * the host's decision, not the kit's.
+     */
+    plan?: unknown;
 };
 /**
  * Lifecycle events emitted as the flow runs, for host-side analytics. The kit owns

package/dist/{currentSession-EOHU64QD.d.ts → currentSession-DD6dKB0i.d.ts}

@@ -471,6 +471,19 @@ type OnboardingResult = {
     answers: Record<string, unknown>;
     /** The raw message thread, for custom downstream parsing. */
     raw: Message[];
+    /**
+     * The backend's onboarding plan, when it sent one. Present ONLY on the AI path: a tenant running
+     * the static flow, or any run the server finished without a plan, leaves this `undefined` AND
+     * leaves the key off the result object entirely — so a host written before plans existed sees
+     * byte-identically what it always saw.
+     *
+     * ⚠️ The kit does NOT interpret this and does NOT validate it. It checks one structural fact (a
+     * plan is an object) and hands the payload straight through, unread, unlogged, and never attached
+     * to an analytics event. THE HOST MUST VALIDATE IT before applying it: the fields are
+     * backend-authored, they may gain new ones without a kit release, and what any of them mean is
+     * the host's decision, not the kit's.
+     */
+    plan?: unknown;
 };
 /**
  * Lifecycle events emitted as the flow runs, for host-side analytics. The kit owns

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, U as PermissionPlacement, c as ClientEvent, g as EnvelopeSource } from './currentSession-DgJf0fRz.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-DgJf0fRz.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, U as PermissionPlacement, c as ClientEvent, g as EnvelopeSource } from './currentSession-Cs3lweFZ.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-Cs3lweFZ.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';

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, U as PermissionPlacement, c as ClientEvent, g as EnvelopeSource } from './currentSession-EOHU64QD.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-EOHU64QD.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, U as PermissionPlacement, c as ClientEvent, g as EnvelopeSource } from './currentSession-DD6dKB0i.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-DD6dKB0i.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';

package/dist/index.js

@@ -1127,6 +1127,26 @@ var deriveAnswers = (messages) => {
   return out;
 };
 
+// src/utils/readPlan.ts
+var PLAN_PART_KIND = "onboarding_plan";
+var isRecord = (value) => typeof value === "object" && value !== null && !Array.isArray(value);
+var hasDataParts = (value) => isRecord(value) && Array.isArray(value.dataParts);
+var planFromPart = (part) => {
+  if (!isRecord(part) || part.kind !== PLAN_PART_KIND) return void 0;
+  return isRecord(part.plan) ? part.plan : void 0;
+};
+var readPlan = (messages) => {
+  for (let i = messages.length - 1; i >= 0; i--) {
+    const message = messages[i];
+    if (!hasDataParts(message)) continue;
+    for (const part of message.dataParts) {
+      const plan = planFromPart(part);
+      if (plan !== void 0) return plan;
+    }
+  }
+  return void 0;
+};
+
 // src/utils/readProgress.ts
 var readProgress = (response) => {
   var _a;
@@ -1797,7 +1817,10 @@ var OnboardingFlow = ({
   const handleFinish = React19.useCallback(() => {
     if (finished.current) return;
     finished.current = true;
-    onCompleteRef.current({ answers: deriveAnswers(messages), raw: messages });
+    const result = { answers: deriveAnswers(messages), raw: messages };
+    const plan = readPlan(messages);
+    if (plan !== void 0) result.plan = plan;
+    onCompleteRef.current(result);
   }, [messages]);
   const handleRetry = React19.useCallback(() => {
     attempts.current = 0;