@appilots/sdk 0.7.0 → 0.10.0

package/dist/index.d.mts

@@ -1,8 +1,8 @@
-import { P as PartialThemeTokens, A as AppilotsThemeTokens, a as AppilotsLocale, b as AgentAction, I as InteractionElementSnapshot, C as ComponentRegistry, c as AgentPermissions, S as ScreenSnapshot, F as FieldEntry, d as AppilotsEvent } from './index-nI-s3Exg.mjs';
-export { e as AgentActionType, f as AgentMessage, g as AppilotsClient, h as AppilotsClientOptions, i as AppilotsConfig, j as AppilotsEventHandler, k as AppilotsEventType, l as AppilotsProvider, m as AppilotsProviderProps, n as AppilotsTraceEntry, o as AppilotsUser, B as BreadcrumbItem, p as BreadcrumbState, q as ButtonSnapshot, r as ChatMessage, s as ChoiceGroupSnapshot, t as ChoiceOptionSnapshot, u as ComponentEntry, v as ComponentKind, E as EscalationState, w as FormFillPayload, x as InputSnapshot, y as InteractionElementListContext, L as ListItemSnapshot, z as ListSnapshot, M as MessageRole, N as NavigationPayload, R as RateLimitedError, D as RemotePersonalization, G as SDK_VERSION, H as SliderEntry, J as SuggestedPrompt, T as TargetEntry, K as ToggleEntry, O as ToggleSnapshot, U as UIInteractionPayload, Q as UseAppilotsFieldOptions, V as UseAppilotsSliderOptions, W as UseAppilotsTargetOptions, X as UseAppilotsToggleOptions, Y as UseSuggestedPromptsOptions, Z as UseSuggestedPromptsReturn, _ as clearAppilotsDebugTraces, $ as componentRegistry, a0 as createComponentRegistry, a1 as defaultDarkTheme, a2 as defaultLightTheme, a3 as describeAction, a4 as getAppilotsDebugTraces, a5 as humanizeError, a6 as mergeThemeTokens, a7 as recordAppilotsDebugTrace, a8 as subscribeAppilotsDebugTraces, a9 as useAppilots, aa as useAppilotsActions, ab as useAppilotsChat, ac as useAppilotsContext, ad as useAppilotsField, ae as useAppilotsNavigation, af as useAppilotsSlider, ag as useAppilotsTarget, ah as useAppilotsToggle, ai as useSuggestedPrompts } from './index-nI-s3Exg.mjs';
+import { P as PartialThemeTokens, A as AppilotsThemeTokens, a as AppilotsLocale, b as AgentAction, I as InteractionElementEntry, C as ComponentRegistry, c as AgentPermissions, S as ScreenSnapshot, F as FieldEntry, d as AppilotsEvent } from './index-BPZ0j71S.mjs';
+export { e as AgentActionType, f as AgentMessage, g as AppilotsClient, h as AppilotsClientOptions, i as AppilotsConfig, j as AppilotsEventHandler, k as AppilotsEventType, l as AppilotsProvider, m as AppilotsProviderProps, n as AppilotsTraceEntry, o as AppilotsUser, B as BreadcrumbItem, p as BreadcrumbState, q as ButtonSnapshot, r as ChatMessage, s as ChoiceGroupSnapshot, t as ChoiceOptionSnapshot, u as ComponentEntry, v as ComponentKind, E as EscalationState, w as FormFillPayload, x as InputSnapshot, y as InteractionElementListContext, z as InteractionElementSnapshot, L as ListItemSnapshot, D as ListSnapshot, M as MessageRole, N as NavigationPayload, R as RateLimitedError, G as RemotePersonalization, H as SliderEntry, J as SuggestedPrompt, T as TargetEntry, K as ToggleEntry, O as ToggleSnapshot, U as UIInteractionPayload, Q as UseAppilotsFieldOptions, V as UseAppilotsSliderOptions, W as UseAppilotsTargetOptions, X as UseAppilotsToggleOptions, Y as UseSuggestedPromptsOptions, Z as UseSuggestedPromptsReturn, _ as clearAppilotsDebugTraces, $ as componentRegistry, a0 as createComponentRegistry, a1 as defaultDarkTheme, a2 as defaultLightTheme, a3 as describeAction, a4 as getAppilotsDebugTraces, a5 as humanizeError, a6 as mergeThemeTokens, a7 as recordAppilotsDebugTrace, a8 as subscribeAppilotsDebugTraces, a9 as useAppilots, aa as useAppilotsActions, ab as useAppilotsChat, ac as useAppilotsContext, ad as useAppilotsField, ae as useAppilotsNavigation, af as useAppilotsSlider, ag as useAppilotsTarget, ah as useAppilotsToggle, ai as useSuggestedPrompts } from './index-BPZ0j71S.mjs';
 import * as React$1 from 'react';
 import React__default from 'react';
-export { A as AppilotsNavigationContainer, N as NavigationConfig, b as ScreenMetadata, r as registerScreen } from './registerScreen-D1oGm28T.mjs';
+export { AppilotsNavigationContainer, NavigationConfig, ScreenMetadata, registerScreen, setCurrentScreen } from './navigation/index.mjs';
 
 interface AppilotsThemeProviderProps {
     /**
@@ -111,6 +111,20 @@ interface AppilotsStrings {
     reject: string;
     /** Generic "cancelled by the user" message after a reject. */
     cancelledByUser: string;
+    /** Title of the confirm card for a destructive action. */
+    confirmDestructiveTitle: string;
+    /** Title of the confirm card for a non-destructive confirmation. */
+    confirmTitle: string;
+    /** Body of the confirm card. `{action}` is replaced with the action's own description. */
+    confirmMessage: string;
+    /** Approve button when the action is destructive — states what will happen. */
+    confirmDestructiveApprove: string;
+    /** Approve button for a non-destructive confirmation. */
+    confirmApprove: string;
+    /** Cancel button on the confirm card. */
+    confirmCancel: string;
+    /** Last-resort name for an action with no description of its own. */
+    confirmThisAction: string;
     /** Fallback humanised name for an unknown action type. */
     unknownAction: string;
     /** Generic friendly error when nothing else fits. */
@@ -276,12 +290,15 @@ interface LegacyThemeShape {
     fontFamily?: string;
 }
 /**
- * Outer wrapper — sets up Theme + i18n providers so the inner component
- * (and the ConfirmDialog) all read from the same resolved tokens. This
- * lets a developer mount AppilotsChat without also wrapping their app
- * in a `<AppilotsThemeProvider>` manually.
+ * Public entry point.
+ *
+ * The chat is a leaf in the host app's tree, so its failure barrier is
+ * the simple case: nothing of the customer's app is inside it, and the
+ * degraded state can just be "no assistant". Rendering an error card
+ * inside somebody else's product would be worse than rendering nothing
+ * — they did not ask us to put a broken box on their screen.
  */
-declare function AppilotsChat(props: AppilotsChatProps): React__default.JSX.Element;
+declare function AppilotsChat(props: AppilotsChatProps): React__default.JSX.Element | null;
 /**
  * Re-exports kept for backwards compatibility — the legacy
  * `AppilotsChatTheme` type used to live on this module. Prefer
@@ -368,6 +385,20 @@ interface BreadcrumbPalette {
     /** "failed" tone AND every destructive badge/CTA (confirm card, reject button). */
     error: string;
 }
+/**
+ * The subset of the SDK's strings the confirm card needs. Declared
+ * structurally rather than importing `AppilotsStrings` so this module
+ * stays a pure presentation helper with no i18n dependency.
+ */
+interface ConfirmCardStrings {
+    confirmDestructiveTitle: string;
+    confirmTitle: string;
+    confirmMessage: string;
+    confirmDestructiveApprove: string;
+    confirmApprove: string;
+    confirmCancel: string;
+    confirmThisAction: string;
+}
 
 /**
  * ActionBreadcrumb — compact, line-per-action progress UI.
@@ -404,6 +435,12 @@ interface ActionBreadcrumbProps {
      * pre-4.2 shape of this prop set) keep rendering exactly as before.
      */
     palette?: Partial<Omit<BreadcrumbPalette, 'primary' | 'text'>>;
+    /**
+     * Resolved confirm-card copy for the host's locale. Optional so every
+     * existing caller keeps compiling; when absent the card falls back to
+     * the pt-BR literals it always shipped (#402). AppilotsChat passes it.
+     */
+    confirmStrings?: ConfirmCardStrings;
     /**
      * Approve/reject inline buttons appear when this returns true for an
      * action in `pending` state. `confirm`-type actions are normally
@@ -414,7 +451,7 @@ interface ActionBreadcrumbProps {
     onApprove?: (actionId: string) => void;
     onReject?: (actionId: string) => void;
 }
-declare function ActionBreadcrumb({ actions, primaryColor, textColor, fontFamily, palette, requireApprovalFor, onApprove, onReject, }: ActionBreadcrumbProps): React__default.JSX.Element | null;
+declare function ActionBreadcrumb({ actions, primaryColor, textColor, fontFamily, palette, confirmStrings, requireApprovalFor, onApprove, onReject, }: ActionBreadcrumbProps): React__default.JSX.Element | null;
 
 interface ChatIconProps {
     /** Outer width/height in points. Default 24. */
@@ -478,7 +515,19 @@ interface ListScrollMetrics {
     contentLength: number;
 }
 interface ListEntry {
-    kind: 'list';
+    /**
+     * `'list'` is a collection with rows — the agent can reason about
+     * ordinals, totals and per-item content. `'scroll'` is a bare
+     * scrollable surface (a `ScrollView` holding a form or a detail page):
+     * it has no rows, no total, and no ordinals — the ONLY thing the agent
+     * can do with it is page up/down to reveal content below the fold.
+     *
+     * They share this registry because they share the scroll handles, but
+     * they must never share a description: a `ScrollView` reported as a
+     * list with zero rows would invite "selecione o terceiro" against a
+     * container that has no third anything.
+     */
+    kind: 'list' | 'scroll';
     /** Stable runtime id assigned from testID/accessibilityLabel or generated. */
     id: string;
     /** Component name: FlatList, SectionList, VirtualizedList, FlashList, etc. */
@@ -523,7 +572,6 @@ declare class ListRegistryImpl {
 declare const listRegistry: ListRegistry;
 declare function createListRegistry(): ListRegistry;
 
-type InteractionElementEntry = InteractionElementSnapshot;
 type Listener = (id: string, entry: InteractionElementEntry | null) => void;
 type ElementRegistry = ElementRegistryImpl;
 declare class ElementRegistryImpl {
@@ -613,6 +661,17 @@ interface AppilotsRC {
     apiBaseUrl?: string;
     /** Alias for apiBaseUrl (supported for convenience) */
     apiUrl?: string;
+    /**
+     * Alias for apiBaseUrl — the name `@appilots/cli` uses, and therefore
+     * the name that is actually in people's `.appilotsrc`.
+     *
+     * This used to be read by the CLI only. The SDK reads the very same
+     * file through the Metro plugin and simply ignored the key, so an app
+     * pointed at a staging or local API kept talking to production and
+     * nothing said so: the CLI obeyed, the app did not, and both looked
+     * fine. Accepted here so one file means one thing.
+     */
+    serverUrl?: string;
     /** Agent permissions */
     permissions?: Partial<AgentPermissions>;
     /** Enable debug logging */
@@ -682,6 +741,30 @@ declare function _patchJsxRuntimes(jsxRuntime: any, jsxDevRuntime: any): void;
  * Check if auto-tracking is enabled.
  */
 declare function isAutoTrackingEnabled(): boolean;
+/** Which of the three element factories interception actually reached. */
+interface AutoTrackingState {
+    /** `enableAppilotsAutoTracking()` ran. */
+    enabled: boolean;
+    createElementPatched: boolean;
+    /** `react/jsx-runtime` — jsx()/jsxs(), the transform release builds use. */
+    jsxRuntimePatched: boolean;
+    /** `react/jsx-dev-runtime` — jsxDEV(), development only. */
+    jsxDevRuntimePatched: boolean;
+    /** False once the guard latched interception off after repeated failures. */
+    interceptionActive: boolean;
+}
+/**
+ * Report which patches landed (#388).
+ *
+ * `enabled` alone is not the answer an integrator needs: the JSX
+ * runtime patch is the one that can silently not happen — bundlers
+ * resolve `react/jsx-runtime` differently, which is why `metro.js`
+ * exists to hand the modules back in. `enabled: true` with
+ * `jsxRuntimePatched: false` on a build using the automatic transform
+ * is a registry that will stay empty, and it looks exactly like a
+ * walker that stopped recognizing things.
+ */
+declare function getAutoTrackingState(): AutoTrackingState;
 
 /**
  * captureSnapshot — the public entry point for runtime UI introspection.
@@ -698,15 +781,6 @@ declare function isAutoTrackingEnabled(): boolean;
 
 declare function captureSnapshot(): ScreenSnapshot;
 
-/**
- * fiberRoot — module-level holder for the root fiber captured by
- * AppilotsFiberRoot. The fiber reference is set during the first render
- * and is used by captureSnapshot() to walk the React tree on demand.
- *
- * Fiber nodes are mutable: React updates their .child/.sibling pointers
- * as the tree re-renders. Storing a reference once is sufficient — we
- * always see the latest tree when we walk.
- */
 /**
  * Why capture failed, when it did.
  *
@@ -716,8 +790,23 @@ declare function captureSnapshot(): ScreenSnapshot;
  *   other way — the app renders fine and only introspection is blind.
  * - `never-mounted`: something asked for a snapshot before
  *   `<AppilotsProvider>` committed (or outside it entirely).
+ * - `render-crashed`: the SDK's own render surface threw and the error
+ *   boundary degraded it. Unlike the other two this is OUR bug, not a
+ *   host-app integration problem — see `recordRenderFailure`.
+ * - `names-mangled`: the bundle renamed the React Native components the
+ *   walker matches by name (#386). Not a capture failure — the fiber
+ *   root is fine — but the same shape of harm: the app renders
+ *   correctly and detection degrades to the structural fallbacks, in
+ *   silence. See `introspection/nameMangling.ts`.
+ * - `walk-recognized-nothing`: the walker traversed a substantial tree
+ *   and none of its eight leaf branches matched (#388). Like
+ *   `names-mangled` this arrives with `captured: true`, and for the
+ *   same reason: capture is not the thing that broke. What it reports
+ *   is the state that used to be invisible — an empty snapshot taken
+ *   from a screen that was NOT empty. `appilotsSelfCheck()` says which
+ *   branch died; this says that one did.
  */
-type IntrospectionFailureReason = 'sentinel-missing-internals' | 'never-mounted';
+type IntrospectionFailureReason = 'sentinel-missing-internals' | 'never-mounted' | 'render-crashed' | 'names-mangled' | 'walk-recognized-nothing';
 interface IntrospectionDiagnostics {
     /** True once a root fiber has been captured. */
     captured: boolean;
@@ -735,6 +824,211 @@ interface IntrospectionDiagnostics {
  */
 declare function getIntrospectionDiagnostics(): IntrospectionDiagnostics;
 
+/**
+ * #386 — did the bundler rename the components we match by name?
+ *
+ * Most of the introspection matches components by name, and
+ * `getTypeName` falls back to the function or class name whenever a
+ * component sets no `displayName`. That name is the one thing a
+ * minifier rewrites.
+ *
+ * Bundling `apps/example-app` twice with Metro 0.81.5 / RN 0.76.9
+ * settles what happens when it runs:
+ *
+ * ```
+ *                          --minify false   --minify true
+ *   function Switch              1                0
+ *   function Modal(              1                0
+ *   function FlatList            1                0
+ *   function SectionList         1                0
+ *   function VirtualizedList     4                0
+ *   displayName='Text'           2                2
+ * ```
+ *
+ * Everything that names itself survives, because a `displayName` is a
+ * string literal. Everything that does not is gone.
+ *
+ * The React Native CLI's own release build does NOT minify — Hermes
+ * makes it unnecessary, so `react-native-xcode.sh` passes
+ * `--minify false` and the Gradle plugin sets
+ * `minifyEnabled = !hermesEnabled`. So the default pipeline is fine.
+ * Expo/EAS, Re.Pack, a custom `minifierConfig`, or `hermesEnabled=false`
+ * are not this repository's to verify.
+ *
+ * The structural fallbacks (a11y role for Switch, the native host for
+ * Modal, the props signature for lists) are what actually keep working.
+ * This probe exists because the failure mode is silent: the app renders
+ * perfectly and only the agent goes blind, exactly like
+ * `sentinel-missing-internals`. A degraded integration should be
+ * legible in a diagnostics dump instead of being guessed at from a
+ * support thread.
+ */
+/**
+ * Components whose runtime name we compare against what we expect.
+ *
+ * Deliberately a `displayName` holder AND a bare one: if BOTH are
+ * wrong, something stranger than minification is going on, and if only
+ * the bare one is wrong we know exactly which fallbacks are carrying
+ * the integration.
+ */
+interface NameManglingProbe {
+    /** True when a name-only component came back under a different name. */
+    mangled: boolean;
+    /** What each probed component actually reported, for a bug report. */
+    observed: Record<string, string | null>;
+}
+
+type GeometryAvailability = 
+/** A host is installed and returning rects. */
+'available'
+/** No host installed — old architecture, or the provider never wired it. */
+ | 'unavailable'
+/** A host is installed but every instance refused to measure. */
+ | 'silent';
+
+/**
+ * walkFiber — Depth-first traversal of a React fiber tree.
+ *
+ * Given a root fiber, visits every descendant and extracts data about
+ * UI primitives (Text, TextInput, TouchableOpacity, Pressable, Switch,
+ * ActivityIndicator, Modal) into a ScreenSnapshot.
+ *
+ * Designed to be robust against monorepo setups where module instances
+ * differ — component types are matched by displayName/name rather than
+ * reference equality.
+ */
+
+/**
+ * How many times each leaf branch of the walker RECOGNIZED a fiber,
+ * over one walk (#388).
+ *
+ * `visitedFibers` answers "did the traversal run?". These answer "did
+ * it understand anything?" — the question that separates a genuinely
+ * empty screen from a walker whose matching stopped working. Every
+ * branch but `adjustable` consults `getTypeName` somewhere, and a name
+ * is the one thing a bundler rewrites, a wrapper component shadows and
+ * an RN upgrade renames. When they break they break in silence, and
+ * all that reaches the agent is an empty snapshot.
+ *
+ * Hits count RECOGNITIONS, not snapshot entries. The two differ on
+ * purpose: `<Text>{''}</Text>` and a de-duplicated button are branches
+ * that fired and produced nothing, and the gap between the counters
+ * and the snapshot is the second thing worth reading here.
+ */
+interface WalkDetectorCounts {
+    Text: number;
+    TextInput: number;
+    Switch: number;
+    ActivityIndicator: number;
+    Modal: number;
+    adjustable: number;
+    pressable: number;
+    /** Containers `isAlwaysListContainer`/`isHeuristicListContainer` claimed. */
+    listContainers: number;
+}
+
+/**
+ * appilotsSelfCheck — "is the integration actually working, in THIS
+ * binary?" (#388)
+ *
+ * Everything the SDK knew about its own health used to be either a
+ * `console.log` (gone from a release build, and unreadable on a device
+ * that is already in review) or `getIntrospectionDiagnostics()`, which
+ * answers a narrower question than it looks like it does: it reports
+ * whether the fiber ROOT was captured, not whether the walk that
+ * follows understood anything. So the single most common degraded
+ * state — root captured, tree walked, nothing recognized — reported as
+ * `{captured: true, failureReason: null}`. Green and blind.
+ *
+ * This is the pull half of the fix. It costs one walk, allocates
+ * nothing that outlives the call, and is meant to be wired to a hidden
+ * dev-menu button: `JSON.stringify(appilotsSelfCheck())`, pasted into a
+ * support thread, replaces the debug-build-and-reproduce round trip
+ * that a design partner cannot always do at all.
+ *
+ * The push half is `walk-recognized-nothing` in
+ * `IntrospectionFailureReason` — the same finding, reached without
+ * anyone asking.
+ *
+ * How to read the report:
+ *
+ *   walk.visitedFibers large + every `detectors` count 0
+ *     → the tree is there and the walker stopped matching it. Compare
+ *       `nameMangling` first: it names the components whose runtime
+ *       name no longer matches.
+ *   detectors.Text > 0 + detectors.Switch === 0 on a screen that
+ *   visibly has a switch
+ *     → one branch, not the walker. That is a walkFiber bug (#167
+ *       territory), and the branch is named.
+ *   registry counts > 0 + detectors all 0
+ *     → auto-tracking is registering components the walk cannot find.
+ *   registry counts 0 + autoTracking.enabled false
+ *     → `enableAppilotsAutoTracking()` never ran. Same empty screen,
+ *       completely different fix.
+ */
+
+interface SelfCheckWalk {
+    visitedFibers: number;
+    skippedHidden: number;
+    elapsedMs: number;
+}
+interface SelfCheckRegistry {
+    fields: number;
+    toggles: number;
+    sliders: number;
+    targets: number;
+    lists: number;
+    /** Interaction elements from the last `captureSnapshot()`, not this walk. */
+    elements: number;
+}
+interface AppilotsSelfCheckReport {
+    sdkVersion: string;
+    reactVersion: string | null;
+    route: string | null;
+    /** Unchanged — the existing capture-health record, verbatim. */
+    introspection: IntrospectionDiagnostics;
+    autoTracking: AutoTrackingState;
+    walk: SelfCheckWalk;
+    /** Per-branch recognitions from the walk this call just performed. */
+    detectors: WalkDetectorCounts;
+    registry: SelfCheckRegistry;
+    /**
+     * The #386 probe, when `<AppilotsProvider>` has run it. Non-null with
+     * `mangled: true` is the first explanation to check for name-based
+     * detectors reading zero.
+     */
+    nameMangling: NameManglingProbe | null;
+    /**
+     * Whether this build can tell an on-screen control from one below the
+     * fold.
+     *
+     * Three states, and they need different answers:
+     *   `unavailable` — the old React Native architecture, which has no
+     *     synchronous window-relative rect. Expected, not a fault.
+     *   `silent`      — a reader IS installed and every instance came back
+     *     empty. Reads identically to the above from outside and is a bug.
+     *   `available`   — working.
+     */
+    geometry: {
+        availability: GeometryAvailability;
+        asked: number;
+        answered: number;
+    };
+}
+/**
+ * Walk the tree once and report what the SDK can see.
+ *
+ * Side-effect-free by design: unlike `captureSnapshot()` it does not
+ * replace the element registry, does not reconcile sliders, and does
+ * not record a diagnostic. Calling it must never change what the next
+ * agent turn observes — a diagnostic that perturbs the thing it
+ * measures is worse than none.
+ *
+ * With no fiber root the walk is skipped and the zeros are honest:
+ * `introspection.captured` is the field that says why.
+ */
+declare function appilotsSelfCheck(): AppilotsSelfCheckReport;
+
 /**
  * createAppilotsInput — HOC factory that wraps any TextInput-like component
  * and auto-registers it with the ComponentRegistry.
@@ -958,4 +1252,13 @@ interface ExecutorContext {
 }
 declare function executeAction(action: AgentAction, context: ExecutorContext): Promise<ActionResult>;
 
-export { ActionBreadcrumb, type ActionBreadcrumbProps, type ActionResult, AgentAction, AgentPermissions, type AppilotsButtonProps, AppilotsChat, type AppilotsChatMode, type AppilotsChatPosition, type AppilotsChatProps, type AppilotsChatTheme, AppilotsEvent, AppilotsI18nProvider, type AppilotsI18nProviderProps, type AppilotsInputProps, AppilotsLocale, type AppilotsRC, AppilotsRegistryProvider, type AppilotsStringKey, type AppilotsStrings, type AppilotsSwitchProps, AppilotsThemeProvider, type AppilotsThemeProviderProps, AppilotsThemeTokens, ChatIcon, type ChatIconProps, ComponentRegistry, ConfirmDialog, type ConfirmDialogProps, type ElementRegistry, type ExecutorContext, FieldEntry, HeadsetIcon, type HeadsetIconProps, type InteractionElementEntry, InteractionElementSnapshot, type IntrospectionDiagnostics, type IntrospectionFailureReason, type ListEntry, type ListRegistry, PartialThemeTokens, ScreenSnapshot, type TailwindResolvedConfig, _patchJsxRuntimes, appilotsTheme, appilotsThemeFromTailwind, captureSnapshot, createAppilotsButton, createAppilotsInput, createAppilotsSwitch, createElementRegistry, createListRegistry, detectDeviceLocale, elementRegistry, enableAppilotsAutoTracking, executeAction, getGlobalConfig, getIntrospectionDiagnostics, initAppilots, isAutoTrackingEnabled, listRegistry, resolveLocale, useAppilotsI18n, useAppilotsTheme, useResolvedRegistry };
+/**
+ * GENERATED by scripts/release/sync-sdk-versions.mjs — do not edit.
+ *
+ * The version `@appilots/sdk` reports on the wire
+ * (`X-Appilots-Sdk-Version`). Kept identical to package.json by the
+ * release flow; `version.test.ts` fails if the two ever disagree.
+ */
+declare const SDK_VERSION = "0.10.0";
+
+export { ActionBreadcrumb, type ActionBreadcrumbProps, type ActionResult, AgentAction, AgentPermissions, type AppilotsButtonProps, AppilotsChat, type AppilotsChatMode, type AppilotsChatPosition, type AppilotsChatProps, type AppilotsChatTheme, AppilotsEvent, AppilotsI18nProvider, type AppilotsI18nProviderProps, type AppilotsInputProps, AppilotsLocale, type AppilotsRC, AppilotsRegistryProvider, type AppilotsSelfCheckReport, type AppilotsStringKey, type AppilotsStrings, type AppilotsSwitchProps, AppilotsThemeProvider, type AppilotsThemeProviderProps, AppilotsThemeTokens, type AutoTrackingState, ChatIcon, type ChatIconProps, ComponentRegistry, ConfirmDialog, type ConfirmDialogProps, type ElementRegistry, type ExecutorContext, FieldEntry, HeadsetIcon, type HeadsetIconProps, InteractionElementEntry, type IntrospectionDiagnostics, type IntrospectionFailureReason, type ListEntry, type ListRegistry, type NameManglingProbe, PartialThemeTokens, SDK_VERSION, ScreenSnapshot, type SelfCheckRegistry, type SelfCheckWalk, type TailwindResolvedConfig, type WalkDetectorCounts, _patchJsxRuntimes, appilotsSelfCheck, appilotsTheme, appilotsThemeFromTailwind, captureSnapshot, createAppilotsButton, createAppilotsInput, createAppilotsSwitch, createElementRegistry, createListRegistry, detectDeviceLocale, elementRegistry, enableAppilotsAutoTracking, executeAction, getAutoTrackingState, getGlobalConfig, getIntrospectionDiagnostics, initAppilots, isAutoTrackingEnabled, listRegistry, resolveLocale, useAppilotsI18n, useAppilotsTheme, useResolvedRegistry };