@sonordev/site-kit 7.1.2 → 7.2.0

package/src/{engage → chat}/README.md

@@ -1,58 +1,69 @@
-# Engage — `@sonordev/site-kit/engage`
+# Website chat — `@sonordev/site-kit/chat`
 
-Popups, nudges, bars, slide-ins, and chat widgets — all configured from the Sonor dashboard.
+Echo's chat launcher and conversation on your site, configured in Sonor
+(Messages → Chat settings). AI answers, live handoff to your team, and an
+offline form when nobody's around.
 
 ## Usage
 
-Auto-included by `SiteKitLayout`. For standalone use:
+`SiteKitLayout` mounts it for you, after the page goes idle:
+
+```tsx
+<SiteKitLayout>{children}</SiteKitLayout>                          // chat on (default)
+<SiteKitLayout chat={{ offsetBottom: '88px' }}>{children}</SiteKitLayout>
+<SiteKitLayout chat={false}>{children}</SiteKitLayout>             // no chat
+```
+
+On a site without `SiteKitLayout`, mount `SiteChat` the same way:
 
 ```tsx
 'use client'
-import { EngageWidget } from '@sonordev/site-kit/engage'
-
-export default function Layout({ children }) {
-  return (
-    <>
-      {children}
-      <EngageWidget />
-    </>
-  )
+import { SiteChat } from '@sonordev/site-kit/chat'
+
+export function Chat() {
+  return <SiteChat position="bottom-right" />
 }
 ```
 
+`SiteChat` waits for the browser to go idle, skips cross-origin frames and
+localhost (like analytics), and downloads the chat widget only when it
+renders. `ChatWidget` is the widget itself, for a page that resolves those
+choices on its own.
+
 ## Props
 
 ```ts
-interface EngageWidgetProps {
-  apiUrl?: string             // Default: https://api.sonor.io
-  apiKey?: string             // From SiteKitLayout or env
-  projectId?: string          // For chat routing
+interface SiteChatProps {
+  apiUrl?: string                            // Default: from SiteKitLayout, else https://api.sonor.io
+  apiKey?: string                            // Default: from SiteKitLayout
+  projectId?: string                         // For chat routing. Resolved from the key when absent
   position?: 'bottom-right' | 'bottom-left'  // Default: 'bottom-right'
   offsetBottom?: string | number             // Default: '20px'. See "Launcher placement"
-  zIndex?: number             // Default: 9999. Popups, nudges, bars and the chat. See "Stacking"
-  chatEnabled?: boolean       // Default: true. See "The chat switch"
-  debug?: boolean
+  zIndex?: number                            // Default: 9999. See "Stacking"
+  allowInFrame?: boolean                     // Show inside a cross-origin frame. Default: false
+  allowLocalhost?: boolean                   // Show on localhost. Default: false
 }
 ```
 
-Through `SiteKitLayout`, the same options go in `engage={{ ... }}`.
+Through `SiteKitLayout`, the placement options go in `chat={{ ... }}`. The
+deprecated `engage={{ ... }}` still works through 7.x.
 
 ## The chat switch
 
-Echo follows the project's **Enable Chat Widget** switch in Sonor (Engage,
-Chat settings). A project that has never saved chat settings counts as on, so
-Echo is on by default and only an owner who switches it off hides it. It also
-needs the project's **Engage** module on (Project Settings); without it Sonor
-answers off, since the chat has nowhere to take a visitor's message.
+Echo follows the project's **Show the chat widget** switch in Sonor
+(Messages → Chat settings). A project that has never saved chat settings
+counts as on, so Echo is on by default and only an owner who switches it off
+hides it. It also needs the project's **Website chat** module on (Project
+Settings); without it Sonor answers off, since the chat has nowhere to take a
+visitor's message.
 
 - The launcher appears once `GET /engage/widget/config` answers. Nothing
   renders before that, so a switched-off site never flashes a launcher, and
   it never starts Echo's availability polling.
 - If the config can't be fetched, the launcher stays hidden. The chat can't
   run without the API anyway.
-- `chatEnabled: false` (or `engage={false}`) in code still turns chat off
-  whatever the switch says. Code can turn Echo off; it can't force it on over
-  the owner's switch.
+- `chat={false}` in code still turns chat off whatever the switch says. Code
+  can turn Echo off; it can't force it on over the owner's switch.
 
 ## Liquid Glass (6.1.0)
 
@@ -75,7 +86,7 @@ recipe (`src/shared/glass.tsx`), the same material as the mobile CTA bar
   panel, and otherwise pulls it toward black (light panel) or white (dark
   panel) just far enough to clear it: `#d4af37` gold becomes `#887023`. Fills
   (launcher, avatar, the visitor's bubbles, buttons) keep the raw brand. One
-  helper decides this, `src/engage/brand-color.ts`; route any new brand
+  helper decides this, `src/chat/brand-color.ts`; route any new brand
   foreground through it. `--sk-primary` can be hex, `rgb()` or `hsl()`.
 - **Fields are 16px.** iOS Safari zooms the whole page into any focused field
   under 16px; the chat input and the inline Echo forms were 13.5-14px.
@@ -104,7 +115,7 @@ it without `!important`. Don't write that override; declare the offset instead.
 **A fixed offset, every page:** pass `offsetBottom`.
 
 ```tsx
-<SiteKitLayout engage={{ offsetBottom: '88px' }}>{children}</SiteKitLayout>
+<SiteKitLayout chat={{ offsetBottom: '88px' }}>{children}</SiteKitLayout>
 ```
 
 Any CSS length works (`'5.5rem'`, `'calc(4rem + 8px)'`); a number is pixels.
@@ -148,13 +159,14 @@ popup maxHeight = 100dvh - launcher bottom - 100px
 
 ### Stacking
 
-`zIndex` is the one layer everything Engage renders sits on: popups, nudges,
-bars and the chat launcher. The chat popup sits one layer beneath the
-launcher. The default is 9999, above almost anything a site draws, so lower it
-when your own fixed UI (a mobile menu, a cookie banner) has to cover the chat:
+`zIndex` is the layer the chat launcher sits on, with the chat window one
+layer beneath it. Through `SiteKitLayout` the same number also stacks the
+site's popups, banners and toasts. The default is 9999, above almost anything
+a site draws, so lower it when your own fixed UI (a mobile menu, a cookie
+banner) has to cover the chat:
 
 ```tsx
-<SiteKitLayout engage={{ zIndex: 40 }}>{children}</SiteKitLayout>
+<SiteKitLayout chat={{ zIndex: 40 }}>{children}</SiteKitLayout>
 ```
 
 ```
@@ -162,9 +174,9 @@ launcher z-index = zIndex (default 9999)
 popup z-index    = zIndex - 1
 ```
 
-At `zIndex` 0 or below the popup shares the launcher's layer instead, because
--1 would put it behind the page's own content. The launcher still paints on
-top.
+At `zIndex` 0 or below the chat window shares the launcher's layer instead,
+because -1 would put it behind the page's own content. The launcher still
+paints on top.
 
 ### Layout vs visual viewport on phones
 
@@ -194,29 +206,9 @@ It's opt-in: while a field has focus the gap grows to the keyboard's height,
 so everything that reads it rides above the keyboard. `useVisualViewportGap()`
 is the hook form for an existing client component.
 
-## Element Types
-
-| Type | Description |
-|------|-------------|
-| `popup` | Modal overlay with CTA |
-| `nudge` | Small corner notification |
-| `bar` | Top/bottom sticky bar |
-| `slide-in` | Side panel |
-| `chat` | AI/live chat widget |
+## Chat config
 
-## Targeting & Triggers
-
-All configured in the Sonor dashboard — no code changes needed:
-
-- **Page targeting** — include/exclude paths with wildcard support
-- **Device targeting** — desktop, mobile, tablet
-- **Visitor targeting** — new vs returning visitors
-- **Triggers** — immediate, delay (seconds), scroll (%), exit-intent, click, custom
-- **Frequency capping** — once, once-per-session, every N days
-
-## Chat Widget
-
-Supports AI mode (Echo), live mode, and hybrid (AI + human handoff):
+AI mode (Echo), live mode, and hybrid (AI with a human handoff). `ChatWidget` takes these as `config`; Sonor sends the rest from Chat settings:
 
 ```ts
 interface ChatConfig {
@@ -236,6 +228,15 @@ interface ChatConfig {
 }
 ```
 
-## Tracking
+## Popups
+
+Popups, banners and toasts are their own module now:
+[Popups and banners](../website/README.md) (`@sonordev/site-kit/website/popups`).
+
+## `@sonordev/site-kit/engage` (deprecated)
 
-Impressions and clicks are automatically tracked via the Sonor API. Shares visitor ID (`_sk_vid`) with Analytics for cross-module attribution.
+Engage was retired in Sonor. Its entry stays through 7.x so old imports keep
+building: `ChatWidget` and the chat types re-export from here, and
+`EngageWidget` draws `SiteChat` and `SitePopups`. Engage Studio's renderer
+(`DesignRenderer`) is gone; popups render from blocks. Import
+`@sonordev/site-kit/chat` and `@sonordev/site-kit/website/popups` instead.

package/src/forms/README.md

@@ -78,12 +78,12 @@ import { useForm } from '@sonordev/site-kit/forms'
 
 export function ContactForm() {
   const {
-    fields, values, errors, setFieldValue, submit, isSubmitting,
+    fields, values, errors, setFieldValue, handleSubmit, toolAttributes, isSubmitting,
     step, totalSteps, isMultiStep, nextStep, prevStep, isLastStep,
   } = useForm('contact-form')
 
   return (
-    <form onSubmit={(e) => { e.preventDefault(); submit() }}>
+    <form {...toolAttributes} onSubmit={handleSubmit}>
       {fields.map(field => (
         <div key={field.slug}>
           <label>{field.label}</label>
@@ -166,7 +166,12 @@ interface UseFormReturn {
   canGoPrev: boolean
   isLastStep: boolean
   validate: () => boolean
-  submit: () => Promise<void>
+  // Resolves with what happened: { status: 'sent' | 'invalid' | 'failed' | 'busy' | 'next_step', ... }
+  submit: (options?: FormSubmitOptions) => Promise<FormSubmitOutcome>
+  // A ready-made <form onSubmit>: steps or submits, and answers an AI agent (see below)
+  handleSubmit: (event: FormEvent<HTMLFormElement>) => void
+  // WebMCP attributes for your <form>; null until the config loads
+  toolAttributes: { toolname: string; tooldescription: string } | null
   isSubmitting: boolean
   isComplete: boolean
   reset: () => void
@@ -212,6 +217,47 @@ it, so Sonor refuses those before anything is written: the visitor sees an
 error and you get no lead. Submit through site-kit, and define the form's
 fields in Sonor so both can render and validate them.
 
+## Agent-ready forms (7.2.0)
+
+People increasingly ask an AI assistant to fill out a form for them: a quote
+request, a booking, a newsletter signup. Assistants act on what the page's
+markup says each control is, so managed forms now say it clearly. There's
+nothing to configure.
+
+- **Autocomplete tokens.** Name, email, phone, company, website and address
+  fields carry the right `autocomplete` token (`given-name`, `email`, `tel`,
+  `organization`, `url`, `postal-code`, ...), read from the field's CRM
+  destination in Sonor, then its type, slug and label. Browser autofill and
+  password managers use the same tokens.
+- **Accessible wiring.** Error and help text are tied to their control
+  (`aria-describedby`), an errored control says so (`aria-invalid`), radio and
+  checkbox groups are named by their question, and rating stars by their
+  value.
+- **WebMCP.** Every interactive managed form carries the declarative WebMCP
+  attributes (`toolname`, `tooldescription`), so a browser agent that supports
+  WebMCP can treat it as a tool. It fills the same fields a person would, and
+  the submit runs the same validation. There's no `toolautosubmit`: the
+  assistant fills the form and the person it's helping presses Send.
+  Browsers without WebMCP ignore the attributes.
+- **Agent-sent leads are tagged.** When the browser reports that an agent
+  pressed submit (`SubmitEvent.agentInvoked`), the submission carries that
+  flag and the lead is tagged in Sonor, so you can see how those leads compare
+  over time. It's the browser's word, so it never changes how a submission is
+  checked. The agent is handed the outcome of its submit (`respondWith`).
+- **Nothing typed before the form loads is lost.** `ServerForm` renders the
+  form in the page HTML and loads the interactive version at idle. Since
+  7.2.0, typing into the server-rendered form starts that upgrade at once and
+  what was typed carries over, and a Send pressed before the upgrade is held
+  and sent the moment it lands. The server-rendered Send button stays disabled
+  until the page can catch the click.
+
+With `useForm`, spread `toolAttributes` on your `<form>` and use
+`handleSubmit` as its `onSubmit` to get the same behavior.
+
+`ServerForm`'s `enhance` prop is ignored since 7.2.0. Only the interactive
+form can send a managed form, so `enhance={false}` only ever produced a form
+that silently went nowhere.
+
 ## Styles
 
 ```tsx

package/src/layout/README.md

@@ -28,9 +28,11 @@ interface SiteKitLayoutProps {
   children: React.ReactNode
   apiKey?: string                         // Defaults to SONOR_API_KEY env var
   apiUrl?: string                         // Defaults to SONOR_API_URL, then https://api.sonor.io
-  projectId?: string                      // For Engage chat routing (auto-resolved if omitted)
+  projectId?: string                      // For chat routing (auto-resolved if omitted)
   analytics?: boolean | AnalyticsConfig   // Default: true
-  engage?: boolean | EngageConfig         // Default: true
+  chat?: boolean | ChatLayoutConfig       // Default: true (website chat; config = launcher placement)
+  popups?: boolean                        // Default: true (Website → Popups & Banners)
+  engage?: boolean | EngageConfig         // Deprecated: false turns chat and popups off; an object configures the launcher
   signal?: boolean | SignalConfig         // Default: false
   sitemapSync?: boolean                   // Default: false (build-time + server reconciler own this)
   fleet?: boolean                         // Default: true (once-per-session kit version heartbeat)
@@ -43,7 +45,7 @@ interface SiteKitLayoutProps {
 }
 ```
 
-Module options live with each module: [Analytics](../analytics/README.md) (`trackPageViews`, `excludePaths`, `site`, `allowInFrame`, `allowLocalhost`) and [Engage](../engage/README.md) (`position`, `chatEnabled`, and launcher placement).
+Module options live with each module: [Analytics](../analytics/README.md) (`trackPageViews`, `excludePaths`, `site`, `allowInFrame`, `allowLocalhost`) [Website chat](../chat/README.md) (`position`, `offsetBottom`, `zIndex`, `allowInFrame`) and [Popups and banners](../website/README.md).
 
 ## What It Composes
 
@@ -54,12 +56,13 @@ Module options live with each module: [Analytics](../analytics/README.md) (`trac
 
 **Client-side (lazy-loaded island):**
 - `AnalyticsProvider` — page views, scroll depth, heatmap clicks, Web Vitals
-- `EngageWidget` — popups, nudges, chat
+- `SitePopups` — popups, banners and toasts
+- `SiteChat` — website chat (Echo)
 - `SignalBridge` — A/B experiments, behavior tracking (opt-in)
 - `SitemapSync` — parses `/sitemap.xml` and syncs to Sonor (opt-in)
 - `FleetHeartbeat` — reports the kit version and enabled modules once per session
 
-Since 4.0.0 none of these wrap your page. `{children}` renders first and every module mounts after it as a childless sibling, so `SiteKitLayout` never pushes a route to client rendering. Analytics, Engage, SitemapSync and the heartbeat also wait for window load + idle (or the first interaction) unless you pass `defer={false}`. `SignalBridge` isn't deferred, so experiment variants apply early. Visitor and session IDs come from a shared storage singleton rather than a provider.
+Since 4.0.0 none of these wrap your page. `{children}` renders first and every module mounts after it as a childless sibling, so `SiteKitLayout` never pushes a route to client rendering. Analytics, chat, popups, SitemapSync and the heartbeat also wait for window load + idle (or the first interaction) unless you pass `defer={false}`. `SignalBridge` isn't deferred, so experiment variants apply early. Visitor and session IDs come from a shared storage singleton rather than a provider.
 
 ## Note
 

package/src/seo/README.md

@@ -143,6 +143,8 @@ It renders one `application/ld+json` script (an `@graph` when there's more than
 - a `BreadcrumbList` built from the path, when there isn't one already and the project has a site URL (skipped on `/`)
 - a speakable `WebPage` or `Article` node, when `speakable`, `pageName` and `pageUrl` are all set
 
+Everything Sonor supplies (its schema rows, `managed_schema` and the entity graph) loses any template placeholder first. A node whose values are a template's unfilled slots is dropped: a URL on a reserved example domain (`example.com`), a name like "Example" or "Your Business Name", a placeholder phone such as `+1-000-000-0000`, a slot like `[Resident Name]` or `{plan.name}`, or an object that's only a note about what goes there. Its real siblings and parents stay, so an `FAQPage` keeps its questions when only its publisher was a placeholder, and the `BreadcrumbList` fallback still applies when a placeholder breadcrumb is dropped. Your `additionalSchemas` are never touched. The rule is `@sonordev/contracts/schema-placeholders`.
+
 | Prop | Default | Notes |
 |------|---------|-------|
 | `path` | | Required. |
@@ -157,7 +159,7 @@ It's wrapped in `Suspense`, so the fetch never holds up the rest of the page. Th
 
 ### `<LLMSchema path>`
 
-Renders the page's `managed_llm_schema` as a `WebPage` JSON-LD script marked `data-llm-optimized="true"`, linked to the site's `WebSite` node when the project has a site URL. It renders nothing when the page has no LLM schema.
+Renders the page's `managed_llm_schema` as a `WebPage` JSON-LD script marked `data-llm-optimized="true"`, linked to the site's `WebSite` node when the project has a site URL. It renders nothing when the page has no LLM schema, or when that schema is a template placeholder (see `<ManagedSchema>`).
 
 ### Schema helpers
 

package/src/sync/README.md

@@ -59,6 +59,16 @@ Expired meeting details and time reservations show a recovery action. Guests can
 
 Navigation is disabled while a reservation or booking request is running. Stale responses cannot reopen a previous step, and holds created after the widget is removed are released.
 
+## Accessibility
+
+Screen readers and AI agent browsers (which act on elements by their accessible names) can book without guessing:
+
+- **Days** are buttons named with the full date, year included: "Wednesday, October 7, 2026". The picked day is pressed (`aria-pressed="true"`), and days that can't be booked are disabled.
+- **Times** are buttons named with the time and the date, "10:30 AM, Wednesday, October 7, 2026", in the booking's time zone. They still show just the time. The picked time is pressed.
+- **Confirm**, the button that reserves the picked time, is named "Confirm 10:30 AM, Wednesday, October 7, 2026".
+
+Every name contains what its button shows (a time's and Confirm's start with it), so voice control can still target a button by its visible text (WCAG 2.5.3). None of this changes what the widget sends.
+
 ## API Functions
 
 ```ts

package/src/website/README.md

@@ -0,0 +1,133 @@
+# Popups and banners — `@sonordev/site-kit/website/popups`
+
+The popups, banners and toasts you publish in Sonor (Website → Popups &
+Banners), shown on your site where and when you set them, in the site's own
+design.
+
+## Usage
+
+`SiteKitLayout` mounts it for you, after the page goes idle:
+
+```tsx
+<SiteKitLayout>{children}</SiteKitLayout>                  // popups on (default)
+<SiteKitLayout popups={false}>{children}</SiteKitLayout>   // no popups
+```
+
+On a site without `SiteKitLayout`, mount `SitePopups` the same way:
+
+```tsx
+'use client'
+import { SitePopups } from '@sonordev/site-kit/website/popups'
+
+export function Popups() {
+  return <SitePopups />
+}
+```
+
+A project with nothing published costs one request and draws nothing. The
+renderer downloads only when a popup is about to open.
+
+## Props
+
+```ts
+interface SitePopupsProps {
+  apiUrl?: string          // Default: from SiteKitLayout, else https://api.sonor.io
+  apiKey?: string          // Default: from SiteKitLayout
+  zIndex?: number          // The layer popups, banners and toasts sit on. Default: 9999
+  allowInFrame?: boolean   // Show inside a cross-origin frame. Default: false
+  allowLocalhost?: boolean // Show on localhost. Default: false
+  debug?: boolean
+}
+```
+
+Through `SiteKitLayout`, `zIndex` comes from `chat={{ zIndex }}`, so the chat
+launcher and popups share one layer.
+
+## What shows
+
+Each popup is a set of blocks (heading, formatted text, image, button,
+divider) drawn in your site's design: its colors, fonts, radius and buttons.
+`SiteKitLayout` measures the design from the home page at idle and reports it
+to Sonor, so the popup builder previews popups the way they'll look. Its
+`design` prop declares any part of it yourself
+(`design={{ primary: 'var(--brand)', fontHeading: 'Fraunces, serif' }}`).
+
+| Placement | What it is |
+|-----------|------------|
+| Popup | Centred over a dimmed page. One at a time: a second waits until the first closes |
+| Banner | A bar along the top or bottom edge |
+| Toast | A small card in a corner (slide-in) |
+
+## Targeting and triggers
+
+All set in Sonor, no code changes:
+
+- **Pages**: include and exclude paths, with `*` for a prefix (`/services/*`)
+- **Devices**: desktop, mobile, tablet
+- **Schedule**: start and end dates
+- **Trigger**: immediately, after a delay, at a scroll depth, or on exit intent
+- **Frequency**: once, once per session, or every N days. Closing a popup and
+  pressing its button both count as seen.
+
+A popup targeted at one page leaves when the visitor navigates away from it.
+
+### Popups wait for forms
+
+A popup or toast that opens on its own first checks whether the visitor is in
+the middle of a form, and waits while they are. Mid-form means:
+
+- focus is in a form field, or in a card field embedded in a form;
+- a form has a field they've filled in and haven't sent yet;
+- a site-kit form is sending.
+
+It opens a moment after focus leaves the form, or once the form has been sent
+and cleared. It never gives up: while the visitor stays mid-form, it keeps
+waiting. Banners show at once, since they don't take focus or hide the page.
+
+Why it matters: a modal popup takes focus and hides the rest of the page from
+assistive technology while it's open. Opening one mid-form throws a person out
+of the field they're typing in, and an AI agent browser filling the form for
+someone (agents act on the accessibility tree) loses every field it was about
+to fill.
+
+## Accessibility
+
+Popups, toasts and banners are built so people and agent browsers can find
+them and their controls by name:
+
+- **A popup** is a modal dialog (`role="dialog"`, `aria-modal="true"`) named
+  by its heading. It takes focus when it opens, keeps Tab inside, closes on
+  Escape or a click outside it, and puts focus back where it was.
+- **A toast** is a named, non-modal dialog, and **a banner** is a named
+  region. Both close on Escape and leave focus where it is.
+- **Close buttons are named "Close"**, whatever they show.
+
+## Tracking
+
+Each popup's impression (once half of it is on screen) and button presses are
+counted in Sonor, against the same visitor ID (`_sk_vid`) analytics uses.
+
+## Drawing one popup yourself
+
+`PopupBlocks` is the renderer `SitePopups` uses, for drawing one popup from
+its blocks (a preview, a custom placement):
+
+```tsx
+import { PopupBlocks } from '@sonordev/site-kit/website/popups'
+
+<PopupBlocks
+  blocks={[{ type: 'heading', text: 'Spring cleanups are booking' }]}
+  placement="popup"
+  onClose={() => setOpen(false)}
+/>
+```
+
+`inline` renders it in place, without the overlay or focus handling.
+
+## Engage (retired)
+
+Engage was retired in Sonor, and its popups with it. Popups made in Engage
+Studio (a `design_json` without blocks) aren't drawn by site-kit 7.2 or later;
+make them again in Website → Popups & Banners. `@sonordev/site-kit/engage`
+still builds through 7.x: its `EngageWidget` draws `SitePopups` and the
+website chat.

package/dist/ChatWidget-UCDWMWCW.js

@@ -1,15 +0,0 @@
-export { ChatWidget, EchoChat, isChatEnabled } from './chunk-RHNWA34F.js';
-import './chunk-JE4A5S4F.js';
-import './chunk-NDF4A5JM.js';
-import './chunk-6T6CQVNL.js';
-import './chunk-V6FDQLR7.js';
-import './chunk-AQSNPZY4.js';
-import './chunk-5SQK3D53.js';
-import './chunk-NJCTQH2P.js';
-import './chunk-S22FSH7C.js';
-import './chunk-L2V5PUFN.js';
-import './chunk-GJWI74ZZ.js';
-import './chunk-3SDOQUUF.js';
-import './chunk-VDF5DFWT.js';
-import './chunk-AH5Q262S.js';
-import './chunk-PKBMQBKP.js';

package/dist/EngageWidget-7ZYSK4GE.js

@@ -1,11 +0,0 @@
-export { EngageWidget } from './chunk-YCJT4JJG.js';
-import './chunk-NDF4A5JM.js';
-import './chunk-6T6CQVNL.js';
-import './chunk-24QZEO3Q.js';
-import './chunk-GJWI74ZZ.js';
-import './chunk-43OCZ3JA.js';
-import './chunk-EKBEOXTH.js';
-import './chunk-3SDOQUUF.js';
-import './chunk-VDF5DFWT.js';
-import './chunk-AH5Q262S.js';
-import './chunk-PKBMQBKP.js';

package/dist/ManagedForm-H7BVAH2W.js

@@ -1,14 +0,0 @@
-export { ManagedForm } from './chunk-CSTQDNGK.js';
-import './chunk-D5EC5KVO.js';
-import './chunk-DXO6SBMD.js';
-import './chunk-LUXVWITO.js';
-import './chunk-V6FDQLR7.js';
-import './chunk-AQSNPZY4.js';
-import './chunk-5SQK3D53.js';
-import './chunk-NJCTQH2P.js';
-import './chunk-L2V5PUFN.js';
-import './chunk-GJWI74ZZ.js';
-import './chunk-3SDOQUUF.js';
-import './chunk-VDF5DFWT.js';
-import './chunk-AH5Q262S.js';
-import './chunk-PKBMQBKP.js';

package/dist/SitemapSync-XBANGKHZ.js

@@ -1,8 +0,0 @@
-export { SitemapSync } from './chunk-UXOGCKL6.js';
-import './chunk-YVKRYQRG.js';
-import './chunk-43OCZ3JA.js';
-import './chunk-EKBEOXTH.js';
-import './chunk-3SDOQUUF.js';
-import './chunk-VDF5DFWT.js';
-import './chunk-AH5Q262S.js';
-import './chunk-PKBMQBKP.js';

package/dist/chunk-NDF4A5JM.js

@@ -1,37 +0,0 @@
-import { VISUAL_VIEWPORT_GAP_PROPERTY } from './chunk-6T6CQVNL.js';
-
-// src/engage/launcher-placement.ts
-var DEFAULT_LAUNCHER_OFFSET_BOTTOM = "20px";
-var DEFAULT_ENGAGE_Z_INDEX = 9999;
-var LAUNCHER_OFFSET_PROPERTY = "--sk-echo-offset-bottom";
-var SIDE_GUTTER = "20px";
-var POPUP_ABOVE_LAUNCHER = "70px";
-var POPUP_VERTICAL_RESERVE = "100px";
-function toCssLength(value) {
-  if (typeof value === "number") return Number.isFinite(value) ? `${value}px` : void 0;
-  const trimmed = value?.trim();
-  return trimmed ? trimmed : void 0;
-}
-function chatLauncherStyles({ position, offsetBottom, zIndex } = {}) {
-  const side = position === "bottom-left" ? { left: SIDE_GUTTER } : { right: SIDE_GUTTER };
-  const offset = toCssLength(offsetBottom) ?? DEFAULT_LAUNCHER_OFFSET_BOTTOM;
-  const layer = typeof zIndex === "number" && Number.isFinite(zIndex) ? zIndex : DEFAULT_ENGAGE_Z_INDEX;
-  const clearance = `var(${LAUNCHER_OFFSET_PROPERTY}, ${offset}) + env(safe-area-inset-bottom, 0px) + var(${VISUAL_VIEWPORT_GAP_PROPERTY}, 0px)`;
-  return {
-    launcher: {
-      ...side,
-      bottom: `calc(${clearance})`
-    },
-    popup: {
-      ...side,
-      bottom: `calc(${clearance} + ${POPUP_ABOVE_LAUNCHER})`,
-      maxHeight: `calc(100dvh - (${clearance}) - ${POPUP_VERTICAL_RESERVE})`
-    },
-    // One beneath the launcher. At 0 or below, the same layer instead: -1
-    // would paint the popup behind the page's own content, and at a shared
-    // layer the launcher, which renders after the popup, still paints on top.
-    zIndex: { launcher: layer, popup: layer > 0 ? layer - 1 : layer }
-  };
-}
-
-export { DEFAULT_ENGAGE_Z_INDEX, DEFAULT_LAUNCHER_OFFSET_BOTTOM, chatLauncherStyles };