@burdenoff/website-sdk 2026.922.5 → 2026.923.2

package/dist/components/explore.d.mts

@@ -1,180 +1,4 @@
-import * as react from 'react';
-import { E as ExploreProduct, a as ExploreReference } from '../explore-types-DvQPiL1t.mjs';
-
-interface ExplorePageProps {
-    /**
-     * SEO metadata. Every field is optional and each one falls back to a default
-     * derived from {@link ExplorePageProps.productSlug}, so a site that passes
-     * nothing still gets a correct head — see `defaultExploreSeo`.
-     *
-     * Pass this only to say something the default cannot. All 38 sites used to
-     * hard-code the same two sentences here, which is how every one of them ended
-     * up announcing "Explore Burdenoff products with AI" — product-first on a page
-     * whose whole purpose is to ask the visitor about their problem, and simply
-     * the wrong brand on 37 of them.
-     */
-    seo?: {
-        title?: string;
-        description?: string;
-        keywords?: string;
-        image?: string;
-        url?: string;
-    };
-    /** Slug of the product site this page lives on — a soft hint to the harness. */
-    productSlug?: string;
-    /**
-     * Example prompts shown when `exploreCatalog` supplies none. Resolution
-     * order: catalog → this prop → the SDK's built-in list.
-     */
-    examplePrompts?: string[];
-    /** Extra classes for the page root. */
-    className?: string;
-    /**
-     * `viewport` (default) pins the chat to the viewport with an internally
-     * scrolling transcript — the right feel for a dedicated `/explore` route.
-     * `auto` lets the page grow, for embedding inside a longer page.
-     *
-     * `viewport` also means "this component IS the page": only in that mode does it take over
-     * `history.scrollRestoration` and correct a restored scroll offset that has parked the
-     * page in the site footer. An `auto` embed never touches its host page's scrolling.
-     */
-    heightMode?: "viewport" | "auto";
-    /**
-     * Chrome to subtract in `viewport` mode — the site header height. A number is treated as
-     * pixels. Default `0`.
-     *
-     * Pre-measurement fallback ONLY. Once mounted the pane measures its own top, so an
-     * approximate value is fine and the keyboard case is handled; see `measurePane` in
-     * `ExplorePage`.
-     */
-    viewportOffset?: string | number;
-    /** SPA navigation for internal CTA paths. Falls back to a plain link. */
-    onNavigate?: (path: string) => void;
-    /** Fired with the message text every time a send is accepted. */
-    onSend?: (message: string) => void;
-    /** Overrides `exploreCatalog.welcomeTitle` — also the page `<h1>`. */
-    welcomeTitle?: string;
-    /** Overrides `exploreCatalog.welcomeBody`. */
-    welcomeBody?: string;
-    /**
-     * BCP-47 locale to render in. Defaults to the document's own `lang`, then the browser.
-     * Only the six the products ship are recognised (en, zh, hi, es, ar, ta); anything else
-     * falls back to English.
-     */
-    locale?: string;
-}
-/**
- * The product's own logo, derived from the reference's origin.
- *
- * Every Burdenoff product site serves `/favicon.svg`, so the logo needs no registry and no
- * bundled assets — the reference URL already names the product. Deliberately NOT
- * `/favicon-512.png`: that path returns 200 with `text/html` because the SPA fallback
- * answers unknown paths, so it would render as a broken image rather than 404 into the
- * fallback below.
- */
-declare function logoUrlOf(url: string): string | null;
-/**
- * Origins an answer may embed images from: every catalog product's website, apex and
- * `www.` alike (Botlit ships on www.botlit.ai, everything else on the apex, and either can
- * appear in the corpus). https only.
- */
-declare function inlineImageOrigins(products: readonly Pick<ExploreProduct, "website">[]): Set<string>;
-/**
- * True when `src` is an https URL on a catalog product site. The backend already strips
- * every image it did not put in the answer; this is the browser's own check, so a model
- * that slips an arbitrary URL past it still cannot make the visitor's browser fetch it.
- */
-declare function isInlineImageAllowed(src: unknown, origins: ReadonlySet<string>): src is string;
-/**
- * The kinds of page an answer can cite.
- *
- * `PAGE` is the catch-all for a catalog site's own marketing pages, so the list is total for
- * anything on one of our origins; a reference that is NOT on a catalog origin gets no kind at
- * all (see `referenceKindOf`).
- */
-type ExploreReferenceKind = "CONCEPT" | "DOCS" | "PRICING" | "USE_CASE" | "PAGE";
-/**
- * What KIND of page a reference points at, decided from its URL alone.
- *
- * Deliberately not from the title: titles are model-written prose in six languages, so
- * "Pricing" in one answer is "Precios" in the next and "Plans and pricing" in the one after.
- * The URL is the only part of a reference nobody paraphrases.
- *
- * Reasoned against the catalog origins exactly as `isInlineImageAllowed` is: a URL that is
- * not on a product site we list gets `null` rather than a guessed label, because the whole
- * value of the row is that it says what the evidence IS.
- */
-declare function referenceKindOf(url: string, origins: ReadonlySet<string>): ExploreReferenceKind | null;
-/**
- * Apex origin → the product's display name, built from the catalog the same way
- * `inlineImageOrigins` builds its allow-list.
- *
- * The display name matters: `ExploreReference.product` carries the slug, so a row built from
- * it says "vibecontrols" next to a page that calls itself VibeControls everywhere else.
- */
-declare function productNamesByOrigin(products: readonly Pick<ExploreProduct, "name" | "website">[]): Map<string, string>;
-/** The shape of one answer's evidence, as the chips render it. */
-interface ExploreProvenance {
-    /** Every reference the answer cites, including any we could not classify. */
-    total: number;
-    /** Kinds present, in `REFERENCE_KIND_ORDER`, with how many sources each covers. */
-    kinds: Array<{
-        kind: ExploreReferenceKind;
-        count: number;
-    }>;
-    /** Product names, in the order the answer first cited them. */
-    products: string[];
-}
-/**
- * Summarise what an answer is grounded in. Pure, and derived entirely from `references` —
- * there is no backend field behind this row.
- */
-declare function summariseReferences(references: readonly ExploreReference[], origins: ReadonlySet<string>, productNames: ReadonlyMap<string, string>): ExploreProvenance;
-/**
- * An answer as READABLE TEXT, for the clipboard.
- *
- * What counts as "our internal markup artefacts", and why each choice:
- *
- * - **Image embeds go.** `![Concept illustration of …](https://…/01.webp)` is a picture this
- *   page injected into the answer; pasted into an email it is a URL and an alt string, and
- *   neither is the answer. The caption line the backend writes under it is ordinary prose and
- *   stays.
- * - **Links become `label (url)`.** The destination is information the reader may need; the
- *   bracket-paren syntax is not. Dropping the URL would quietly strip the page it came from.
- * - **Citation markers `[3]` stay.** They are the only attribution the copied text carries,
- *   and they are the answer's own — not something the UI added. The sources they point at are
- *   listed right next to the button that copied this.
- * - **Emphasis, headings, blockquote and rule markers go**, because `**` and `###` are
- *   instructions to a renderer, not words.
- * - **A table keeps its pipes.** Pasted into a README, an issue or a chat it is a table
- *   again; flattened into sentences it is not.
- * - **Fenced code is verbatim**, fences included, minus nothing but the fence lines
- *   themselves: stripping `*` or `_` inside a code block would corrupt the code.
- *
- * Built from `message.content` rather than from the rendered DOM: `textContent` on the bubble
- * would fold every paragraph, list item and table cell into one run-on line.
- */
-declare function answerPlainText(markdown: string): string;
-/**
- * The same answer as something to SAY, for read-aloud.
- *
- * It shares every rule above but the two that are right for a paste and wrong for a voice:
- *
- * - **A link is its label.** The clipboard keeps `label (https://…)` because a pasted answer
- *   loses the page otherwise. Spoken, that is a URL spelled out character by character in
- *   the middle of a sentence — and the prompt asks for two to five links in every answer, so
- *   it is not an edge case. The sources are listed under the answer either way.
- * - **A table is read as rows, not as pipes.** `| --- | --- |` is a line of punctuation and
- *   the pipes are column rules, neither of which is a word. Each row is read with its cells
- *   under their own column headings — the phone layout, out loud — so a plan list still says
- *   which number is the price. Comparisons and plan lists are exactly the answers the
- *   feature was built for (CONTRACT.md §7), which is what makes this worth a second mode.
- *
- * Everything else stays deliberately identical, including citation markers: they are the
- * answer's own attribution in both, and a listener hearing "two" after a claim is hearing
- * the same thing a reader sees.
- */
-declare function answerSpeechText(markdown: string): string;
-declare function ExplorePage({ seo, productSlug, examplePrompts, className, heightMode, viewportOffset, onNavigate, onSend, welcomeTitle, welcomeBody, locale, }: ExplorePageProps): react.JSX.Element;
-
-export { ExplorePage, type ExplorePageProps, type ExploreProvenance, type ExploreReferenceKind, answerPlainText, answerSpeechText, inlineImageOrigins, isInlineImageAllowed, logoUrlOf, productNamesByOrigin, referenceKindOf, summariseReferences };
+import 'react';
+export { c as ExplorePage, d as ExplorePageProps, h as ExploreProvenance, j as ExploreReferenceKind, e as answerPlainText, f as answerSpeechText, i as inlineImageOrigins, g as isInlineImageAllowed, l as logoUrlOf, p as productNamesByOrigin, r as referenceKindOf, s as summariseReferences } from '../explore-D25zoXy9.mjs';
+import '../explore-types-B5sdOC5M.mjs';
+import 'react-markdown';

package/dist/components/explore.d.ts

@@ -1,180 +1,4 @@
-import * as react from 'react';
-import { E as ExploreProduct, a as ExploreReference } from '../explore-types-DvQPiL1t.js';
-
-interface ExplorePageProps {
-    /**
-     * SEO metadata. Every field is optional and each one falls back to a default
-     * derived from {@link ExplorePageProps.productSlug}, so a site that passes
-     * nothing still gets a correct head — see `defaultExploreSeo`.
-     *
-     * Pass this only to say something the default cannot. All 38 sites used to
-     * hard-code the same two sentences here, which is how every one of them ended
-     * up announcing "Explore Burdenoff products with AI" — product-first on a page
-     * whose whole purpose is to ask the visitor about their problem, and simply
-     * the wrong brand on 37 of them.
-     */
-    seo?: {
-        title?: string;
-        description?: string;
-        keywords?: string;
-        image?: string;
-        url?: string;
-    };
-    /** Slug of the product site this page lives on — a soft hint to the harness. */
-    productSlug?: string;
-    /**
-     * Example prompts shown when `exploreCatalog` supplies none. Resolution
-     * order: catalog → this prop → the SDK's built-in list.
-     */
-    examplePrompts?: string[];
-    /** Extra classes for the page root. */
-    className?: string;
-    /**
-     * `viewport` (default) pins the chat to the viewport with an internally
-     * scrolling transcript — the right feel for a dedicated `/explore` route.
-     * `auto` lets the page grow, for embedding inside a longer page.
-     *
-     * `viewport` also means "this component IS the page": only in that mode does it take over
-     * `history.scrollRestoration` and correct a restored scroll offset that has parked the
-     * page in the site footer. An `auto` embed never touches its host page's scrolling.
-     */
-    heightMode?: "viewport" | "auto";
-    /**
-     * Chrome to subtract in `viewport` mode — the site header height. A number is treated as
-     * pixels. Default `0`.
-     *
-     * Pre-measurement fallback ONLY. Once mounted the pane measures its own top, so an
-     * approximate value is fine and the keyboard case is handled; see `measurePane` in
-     * `ExplorePage`.
-     */
-    viewportOffset?: string | number;
-    /** SPA navigation for internal CTA paths. Falls back to a plain link. */
-    onNavigate?: (path: string) => void;
-    /** Fired with the message text every time a send is accepted. */
-    onSend?: (message: string) => void;
-    /** Overrides `exploreCatalog.welcomeTitle` — also the page `<h1>`. */
-    welcomeTitle?: string;
-    /** Overrides `exploreCatalog.welcomeBody`. */
-    welcomeBody?: string;
-    /**
-     * BCP-47 locale to render in. Defaults to the document's own `lang`, then the browser.
-     * Only the six the products ship are recognised (en, zh, hi, es, ar, ta); anything else
-     * falls back to English.
-     */
-    locale?: string;
-}
-/**
- * The product's own logo, derived from the reference's origin.
- *
- * Every Burdenoff product site serves `/favicon.svg`, so the logo needs no registry and no
- * bundled assets — the reference URL already names the product. Deliberately NOT
- * `/favicon-512.png`: that path returns 200 with `text/html` because the SPA fallback
- * answers unknown paths, so it would render as a broken image rather than 404 into the
- * fallback below.
- */
-declare function logoUrlOf(url: string): string | null;
-/**
- * Origins an answer may embed images from: every catalog product's website, apex and
- * `www.` alike (Botlit ships on www.botlit.ai, everything else on the apex, and either can
- * appear in the corpus). https only.
- */
-declare function inlineImageOrigins(products: readonly Pick<ExploreProduct, "website">[]): Set<string>;
-/**
- * True when `src` is an https URL on a catalog product site. The backend already strips
- * every image it did not put in the answer; this is the browser's own check, so a model
- * that slips an arbitrary URL past it still cannot make the visitor's browser fetch it.
- */
-declare function isInlineImageAllowed(src: unknown, origins: ReadonlySet<string>): src is string;
-/**
- * The kinds of page an answer can cite.
- *
- * `PAGE` is the catch-all for a catalog site's own marketing pages, so the list is total for
- * anything on one of our origins; a reference that is NOT on a catalog origin gets no kind at
- * all (see `referenceKindOf`).
- */
-type ExploreReferenceKind = "CONCEPT" | "DOCS" | "PRICING" | "USE_CASE" | "PAGE";
-/**
- * What KIND of page a reference points at, decided from its URL alone.
- *
- * Deliberately not from the title: titles are model-written prose in six languages, so
- * "Pricing" in one answer is "Precios" in the next and "Plans and pricing" in the one after.
- * The URL is the only part of a reference nobody paraphrases.
- *
- * Reasoned against the catalog origins exactly as `isInlineImageAllowed` is: a URL that is
- * not on a product site we list gets `null` rather than a guessed label, because the whole
- * value of the row is that it says what the evidence IS.
- */
-declare function referenceKindOf(url: string, origins: ReadonlySet<string>): ExploreReferenceKind | null;
-/**
- * Apex origin → the product's display name, built from the catalog the same way
- * `inlineImageOrigins` builds its allow-list.
- *
- * The display name matters: `ExploreReference.product` carries the slug, so a row built from
- * it says "vibecontrols" next to a page that calls itself VibeControls everywhere else.
- */
-declare function productNamesByOrigin(products: readonly Pick<ExploreProduct, "name" | "website">[]): Map<string, string>;
-/** The shape of one answer's evidence, as the chips render it. */
-interface ExploreProvenance {
-    /** Every reference the answer cites, including any we could not classify. */
-    total: number;
-    /** Kinds present, in `REFERENCE_KIND_ORDER`, with how many sources each covers. */
-    kinds: Array<{
-        kind: ExploreReferenceKind;
-        count: number;
-    }>;
-    /** Product names, in the order the answer first cited them. */
-    products: string[];
-}
-/**
- * Summarise what an answer is grounded in. Pure, and derived entirely from `references` —
- * there is no backend field behind this row.
- */
-declare function summariseReferences(references: readonly ExploreReference[], origins: ReadonlySet<string>, productNames: ReadonlyMap<string, string>): ExploreProvenance;
-/**
- * An answer as READABLE TEXT, for the clipboard.
- *
- * What counts as "our internal markup artefacts", and why each choice:
- *
- * - **Image embeds go.** `![Concept illustration of …](https://…/01.webp)` is a picture this
- *   page injected into the answer; pasted into an email it is a URL and an alt string, and
- *   neither is the answer. The caption line the backend writes under it is ordinary prose and
- *   stays.
- * - **Links become `label (url)`.** The destination is information the reader may need; the
- *   bracket-paren syntax is not. Dropping the URL would quietly strip the page it came from.
- * - **Citation markers `[3]` stay.** They are the only attribution the copied text carries,
- *   and they are the answer's own — not something the UI added. The sources they point at are
- *   listed right next to the button that copied this.
- * - **Emphasis, headings, blockquote and rule markers go**, because `**` and `###` are
- *   instructions to a renderer, not words.
- * - **A table keeps its pipes.** Pasted into a README, an issue or a chat it is a table
- *   again; flattened into sentences it is not.
- * - **Fenced code is verbatim**, fences included, minus nothing but the fence lines
- *   themselves: stripping `*` or `_` inside a code block would corrupt the code.
- *
- * Built from `message.content` rather than from the rendered DOM: `textContent` on the bubble
- * would fold every paragraph, list item and table cell into one run-on line.
- */
-declare function answerPlainText(markdown: string): string;
-/**
- * The same answer as something to SAY, for read-aloud.
- *
- * It shares every rule above but the two that are right for a paste and wrong for a voice:
- *
- * - **A link is its label.** The clipboard keeps `label (https://…)` because a pasted answer
- *   loses the page otherwise. Spoken, that is a URL spelled out character by character in
- *   the middle of a sentence — and the prompt asks for two to five links in every answer, so
- *   it is not an edge case. The sources are listed under the answer either way.
- * - **A table is read as rows, not as pipes.** `| --- | --- |` is a line of punctuation and
- *   the pipes are column rules, neither of which is a word. Each row is read with its cells
- *   under their own column headings — the phone layout, out loud — so a plan list still says
- *   which number is the price. Comparisons and plan lists are exactly the answers the
- *   feature was built for (CONTRACT.md §7), which is what makes this worth a second mode.
- *
- * Everything else stays deliberately identical, including citation markers: they are the
- * answer's own attribution in both, and a listener hearing "two" after a claim is hearing
- * the same thing a reader sees.
- */
-declare function answerSpeechText(markdown: string): string;
-declare function ExplorePage({ seo, productSlug, examplePrompts, className, heightMode, viewportOffset, onNavigate, onSend, welcomeTitle, welcomeBody, locale, }: ExplorePageProps): react.JSX.Element;
-
-export { ExplorePage, type ExplorePageProps, type ExploreProvenance, type ExploreReferenceKind, answerPlainText, answerSpeechText, inlineImageOrigins, isInlineImageAllowed, logoUrlOf, productNamesByOrigin, referenceKindOf, summariseReferences };
+import 'react';
+export { c as ExplorePage, d as ExplorePageProps, h as ExploreProvenance, j as ExploreReferenceKind, e as answerPlainText, f as answerSpeechText, i as inlineImageOrigins, g as isInlineImageAllowed, l as logoUrlOf, p as productNamesByOrigin, r as referenceKindOf, s as summariseReferences } from '../explore-I4QnY4J9.js';
+import '../explore-types-B5sdOC5M.js';
+import 'react-markdown';