@sonordev/site-kit 7.1.1 → 7.2.0

package/dist/contracts/seo-meta.d.ts

@@ -4,17 +4,16 @@
  * Single source of truth for "is this machine-generated seo_pages.managed_title
  * / managed_meta_description fit to ship?". site-kit applies it at render time
  * (getManagedMetadata falls back to the page's own title/description), and
- * signal-api imports it (`src/shared/utils/seo-meta-quality.util.ts`) to gate
- * every generated title before it's written, so the two can't disagree.
+ * Signal applies it to every generated title before it's written, so the two
+ * can't disagree.
  *
- * Why it exists (2026-09-15): Signal's meta generator used the raw domain as
- * the brand whenever it could not resolve one, so ~500 managed titles across
- * 20+ projects shipped as "Apartments for Rent | abbeyglenapts.com", were
- * hard-cut at 60 chars ("… | reinhartheatingandcooli"), lost the suffix to a
- * word-boundary cut ("Contact Reinhart Heating and Cooling |"), or had the
- * model rebuild a brand out of the domain ("About SSO Shkosh Apartments | SSO
- * Shkosh" for ssoshkoshapts.com — the brand is SS Oshkosh Apartments). Sites
- * rendered them verbatim.
+ * Why it exists: a meta generator that uses the raw domain as the brand when it
+ * can't resolve one ships titles like "Apartments for Rent |
+ * maplecourtapts.com", hard-cuts them at 60 chars ("… |
+ * brightsideheatingandcooli"), loses the suffix to a word-boundary cut
+ * ("Contact Brightside Heating and Cooling |"), or rebuilds a brand out of the
+ * domain ("About BBE Llis Apartments | BBE Llis" for bbellisapts.com, when the
+ * brand is BB Ellis Apartments). Sites render them verbatim.
  *
  * Every rule derives from the site's own identity (its hosts and brand), so
  * there is no list of bad strings to maintain. Pure string logic — no I/O, no
@@ -24,7 +23,7 @@
 export declare const SEO_META_CONTRACT_VERSION: 1;
 /** Who the site is. Hosts come from the project/site config, the brand from the resolved business name — never from the domain. */
 export interface MetaIdentity {
-    /** The site's brand, e.g. "SS Oshkosh Apartments". */
+    /** The site's brand, e.g. "BB Ellis Apartments". */
     brand?: string | null;
     /** Other correct spellings of the brand. */
     brandAliases?: Array<string | null | undefined>;
@@ -34,7 +33,7 @@ export interface MetaIdentity {
 export type TitleProblem = 'empty' | 'placeholder' | 'dangling-separator' | 'hostname' | 'mangled-brand';
 export type DescriptionProblem = 'empty' | 'hostname' | 'mangled-brand' | 'truncated';
 export type SuffixProblem = 'hostname' | 'mangled-brand';
-/** "https://www.AbbeyGlenApts.com:443/x" → "abbeyglenapts.com". Null for anything that isn't a host (no dot, or words). */
+/** "https://www.MapleCourtApts.com:443/x" → "maplecourtapts.com". Null for anything that isn't a host (no dot, or words). */
 export declare function metaHost(value: string | null | undefined): string | null;
 /** True when the text names the brand (an alias, or either one's core) word for word. */
 export declare function namesBrand(text: string, id: MetaIdentity): boolean;

package/dist/contracts/seo-pages.d.ts

@@ -3,13 +3,10 @@
  *
  * Single source of truth for choosing ONE seo_pages row when a (project_id,
  * path/url) lookup matches several, and for scoping a project's rows to one
- * host. site-kit (`@sonordev/site-kit/seo/pages/contract`), sonor-api
- * (`src/modules/seo/seo-page-resolve.util.ts`) and signal-api
- * (`src/shared/utils/seo-page-pick.util.ts`) all import this; none keeps a
- * copy.
+ * host. site-kit (`@sonordev/site-kit/seo/pages/contract`) and both Sonor
+ * APIs import this; none keeps a copy.
  *
- * seo_pages identity became (project_id, site, url) in sonor-api migration
- * 20260702150000_seo_pages_per_site_identity.sql: a multi-site project (one
+ * seo_pages identity is (project_id, site, url): a multi-site project (one
  * Sonor project hosting many domains) keeps one row PER SUB-SITE HOST for
  * shared paths like `/` or `/contact`. Any path/url lookup can therefore match
  * several rows — `.single()`/`.maybeSingle()` error on them (PGRST116) — so
@@ -26,11 +23,9 @@ export declare const SEO_PAGES_CONTRACT_VERSION: 1;
  *
  * Retired pages are kept as tombstones (status='removed') so their history and
  * redirects survive, which means every public read has to opt out of them
- * explicitly. Three reads in llms-content.service.ts never did, and the sitemap
- * sync's removal flag was write-only for as long as the code existed: on
- * 2026-09-20 upforge.io's llms.txt — the file handed straight to AI crawlers —
- * was 32% dead URLs, advertising service areas in Atlanta, Detroit and Tampa
- * that the business has never served.
+ * explicitly. A read that forgets serves dead URLs: an llms.txt, the file
+ * handed straight to AI crawlers, ends up advertising pages the business
+ * retired long ago.
  *
  * Null-safe by design: `status` is nullable with an 'active' default, so a row
  * whose status was explicitly nulled stays live rather than vanishing from the
@@ -80,13 +75,12 @@ export declare function matchSitemapEntryRow<T extends SeoPageRowLike>(candidate
  * that belongs to `site`, keeping at most one row per path.
  *
  * Why this exists: a multi-site project (one Sonor project hosting many
- * domains — bd-aec.com plus 48 sibling domains, truepowersystems.com plus its
- * state microsites) holds one row PER HOST for shared paths like `/` and
- * `/terms`. Any project-wide read that dedupes by path alone therefore keeps an
- * ARBITRARY host's row. Observed 2026-08-25: bd-aec.com's llms.txt described
- * `/` with soqwriters.com's homepage copy and `/terms` with bd-charlotte.com's,
- * and which sibling won changed every time a neighbour rebuilt, because the tie
- * among same-path rows is broken by whatever order Postgres returns.
+ * domains, e.g. example.com plus dozens of city microsites) holds one row PER
+ * HOST for shared paths like `/` and `/terms`. Any project-wide read that
+ * dedupes by path alone therefore keeps an ARBITRARY host's row: example.com's
+ * llms.txt can describe `/` with a sibling's homepage copy, and which sibling
+ * wins changes every time a neighbour rebuilds, because the tie among
+ * same-path rows is broken by whatever order Postgres returns.
  *
  * Rules, per path, via `matchSitemapEntryRow`:
  *  - this host's row wins outright

package/dist/contracts/site-cache.d.ts

@@ -2,11 +2,11 @@
  * How Sonor refreshes a site's cached pages when content changes.
  *
  * A site serves cached pages and caches every fetch from Sonor. When someone
- * edits content in Sonor, sonor-api POSTs the paths and cache tags that
+ * edits content in Sonor, Sonor POSTs the paths and cache tags that
  * changed to the site's revalidation route, authenticated with the project's
  * API key, and the site regenerates just those. site-kit tags its fetches with
  * these names and serves the route (`@sonordev/site-kit/revalidate`);
- * sonor-api sends them. Single source of truth for the names on both sides:
+ * Sonor sends them. Single source of truth for the names on both sides:
  * never spell a tag as a string literal in either.
  */
 /** Where the revalidation route lives on every site. */
@@ -29,7 +29,7 @@ export declare const SITE_CACHE_TAGS: {
     readonly portfolio: 'portfolio';
 };
 export type SiteCacheTag = (typeof SITE_CACHE_TAGS)[keyof typeof SITE_CACHE_TAGS];
-/** The body sonor-api POSTs to the revalidation route. */
+/** The body Sonor POSTs to the revalidation route. */
 export interface SiteRevalidatePayload {
     /** Local paths to regenerate, e.g. `['/services/roofing']`. */
     paths?: string[];
@@ -39,7 +39,7 @@ export interface SiteRevalidatePayload {
     revalidateAll?: boolean;
     /**
      * Only check that the route is installed and the key matches; nothing is
-     * regenerated. sonor-api pings after it registers a site's route, so it
+     * regenerated. Sonor pings after it registers a site's route, so it
      * knows whether an edit goes live in seconds or waits for the cache to age out.
      */
     ping?: boolean;

package/dist/contracts/sites-normalize.d.ts

@@ -14,9 +14,7 @@
  * pushed those entries over their bundle budgets.
  *
  * `./sites` re-exports this, so `@sonordev/contracts/sites` (and site-kit's
- * `sites/contract`) carry it too. The Nest APIs import it from there
- * (sonor-api `src/common/utils/site-host.ts`, signal-api
- * `src/shared/utils/seo-page-pick.util.ts`).
+ * `sites/contract`) carry it too. The Sonor APIs import it from there.
  *
  * Pure string logic only (no Node built-ins) so it is safe in the browser.
  */
@@ -24,7 +22,7 @@
  * normalizeSiteHost — canonical normalizer for a sub-site host value before it
  * is persisted or used as a filter.
  *
- *   `https://OhioPowerStudies.com:3000/path` → `ohiopowerstudies.com`
+ *   `https://Ohio.Example.com:3000/path` → `ohio.example.com`
  *
  * Lowercases, strips protocol, keeps host only (drops path + query), strips
  * port (rollups span dev/prod) and the FQDN root dot. Returns null for

package/dist/contracts/sites.d.ts

@@ -2,10 +2,8 @@
  * @sonordev/contracts/sites — Multi-site "site" dimension host contract (v1)
  *
  * Single source of truth for normalizing and comparing sub-site host values
- * (the multi-site `site` dimension, see CLAUDE.md). site-kit, sonor-api
- * (`src/common/utils/site-host.ts`) and signal-api
- * (`src/shared/utils/seo-page-pick.util.ts`) all import it, so there's no
- * copy to drift.
+ * (the multi-site `site` dimension). site-kit and both Sonor APIs import it,
+ * so there's no copy to drift.
  *
  * Pure string logic only (no Node built-ins) so it is safe in the browser:
  * site-kit itself normalizes `__SITE_KIT_SITE__` with `normalizeSiteHost`.
@@ -28,7 +26,7 @@ export declare function stripWww(host: string): string;
  */
 export declare function sameSite(a: string | null | undefined, b: string | null | undefined): boolean;
 /**
- * Host of a full URL ("https://ohiopowerstudies.com/x" → "ohiopowerstudies.com"),
+ * Host of a full URL ("https://ohio.example.com/x" → "ohio.example.com"),
  * null for site-relative paths ("/services") and unparseable input.
  */
 export declare function hostFromUrl(value: string | null | undefined): string | null;

package/dist/contracts/slot-content.d.ts

@@ -4,7 +4,7 @@
  * The pure half of the slots contract: content types, value validation
  * (normalizeSlotValue), safe links, and the rich-text subset parser. No
  * crypto, so the dashboard can import it in the browser to validate and
- * preview exactly what sonor-api will accept and site-kit will render.
+ * preview exactly what the Sonor API will accept and site-kit will render.
  * `@sonordev/contracts/slots` re-exports all of it next to the signing.
  */
 /**
@@ -66,7 +66,7 @@ export type SlotValueResult = {
 /**
  * Validate and normalize what an editor (or Signal) submits for a slot of
  * `type`, returning the canonical `content` + `value` to store and sign.
- * The single rule for "what a valid slot of this type is": sonor-api runs it
+ * The single rule for "what a valid slot of this type is": the Sonor API runs it
  * on every write and verifySlotContent re-runs it on every read.
  */
 export declare function normalizeSlotValue(type: SlotContentType, input: {

package/dist/contracts/slots.d.ts

@@ -3,23 +3,23 @@
  *
  * Single source of truth for the slot payload shape, value validation, the
  * rich-text subset, and content signing, shared by site-kit (verify + render),
- * sonor-api (validate + sign) and the dashboard (preview). Node only: it signs
+ * the Sonor API (validate + sign) and the dashboard (preview). Node only: it signs
  * with `crypto`.
  *
  * Security model: every SlotContent is HMAC-signed with the project API key.
  * site-kit verifies before rendering and falls back to the developer's static
  * content on any mismatch, so platform-originated content carries provenance
- * end to end. See docs/SITE-KIT-3.0-SPEC-SLOTS.md and docs/WEBSITE-CMS.md.
+ * end to end.
  *
  * v1 (site-kit ≤ 7.0) is plain text only. v2 adds rich text, links and lists,
- * and signs the structured value too. sonor-api serves both: a v1 request gets
+ * and signs the structured value too. Sonor serves both: a v1 request gets
  * text slots signed the v1 way and null for everything else.
  */
 import { type SlotContentType, type SlotValue } from './slot-content';
 export * from './slot-content';
 /** The version this package speaks. Bump on breaking payload changes. */
 export declare const SLOTS_CONTRACT_VERSION = 2;
-/** Versions sonor-api still serves. */
+/** Versions Sonor still serves. */
 export declare const SUPPORTED_SLOTS_CONTRACT_VERSIONS: readonly number[];
 export interface SlotContent {
     slot_id: string;
@@ -63,7 +63,7 @@ export interface SlotResolveRequestEntry {
 export interface SlotsResolveRequest {
     contract_version: number;
     slots: SlotResolveRequestEntry[];
-    /** Multi-site sub-dimension: normalized lowercase host (see CLAUDE.md "site" convention). */
+    /** Multi-site sub-dimension: normalized lowercase host. */
     site?: string;
 }
 export interface SlotsResolveResponse {
@@ -83,7 +83,7 @@ type Signable = Pick<SlotContent, 'slot_id' | 'type' | 'content'> & {
  */
 export declare function slotSigningPayload(content: Signable, version?: number): string;
 /**
- * Sign slot content with the project API key (sonor-api side).
+ * Sign slot content with the project API key (Sonor's side).
  * Returns the hex HMAC-SHA256 signature.
  */
 export declare function signSlotContent(content: Signable, apiKey: string, version?: number): string;

package/dist/contracts/voice.d.ts

@@ -0,0 +1,56 @@
+/**
+ * Stands in for every character that isn't prose (code, quotations, link
+ * destinations). It's neither whitespace nor a word character, so a masked
+ * span still separates words and no pattern can match it.
+ */
+export declare const VOICE_MASK = "\u2800";
+export interface VoiceHit {
+    /** UTF-16 offset into the whole string you passed in, never line-relative. */
+    readonly index: number;
+    /** Length of the span to replace. May include a run of spaces or tabs. */
+    readonly length: number;
+    /** The text at [index, index + length) of the string you passed in. */
+    readonly match: string;
+    /** What to put there, first-letter case preserved. Always a straight apostrophe. */
+    readonly suggestion: string;
+}
+export interface VoiceOptions {
+    /**
+     * The text is a heading or title, so one that opens with "What Is" keeps it.
+     * Applies to every line. Pass the heading text, not the Markdown line: `#`
+     * and list markers must already be blanked.
+     */
+    readonly titleLike?: boolean | undefined;
+    /**
+     * Half-open [start, end) UTF-16 ranges to leave alone, computed from the
+     * exact string passed in. Any order, overlaps and touching ranges allowed.
+     * Start is floored and clamped to 0 (so -Infinity means "from the start"),
+     * end is ceiled and clamped to the text length (so Infinity means "to the
+     * end"), and an empty or out-of-text range is ignored. Every protected
+     * character is masked except "\n" and "\r", which stay as they are (a
+     * protected line break still ends its line). A malformed range (NaN, a
+     * non-number, or start after end) or a truthy value that isn't an array
+     * protects the whole text: protection never fails open. A falsy value means
+     * no ranges.
+     */
+    readonly protectedRanges?: ReadonlyArray<readonly [number, number]> | undefined;
+}
+/**
+ * Full forms the house voice contracts ("do not" -> "don't"). Read one line at
+ * a time: split on "\n"; a "\r" right before it, or at the very end of the
+ * text, ends the line with it; any other "\r" is text.
+ * Sorted by index, never overlapping, [] for ''.
+ */
+export declare function findUncontracted(text: string, options?: VoiceOptions): VoiceHit[];
+/**
+ * `text` with every findUncontracted hit applied. Returns `text` itself when
+ * nothing applies, and for anything that isn't a string. Protected characters
+ * are never rewritten.
+ */
+export declare function contractText(text: string, options?: VoiceOptions): string;
+/**
+ * Contractions a question-form heading or FAQ question must expand
+ * ("What's" -> "What is"). Sorted by index, never overlapping. `titleLike` is
+ * not part of this direction.
+ */
+export declare function findContracted(text: string, options?: Pick<VoiceOptions, 'protectedRanges'>): VoiceHit[];

package/dist/contracts/website.d.ts

@@ -5,14 +5,14 @@
  * SINGLE SOURCE OF TRUTH shared by every side of the Website module's popups:
  *  - the site (site-kit measures its own rendered design and reports it,
  *    publishes it as `--sk-site-*` CSS variables, and renders popup blocks),
- *  - sonor-api (validates the design report and every popup write with these
+ *  - the Sonor API (validates the design report and every popup write with these
  *    normalizers, so a popup can't be saved in a shape the site can't draw),
  *  - the dashboard (the builder's preview reads the same tokens through the
  *    same CSS-variable mapping, so it looks like the site),
  *  - Signal's agents (the block shapes an MCP `propose_site_popup` sends).
  *
  * All four import it: site-kit as `@sonordev/site-kit/website/contract`,
- * sonor-api and the dashboard as `@sonordev/contracts/website`.
+ * the API and the dashboard as `@sonordev/contracts/website`.
  *
  * Why popups carry blocks and the site carries tokens: a popup should look
  * like the site it's on. It says WHAT (a heading, some formatted text, an

package/dist/engage/EngageWidget.d.ts

@@ -1,20 +1,21 @@
 /**
- * @sonordev/site-kit/engage - Engage Widget
+ * @sonordev/site-kit/engage - EngageWidget: deprecated, kept through 7.x.
  *
- * Loads and renders engagement widgets (popups, nudges, bars, chat) via Portal API
- * Supports both legacy config-based rendering and new design_json from Engage Studio
+ * Engage was retired in Sonor. SiteKitLayout mounts website chat and popups
+ * for you (its `chat` and `popups` props). To place them yourself, use
+ * `SiteChat` from `@sonordev/site-kit/chat` and `SitePopups` from
+ * `@sonordev/site-kit/website/popups`. This draws exactly those two, so a
+ * site that still renders <EngageWidget /> keeps working. Removed in 8.0.
  */
 import React from 'react';
-import type { ChatLauncherPlacement } from './types';
-import { type AnalyticsGateOptions } from '../shared/reporting-gate';
-interface EngageWidgetProps extends ChatLauncherPlacement, AnalyticsGateOptions {
-    apiUrl?: string;
-    apiKey?: string;
-    projectId?: string;
+import { type SiteChatProps } from '../chat/SiteChat';
+/** @deprecated Use SiteChat and SitePopups, or SiteKitLayout's `chat` and `popups`. */
+export interface EngageWidgetProps extends SiteChatProps {
+    /** Show the chat launcher. Default true. */
     chatEnabled?: boolean;
-    /** Load and show the site's popups, banners and toasts. Default true. */
+    /** Show the site's popups, banners and toasts. Default true. */
     popupsEnabled?: boolean;
     debug?: boolean;
 }
-export declare function EngageWidget(props: EngageWidgetProps): React.JSX.Element | null;
-export {};
+/** @deprecated Use SiteChat and SitePopups, or SiteKitLayout's `chat` and `popups`. */
+export declare function EngageWidget({ chatEnabled, popupsEnabled, debug, ...props }: EngageWidgetProps): React.JSX.Element;

package/dist/engage/index.d.ts

@@ -1,13 +1,14 @@
 /**
- * @sonordev/site-kit/engage
+ * @sonordev/site-kit/engage — deprecated, kept through 7.x so old imports
+ * keep building. Removed in 8.0.
  *
- * Engagement widgets - popups, nudges, chat
- * DesignRenderer for Engage Studio components
+ * Engage was retired in Sonor. Website chat is `@sonordev/site-kit/chat`
+ * (Sonor → Messages) and popups are `@sonordev/site-kit/website/popups`
+ * (Sonor → Website). Nothing lives here: this re-exports them under the old
+ * names, and EngageWidget draws SiteChat and SitePopups.
  */
-export { EngageWidget } from './EngageWidget';
-export { ChatWidget } from './ChatWidget';
-export { DesignRenderer } from './DesignRenderer';
-export type { DesignDocument, DesignNode, ActionConfig, EngageContext } from './DesignRenderer';
+export { EngageWidget, type EngageWidgetProps } from './EngageWidget';
+export { ChatWidget } from '../chat/ChatWidget';
+export { SONOR_PUBLIC_ECHO_DEFAULTS, getEchoWidgetProps } from '../chat/echo-config';
+export type { EchoPublicConfig } from '../chat/echo-config';
 export * from './types';
-export { SONOR_PUBLIC_ECHO_DEFAULTS, getEchoWidgetProps } from './echo-config';
-export type { EchoPublicConfig } from './echo-config';

package/dist/engage/index.js

@@ -1,12 +1,16 @@
 'use client';
-export { ChatWidget } from '../chunk-V4HUSHZO.js';
-import '../chunk-JE4A5S4F.js';
-export { DesignRenderer, EngageWidget } from '../chunk-B73QPZPH.js';
-import '../chunk-NDF4A5JM.js';
+export { SONOR_PUBLIC_ECHO_DEFAULTS, getEchoWidgetProps } from '../chunk-HODO5BX5.js';
+export { ChatWidget } from '../chunk-64DKGVEI.js';
+import { SiteChat } from '../chunk-NV72HZ4W.js';
 import '../chunk-6T6CQVNL.js';
-import '../chunk-NEKEH4CK.js';
-import '../chunk-AQSNPZY4.js';
+import '../chunk-JE4A5S4F.js';
+import { SitePopups } from '../chunk-EJVQJCG5.js';
+import '../chunk-27FISYK4.js';
+import '../chunk-FR6BYFPC.js';
+import '../chunk-Q6E4OPGG.js';
+import '../chunk-C2FZBUSS.js';
 import '../chunk-5SQK3D53.js';
+import '../chunk-HW7B43E5.js';
 import '../chunk-NJCTQH2P.js';
 import '../chunk-S22FSH7C.js';
 import '../chunk-24QZEO3Q.js';
@@ -14,36 +18,28 @@ import '../chunk-L2V5PUFN.js';
 import '../chunk-GJWI74ZZ.js';
 import '../chunk-43OCZ3JA.js';
 import '../chunk-EKBEOXTH.js';
-import '../chunk-PXZ7LAOY.js';
-import '../chunk-OUNRFXDC.js';
-import '../chunk-6OL23QYD.js';
+import '../chunk-D6ZC7XKZ.js';
+import '../chunk-K4ZHAURD.js';
+import '../chunk-F24FNCTK.js';
 import '../chunk-PKBMQBKP.js';
+import { jsxs, Fragment, jsx } from 'react/jsx-runtime';
 
-// src/engage/echo-config.ts
-var SONOR_PUBLIC_ECHO_DEFAULTS = {
-  signalUrl: "https://signal.sonor.io",
-  welcomeMessage: "Hi! I'm Echo, Sonor's AI assistant. I can answer questions about our platform, help you understand pricing, or get you started with a demo. What would you like to know?",
-  suggestedQuestions: [
-    "What does Sonor do?",
-    "How does Signal AI work?",
-    "What are the pricing plans?",
-    "Can I migrate from HubSpot?",
-    "How does the SEO module work?"
-  ],
-  brandColor: "#2563eb",
-  // blue-600 (~5.2:1 on white, AA); overridden by --sk-primary CSS var or API brand_primary
-  assistantName: "Echo"
-};
-function getEchoWidgetProps(config = SONOR_PUBLIC_ECHO_DEFAULTS) {
-  return {
-    signal_enabled: true,
-    signal_url: config.signalUrl || SONOR_PUBLIC_ECHO_DEFAULTS.signalUrl,
-    welcome_message: config.welcomeMessage || SONOR_PUBLIC_ECHO_DEFAULTS.welcomeMessage,
-    suggested_questions: config.suggestedQuestions || SONOR_PUBLIC_ECHO_DEFAULTS.suggestedQuestions,
-    brand_color: config.brandColor || SONOR_PUBLIC_ECHO_DEFAULTS.brandColor,
-    assistant_name: config.assistantName || SONOR_PUBLIC_ECHO_DEFAULTS.assistantName,
-    assistant_avatar: config.assistantAvatar
-  };
+function EngageWidget({ chatEnabled = true, popupsEnabled = true, debug, ...props }) {
+  const { apiUrl, apiKey, zIndex, allowInFrame, allowLocalhost } = props;
+  return /* @__PURE__ */ jsxs(Fragment, { children: [
+    popupsEnabled && /* @__PURE__ */ jsx(
+      SitePopups,
+      {
+        apiUrl,
+        apiKey,
+        zIndex,
+        allowInFrame,
+        allowLocalhost,
+        debug
+      }
+    ),
+    chatEnabled && /* @__PURE__ */ jsx(SiteChat, { ...props })
+  ] });
 }
 
-export { SONOR_PUBLIC_ECHO_DEFAULTS, getEchoWidgetProps };
+export { EngageWidget };