@sonordev/site-kit 7.1.1 → 7.1.2

package/dist/contracts/portfolio.d.ts

@@ -2,13 +2,9 @@
  * @sonordev/contracts/portfolio — portfolio proof display policy (v1)
  *
  * Single source of truth for the Lighthouse-KPI collapse policy shared by the
- * content side (signal-api generation) and the render side (agency-site-kit
- * display):
- *  - agency-site-kit imports it (`@sonordev/site-kit/portfolio/contract`)
- *    from `src/portfolio/curate-proof.ts`, which keeps the render-only
- *    primitives that bind to its section types.
- *  - signal-api imports it through
- *    `src/modules/skills/portfolio/portfolio-kpi-policy.util.ts`.
+ * content side (Signal's case-study generation) and the render side
+ * (agency-site-kit, which imports it as `@sonordev/site-kit/portfolio/contract`
+ * and keeps the render-only primitives that bind to its section types).
  *
  * Why it exists: generated case studies arrived with four "100/100 Lighthouse X"
  * KPIs repeated across hero, results cards, and a Performance section. One
@@ -17,8 +13,8 @@
  *
  * It is also the single source of truth for METRIC PROVENANCE (below): the
  * three sources a portfolio number can have, what a client-reported number
- * must carry, and which numbers may headline. sonor-api imports those
- * through `src/modules/portfolio/portfolio-metric-source.util.ts`.
+ * must carry, and which numbers may headline. The Sonor API applies the same
+ * rules.
  */
 /** The message a cross-origin-framed site-kit page posts to its embedder once it has painted. */
 export declare const FRAME_READY_MESSAGE: 'sonor:frame-ready';
@@ -109,11 +105,11 @@ export declare const METRIC_SOURCES: readonly ['measured', 'reported', 'estimate
 export type MetricSource = (typeof METRIC_SOURCES)[number];
 /** Who stands behind a client-reported number. */
 export interface MetricAttribution {
-    /** The person, e.g. "Scott Mann". */
+    /** The person, e.g. "Dana Reyes". */
     name: string;
-    /** Their title, e.g. "Director of Business Development". */
+    /** Their title, e.g. "Director of Operations". */
     role?: string;
-    /** Where they work: almost always the client, e.g. "True Power Systems". */
+    /** Where they work: almost always the client, e.g. "Northwind Engineering". */
     organization: string;
     /** The day they reported it, YYYY-MM-DD. */
     date: string;
@@ -140,12 +136,12 @@ export declare function isHeadlineMetric(metric: SourcedMetric): boolean;
 /** The badge a display shows, or null for a missing or unknown source (show nothing rather than guess). */
 export declare function metricSourceLabel(source: unknown): string | null;
 /**
- * The full credit: "Reported by Scott Mann, Director of Business Development,
- * True Power Systems, September 25, 2026". The date is read as a plain day,
+ * The full credit: "Reported by Dana Reyes, Director of Operations, Northwind
+ * Engineering, September 25, 2026". The date is read as a plain day,
  * never through a time zone, so it can't slip to the day before.
  */
 export declare function formatAttribution(by: MetricAttribution): string;
-/** The credit for a tight space (a card, a carousel tile): "per True Power Systems". */
+/** The credit for a tight space (a card, a carousel tile): "per Northwind Engineering". */
 export declare function shortAttribution(by: Pick<MetricAttribution, 'organization'>): string;
 /**
  * Carry a person's reported numbers through a regeneration. The generator can

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/ChatWidget.d.ts

@@ -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[];
@@ -65,7 +65,7 @@ interface WidgetConfigFromApi {
  * 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
+ * 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.

package/dist/engage/EchoUiActions.d.ts

@@ -2,7 +2,7 @@
  * @sonordev/site-kit/engage - 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/engage/EngageWidget.d.ts

@@ -1,7 +1,7 @@
 /**
  * @sonordev/site-kit/engage - Engage Widget
  *
- * Loads and renders engagement widgets (popups, nudges, bars, chat) via Portal API
+ * Loads and renders engagement widgets (popups, nudges, bars, chat) via Sonor API
  * Supports both legacy config-based rendering and new design_json from Engage Studio
  */
 import React from 'react';

package/dist/engage/brand-color.d.ts

@@ -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/element-rules.d.ts

@@ -2,8 +2,8 @@
  * @sonordev/site-kit/engage - the rules EngageWidget applies to popups,
  * banners and toasts, as pure functions (the package's tests have no DOM).
  *
- * Sonor validates every popup before it's published (sonor-api
- * popups/popup-contract.ts), so these are the second check: a link the kit
+ * Sonor validates every popup before it's published, so these are the
+ * second check: a link the kit
  * would follow or an image it would load must be safe here too, whatever the
  * API sent.
  */

package/dist/engage/index.js

@@ -1,10 +1,10 @@
 'use client';
-export { ChatWidget } from '../chunk-V4HUSHZO.js';
+export { ChatWidget } from '../chunk-RHNWA34F.js';
 import '../chunk-JE4A5S4F.js';
-export { DesignRenderer, EngageWidget } from '../chunk-B73QPZPH.js';
+export { DesignRenderer, EngageWidget } from '../chunk-YCJT4JJG.js';
 import '../chunk-NDF4A5JM.js';
 import '../chunk-6T6CQVNL.js';
-import '../chunk-NEKEH4CK.js';
+import '../chunk-V6FDQLR7.js';
 import '../chunk-AQSNPZY4.js';
 import '../chunk-5SQK3D53.js';
 import '../chunk-NJCTQH2P.js';
@@ -14,9 +14,9 @@ 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-3SDOQUUF.js';
+import '../chunk-VDF5DFWT.js';
+import '../chunk-AH5Q262S.js';
 import '../chunk-PKBMQBKP.js';
 
 // src/engage/echo-config.ts

package/dist/engage/types.d.ts

@@ -197,12 +197,12 @@ export interface ChatConfig extends ChatLauncherPlacement {
  * 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 emitted by signal-api `echo.service.ts`. It is a LOCAL
- * contract on purpose — never import it from signal-api (separate package).
+ * 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 — Upforge-specific; the generic widget ignores it (custom Echo chat owns it).
+ * - `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 {

package/dist/fleet/FleetHeartbeat.d.ts

@@ -9,8 +9,8 @@
  *
  * It is mounted as a deferred, CHILDLESS SIBLING — never a wrapper — by
  * SiteKitClientProviders, behind the same idle/first-interaction gate as
- * Analytics and Engage, so it never enters the critical hydration path (see
- * CLAUDE.md "the page must server-render"). It renders null and carries no
+ * Analytics and Engage, so it never enters the critical hydration path (the
+ * page must server-render). It renders null and carries no
  * visitor data.
  */
 import { type AnalyticsGateOptions } from '../shared/reporting-gate';

package/dist/fleet/index.js

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

package/dist/forms/FormSpotlight.d.ts

@@ -10,8 +10,8 @@
  * - a completed field earns its animated checkmark (the existing lock-in
  *   tick + ring)
  * - when a whole row completes and you move on, the fields COLLAPSE INTO A
- *   SENTENCE the form says back — "Nice to meet you, Ramsey." /
- *   "We'll follow up at ramsey@… or 555‑0100." — with a drawn check and a
+ *   SENTENCE the form says back — "Nice to meet you, Jordan." /
+ *   "We'll follow up at jordan@… or 555‑0100." — with a drawn check and a
  *   little edit button to reopen the row
  * - when the last requirement clears, the submit wakes (existing
  *   [data-sk-ready] pop + breathe)

package/dist/forms/ManagedForm.d.ts

@@ -1,7 +1,7 @@
 /**
  * @sonordev/site-kit/forms - Managed Form Component
  *
- * Fetches form config from Portal API and renders fields with validation
+ * Fetches form config from Sonor API and renders fields with validation
  */
 import type { ManagedFormProps } from './types';
 export declare function ManagedForm({ formId, projectId, className, onSuccess, onError, initialConfig, experience, defaultValues, children, }: ManagedFormProps): import("react").JSX.Element;

package/dist/forms/StaticForm.d.ts

@@ -18,7 +18,7 @@
  * whole forms runtime — validation, spotlight, celebration, momentum — as an
  * INITIAL script, on the LCP-critical path.
  *
- * Measured on upforge.io's homepage: 48 KB of form code in the initial chunk
+ * Measured on a real homepage: 48 KB of form code in the initial chunk
  * set cost 6 Lighthouse points (88 -> 82, LCP 3.8s -> 4.7s). Deferring the
  * client component recovered the score but deleted the form from the HTML,
  * taking the crawlable fields with it. Neither half was acceptable; a

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

@@ -6,8 +6,8 @@
  * drop-off. Lives on the shared tracking session (tracking-session.ts), one per
  * form_analytics row, never one per tracker.
  *
- * Wire shape, per field slug (the API caps these — keep them in sync with
- * sonor-api `forms/form-field-interactions.util.ts`):
+ * Wire shape, per field slug (the API caps these; keep them in sync with the
+ * API's limits):
  *   { completed: boolean, focusCount: number, timeMs: number }
  *
  * `completed` isn't stored here. The caller evaluates it at report time against

package/dist/forms/form-loaded-at.d.ts

@@ -1,7 +1,7 @@
 /**
  * The `_formLoadedAt` render stamp: when this form appeared in the browser.
- * Sonor's proof-of-page-load gate reads it (with the analytics identity) to
- * tell a person who loaded the page from a bot POSTing at the endpoint.
+ * It's part of the evidence Sonor needs that a browser rendered the page
+ * before it accepts a submission.
  *
  * Single source of truth for the stamp, used by useForm and FormClient
  * (ManagedForm). It's set on mount, not during render: a Cache Components

package/dist/forms/formsApi.d.ts

@@ -2,7 +2,7 @@
  * @sonordev/site-kit/forms - Forms API Client
  *
  * Full API client for form management. Allows developers to create, update,
- * and delete forms programmatically. Changes sync to Portal automatically.
+ * and delete forms programmatically. Changes sync to Sonor automatically.
  *
  * @example
  * ```tsx
@@ -97,7 +97,7 @@ export interface CreateFormInput {
     slug: string;
     name: string;
     /**
-     * Sub-site host this form belongs to (e.g. `ohiopowerstudies.com`). Lets
+     * Sub-site host this form belongs to (e.g. `ohio.example.com`). Lets
      * one Sonor project host one form per microsite — the dashboard's site
      * picker scopes the Forms list by this value. Optional for project-wide
      * forms. CLI scripts (migrate-contact-form) should derive this from

package/dist/forms/index.d.ts

@@ -58,7 +58,7 @@
  *   Every managed form renders the SPOTLIGHT experience by default: the
  *   familiar layout, alive. A glowing ring visits the field you are in, and
  *   each completed row collapses into a sentence the form says back —
- *   "Nice to meet you, Ramsey." — with an edit control to reopen it.
+ *   "Nice to meet you, Jordan." — with an edit control to reopen it.
  *
  *   Nothing to install, nothing to wire: same fields, same validation, same
  *   spam defense. SSR and no-JS render the plain form, so the lead is always