@sonordev/site-kit 7.1.1 → 7.2.0

package/dist/articles/excerpt.d.ts

@@ -10,9 +10,8 @@
  *
  * The AI article pipeline stores content as JSON sections
  * (`{"heading": "## ...", "content": "## ...\n\nIf you're asking **how**..."}`)
- * and that value has been shipping verbatim into <meta name="description">.
- * nkylawfirm.com had three live articles whose SERP snippet was raw JSON with
- * markdown asterisks and literal \n. Parse the sections out, strip markdown,
- * and cap at a sentence boundary.
+ * and that value can ship verbatim into <meta name="description">, leaving a
+ * SERP snippet of raw JSON with markdown asterisks and literal \n. Parse the
+ * sections out, strip markdown, and cap at a sentence boundary.
  */
 export declare function sanitizeExcerpt(raw: string | undefined | null, maxLength?: number): string;

package/dist/articles/index.d.ts

@@ -62,8 +62,8 @@ export type { ClusterNavigationProps } from './ClusterNavigation';
  * `CLIENT_ENTRIES`, `src/shared/build-entries.ts`), so every module it reaches
  * is client code by declaration. `ClusterLandingPage` is an async component that
  * awaits `getTopicCluster` from `./server-core`, so exporting it from here put
- * that module's `x-api-key` fetch into the browser bundle — confirmed in a real
- * upforge-nextjs build, in `.next/static/chunks/`. It also could never have
+ * that module's `x-api-key` fetch into the browser bundle (confirmed in a real
+ * site's build, in `.next/static/chunks/`). It also could never have
  * worked as a client component: async components are server-only.
  *
  * The type stays — `export type` is erased at build time and reaches no runtime

package/dist/articles/index.js

@@ -1,6 +1,6 @@
 'use client';
-import { NewsletterShell } from '../chunk-SC4MZGWZ.js';
 export { ArticleFAQ } from '../chunk-GKGSXUVQ.js';
+import { NewsletterShell } from '../chunk-SC4MZGWZ.js';
 import { getAuthorSocialLinks, readingTimeMinutes } from '../chunk-FV2VD7WM.js';
 export { ClusterNavigation, ServiceCallout, ServiceCallouts } from '../chunk-FV2VD7WM.js';
 import '../chunk-GYF2ULVO.js';
@@ -15,7 +15,7 @@ import '../chunk-PKBMQBKP.js';
 import React, { useState, Suspense, useEffect } from 'react';
 import { jsx, jsxs } from 'react/jsx-runtime';
 
-var ManagedNewsletterForm = React.lazy(() => import('../ManagedNewsletterForm-LPIKGJF4.js'));
+var ManagedNewsletterForm = React.lazy(() => import('../ManagedNewsletterForm-BO3WCGXX.js'));
 function NewsletterWidget({
   title = "Subscribe to Our Newsletter",
   description = "Get the latest posts delivered straight to your inbox.",

package/dist/articles/news-sitemap.d.ts

@@ -26,7 +26,7 @@ export interface NewsSitemapPost extends ArticleRoutePost {
 }
 export interface NewsSitemapOptions extends PublicationRoutingOptions {
     siteUrl: string;
-    /** The publication name, exactly as it appears on the articles (e.g. "The Forge by Upforge"). */
+    /** The publication name, exactly as it appears on the articles (e.g. "The Journal by Example Co."). */
     publicationName: string;
     /** ISO 639 language code. Defaults to "en". */
     language?: string;

package/dist/articles/processArticleHtml.d.ts

@@ -1,5 +1,5 @@
 /**
- * Post-process Portal/article HTML for safe, consistent link behavior.
+ * Post-process Sonor/article HTML for safe, consistent link behavior.
  * Server-safe string transforms only (no DOM).
  */
 /**

package/dist/articles/server-core.d.ts

@@ -74,8 +74,8 @@ export declare function getArticle(slug: string, options?: {
  *
  * `getArticle` returns null for a mistyped or deleted slug, and the page
  * used to carry on rendering a "not found" message with HTTP 200 and an
- * indexable title: a soft 404 on every bad post URL (vsf-consulting-nextjs
- * /insights, found 2026-09-15). This calls Next's `notFound()` instead, so the
+ * indexable title: a soft 404 on every bad post URL. This calls Next's
+ * `notFound()` instead, so the
  * route answers 404 with `noindex`.
  *
  * Call it from `generateMetadata` (or the page) before rendering `Article`:
@@ -293,7 +293,7 @@ export declare function generateRssFeed(options: RssFeedOptions): Promise<string
 export declare function generateAtomFeed(options: RssFeedOptions): Promise<string>;
 /**
  * Fetch all active topic clusters for the project.
- * Uses the real cluster data from Portal API (not heuristic-based).
+ * Uses the real cluster data from Sonor API (not heuristic-based).
  */
 export declare function getTopicClusters(options?: {
     site?: string;
@@ -449,7 +449,7 @@ export declare function generateAuthorPageMetadata(author: ArticleAuthor, option
  * keeps its existing public API.
  */
 export { authorEntityId, generateArticleAuthorNode, generateAuthorPersonSchema, generateAuthorSchema, withArticleAuthorIdentity, type AuthorSchemaOptions, } from './author-schema';
-/** Portal article document shape (alias of `Article` from `./types`) */
+/** Sonor article document shape (alias of `Article` from `./types`) */
 export type { Article as ArticleRecord } from './types';
 export { articleCategorySlug, createPublicationRoutes, resolveArticleUrl, resolvePublicationUrl } from './routes';
 export type { ArticleRoutePost, PublicationRoutingOptions } from './routes';

package/dist/articles/server-ui.js

@@ -2,12 +2,13 @@ import { readingTimeMinutes, ServiceCallouts, ClusterNavigation, getAuthorSocial
 export { ClusterNavigation } from '../chunk-FV2VD7WM.js';
 import { widgetStyle, widgetTitleStyle } from '../chunk-GYF2ULVO.js';
 import { resolvePublicationSiteUrl, addExternalLinkTargets } from '../chunk-L5UOHS6E.js';
-import { fetchArticleBySlug, fetchRelatedArticles, fetchArticleCategories, getTopicCluster } from '../chunk-TXBAOEKG.js';
+import { fetchArticleBySlug, fetchRelatedArticles, fetchArticleCategories, getTopicCluster } from '../chunk-PKGN32AU.js';
 export { articleTableCss, wrapArticleTables } from '../chunk-Y3INC4QJ.js';
 import { resolveArticleArtwork, articleArtworkImageStyle } from '../chunk-QXMIKDOL.js';
 export { resolveArticleArtwork } from '../chunk-QXMIKDOL.js';
 import { createPublicationRoutes, articleCategorySlug } from '../chunk-WMVK77ND.js';
 export { articleCategorySlug, createPublicationRoutes, resolveArticleUrl, resolvePublicationUrl } from '../chunk-WMVK77ND.js';
+import '../chunk-VWWITFWM.js';
 import { withSiteParam } from '../chunk-MJP63SSS.js';
 import '../chunk-X6F6SO4S.js';
 import '../chunk-MH2DSGC6.js';
@@ -132,7 +133,7 @@ async function Article({
     ...item,
     answer: addExternalLinkTargets(item.answer || "", siteUrlResolved)
   })) ?? faqRaw;
-  const { ArticleViewTracker } = await import('../ArticleViewTracker-CMBSJR3N.js');
+  const { ArticleViewTracker } = await import('../ArticleViewTracker-TM5AMGN2.js');
   if (children) {
     return /* @__PURE__ */ jsxs(Fragment, { children: [
       /* @__PURE__ */ jsx(ArticleViewTracker, { slug: post.slug, site }),

package/dist/articles/server.d.ts

@@ -74,8 +74,8 @@ export declare function getArticle(slug: string, options?: {
  *
  * `getArticle` returns null for a mistyped or deleted slug, and the page
  * used to carry on rendering a "not found" message with HTTP 200 and an
- * indexable title: a soft 404 on every bad post URL (vsf-consulting-nextjs
- * /insights, found 2026-09-15). This calls Next's `notFound()` instead, so the
+ * indexable title: a soft 404 on every bad post URL. This calls Next's
+ * `notFound()` instead, so the
  * route answers 404 with `noindex`.
  *
  * Call it from `generateMetadata` (or the page) before rendering `Article`:
@@ -293,7 +293,7 @@ export declare function generateRssFeed(options: RssFeedOptions): Promise<string
 export declare function generateAtomFeed(options: RssFeedOptions): Promise<string>;
 /**
  * Fetch all active topic clusters for the project.
- * Uses the real cluster data from Portal API (not heuristic-based).
+ * Uses the real cluster data from Sonor API (not heuristic-based).
  */
 export declare function getTopicClusters(options?: {
     site?: string;
@@ -449,7 +449,7 @@ export declare function generateAuthorPageMetadata(author: ArticleAuthor, option
  * keeps its existing public API.
  */
 export { authorEntityId, generateArticleAuthorNode, generateAuthorPersonSchema, generateAuthorSchema, withArticleAuthorIdentity, type AuthorSchemaOptions, } from './author-schema';
-/** Portal article document shape (alias of `Article` from `./types`) */
+/** Sonor article document shape (alias of `Article` from `./types`) */
 export type { Article as ArticleRecord } from './types';
 export { articleCategorySlug, createPublicationRoutes, resolveArticleUrl, resolvePublicationUrl } from './routes';
 export type { ArticleRoutePost, PublicationRoutingOptions } from './routes';

package/dist/articles/server.js

@@ -1,7 +1,8 @@
-export { FEED_DEFAULT_ITEMS, NEWS_SITEMAP_MAX_URLS, NEWS_SITEMAP_WINDOW_MS, SEO_LIMITS, buildNewsSitemapXml, cdata, generateAllArticleSchemas, generateArticleCategoryMetadata, generateArticleListSchema, generateArticleMetadata, generateArticleSchema, generateArticleSitemap, generateArticleStaticParams, generateAtomFeed, generateAuthorPageMetadata, generateAuthorStaticParams, generateBreadcrumbSchema, generateCategoryStaticParams, generateClusterArticleSchema, generateClusterBreadcrumbSchema, generateClusterItemListSchema, generateClusterLandingSchema, generateClusterPageMetadata, generateFaqSchema, generateHowToSchema, generateNewsSitemap, generatePublicationMetadata, generateRssFeed, getAllArticleSlugs, getAllArticles, getAllAuthorSlugs, getArticle, getArticleCategories, getAuthorBySlug, getAuthorPosts, getClusterNavigation, getPostsByCategory, getRelatedInsights, getTopicCluster, getTopicClusters, recentNewsPosts, requireArticle, sanitizeExcerpt, validateArticleSeo, validateMetaDescription, validateSeoTitle } from '../chunk-TXBAOEKG.js';
+export { FEED_DEFAULT_ITEMS, NEWS_SITEMAP_MAX_URLS, NEWS_SITEMAP_WINDOW_MS, SEO_LIMITS, buildNewsSitemapXml, cdata, generateAllArticleSchemas, generateArticleCategoryMetadata, generateArticleListSchema, generateArticleMetadata, generateArticleSchema, generateArticleSitemap, generateArticleStaticParams, generateAtomFeed, generateAuthorPageMetadata, generateAuthorStaticParams, generateBreadcrumbSchema, generateCategoryStaticParams, generateClusterArticleSchema, generateClusterBreadcrumbSchema, generateClusterItemListSchema, generateClusterLandingSchema, generateClusterPageMetadata, generateFaqSchema, generateHowToSchema, generateNewsSitemap, generatePublicationMetadata, generateRssFeed, getAllArticleSlugs, getAllArticles, getAllAuthorSlugs, getArticle, getArticleCategories, getAuthorBySlug, getAuthorPosts, getClusterNavigation, getPostsByCategory, getRelatedInsights, getTopicCluster, getTopicClusters, recentNewsPosts, requireArticle, sanitizeExcerpt, validateArticleSeo, validateMetaDescription, validateSeoTitle } from '../chunk-PKGN32AU.js';
 export { articleTableCss, wrapArticleTables } from '../chunk-Y3INC4QJ.js';
 export { authorEntityId, generateArticleAuthorNode, generateAuthorPersonSchema, generateAuthorSchema, resolveArticleArtwork, withArticleAuthorIdentity } from '../chunk-QXMIKDOL.js';
 export { articleCategorySlug, createPublicationRoutes, resolveArticleUrl, resolvePublicationUrl } from '../chunk-WMVK77ND.js';
+import '../chunk-VWWITFWM.js';
 import '../chunk-MJP63SSS.js';
 import '../chunk-X6F6SO4S.js';
 import '../chunk-MH2DSGC6.js';

package/dist/articles/types.d.ts

@@ -125,7 +125,7 @@ export interface ArticleAuthor {
     author_page_url?: string;
     /**
      * schema.org `@id` for this person, shared by every site that describes
-     * them (blog_authors.entity_id), e.g. `https://ramseydeal.com/#person`.
+     * them (blog_authors.entity_id), e.g. `https://example.com/#person`.
      * Unset: the kit uses `<author page URL>#person`.
      */
     entity_id?: string | null;

package/dist/{engage → chat}/ChatWidget.d.ts

@@ -1,5 +1,5 @@
 /**
- * @sonordev/site-kit/engage - Chat Widget (Redesigned)
+ * @sonordev/site-kit/chat - Chat Widget (Redesigned)
  *
  * Features:
  * - Pulls brand colors (primary/secondary) + business info from project settings via API
@@ -17,7 +17,7 @@ interface ChatWidgetProps {
     projectId?: string;
     config?: Partial<ChatConfig>;
     apiUrl?: string;
-    /** Signal API base URL for direct AI chat (no Portal passthrough) */
+    /** Signal API base URL for direct AI chat (no Sonor passthrough) */
     signalUrl?: string;
     /** Clickable question chips shown in the welcome screen before the first message */
     suggested_questions?: string[];
@@ -63,9 +63,9 @@ interface WidgetConfigFromApi {
  * Whether Echo belongs on this site, given the project's widget config.
  *
  * Sonor decides this and sends it as `is_enabled` on `GET /engage/widget/config`:
- * the Engage "Enable Chat Widget" switch (a project that never saved chat
- * settings counts as on) and the project's Engage module, resolved once
- * server-side (sonor-api `resolveChatSwitch`). Only an explicit `false` hides
+ * the "Show the chat widget" switch (Messages → Chat settings; a project that
+ * never saved chat settings counts as on) and the project's Website chat
+ * module (Project Settings), resolved once server-side. Only an explicit `false` hides
  * Echo, which also keeps an API that predates the field showing it. `null`
  * means the config hasn't arrived or couldn't be fetched, and the chat can't
  * run without it either.
@@ -85,8 +85,9 @@ interface EchoChatProps extends ChatWidgetProps {
 /**
  * Echo itself, mounted by ChatWidget once the project's config says chat is
  * on. Exported for the launcher tests, which render it with a resolved config
- * because the package's vitest has no DOM to run ChatWidget's fetch in. Not
- * part of the public `@sonordev/site-kit/engage` API.
+ * because the package's vitest has no DOM to run ChatWidget's fetch in.
+ * `@sonordev/site-kit/chat` re-exports it, but a site should mount ChatWidget
+ * (or SiteChat), which fetches the config and follows the project's switch.
  */
 export declare function EchoChat({ projectId, widgetConfig, config, apiUrl: propApiUrl, signalUrl: propSignalUrl, suggested_questions: propSuggestedQuestions, assistant_name: propAssistantName, welcome_message: propWelcomeMessage, assistant_avatar: propAssistantAvatar }: EchoChatProps): React.JSX.Element;
 export {};

package/dist/{engage → chat}/EchoUiActions.d.ts

@@ -1,8 +1,8 @@
 /**
- * @sonordev/site-kit/engage - Echo UI Actions
+ * @sonordev/site-kit/chat - Echo UI Actions
  *
  * Renders the optional `uiActions` the visitor Echo concierge returns alongside
- * a chat reply (see signal-api echo.service.ts). Rendered beneath the assistant
+ * a chat reply. Rendered beneath the assistant
  * message in ChatWidget, on-brand with the widget's primary-color tokens and
  * the brand foreground colours from brand-color.ts.
  *
@@ -10,8 +10,8 @@
  *                         forms `useForm` fetch/validate/submit path) with optional prefill.
  * - suggest_action      → clickable chip; sends the message as the next turn, or
  *                         navigates when the action is a path/URL.
- * - show_portfolio_item → intentionally ignored. Portfolio is Upforge-specific
- *                         and Upforge runs its own custom Echo chat, not this widget.
+ * - show_portfolio_item → intentionally ignored: the generic widget has no
+ *                         portfolio view; a site with its own chat UI handles it.
  */
 import React from 'react';
 import type { UiAction } from './types';

package/dist/chat/SiteChat.d.ts

@@ -0,0 +1,25 @@
+/**
+ * @sonordev/site-kit/chat - SiteChat: the Website chat a site shows
+ * (Sonor → Messages).
+ *
+ * Echo's launcher, mounted once the browser is idle. SiteKitLayout mounts it
+ * for you (its `chat` prop); mount it yourself only on a site without
+ * SiteKitLayout. ChatWidget, its markdown renderer and its socket download
+ * when it first renders, never with the page. It shows only while the
+ * project's chat is switched on in Sonor (see ChatWidget's isChatEnabled).
+ */
+import React from 'react';
+import type { ChatLauncherPlacement } from './types';
+import { type AnalyticsGateOptions } from '../shared/reporting-gate';
+export interface SiteChatProps extends ChatLauncherPlacement, AnalyticsGateOptions {
+    apiUrl?: string;
+    apiKey?: string;
+    /** For chat routing. Resolved from the API key when absent. */
+    projectId?: string;
+}
+/**
+ * Same gate as analytics (frames, localhost, a key to send with): a chat
+ * launcher in a case study's device frame would talk to the agency's visitor,
+ * not this site's.
+ */
+export declare function SiteChat(props: SiteChatProps): React.JSX.Element | null;

package/dist/{engage → chat}/brand-color.d.ts

@@ -1,5 +1,5 @@
 /**
- * @sonordev/site-kit/engage — Echo's brand colours
+ * @sonordev/site-kit/chat — Echo's brand colours
  *
  * Single source of truth for how Echo turns the site's brand colour into
  * foreground colours. ChatWidget and EchoUiActions route every such decision
@@ -14,7 +14,7 @@
  *     when it already reads, otherwise the brand pulled toward black (light
  *     panel) or white (dark panel) just far enough to clear WCAG AA.
  *
- * Why: a light brand (Gunning Homes' #d4af37 gold, any yellow) drawn as text
+ * Why: a light brand (a #d4af37 gold, any yellow) drawn as text
  * on the ~86% white panel sat at about 2:1.
  */
 /** Light enough that text and icons on a fill of it should be dark. Unreadable colours count as dark. */

package/dist/{engage → chat}/chat-messages.d.ts

@@ -1,5 +1,5 @@
 /**
- * @sonordev/site-kit/engage — Echo's transcript: message shapes and turns
+ * @sonordev/site-kit/chat — Echo's transcript: message shapes and turns
  *
  * Single source of truth for what ChatWidget adds to the transcript when a
  * visitor speaks, and for the one AI turn every send path goes through.

package/dist/{engage → chat}/echo-config.d.ts

@@ -1,5 +1,5 @@
 /**
- * @sonordev/site-kit/engage - Echo Public Configuration
+ * @sonordev/site-kit/chat - Echo Public Configuration
  *
  * Helpers for configuring the ChatWidget with Echo-specific defaults
  * for the Sonor public site (sonor.io).

package/dist/chat/index.d.ts

@@ -2,10 +2,14 @@
  * @sonordev/site-kit/chat — Website chat (Sonor → Messages).
  *
  * The chat launcher and Echo conversation a site shows. SiteKitLayout mounts
- * it for you (its `chat` prop, `engage` before 6.6); import it here to place
- * it yourself. It used to live in `./engage`, which still re-exports it.
+ * it for you (its `chat` prop); `SiteChat` places it yourself the same way
+ * (idle-deferred, gated like analytics), and `ChatWidget` is the widget
+ * itself. `@sonordev/site-kit/engage` (deprecated) re-exports these.
  */
-export { ChatWidget, EchoChat, isChatEnabled } from '../engage/ChatWidget';
-export { chatLauncherStyles, DEFAULT_LAUNCHER_OFFSET_BOTTOM } from '../engage/launcher-placement';
-export type { ChatLauncherStyles } from '../engage/launcher-placement';
-export type { ChatAvailability, ChatConfig, ChatConversation, ChatLauncherPlacement, ChatLauncherPosition, ChatMessage, UiAction, UiActionType, } from '../engage/types';
+export { SiteChat, type SiteChatProps } from './SiteChat';
+export { ChatWidget, EchoChat, isChatEnabled } from './ChatWidget';
+export { chatLauncherStyles, DEFAULT_LAUNCHER_OFFSET_BOTTOM } from './launcher-placement';
+export type { ChatLauncherStyles } from './launcher-placement';
+export { SONOR_PUBLIC_ECHO_DEFAULTS, getEchoWidgetProps } from './echo-config';
+export type { EchoPublicConfig } from './echo-config';
+export type { ChatAvailability, ChatConfig, ChatConversation, ChatLauncherPlacement, ChatLauncherPosition, ChatMessage, UiAction, UiActionType, } from './types';

package/dist/chat/index.js

@@ -1,16 +1,22 @@
 'use client';
-export { ChatWidget, EchoChat, isChatEnabled } from '../chunk-V4HUSHZO.js';
-import '../chunk-JE4A5S4F.js';
-export { DEFAULT_LAUNCHER_OFFSET_BOTTOM, chatLauncherStyles } from '../chunk-NDF4A5JM.js';
+export { SONOR_PUBLIC_ECHO_DEFAULTS, getEchoWidgetProps } from '../chunk-HODO5BX5.js';
+export { ChatWidget, DEFAULT_LAUNCHER_OFFSET_BOTTOM, EchoChat, chatLauncherStyles, isChatEnabled } from '../chunk-64DKGVEI.js';
+export { SiteChat } from '../chunk-NV72HZ4W.js';
 import '../chunk-6T6CQVNL.js';
-import '../chunk-NEKEH4CK.js';
-import '../chunk-AQSNPZY4.js';
+import '../chunk-JE4A5S4F.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-L2V5PUFN.js';
 import '../chunk-GJWI74ZZ.js';
-import '../chunk-PXZ7LAOY.js';
-import '../chunk-OUNRFXDC.js';
-import '../chunk-6OL23QYD.js';
+import '../chunk-43OCZ3JA.js';
+import '../chunk-EKBEOXTH.js';
+import '../chunk-D6ZC7XKZ.js';
+import '../chunk-K4ZHAURD.js';
+import '../chunk-F24FNCTK.js';
 import '../chunk-PKBMQBKP.js';

package/dist/{engage → chat}/launcher-placement.d.ts

@@ -1,5 +1,5 @@
 /**
- * @sonordev/site-kit/engage - Chat launcher placement
+ * @sonordev/site-kit/chat - Chat launcher placement
  *
  * Single source of truth for where the Echo launcher sits and, derived from
  * it, where the chat popup opens, on screen and in the stacking order.
@@ -14,12 +14,6 @@ import type { CSSProperties } from 'react';
 import type { ChatLauncherPlacement } from './types';
 /** Launcher clearance above the bottom edge when a site sets nothing. */
 export declare const DEFAULT_LAUNCHER_OFFSET_BOTTOM = "20px";
-/**
- * Layer everything Engage renders stacks on when a site sets nothing:
- * popups, nudges, bars and the chat launcher, with the chat popup one below.
- * EngageWidget's default comes from here too.
- */
-export declare const DEFAULT_ENGAGE_Z_INDEX = 9999;
 /**
  * Custom property a stylesheet can set to move the launcher. Wins over the
  * `offsetBottom` option. Deliberately never declared by the kit: a property

package/dist/{engage → chat}/socket-loader.d.ts

@@ -1,8 +1,8 @@
 import type { Socket } from 'socket.io-client';
 /**
  * Lazy socket.io loader — kept in a separate file so bundlers
- * (Turbopack, webpack) never pull socket.io-client into the main
- * engage chunk.  Only loaded when the user actually opens the chat.
+ * (Turbopack, webpack) never pull socket.io-client into the chat
+ * chunk. Only loaded when the user actually opens the chat.
  *
  * This module owns site-kit's entire socket.io surface. If you are wondering
  * why package.json declares `engine.io-client` and `socket.io-parser` when

package/dist/chat/types.d.ts

@@ -0,0 +1,136 @@
+/**
+ * @sonordev/site-kit/chat: Website chat types (Sonor → Messages).
+ */
+/** 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: the layout's `chat` config,
+ * SiteChat'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.
+     *
+     * Through SiteKitLayout the same number also stacks popups, banners and
+     * toasts, so everything a site's widgets render 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;
+}

package/dist/chunk-27FISYK4.js

@@ -0,0 +1,4 @@
+// src/shared/layers.ts
+var DEFAULT_WIDGET_Z_INDEX = 9999;
+
+export { DEFAULT_WIDGET_Z_INDEX };