@sonordev/site-kit 7.1.2 → 7.2.0

package/dist/engage/types.d.ts

@@ -1,254 +1,29 @@
 /**
- * @sonordev/site-kit/engage - Type definitions
+ * @sonordev/site-kit/engage types: deprecated, kept through 7.x so old
+ * imports compile. Engage was retired in Sonor. Chat types live in
+ * `@sonordev/site-kit/chat`, popup types in `@sonordev/site-kit/website/popups`.
+ * Nothing here has runtime code. Removed in 8.0.
  */
-import type { DesignDocument } from './DesignRenderer';
-import type { PopupBlock } from '../website/contract';
-export type WidgetType = 'popup' | 'nudge' | 'bar' | 'chat' | 'slide-in';
-export interface EngageElement {
-    id: string;
-    project_id: string;
-    name: string;
-    type: WidgetType;
-    config: WidgetConfig;
-    targeting: TargetingRules;
-    trigger: TriggerConfig;
-    is_active: boolean;
-    priority: number;
-    created_at: string;
-    updated_at: string;
-    /**
-     * Website → Popups & Banners: the popup as blocks, drawn in the site's own
-     * design by PopupBlocks. Sent alongside design_json, which older site-kits
-     * still draw; a site-kit that knows blocks prefers them.
-     */
-    blocks?: PopupBlock[];
-    /**
-     * Where a blocks popup sits. `type`/`config` describe it for older kits
-     * (which can't pin a bar to the bottom); this says what it actually is.
-     */
-    layout?: {
-        placement: 'popup' | 'bar' | 'slide-in';
-        edge?: 'top' | 'bottom';
-        corner?: 'bottom-left' | 'bottom-right' | 'top-left' | 'top-right';
-        /** The popup's own accent, over the site's. */
-        accent?: string;
-    };
-    design_json?: DesignDocument;
-    compiled_bundle_url?: string;
-    status?: 'draft' | 'published' | 'archived' | 'paused';
-}
-export interface WidgetConfig {
-    /** Visual style */
-    theme?: 'light' | 'dark' | 'custom';
-    position?: 'center' | 'top' | 'bottom' | 'left' | 'right' | 'bottom-left' | 'bottom-right' | 'top-left' | 'top-right';
-    /** Content */
-    title?: string;
-    message?: string;
-    imageUrl?: string;
-    /** CTA */
-    ctaText?: string;
-    ctaUrl?: string;
-    ctaAction?: 'link' | 'close' | 'form' | 'chat';
-    /** Form (if ctaAction is 'form') */
-    formId?: string;
-    /** Styling */
-    backgroundColor?: string;
-    textColor?: string;
-    ctaBackgroundColor?: string;
-    ctaTextColor?: string;
-    borderRadius?: number;
-    /** Behavior */
-    closable?: boolean;
-    showOverlay?: boolean;
-    overlayOpacity?: number;
-}
-export interface TargetingRules {
-    /** Page targeting */
-    pages?: {
-        include?: string[];
-        exclude?: string[];
-    };
-    /** Device targeting */
-    devices?: ('desktop' | 'mobile' | 'tablet')[];
-    /** Visitor targeting */
-    visitor?: {
-        type?: 'new' | 'returning' | 'all';
-        minSessions?: number;
-        maxSessions?: number;
-    };
-    /** Source targeting */
-    source?: {
-        utm_source?: string[];
-        utm_medium?: string[];
-        utm_campaign?: string[];
-        referrer?: string[];
-    };
-    /** Time targeting */
-    schedule?: {
-        startDate?: string;
-        endDate?: string;
-        daysOfWeek?: number[];
-        startTime?: string;
-        endTime?: string;
-        timezone?: string;
-    };
-}
-export interface TriggerConfig {
-    type: 'immediate' | 'delay' | 'scroll' | 'exit-intent' | 'click' | 'custom';
-    /** Delay in seconds (for 'delay' type) */
-    delay?: number;
-    /** Scroll percentage (for 'scroll' type) */
-    scrollPercentage?: number;
-    /** CSS selector (for 'click' type) */
-    clickSelector?: string;
-    /** Custom event name (for 'custom' type) */
-    customEvent?: string;
-    /** Frequency capping */
-    frequency?: {
-        type: 'always' | 'once' | 'once-per-session' | 'every-n-days';
-        days?: number;
-    };
-}
-/** The corner the Echo chat launcher sits in. */
-export type ChatLauncherPosition = 'bottom-right' | 'bottom-left';
-/**
- * Where the Echo chat launcher sits, including the layer it stacks on. The
- * single definition of launcher placement: EngageConfig (here and in
- * `@sonordev/site-kit/layout`), EngageWidget's props and ChatConfig all
- * extend it, so a new placement option is added once. ChatWidget turns it
- * into styles through `chatLauncherStyles` (./launcher-placement).
- */
-export interface ChatLauncherPlacement {
-    /** Corner. Default: 'bottom-right' */
-    position?: ChatLauncherPosition;
-    /**
-     * Distance from the bottom of the viewport to the launcher, as any CSS
-     * length (`'88px'`, `'5.5rem'`, `'calc(4rem + 8px)'`). A number is pixels.
-     * Default: `'20px'`.
-     *
-     * The device's safe-area inset is added on top, so pass the clearance you
-     * want above your own UI, not the inset. The chat popup opens above the
-     * launcher wherever this puts it.
-     *
-     * A `--sk-echo-offset-bottom` custom property set anywhere above the
-     * launcher (`:root`, `body`, a media query, a `:has()` rule) wins over this
-     * value. Use that when the offset depends on the page or the breakpoint,
-     * such as clearing a sticky bar that only some pages render.
-     */
-    offsetBottom?: string | number;
-    /**
-     * Stacking layer. The launcher sits on it and the chat popup one layer
-     * beneath. Default: 9999.
-     *
-     * On EngageConfig and EngageWidget the same number also stacks popups,
-     * nudges and bars, so everything Engage renders shares one layer. Lower it
-     * when the site's own fixed UI (a mobile menu, a cookie banner) has to
-     * cover the chat.
-     */
-    zIndex?: number;
-}
-export interface ChatConfig extends ChatLauncherPlacement {
-    /** Widget position */
-    position: ChatLauncherPosition;
-    /** Widget appearance */
-    buttonIcon?: 'chat' | 'help' | 'custom';
-    buttonColor?: string;
-    buttonText?: string;
-    /** Brand primary color */
-    brandPrimary?: string;
-    /** Welcome message */
-    welcomeMessage?: string;
-    /** Operating hours */
-    operatingHours?: {
-        enabled: boolean;
-        timezone: string;
-        hours: {
-            [day: number]: {
-                start: string;
-                end: string;
-            } | null;
-        };
-    };
-    /** AI vs Live Chat */
-    mode: 'ai' | 'live' | 'hybrid';
-    /** AI settings (if mode is 'ai' or 'hybrid') */
-    aiSettings?: {
-        skillId?: string;
-        handoffToLive?: boolean;
-        handoffKeywords?: string[];
-        /** When AI should suggest handoff based on sentiment or keywords */
-        handoffTriggers?: {
-            negativesentiment?: boolean;
-            keywords?: string[];
-            afterMessages?: number;
-        };
-    };
-    /** Offline mode settings (when no agents available) */
-    offlineMode?: 'form' | 'ai' | 'message';
-    /** Form slug to show when offline (defaults to 'contact') */
-    offlineFormSlug?: string;
-    /** AI fallback when no agents online (hybrid mode) */
-    aiFallbackEnabled?: boolean;
-    /** Custom offline message */
-    offlineMessage?: string;
-}
-/**
- * UI actions the visitor Echo endpoint (POST /echo/public/chat) may return on
- * the JSON response alongside `content` / `conversationId`. The chat widget
- * renders each as an inline card or chip beneath the assistant message.
- *
- * This mirrors the shape Echo's endpoint sends. It is a LOCAL contract on
- * purpose: the kit never imports from the API.
- *
- * - `show_form`            → data.formSlug (+ optional data.prefill) — offer the managed form inline.
- * - `suggest_action`       → data.action + data.message — clickable chip (send message or navigate).
- * - `show_portfolio_item`  → data.slug — the generic widget ignores it (a site's own chat UI handles it).
- */
-export type UiActionType = 'show_form' | 'suggest_action' | 'show_portfolio_item';
-export interface UiAction {
-    type: UiActionType | string;
-    data: Record<string, unknown>;
-}
-export interface ChatMessage {
-    id: string;
-    conversation_id: string;
-    role: 'user' | 'assistant' | 'agent' | 'system';
-    content: string;
-    metadata?: Record<string, unknown>;
-    created_at: string;
-    /** Name of the agent (for agent messages) */
-    sender_name?: string;
-    /** Avatar URL of the agent */
-    sender_avatar?: string;
-}
-export interface ChatConversation {
-    id: string;
-    project_id: string;
-    visitor_id: string;
-    status: 'active' | 'ai' | 'pending_handoff' | 'human' | 'closed';
-    assigned_to?: string;
-    last_message_at: string;
-    created_at: string;
-    /** AI summary of the conversation */
-    ai_summary?: string;
-    /** Visitor info */
-    visitor_name?: string;
-    visitor_email?: string;
-}
-/** Availability status returned by the widget API */
-export interface ChatAvailability {
-    available: boolean;
-    mode: 'live' | 'ai' | 'offline';
-    agentsOnline: number;
-    operatingHoursActive: boolean;
-}
+import type { ChatLauncherPlacement } from '../chat/types';
+export type { ChatAvailability, ChatConfig, ChatConversation, ChatLauncherPlacement, ChatLauncherPosition, ChatMessage, UiAction, UiActionType, } from '../chat/types';
+import type { SitePopup, SitePopupConfig, SitePopupTargeting, SitePopupTrigger, SitePopupType } from '../website/popup-types';
+/** @deprecated Use `SitePopup` from `@sonordev/site-kit/website/popups`. */
+export type EngageElement = SitePopup;
+/** @deprecated Use `SitePopupType` from `@sonordev/site-kit/website/popups`. */
+export type WidgetType = SitePopupType;
+/** @deprecated Use `SitePopupConfig` from `@sonordev/site-kit/website/popups`. */
+export type WidgetConfig = SitePopupConfig;
+/** @deprecated Use `SitePopupTargeting` from `@sonordev/site-kit/website/popups`. */
+export type TargetingRules = SitePopupTargeting;
+/** @deprecated Use `SitePopupTrigger` from `@sonordev/site-kit/website/popups`. */
+export type TriggerConfig = SitePopupTrigger;
+/** @deprecated Use SiteKitLayout's `chat` and `popups` props. */
 export interface EngageConfig extends ChatLauncherPlacement {
     projectId: string;
-    /** Enable chat */
     chatEnabled?: boolean;
-    /** Debug mode */
     debug?: boolean;
 }
+/** @deprecated Unused since Engage was retired. */
 export interface EngageAnalytics {
     element_id: string;
     event_type: 'impression' | 'click' | 'close' | 'submit' | 'dismiss';

package/dist/fleet/FleetHeartbeat.d.ts

@@ -9,7 +9,7 @@
  *
  * It is mounted as a deferred, CHILDLESS SIBLING — never a wrapper — by
  * SiteKitClientProviders, behind the same idle/first-interaction gate as
- * Analytics and Engage, so it never enters the critical hydration path (the
+ * Analytics and chat, so it never enters the critical hydration path (the
  * page must server-render). It renders null and carries no
  * visitor data.
  */

package/dist/fleet/index.js

@@ -1,10 +1,10 @@
 'use client';
-export { FLEET_HEARTBEAT_PATH, FleetHeartbeat, detectNextVersion, sendFleetHeartbeat } from '../chunk-NK4CSJNP.js';
+export { FLEET_HEARTBEAT_PATH, FleetHeartbeat, detectNextVersion, sendFleetHeartbeat } from '../chunk-CF5QNFYU.js';
 export { FLEET_CONTRACT_VERSION, FLEET_MODULES, FLEET_MODULES_MAX, FLEET_SITE_MAX_LENGTH, FLEET_VERSION_MAX_LENGTH, FLEET_VERSION_PATTERN, buildFleetHeartbeatPayload, isFleetModule, normalizeFleetModules, normalizeFleetSite, sanitizeFleetVersion } from '../chunk-ZTZQPYP6.js';
 import '../chunk-YC7ELZS3.js';
 import '../chunk-43OCZ3JA.js';
 import '../chunk-EKBEOXTH.js';
-import '../chunk-3SDOQUUF.js';
-import '../chunk-VDF5DFWT.js';
-import '../chunk-AH5Q262S.js';
+import '../chunk-D6ZC7XKZ.js';
+import '../chunk-K4ZHAURD.js';
+import '../chunk-F24FNCTK.js';
 import '../chunk-PKBMQBKP.js';

package/dist/forms/FormEnhancer.d.ts

@@ -2,23 +2,36 @@
  * FormEnhancer — the only client code a managed form needs up front.
  *
  * Renders the server-rendered shell (<StaticForm>, passed as `children`) until
- * an idle/first-interaction gate fires, then lazy-imports the interactive form
- * and swaps it in. Everything expensive — validation, conditional logic,
+ * an idle/first-interaction gate fires, then imports the interactive form and
+ * swaps it in. Everything expensive — validation, conditional logic,
  * spotlight/stage, celebration, momentum — lives behind that dynamic import,
  * so a page ships this boundary and nothing else in its initial chunk set.
  *
- * The shell is a REAL form the whole time (native action + signed token), so
- * the progression is:
+ * Since 6.3.2 there is no no-JavaScript submit (the native POST door was a
+ * bot magnet and took no real leads), so the shell is a real form a visitor
+ * can read and type into, but only the enhancement sends it. The progression:
  *
- *   no JS at all      -> shell, submits natively. Works.
- *   JS, pre-idle      -> shell, submits natively. Works.
- *   JS, post-idle     -> enhanced form, submits over JSON. Works, with delight.
- *   chunk 404s        -> shell stays. Works. (Never left blank.)
+ *   no JS at all      -> shell; its Send button stays disabled. Nothing is
+ *                        lost to a POST that goes nowhere.
+ *   JS, pre-swap      -> shell. A submit is caught here and replayed by the
+ *                        interactive form the moment it mounts.
+ *   JS, post-swap     -> enhanced form, submits over JSON, with delight.
+ *   chunk 404s        -> shell stays. (Never left blank.)
  *
- * That last line is the invariant to protect: the shell is only removed once
- * the enhancement has actually rendered. Do not "hide the shell then load" —
- * a CDN hiccup would leave a visitor staring at an empty box where the form
- * used to be.
+ * Two rules keep the swap from losing anything (7.2.0):
+ *
+ *   - The shell stays mounted, untouched, until the interactive form's code
+ *     has loaded. The old version re-mounted the shell inside a Suspense
+ *     fallback the moment the gate fired, which reset every control and
+ *     dropped focus mid-click.
+ *   - What's in the shell's controls at the moment of the swap is carried
+ *     into the interactive form (form-dom-values.ts), including a date typed
+ *     into the plain date input. Typing into the shell, or a browser agent
+ *     filling it, also starts the swap at once instead of waiting for idle.
+ *
+ * The invariant to protect: the shell is only removed once the enhancement
+ * has actually rendered. Do not "hide the shell then load" — a CDN hiccup
+ * would leave a visitor staring at an empty box where the form used to be.
  *
  * ── Entrance animation ──────────────────────────────────────────────────
  *

package/dist/forms/ServerForm.d.ts

@@ -17,13 +17,14 @@
  * What each layer is for:
  *
  *   getFormConfig  — server fetch, ISR-cached. No client round trip.
- *   StaticForm     — real HTML form: fields, honeypot, signed native token.
- *                    Submits without JavaScript.
- *   FormEnhancer   — ~1 KB client boundary. Lazy-loads the interactive form
- *                    at idle and swaps it in over the shell.
+ *   StaticForm     — real HTML form: every field and the honeypot, readable
+ *                    by people and crawlers before any script runs.
+ *   FormEnhancer   — ~1 KB client boundary. Loads the interactive form at idle
+ *                    (or as soon as someone types into the shell) and swaps it
+ *                    in, carrying over anything already typed.
  *
- * Set `enhance={false}` for a form that should never load JavaScript at all —
- * the native POST handles it, and the page ships zero form script.
+ * Since 6.3.2 only the enhancement can send a managed form (the no-JavaScript
+ * POST was removed), so every ServerForm enhances.
  *
  * The client `ManagedForm` from `@sonordev/site-kit/forms` still exists and
  * still works; reach for it only when the form must live inside an existing
@@ -44,9 +45,9 @@ export interface ServerFormProps {
     /** Entrance animation for the idle upgrade. See FormEnhancer. */
     enter?: FormEnterAnimation;
     /**
-     * false = ship no form JavaScript at all. The static form still submits via
-     * the native endpoint; you lose inline validation, the experiences, and the
-     * celebration. Good for a footer newsletter field, wrong for a long form.
+     * @deprecated Ignored since 7.2.0. There is no no-JavaScript submit (6.3.2
+     * removed it), so a form that never loads its script can't send, and
+     * `false` only ever produced a form that silently went nowhere.
      */
     enhance?: boolean;
     /**
@@ -65,4 +66,4 @@ export interface ServerFormProps {
     /** Passed through to getFormConfig (api key / url / revalidate). */
     configOptions?: GetFormConfigOptions;
 }
-export declare function ServerForm({ formId, className, experience, enter, enhance, defer, initialConfig, configOptions, defaultValues, }: ServerFormProps): Promise<React.JSX.Element>;
+export declare function ServerForm({ formId, className, experience, enter, defer, initialConfig, configOptions, defaultValues, }: ServerFormProps): Promise<React.JSX.Element>;

package/dist/forms/StaticForm.d.ts

@@ -8,7 +8,9 @@
  * (/api/public/forms/submit-native, a signed token in the page HTML) took
  * 10,500 bot submissions across the fleet and not one real lead, because a bot
  * only had to download the page to borrow the token. `method="post"` stays so
- * a click before hydration never puts the visitor's details in a URL.
+ * nothing typed can end up in a URL, and since 7.2.0 the Send button renders
+ * disabled until FormEnhancer is ready to catch the submit, so a click before
+ * hydration no longer posts the page to itself and throws the input away.
  *
  * ── Why this exists ─────────────────────────────────────────────────────
  *

package/dist/forms/field-autocomplete.d.ts

@@ -0,0 +1,28 @@
+/**
+ * @sonordev/site-kit/forms - autocomplete tokens for managed form fields
+ *
+ * Browser autofill, password managers and AI agents filling a form for
+ * someone all read a field's `autocomplete` token to know what it wants.
+ * Without one they guess from the label, and a guess is how a phone number
+ * ends up in the company field. Managed forms shipped no tokens at all before
+ * 7.2.0.
+ *
+ * Single source of truth for which token a managed field gets. FormField is
+ * the only caller; every experience (classic, spotlight, stage, the static
+ * shell) renders its controls through FormField.
+ *
+ * Precedence: the field's CRM destination (`destination_field`, set in
+ * Sonor) > its input type > its slug > its label. When nothing matches the
+ * attribute is omitted. A wrong token is worse than none, so matching is
+ * deliberately narrow: exact keys only, plus Sonor's random slug suffixes
+ * (`email_k3x9pq2m`).
+ */
+import type { FormField } from './types';
+/**
+ * The `autocomplete` token for one managed field, or undefined to omit it.
+ * Only text-like inputs and selects get one; a message box, a date or a
+ * checkbox never does.
+ */
+export declare function autocompleteFor(field: Pick<FormField, 'field_type' | 'slug' | 'label'> & {
+    destination_field?: string;
+}): string | undefined;

package/dist/forms/form-dom-values.d.ts

@@ -0,0 +1,42 @@
+/**
+ * @sonordev/site-kit/forms - reading a managed form's values out of the DOM
+ *
+ * Two moments need what is actually in the controls rather than what React
+ * last heard about:
+ *
+ *   1. The enhancement swap. The server-rendered shell is plain HTML, so
+ *      whatever a visitor (or an agent) typed before the interactive form
+ *      loaded lives only in the DOM. FormEnhancer reads it here and seeds the
+ *      interactive form with it. Before 7.2.0 the swap threw it away.
+ *   2. A submit. A browser agent can set a control's value without the input
+ *      event React listens for. FormClient compares the DOM with its state
+ *      at submit time and adopts anything it missed, instead of rejecting a
+ *      filled form as empty.
+ *
+ * Single source of truth for turning form controls back into field values,
+ * typed the way FormClient stores them (checkbox groups and multi-selects as
+ * arrays, a lone checkbox as a boolean, ratings and sliders as numbers).
+ */
+import type { FormField } from './types';
+/**
+ * Nothing worth seeding or adopting: an empty value (field-rules.ts), an
+ * unticked lone checkbox, or whitespace.
+ */
+export declare function isBlank(value: unknown): boolean;
+/**
+ * The value of every answerable field, read from the form's controls.
+ * Fields with no control in the DOM (another step, conditionally hidden) and
+ * blank fields are left out, as is the honeypot.
+ */
+export declare function readFormControlValues(form: HTMLFormElement | null | undefined, fields: FormField[] | undefined, honeypotName: string): Record<string, unknown>;
+/**
+ * What the shell holds beyond each field's configured default: the part of
+ * the shell worth carrying into the interactive form.
+ */
+export declare function shellValuesToCarry(form: HTMLFormElement | null | undefined, fields: FormField[] | undefined, honeypotName: string): Record<string, unknown>;
+/**
+ * Values present in the DOM that React state doesn't have: a control set
+ * without an input event. Only fills a blank state value; never overrides
+ * something the visitor typed through React.
+ */
+export declare function unseenControlValues(form: HTMLFormElement | null | undefined, fields: FormField[] | undefined, honeypotName: string, state: Record<string, unknown>): Record<string, unknown>;

package/dist/forms/index.js

@@ -1,21 +1,23 @@
 'use client';
 export { FormCelebration } from '../chunk-YGGDU6C3.js';
-export { FormClient, ManagedForm } from '../chunk-CSTQDNGK.js';
-import '../chunk-D5EC5KVO.js';
+export { FormClient, ManagedForm } from '../chunk-IAM3D3RL.js';
+import '../chunk-D5DCBD4Y.js';
 export { DatePicker } from '../chunk-SOD2F6C2.js';
-export { FormEnhancer } from '../chunk-VLARKWZU.js';
+export { FormEnhancer } from '../chunk-OWZ7ATLZ.js';
 import '../chunk-YC7ELZS3.js';
 import '../chunk-DXO6SBMD.js';
-export { FormField as FormFieldComponent } from '../chunk-LUXVWITO.js';
-export { useForm, useFormTracking } from '../chunk-V6FDQLR7.js';
-import '../chunk-AQSNPZY4.js';
+export { FormField as FormFieldComponent } from '../chunk-4NTBQNHA.js';
+export { useForm, useFormTracking } from '../chunk-FR6BYFPC.js';
+import '../chunk-Q6E4OPGG.js';
+import '../chunk-C2FZBUSS.js';
 export { DEFAULT_FORM_SUCCESS_MESSAGE } from '../chunk-5SQK3D53.js';
+import '../chunk-HW7B43E5.js';
 import '../chunk-NJCTQH2P.js';
 import '../chunk-L2V5PUFN.js';
 import '../chunk-GJWI74ZZ.js';
-import { sonorFetch } from '../chunk-3SDOQUUF.js';
-import '../chunk-VDF5DFWT.js';
-import '../chunk-AH5Q262S.js';
+import { sonorFetch } from '../chunk-D6ZC7XKZ.js';
+import '../chunk-K4ZHAURD.js';
+import '../chunk-F24FNCTK.js';
 import '../chunk-PKBMQBKP.js';
 
 // src/forms/formsApi.ts

package/dist/forms/server.js

@@ -1,11 +1,13 @@
-export { ServerForm, getFormConfig } from '../chunk-V3PUVBME.js';
-import '../chunk-VLARKWZU.js';
+export { ServerForm, getFormConfig } from '../chunk-5V2V5C3Y.js';
+import '../chunk-OWZ7ATLZ.js';
 import '../chunk-YC7ELZS3.js';
-export { StaticForm } from '../chunk-CIG5UL2S.js';
+export { StaticForm } from '../chunk-ZTLMPUO6.js';
 import '../chunk-DXO6SBMD.js';
-import '../chunk-LUXVWITO.js';
+import '../chunk-4NTBQNHA.js';
 import '../chunk-X6F6SO4S.js';
 import '../chunk-MH2DSGC6.js';
+import '../chunk-C2FZBUSS.js';
 import '../chunk-5SQK3D53.js';
+import '../chunk-HW7B43E5.js';
 import '../chunk-NJCTQH2P.js';
 import '../chunk-PKBMQBKP.js';

package/dist/forms/static.js

@@ -1,6 +1,7 @@
-export { StaticForm } from '../chunk-CIG5UL2S.js';
+export { StaticForm } from '../chunk-ZTLMPUO6.js';
 import '../chunk-DXO6SBMD.js';
-import '../chunk-LUXVWITO.js';
+import '../chunk-4NTBQNHA.js';
 import '../chunk-5SQK3D53.js';
+import '../chunk-HW7B43E5.js';
 import '../chunk-NJCTQH2P.js';
 import '../chunk-PKBMQBKP.js';

package/dist/forms/submitForm.d.ts

@@ -24,13 +24,20 @@ export interface SubmitFormArgs {
     honeypotValue: string;
     /** Timestamp (ms) the form was first rendered — a weak anti-bot timing signal. */
     formLoadedAt: number;
+    /**
+     * The browser reported that an AI agent pressed submit (WebMCP's
+     * `SubmitEvent.agentInvoked`). Sent so Sonor can tag the lead for the
+     * business; it is the browser's word, so it never changes how the
+     * submission is checked.
+     */
+    agentInvoked?: boolean;
 }
 /**
  * Submit a managed form. Throws on failure (network, timeout, or a non-2xx
  * response) with a human-readable message; resolves with the parsed API
  * response on success.
  */
-export declare function submitForm({ config, values, honeypotValue, formLoadedAt, }: SubmitFormArgs): Promise<FormSubmitResult>;
+export declare function submitForm({ config, values, honeypotValue, formLoadedAt, agentInvoked, }: SubmitFormArgs): Promise<FormSubmitResult>;
 /**
  * The receipt Sonor returns plus the values that were sent. `onSuccess`
  * callers need the values (free-audit reads the website and email back), and

package/dist/forms/types.d.ts

@@ -127,6 +127,45 @@ export interface ConditionalLogic {
  * on purpose (a bot must not learn it was caught), so nothing here says
  * whether the lead was accepted, routed or scored.
  */
+/**
+ * Options for a managed form's `submit()`. All optional; `submit()` with no
+ * argument behaves exactly as it always has.
+ */
+export interface FormSubmitOptions {
+    /**
+     * The browser reported that an AI agent pressed submit (WebMCP's
+     * `SubmitEvent.agentInvoked`). Sonor tags the lead so the business can see
+     * how agent-sent leads compare; it changes nothing else about the submit.
+     */
+    agentInvoked?: boolean;
+    /**
+     * Values found in the form's controls that React state never received (a
+     * control set without an input event). Merged over blank state values
+     * before validating. See form-dom-values.ts.
+     */
+    domFills?: Record<string, unknown>;
+}
+/**
+ * What `submit()` resolves with. Callers that ignore it keep working; an
+ * agent that submitted through WebMCP is handed this as its result.
+ */
+export type FormSubmitOutcome = {
+    status: 'sent';
+    message: string;
+    submissionId?: string;
+} | {
+    status: 'invalid';
+    errors: Record<string, string>;
+} | {
+    status: 'failed';
+    message: string;
+} | {
+    status: 'busy';
+} | {
+    status: 'next_step';
+    step: number;
+    totalSteps: number;
+};
 export interface FormSubmitResult {
     success: boolean;
     /** The form_submissions row id (same as submissionId). */
@@ -197,7 +236,7 @@ export interface ExperienceRenderProps {
     isFieldVisible: (field: FormField) => boolean;
     fieldIsComplete: (field: FormField) => boolean;
     applyFieldError: (slug: string, error: string) => void;
-    submit: () => Promise<void>;
+    submit: (options?: FormSubmitOptions) => Promise<FormSubmitOutcome>;
     trackStepChange: (step: number) => void;
     /** Pass to each FormField's onFocus/onBlur (field_interactions). */
     trackFieldFocus: (slug: string) => void;
@@ -269,7 +308,7 @@ export interface FormRenderProps {
     /** Go to specific step */
     goToStep: (step: number) => void;
     /** Submit the form */
-    submit: () => Promise<void>;
+    submit: (options?: FormSubmitOptions) => Promise<FormSubmitOutcome>;
     /** Set field value */
     setFieldValue: (key: string, value: unknown) => void;
     /** Check if field should be visible (conditional logic) */