@sonordev/site-kit 7.1.2 → 7.3.0

package/dist/website/index.js

@@ -1,13 +1,13 @@
 'use client';
-export { SiteDesignReporter } from '../chunk-Q4W23JYM.js';
-export { SITE_DESIGN_PATH, cleanFontStack, colorToHex, getSiteDesignTokens, measureSiteDesign, readDeclaredDesign, sendSiteDesign } from '../chunk-PGMVL4AB.js';
-export { DEFAULT_POPUP_TOKENS, PopupBlocks } from '../chunk-JSZN6LDZ.js';
+export { SiteDesignReporter } from '../chunk-MRQ2U4LZ.js';
+export { SITE_DESIGN_PATH, cleanFontStack, colorToHex, getSiteDesignTokens, measureSiteDesign, readDeclaredDesign, sendSiteDesign } from '../chunk-I2YX3HVD.js';
+export { DEFAULT_POPUP_TOKENS, PopupBlocks } from '../chunk-BF7TZYC3.js';
 import '../chunk-IHG36STL.js';
 import '../chunk-YC7ELZS3.js';
 import '../chunk-S22FSH7C.js';
 import '../chunk-43OCZ3JA.js';
 import '../chunk-EKBEOXTH.js';
-import '../chunk-3SDOQUUF.js';
-import '../chunk-VDF5DFWT.js';
-import '../chunk-AH5Q262S.js';
+import '../chunk-BEBR4OJD.js';
+import '../chunk-WGG6GTKW.js';
+import '../chunk-56KNHB4U.js';
 import '../chunk-PKBMQBKP.js';

package/dist/website/popup-rules.d.ts

@@ -0,0 +1,46 @@
+/**
+ * @sonordev/site-kit/website/popups - the rules SitePopups applies to the
+ * popups, banners and toasts published for a site, as pure functions (the
+ * package's tests have no DOM).
+ */
+import type { SitePopup } from './popup-types';
+import type { PopupPlacement } from './PopupBlocks';
+/** Exact path, or a prefix ending in `*`. The grammar Sonor stores page patterns in. */
+export declare function matchPath(pathname: string, pattern: string): boolean;
+export type DeviceType = 'desktop' | 'mobile' | 'tablet';
+export declare function deviceFromUserAgent(ua: string): DeviceType;
+/**
+ * The storage key that remembers a visitor saw (closed or clicked) a popup.
+ * The `_engage_` prefix predates the Website module; renaming it would show
+ * every "once" popup to visitors who already closed it.
+ */
+export declare function seenKey(popupId: string): string;
+interface SeenStore {
+    local: Pick<Storage, 'getItem'> | null;
+    session: Pick<Storage, 'getItem'> | null;
+}
+/** Whether a popup's targeting and frequency cap allow it on this page, for this visitor. */
+export declare function isEligible(popup: SitePopup, pathname: string, device: DeviceType, store: SeenStore, now?: number): boolean;
+/**
+ * What a popup draws as: centred over a dimmed page, a bar along an edge, or
+ * a slide-in (a toast) in a corner. Its `layout` says what it actually is;
+ * `type` describes it for older kits. Undefined for a popup without blocks:
+ * that's Sonor's Engage Studio `design_json`, which this kit doesn't draw.
+ * Single source of truth for which popups SitePopups draws, the
+ * one-popup-at-a-time rule and the form wait.
+ */
+export declare function popupPlacement(popup: SitePopup): PopupPlacement | undefined;
+/**
+ * Whether a popup waits until the visitor isn't mid-form before it opens on
+ * its own (shared/mid-form). Popups and toasts do. Banners don't: they
+ * neither take focus nor hide the page.
+ */
+export declare function waitsForForms(popup: SitePopup): boolean;
+/**
+ * The active list after `id` asks to show. A popup (the kind centred over a
+ * dimmed page) waits while another is open, so two never stack; banners and
+ * toasts show alongside. Popups arrive from Sonor highest priority first, so
+ * the first popup to trigger is the one that wins a tie.
+ */
+export declare function activatePopup(active: string[], id: string, popups: SitePopup[]): string[];
+export {};

package/dist/website/popup-types.d.ts

@@ -0,0 +1,113 @@
+/**
+ * @sonordev/site-kit/website/popups: what a published popup looks like.
+ *
+ * Sonor → Website → Popups & Banners. The API serves them from
+ * `GET /engage/widget/elements` (its route keeps the retired module's name).
+ */
+import type { PopupBlock } from './contract';
+/** What Sonor says a popup is. A blocks popup's `layout` says where it actually sits. */
+export type SitePopupType = 'popup' | 'nudge' | 'bar' | 'chat' | 'slide-in';
+/** A popup, banner or toast published for this site (Sonor → Website → Popups & Banners). */
+export interface SitePopup {
+    id: string;
+    project_id: string;
+    name: string;
+    type: SitePopupType;
+    config: SitePopupConfig;
+    targeting: SitePopupTargeting;
+    trigger: SitePopupTrigger;
+    is_active: boolean;
+    priority: number;
+    created_at: string;
+    updated_at: string;
+    /**
+     * The popup as blocks, drawn in the site's own design by PopupBlocks. A
+     * popup without blocks isn't drawn: Sonor's older `design_json` (Engage
+     * Studio) is for site-kits before 7.2.0, and is ignored here.
+     */
+    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;
+    };
+    status?: 'draft' | 'published' | 'archived' | 'paused';
+}
+export interface SitePopupConfig {
+    /** 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 SitePopupTargeting {
+    /** 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 SitePopupTrigger {
+    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;
+    };
+}

package/dist/website/popups.d.ts

@@ -7,11 +7,7 @@
  * import it to place it yourself. `PopupBlocks` is the renderer, for drawing
  * one popup from its blocks.
  */
-import React from 'react';
-import { EngageWidget } from '../engage/EngageWidget';
-export type SitePopupsProps = Omit<React.ComponentProps<typeof EngageWidget>, 'chatEnabled'>;
-/** The site's published popups, banners and toasts. No chat launcher (that's `./chat`). */
-export declare function SitePopups(props: SitePopupsProps): React.JSX.Element;
+export { SitePopups, type SitePopupsProps } from './SitePopups';
 export { PopupBlocks, DEFAULT_POPUP_TOKENS, type PopupBlocksProps, type PopupPlacement } from './PopupBlocks';
-export type { EngageElement as SitePopup } from '../engage/types';
+export type { SitePopup, SitePopupConfig, SitePopupTargeting, SitePopupTrigger, SitePopupType, } from './popup-types';
 export type { PopupBlock, SiteDesignTokens } from './contract';

package/dist/website/popups.js

@@ -1,22 +1,14 @@
 'use client';
-export { DEFAULT_POPUP_TOKENS, PopupBlocks } from '../chunk-JSZN6LDZ.js';
+export { DEFAULT_POPUP_TOKENS, PopupBlocks } from '../chunk-BF7TZYC3.js';
 import '../chunk-IHG36STL.js';
-import { EngageWidget } from '../chunk-YCJT4JJG.js';
-import '../chunk-NDF4A5JM.js';
-import '../chunk-6T6CQVNL.js';
+export { SitePopups } from '../chunk-YJLS6JBI.js';
+import '../chunk-27FISYK4.js';
 import '../chunk-S22FSH7C.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-BEBR4OJD.js';
+import '../chunk-WGG6GTKW.js';
+import '../chunk-56KNHB4U.js';
 import '../chunk-PKBMQBKP.js';
-import { jsx } from 'react/jsx-runtime';
-
-function SitePopups(props) {
-  return /* @__PURE__ */ jsx(EngageWidget, { ...props, chatEnabled: false });
-}
-
-export { SitePopups };

package/dist/{writeLLMsTxt-G3JBNBC5.js → writeLLMsTxt-2NQVDGYI.js}

@@ -1,9 +1,9 @@
-export { writeLLMsTxtToPublic } from './chunk-QEDHRBAT.js';
-import './chunk-GLHQ3LRO.js';
+export { writeLLMsTxtToPublic } from './chunk-Z65DHMTW.js';
+import './chunk-6U3VLV2C.js';
 import './chunk-L5UOHS6E.js';
 import './chunk-WMVK77ND.js';
 import './chunk-VX5CMNMM.js';
-import './chunk-4Y5FWDPM.js';
+import './chunk-NZ4RXN3G.js';
 import './chunk-MJP63SSS.js';
 import './chunk-YVKRYQRG.js';
 import './chunk-FESKKJAS.js';

package/docs/MIGRATING-TO-7.md

@@ -20,6 +20,13 @@ idempotent: running it twice changes nothing the second time. It works from
 any 2.x-6.x site: copies of sites on 4.2, 5.8 and 6.5 were migrated with it
 and built.
 
+It leaves nothing in the project but the change. Since sonor-setup 7.1.2 the
+originals of the files it writes go to a folder in your OS temp directory
+(it prints where, and git has them too), not `.bak` files beside them, and
+it never creates or edits `.env.example`: `.env.local` is the one env file.
+An old fallback such as `process.env.SONOR_API_KEY || process.env.UPTRADE_API_KEY`
+becomes `process.env.SONOR_API_KEY`.
+
 Requirements: Next 16 and Node 20.19+ or 22.12+
 (Netlify's default is 22).
 
@@ -68,12 +75,17 @@ New homes, each the same module as before:
 
 - Website: `./website/{popups,images,slots,cms,landing,cta-bar}`
 - SEO: `./seo/{sitemap,robots,indexnow,redirects,og,og/route,llms,llms/client,llms/contract,meta/contract,pages/contract}`
-- Website chat: `./chat` (out of `./engage`)
+- Website chat: `./chat`, and popups: `./website/popups` (both out of
+  `./engage`, which Sonor retired with the Engage module)
 
 **The old paths keep working through 7.x** and are removed in 8.0. The
-codemod moves them anyway, so a touched site is done in one pass.
-`SiteKitLayout` gains `chat` and `popups` props; `engage` is an alias
-(`engage={false}` still turns both off).
+codemod moves them anyway, so a touched site is done in one pass: chat
+imports go to `./chat`, popup types to `./website/popups` under their new
+names (`EngageElement` is `SitePopup`). It flags `EngageWidget`, which draws
+both and which `SiteKitLayout` already mounts. `SiteKitLayout` gains `chat`
+and `popups` props; `engage` is an alias (`engage={false}` still turns both
+off). Since 7.2.0, popups render only from blocks: one made in Engage Studio
+isn't drawn, so make it again in Sonor (Website → Popups & Banners).
 
 ### 4. ESM only, Next 16 only
 
@@ -85,10 +97,22 @@ site-side script that `require()`s site-kit on an older Node would break.
 The `next` peer is `^16`. Next 16 renamed `middleware.ts` to `proxy.ts`, and
 **the codemod moves it**: the file, a named `middleware` export (to `proxy`),
 and `createMiddleware` from `@sonordev/site-kit/middleware` (to `createProxy`
-from `/proxy`). The old names work through 7.x. It won't move a file that
-sets `runtime` (a proxy file can't; the build throws), and says so: remove
-the export, check the logic still runs on your host, rerun. It never moves
-onto an existing `proxy.ts`. `npx sonor-setup next16` runs just this part.
+from `/proxy`). The old names work through 7.x.
+
+**The proxy goes beside the app directory.** Next reads it from the project
+root, or from `src/` when the app is `src/app`, and silently ignores one
+anywhere else: the build passes, but the site sends no security headers and
+runs no managed redirects. So on a `src/app` site the codemod writes
+`src/proxy.ts`, with the file's relative imports re-pointed. Before
+sonor-setup 7.1.2 it renamed the file in place, which left a root `proxy.ts`
+on those sites; rerunning the codemod moves it, and `npx sonor-setup doctor`
+warns about any proxy Next doesn't read.
+
+It won't move a file that sets `runtime` (a proxy file can't; the build
+throws), and says so: remove the export, check the logic still runs on your
+host, rerun. It never moves onto a proxy Next already runs: with one in each
+place, it reports both and changes neither. `npx sonor-setup next16` runs
+just this part.
 
 ### 5. Removed (nothing used them)
 
@@ -119,7 +143,7 @@ Still accepted and ignored until 8.0, because sites pass them:
   `.env.local`, `.env.production`, `.env`. It used to let `.env.local` beat
   the host.
 
-## Optional, and new in 7.0
+## Optional, and new in 7.x
 
 - **Cache Components.** `cacheComponents: true` in next.config works with
   site-kit now (it failed every page through 6.x). Remove route segment
@@ -134,6 +158,14 @@ Still accepted and ignored until 8.0, because sites pass them:
   `onToolCall: reportToolCallsToSonor()` to its `createMcpHandler`.
 - **`@sonordev/contracts`** is for the APIs and the dashboard; sites keep
   importing `@sonordev/site-kit/*/contract`, which is the same code.
+- **Live updates (7.1).** `npx sonor-setup scaffold` writes the route Sonor
+  calls when content changes, `app/api/seo-revalidate/route.ts`, and
+  `npx sonor-setup doctor` checks for it. A site with articles gets
+  `createRevalidateRoute({ publicationBasePath: '/insights' })` with its own
+  path, read from the app directory (a dynamic page that renders site-kit
+  articles, or a `[slug]` route under a folder like `/blog` or `/news`).
+  When more than one folder looks like the publication, it writes the
+  one-line route and lists them.
 
 ## Kits built on site-kit
 

package/docs.json

@@ -38,7 +38,8 @@
       "title": "Engagement",
       "pages": [
         { "slug": "forms", "title": "Forms", "file": "src/forms/README.md" },
-        { "slug": "chat", "title": "Website chat", "file": "src/engage/README.md" },
+        { "slug": "chat", "title": "Website chat", "file": "src/chat/README.md" },
+        { "slug": "popups", "title": "Popups and banners", "file": "src/website/README.md" },
         { "slug": "cta-bar", "title": "CTA bar", "file": "src/cta-bar/README.md" },
         { "slug": "signal", "title": "Signal (A/B)", "file": "src/signal/README.md" }
       ]

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sonordev/site-kit",
-  "version": "7.1.2",
+  "version": "7.3.0",
   "type": "module",
   "packageManager": "pnpm@11.5.3",
   "description": "Complete client-side integration kit for Sonor - SEO, Analytics, Engage, Forms, Blog",
@@ -461,7 +461,7 @@
     "gsap": "^3.15.0",
     "happy-dom": "^20.14.5",
     "inquirer": "^14.0.2",
-    "next": "16.3.6",
+    "next": "16.3.8",
     "open": "11.0.0",
     "ora": "^9.4.1",
     "playwright": "^1.62.1",

package/src/analytics/README.md

@@ -212,7 +212,7 @@ with `analytics.site` or `NEXT_PUBLIC_SITE_URL` set to a production domain.
 `localhost`, its subdomains, `127.0.0.1`, `[::1]`, and `0.0.0.0` report nothing
 by default: page views, events, conversions, sessions, vitals, scroll and
 heatmap data, fleet heartbeats, and client-side sitemap registrations all use
-`resolveAnalyticsTarget`. Engage doesn't mount its widgets or chat transport.
+`resolveAnalyticsTarget`. Website chat and popups don't mount at all.
 Public hosts and same-origin frames on public hosts still report normally.
 
 For intentional local reporting:
@@ -222,7 +222,7 @@ For intentional local reporting:
 ```
 
 The layout passes this option to AnalyticsProvider, WebVitals, FleetHeartbeat,
-SitemapSync and EngageWidget. Standalone components and `sendFleetHeartbeat`
+SitemapSync, SiteChat and SitePopups. Standalone components and `sendFleetHeartbeat`
 accept it too; standalone `trackEvent`/`trackConversion` use their mounted
 AnalyticsProvider's options. A local cross-origin frame needs **both** opt-ins.
 Neither option bypasses authentication. No environment variable or global

package/src/articles/README.md

@@ -47,7 +47,10 @@ const href = createPublicationRoutes(routing).post({ slug: 'build-first', catego
 provide `postPath: post => '/articles/' + encodeURIComponent(post.slug)`.
 Callbacks return local paths; generated metadata, feeds, and sitemaps separately
 honor a valid `canonical_url`. The same routes apply to Atom and generated
-breadcrumb/cluster schemas. Supplied `schema`/`schema_json` objects stay intact.
+breadcrumb/cluster schemas. Supplied `schema`/`schema_json` objects stay intact, apart
+from template placeholders (an `Organization` named "Example", `example.com` URLs,
+`{post.title}`), which `generateAllArticleSchemas` drops. When nothing real is left,
+it generates the article's schema from its own fields instead.
 
 For custom layouts, `resolveArticleArtwork(post, 'article')` prefers
 `editorial_image`, preserving an empty decorative `editorial_image_alt`.

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.