@burdenoff/website-sdk 2026.922.4 → 2026.923.1

package/dist/index.d.mts

@@ -17,10 +17,12 @@ export { WebsiteSwitcher, WebsiteSwitcherProps } from './components/website-swit
 export { LaunchCountdown, LaunchCountdownProps } from './components/launch-countdown.mjs';
 export { ProblemSolved, ProblemsSolvedSection, ProblemsSolvedSectionProps } from './components/problems-solved.mjs';
 export { DetectedPlatform, ElectronDownloadLink, ElectronDownloadLinkProps, detectElectronPlatform } from './components/electron-download.mjs';
-export { ExplorePage, ExplorePageProps } from './components/explore.mjs';
+import { Components } from 'react-markdown';
+import { A as AnswerRendererStrings } from './explore-D25zoXy9.mjs';
+export { E as ExploreAnswerBody, a as ExploreAnswerBodyProps, b as ExploreAnswerStyles, c as ExplorePage, d as ExplorePageProps, e as answerPlainText, f as answerSpeechText, i as inlineImageOrigins, g as isInlineImageAllowed } from './explore-D25zoXy9.mjs';
 export { ExploreCta, ExploreCtaProps } from './components/explore-cta.mjs';
-export { g as EXPLORE_CATALOG_QUERY, h as EXPLORE_CATALOG_QUERY_WITHOUT_HIGHLIGHTS, i as EXPLORE_MESSAGE_QUERY, c as ExploreCatalog, j as ExploreCatalogQueryData, k as ExploreConceptHighlight, l as ExploreConversation, m as ExploreCtaKind, n as ExploreCtaLink, o as ExploreErrorCode, b as ExploreLimits, d as ExploreMessage, p as ExploreMessageQueryData, q as ExploreMessageRole, r as ExploreMessageStatus, E as ExploreProduct, a as ExploreReference, S as SEND_EXPLORE_MESSAGE_MUTATION, s as SendExploreMessageInput, t as SendExploreMessageMutationData, u as SendExploreMessageResult } from './explore-types-DvQPiL1t.mjs';
-export { D as DEFAULT_EXPLORE_EXAMPLE_PROMPTS, E as ExploreChatError, a as ExploreChatErrorKind, b as ExploreChatPhase, F as FALLBACK_EXPLORE_LIMITS, U as UseExploreChatOptions, c as UseExploreChatResult, d as classifyExploreError, u as useExploreChat } from './use-explore-chat-Dgm-jf96.mjs';
+export { g as ESCALATE_EXPLORE_CONVERSATION_MUTATION, h as EXPLORE_CATALOG_QUERY, i as EXPLORE_CATALOG_QUERY_WITHOUT_HIGHLIGHTS, j as EXPLORE_ESCALATION_NOTE_SOFT_MAX, k as EXPLORE_MESSAGE_QUERY, l as EscalateExploreConversationInput, m as EscalateExploreConversationResult, c as ExploreCatalog, n as ExploreCatalogQueryData, o as ExploreConceptHighlight, p as ExploreConversation, q as ExploreCtaKind, r as ExploreCtaLink, s as ExploreErrorCode, t as ExploreEscalation, b as ExploreLimits, d as ExploreMessage, u as ExploreMessageQueryData, v as ExploreMessageRole, w as ExploreMessageStatus, E as ExploreProduct, a as ExploreReference, S as SEND_EXPLORE_MESSAGE_MUTATION, x as SendExploreMessageInput, y as SendExploreMessageMutationData, z as SendExploreMessageResult, A as looksLikeDeliverableEmail } from './explore-types-B5sdOC5M.mjs';
+export { D as DEFAULT_EXPLORE_EXAMPLE_PROMPTS, E as ExploreChatError, a as ExploreChatErrorKind, b as ExploreChatPhase, c as ExploreEscalateOutcome, d as ExploreEscalateResult, F as FALLBACK_EXPLORE_LIMITS, U as UseExploreChatOptions, e as UseExploreChatResult, f as UseSpeechOutputOptions, g as UseSpeechOutputResult, h as classifyExploreError, s as stopSpeaking, u as useExploreChat, i as useProgressiveReveal, j as useSpeechOutput } from './use-progressive-reveal-Cmy8bA7L.mjs';
 export { RybbitAnalytics, RybbitAnalyticsProps } from './analytics/index.mjs';
 export { PageHead, PageHeadProps } from './seo/index.mjs';
 export { ProductData, ProductProvider, ProductProviderProps, useProduct, useProductConfig } from './product/index.mjs';
@@ -29,7 +31,6 @@ import { VariantProps } from 'class-variance-authority';
 import * as LabelPrimitive from '@radix-ui/react-label';
 export { B as BrowseStoreResult, G as GroupedStoreProducts, P as ProductCard, a as ProductCategory, R as RatingDistribution, S as SearchSuggestion, b as StarRating, c as StoreBrowsePage, d as StoreBrowsePageProps, e as StoreFacet, f as StoreFacets, g as StoreHomePage, h as StoreHomePageProps, i as StorePageProps, j as StoreProduct, k as StoreProductDetailPage, l as StoreProductDetailPageProps, m as StoreProductDetails, n as StorePublisher, o as StoreReview, p as StoreTerminology, q as StoreTypeFilter, T as TypeBadge, r as formatDownloads, s as formatPrice } from './product-card-CGxETsFa.mjs';
 export { EXPLORE_RECAPTCHA_ACTION, RecaptchaV3, cn, getRecaptchaV3Token, loadRecaptchaV3 } from './utils/index.mjs';
-import 'react-markdown';
 import 'clsx';
 
 interface CareersSubmissionFormProps {
@@ -197,31 +198,241 @@ declare function ConceptsPage({ productName, siteUrl, concepts, categories, cta,
  */
 declare function ConceptDetailPage(props: ConceptDetailPageProps): react.JSX.Element;
 
-declare const buttonVariants: (props?: ({
-    variant?: "link" | "default" | "destructive" | "outline" | "secondary" | "ghost" | null | undefined;
-    size?: "icon" | "default" | "sm" | "lg" | null | undefined;
-} & class_variance_authority_types.ClassProp) | undefined) => string;
-interface ButtonProps extends react.ButtonHTMLAttributes<HTMLButtonElement>, VariantProps<typeof buttonVariants> {
-    asChild?: boolean;
-}
-declare const Button: react.ForwardRefExoticComponent<ButtonProps & react.RefAttributes<HTMLButtonElement>>;
-
-declare const Input: react.ForwardRefExoticComponent<Omit<react.DetailedHTMLProps<react.InputHTMLAttributes<HTMLInputElement>, HTMLInputElement>, "ref"> & react.RefAttributes<HTMLInputElement>>;
-
-declare const Label: react.ForwardRefExoticComponent<Omit<LabelPrimitive.LabelProps & react.RefAttributes<HTMLLabelElement>, "ref"> & VariantProps<(props?: class_variance_authority_types.ClassProp | undefined) => string> & react.RefAttributes<HTMLLabelElement>>;
-
-/** Native `<select>` wrapper matching the `Input` design tokens. */
-declare const Select: react.ForwardRefExoticComponent<Omit<react.DetailedHTMLProps<react.SelectHTMLAttributes<HTMLSelectElement>, HTMLSelectElement>, "ref"> & react.RefAttributes<HTMLSelectElement>>;
+/**
+ * Published answers — the shared data contract.
+ *
+ * ## Where the questions come from, and where they must NEVER come from
+ *
+ * Every product website publishes a set of question-and-answer pages built from a **curated
+ * question list**, answered by the live explore API against the baked corpus. The question
+ * list is written by us; the answer is the harness's own output for that question.
+ *
+ * They are **never** built from stored visitor conversations. `explore_messages` holds every
+ * question a real visitor has typed into `/explore`, and publishing those as indexed pages
+ * would be a privacy breach. That the rows carry no name does not save it: a question is not
+ * anonymous content. "Our farm outside Coimbatore has three staff and we are being billed X"
+ * identifies a business with nobody's name attached, and the person who typed it consented to
+ * being answered, not to being published. That table is an analytics and answer-quality input,
+ * which is what it was built for.
+ *
+ * So: nothing in this module, in `answers.tsx`, or in whatever generates a site's
+ * `src/data/answers.ts` may read `ExploreMessage`, `ExploreConversation` or `ExploreFeedback`
+ * rows. A {@link PublishedAnswer} has no conversation id, no message id, no visitor field and
+ * no free text that came from one — by construction, not by a denylist, because a denylist
+ * leaks the first column nobody thought of.
+ *
+ * ## The same care downstream
+ *
+ * A published answer must not contain anything that is not already public on our own
+ * websites. The harness only answers from the corpus, which is built from published pages, and
+ * every source here is a public URL — {@link isPublishedSourceUrl} is the page's own last
+ * check before it renders one as a link.
+ *
+ * ## Shape
+ *
+ * Each site ships a generated `src/data/answers.ts` exporting `ANSWERS`, `ANSWER_TOPICS` and
+ * `ANSWERS_PRODUCT_NAME`, typed against these interfaces — the same arrangement the concept
+ * pages use (`dev/platform/context/concepts/01-architecture.md`). A field renamed here changes
+ * every site's generated data module, so change the generator and this file together.
+ */
 
-declare const Textarea: react.ForwardRefExoticComponent<Omit<react.DetailedHTMLProps<react.TextareaHTMLAttributes<HTMLTextAreaElement>, HTMLTextAreaElement>, "ref"> & react.RefAttributes<HTMLTextAreaElement>>;
+/**
+ * One page an answer cited.
+ *
+ * Always a public URL on one of our own sites: the harness strips every link whose origin is
+ * not in its catalog before the answer is ever stored, and this is what the page renders as a
+ * real, followable link under the answer.
+ */
+interface PublishedAnswerSource {
+    /** Absolute `https://` URL of the page. */
+    url: string;
+    /** The page's own title, as published. */
+    title: string;
+    /** Product display name, when the page belongs to one product. */
+    product?: string;
+}
+/** A curated question, and the answer our assistant produced for it. */
+interface PublishedAnswer {
+    /** Kebab-case, unique per site; the `/answer/<slug>` route. */
+    slug: string;
+    /** 1-based position across the site's answers; drives listing order and previous/next. */
+    order: number;
+    /** The question, as we wrote it. The page's `<h1>`. */
+    question: string;
+    /**
+     * The answer, as GitHub-flavoured markdown — exactly what the harness returned.
+     *
+     * It can contain GFM tables (a comparison or a plan list comes back as one; see
+     * `dev/platform/context/explore/CONTRACT.md` §7), links and concept illustrations, so it is
+     * rendered by the SAME renderer the chat uses and not by a second one.
+     */
+    answer: string;
+    /** Grouping on the index page; matches a {@link PublishedAnswerTopic} name. */
+    topic: string;
+    /** One line under the question, on the card and in the hero. */
+    summary: string;
+    /** The `<meta name="description">` for this answer's page. */
+    metaDescription: string;
+    /** Search keywords, also used by the index page's filter. */
+    keywords: string[];
+    /** The pages the answer cited, in the order it cited them. */
+    sources: PublishedAnswerSource[];
+    /** Slugs of related answers on the same site. */
+    related: string[];
+    /**
+     * When the answer was produced, ISO-8601 (`2026-09-22`, or a full timestamp).
+     *
+     * Shown on the page and put in the structured data. An answer is a snapshot of what the
+     * documentation said on a day; publishing it without saying which day would be the one
+     * genuinely misleading thing about these pages.
+     */
+    answeredAt: string;
+}
+/**
+ * Every field a {@link PublishedAnswer} has, written out once.
+ *
+ * Typed as a TOTAL map of the interface's keys: adding a field to {@link PublishedAnswer}
+ * does not compile until someone also writes it down here, and removing one does not compile
+ * until someone deletes it here. That is the point — the field that would break this feature's
+ * one rule is a conversation id, a message id or a visitor's own words, and nobody adds one of
+ * those to a published contract by accident twice.
+ *
+ * It lives in this module, not in a test, because `tsconfig.json` excludes `**\/*.test.ts(x)`
+ * from the program: a totality constraint written in a test file is never compiled and can
+ * therefore never fail. Here it is compiled by `bun run type-check`, which the PR gate and both
+ * publish workflows run, so the constraint is enforced on every path that ships this package.
+ *
+ * `answers.ssr.test.tsx` then checks the runtime half: that this list still matches the
+ * interface field for field, and that no name in it could hold a visitor's conversation. Sites
+ * generating `src/data/answers.ts` can use it the same way, to assert a generated row carries
+ * these keys and no others.
+ */
+declare const PUBLISHED_ANSWER_FIELDS: Record<keyof PublishedAnswer, true>;
+interface PublishedAnswerTopic {
+    name: string;
+    description: string;
+}
+/** Props the pages pass to a site's link adapter. */
+interface AnswerLinkProps {
+    href: string;
+    className?: string;
+    children: ReactNode;
+    "aria-label"?: string;
+}
+/**
+ * The link the pages render for every internal URL. Sites pass a small adapter around their
+ * router's `Link`, so moving between answers stays a client-side navigation; without one the
+ * pages fall back to a plain `<a href>`.
+ */
+type AnswerLinkComponent = ComponentType<AnswerLinkProps>;
+/** The index route. */
+declare const ANSWERS_PATH = "/answers";
+/** Prefix of every answer detail route: `/answer/<slug>`. */
+declare const ANSWER_PATH_PREFIX = "/answer";
+/** Site-relative URL of one answer's page. */
+declare function answerPath(slug: string): string;
+/**
+ * Resolve a route parameter to its answer. Returns `undefined` for an unknown slug — the site
+ * then redirects to `/answers` rather than rendering a soft 404.
+ */
+declare function getAnswerBySlug(answers: readonly PublishedAnswer[], slug: string | null | undefined): PublishedAnswer | undefined;
+/**
+ * True when a source URL is safe to publish as a link.
+ *
+ * `https` only, and a real host: these pages are prerendered and crawled, so a `javascript:`
+ * or `data:` URL that reached the generated data would ship to every visitor as a live link,
+ * and a relative one would resolve against whichever answer page happened to render it. The
+ * ORIGIN allow-list belongs in the generator, which knows the catalog; this is the page's own
+ * last check, in the same spirit as the inline-image guard in the chat.
+ */
+declare function isPublishedSourceUrl(url: string): boolean;
+/**
+ * The host shown beside a source, `www.` removed.
+ *
+ * Same normalisation the chat's reference cards apply, so a source reads the same way whether
+ * a visitor met it in a conversation or on one of these pages. Returns `""` for anything
+ * unparseable — the label is decorative, and {@link isPublishedSourceUrl} has already decided
+ * whether the link renders at all.
+ */
+declare function answerSourceHost(url: string): string;
 
+interface AnswersPageProps {
+    /** Product display name, e.g. `"VibeControls"`. */
+    productName: string;
+    /** Public origin of the site, e.g. `"https://vibecontrols.com"`. Used for absolute URLs. */
+    siteUrl: string;
+    answers: readonly PublishedAnswer[];
+    /** Section order and descriptions. Answers in an unlisted topic still render, last. */
+    topics?: readonly PublishedAnswerTopic[];
+    /** Call to action rendered in the hero (e.g. the site's primary buttons). */
+    cta?: ReactNode;
+    /** Router adapter for internal links. Defaults to a plain `<a href>`. */
+    linkComponent?: AnswerLinkComponent;
+    /** Overrides the `<h1>`. Default: the localised `"<productName> answers"`. */
+    title?: string;
+    /** Overrides the meta description and the hero lead. */
+    description?: string;
+    /**
+     * BCP-47 locale for the page chrome. Defaults to the document's own `lang`, then the
+     * browser. The ANSWERS themselves are English whatever this says — see `answers-i18n.ts`.
+     */
+    locale?: string;
+    /** Extra classes for the page root. */
+    className?: string;
+}
+interface AnswerDetailPageProps {
+    productName: string;
+    siteUrl: string;
+    /** The answer to render. The site resolves the slug and redirects when it is unknown. */
+    answer: PublishedAnswer;
+    /** Every answer on the site — for related questions and previous / next. */
+    answers: readonly PublishedAnswer[];
+    topics?: readonly PublishedAnswerTopic[];
+    /**
+     * Extra origins an illustration embedded in the answer may load from.
+     *
+     * The site's own origin and the origins of this answer's sources are always allowed, which
+     * covers every image the harness can legitimately have embedded. Pass more only when an
+     * answer cites a page whose images live elsewhere in the catalog, and pass a stable array.
+     */
+    imageOrigins?: readonly string[];
+    /**
+     * Where "Ask your own question" goes. `null` removes the link — pass that on a site with no
+     * `/explore` route, rather than shipping a link to a page that does not exist.
+     */
+    askHref?: string | null;
+    /** Call to action rendered as a band at the end of the page. */
+    cta?: ReactNode;
+    linkComponent?: AnswerLinkComponent;
+    locale?: string;
+    className?: string;
+}
 /**
- * Canonical Burdenoff ecosystem product list used by WebsiteSwitcher.
+ * Heading overrides for a PUBLISHED answer, merged over the shared answer components.
  *
- * Sourced from `~/products/websites/burdenoff-website/src/data/products.ts`.
- * Keep this in sync when products are added, renamed, or moved.
+ * In the chat an answer is one message in a stream and its `#` headings bother nobody. On a
+ * crawled page the outline is the page's structure: the question is the `<h1>` and "Answer"
+ * is an `<h2>`, so an answer that opens with `## Plans` would put a second `<h2>` inside a
+ * section and an answer that opens with `#` would put a SECOND `<h1>` on the page. Both are
+ * things a crawler reads as the page changing subject.
+ *
+ * So every heading the model wrote is pushed below the page's own: `#` and `##` become `<h3>`
+ * (the first real level inside the answer section), and the rest follow, floored at `<h6>`.
+ * The words are untouched — only the level moves.
+ *
+ * Module-level on purpose: react-markdown uses an override as the element TYPE, so rebuilding
+ * this object during a render would remount everything under it.
  */
-declare const ECOSYSTEM_PRODUCTS: WebsiteSwitcherProduct[];
+declare const ANSWER_HEADING_SHIFT: Components;
+/**
+ * `/answers` — every published answer on the site, grouped by topic, with a client-side
+ * search and topic filter. Filters start at "All", so the prerendered page lists everything.
+ */
+declare function AnswersPage({ productName, siteUrl, answers, topics, cta, linkComponent, title, description, locale, className, }: AnswersPageProps): react.JSX.Element;
+/**
+ * `/answer/:slug` — one question, the answer, and the pages it came from.
+ */
+declare function AnswerDetailPage(props: AnswerDetailPageProps): react.JSX.Element;
 
 /**
  * Localisation for the `/explore` chat surface.
@@ -296,6 +507,38 @@ interface ExploreStrings {
     feedbackDismiss: string;
     feedbackThanks: string;
     feedbackNotSent: string;
+    /**
+     * The trigger, in its two homes: `escalateOpen` is the quiet one under an answer we DID
+     * give, and the amber "we could not find this" banner reuses `askHuman` so that sentence
+     * keeps reading as one sentence.
+     */
+    escalateOpen: string;
+    escalateTitle: string;
+    escalateBody: string;
+    escalateEmailLabel: string;
+    escalateEmailPlaceholder: string;
+    escalateNoteLabel: string;
+    escalateSubmit: string;
+    escalateSending: string;
+    escalateCancel: string;
+    /**
+     * Shown for BOTH the client's own pre-flight and the server's `INVALID_EMAIL`. The two
+     * disagree about what is deliverable and the server is right, but the visitor's next
+     * action is identical either way: check the address.
+     */
+    escalateInvalidEmail: string;
+    /**
+     * The success line. Takes `{email}` — and it is filled with the address the SERVER
+     * returned, not the one in the box, because on a repeat handover the reply goes to
+     * whichever address the first one used.
+     *
+     * Used for `created: false` as well: a visitor asking for help is not told "you already
+     * did that".
+     */
+    escalateSent: string;
+    escalateRateLimited: string;
+    escalateCaptcha: string;
+    escalateFailed: string;
     prevSuggestion: string;
     nextSuggestion: string;
     /**
@@ -323,6 +566,21 @@ interface ExploreStrings {
     /** Label of the per-answer copy control, and its failure state. */
     copyAnswer: string;
     copyFailed: string;
+    /**
+     * Label of the per-answer read-aloud control, in its two states.
+     *
+     * A toggle, exactly like the composer's dictation button: one control whose label says
+     * what pressing it does NOW, never a second button that appears while it is speaking.
+     */
+    readAloud: string;
+    stopReading: string;
+    /**
+     * Accessible name of the scrollable box a table in an answer sits in.
+     *
+     * A scrollable region needs a name and a tab stop, or a keyboard visitor cannot reach the
+     * columns that are off the edge. The `<table>` inside it keeps its own semantics.
+     */
+    answerTable: string;
     /** Accessible name of the provenance row under an answer. */
     groundedIn: string;
     /** How many sources the answer cites. `sourceCountMany` takes `{count}`. */
@@ -350,5 +608,155 @@ interface ExploreStrings {
     capabilities: [string, string, string];
     prompts: string[];
 }
+declare function speechLocaleOf(locale: ExploreLocale): string;
+
+/**
+ * Localisation for the published answer pages.
+ *
+ * Same arrangement, and the same reasons, as `explore-i18n.ts`: the strings are bundled
+ * rather than fetched, because these pages are prerendered and a runtime translation request
+ * in front of the first paint would defeat the point of prerendering them. The locale set,
+ * the resolver and the `{placeholder}` filler are IMPORTED from there rather than repeated —
+ * one locale list for the whole explore surface, so a seventh language is added in one place.
+ *
+ * ## What is localised, and what is not
+ *
+ * The chrome — headings, labels, the provenance note, the breadcrumb — is localised into the
+ * six locales the products ship. **The answer itself is English**, because that is what the
+ * harness produced for the curated English question; nothing here translates it, and nothing
+ * here pretends it is translated.
+ *
+ * That split is also MARKED UP, not merely true: the pages carry `dir="rtl"` on their own
+ * subtree in Arabic (`isRtlLocale`, re-exported here so the pages have one locale module), and
+ * put `lang="en"` on the English content inside it. A page that declares itself Arabic and
+ * then prints an English answer tells a screen reader to read English with Arabic phonemes,
+ * and tells a crawler the answer is in a language it is not.
+ *
+ * ## The three borrowed strings
+ *
+ * `answerTable`, `conceptIllustration` and `opensInNewTab` come straight from
+ * `exploreStrings`. They are the words the ANSWER BODY renders, and the answer body is the
+ * same component on both surfaces — two phrasings for the same caveat read as two different
+ * caveats, which is the rule the illustration badge already follows.
+ */
+
+interface AnswerStrings extends AnswerRendererStrings {
+    breadcrumbHome: string;
+    /** The section's own name: breadcrumb, nav item, back link. */
+    answers: string;
+    /** The index page's `<h1>`. Takes `{product}`. */
+    indexHeading: string;
+    /** The lead under it. Takes `{product}`. */
+    indexLead: string;
+    /** `<title>` of the index page; PageHead appends the product name itself. */
+    seoIndexTitle: string;
+    /** Its `<meta name="description">`. Takes `{product}`. */
+    seoIndexDescription: string;
+    searchLabel: string;
+    searchPlaceholder: string;
+    filterByTopic: string;
+    allTopics: string;
+    /** Takes `{shown}` and `{total}`. */
+    showingCount: string;
+    noMatchesTitle: string;
+    noMatchesBody: string;
+    clearFilters: string;
+    noneYetTitle: string;
+    /** Takes `{product}`. */
+    noneYetBody: string;
+    questionCountOne: string;
+    /** Takes `{count}`. */
+    questionCountMany: string;
+    sourceCountOne: string;
+    /** Takes `{count}`. */
+    sourceCountMany: string;
+    answerHeading: string;
+    sourcesHeading: string;
+    sourcesLead: string;
+    aboutTitle: string;
+    /**
+     * The honest description of what the reader is looking at. Takes `{date}`.
+     *
+     * Every clause is load-bearing, and the wording was chosen against the alternatives:
+     *
+     * - **"Produced by our own assistant"** — not "written by our team", which would be false,
+     *   and not "AI-powered answers", which is marketing language for a disclosure.
+     * - **"on {date}"** — an answer is a snapshot of what the documentation said on a day. The
+     *   single genuinely misleading thing these pages could do is present a year-old answer as
+     *   current, so the date is in the sentence rather than in small print beside it.
+     * - **"The pages it drew on are linked under the answer"** — it tells the reader where to
+     *   check, which is the only thing that makes the rest of the note actionable.
+     * - **"not a statement from a person"** — the sentence people actually need. This is a
+     *   marketing surface, and a visitor who takes a generated paragraph for a commitment from
+     *   us has been misled by us.
+     * - **"where it and a linked page disagree, the page is right"** — says which source wins,
+     *   instead of a hedge ("may contain errors") that tells nobody what to do about it.
+     *
+     * Deliberately NOT said: that the answers are "frequently asked" or "the questions our
+     * customers ask most". They are a question set we chose. We have no measurement behind a
+     * popularity claim — and the one table that could measure it is the visitor question log,
+     * which this feature must never read (see `answers-types.ts`).
+     */
+    aboutBody: string;
+    /** Takes `{date}`. */
+    answeredOn: string;
+    topicsHeading: string;
+    relatedHeading: string;
+    /** Takes `{topic}`. */
+    moreInTopic: string;
+    previousQuestion: string;
+    nextQuestion: string;
+    /** Takes `{product}`. */
+    allAnswers: string;
+    askYourOwn: string;
+}
+declare function answerStrings(locale: ExploreLocale): AnswerStrings;
+/**
+ * `answeredAt` as a date a person reads.
+ *
+ * Two things are pinned rather than left to the environment, because these pages are
+ * serialised from the post-hydration DOM: the machine that prerenders them and the browser
+ * that hydrates them must produce the SAME string, or React replaces the node on hydration.
+ *
+ * - **An explicit locale tag**, never the ambient default — the prerender runs in headless
+ *   Chromium on a server whose locale is nobody's.
+ * - **An explicit numbering system.** CLDR has changed the default digits for `ar` before;
+ *   two engines on different CLDR versions would then render the same date differently, and
+ *   the text React hydrated would not be the text it prerendered. All six locales already
+ *   default to Latin digits, so this pins today's output rather than changing it.
+ * - **`timeZone: "UTC"`**, because `new Date("2026-09-22")` is UTC midnight and formatting it
+ *   in a negative-offset zone would print the 21st. A published date that moves by a day
+ *   depending on who looks at it is worse than no date.
+ *
+ * Returns `""` for an unparseable value so a bad row loses its date line rather than printing
+ * "Invalid Date" on a marketing page.
+ */
+declare function formatAnswerDate(value: string, locale: ExploreLocale): string;
+
+declare const buttonVariants: (props?: ({
+    variant?: "link" | "default" | "destructive" | "outline" | "secondary" | "ghost" | null | undefined;
+    size?: "default" | "sm" | "lg" | "icon" | null | undefined;
+} & class_variance_authority_types.ClassProp) | undefined) => string;
+interface ButtonProps extends react.ButtonHTMLAttributes<HTMLButtonElement>, VariantProps<typeof buttonVariants> {
+    asChild?: boolean;
+}
+declare const Button: react.ForwardRefExoticComponent<ButtonProps & react.RefAttributes<HTMLButtonElement>>;
+
+declare const Input: react.ForwardRefExoticComponent<Omit<react.DetailedHTMLProps<react.InputHTMLAttributes<HTMLInputElement>, HTMLInputElement>, "ref"> & react.RefAttributes<HTMLInputElement>>;
+
+declare const Label: react.ForwardRefExoticComponent<Omit<LabelPrimitive.LabelProps & react.RefAttributes<HTMLLabelElement>, "ref"> & VariantProps<(props?: class_variance_authority_types.ClassProp | undefined) => string> & react.RefAttributes<HTMLLabelElement>>;
+
+/** Native `<select>` wrapper matching the `Input` design tokens. */
+declare const Select: react.ForwardRefExoticComponent<Omit<react.DetailedHTMLProps<react.SelectHTMLAttributes<HTMLSelectElement>, HTMLSelectElement>, "ref"> & react.RefAttributes<HTMLSelectElement>>;
+
+declare const Textarea: react.ForwardRefExoticComponent<Omit<react.DetailedHTMLProps<react.TextareaHTMLAttributes<HTMLTextAreaElement>, HTMLTextAreaElement>, "ref"> & react.RefAttributes<HTMLTextAreaElement>>;
+
+/**
+ * Canonical Burdenoff ecosystem product list used by WebsiteSwitcher.
+ *
+ * Sourced from `~/products/websites/burdenoff-website/src/data/products.ts`.
+ * Keep this in sync when products are added, renamed, or moved.
+ */
+declare const ECOSYSTEM_PRODUCTS: WebsiteSwitcherProduct[];
 
-export { Button, type ButtonProps, CONCEPTS_PATH, CONCEPT_ILLUSTRATION_NOTICE, CONCEPT_PATH_PREFIX, CareersPostingOption, CareersSubmissionForm, type CareersSubmissionFormProps, type Concept, type ConceptCategory, ConceptDetailPage, type ConceptDetailPageProps, type ConceptDevice, type ConceptImage, type ConceptLinkComponent, type ConceptLinkProps, ConceptsPage, type ConceptsPageProps, ECOSYSTEM_PRODUCTS, EXPLORE_LOCALES, type ExploreLocale, type ExploreStrings, Input, Label, Select, Textarea, WebsiteSwitcherProduct, buttonVariants, conceptPath, getConceptBySlug, isValidUrl };
+export { ANSWERS_PATH, ANSWER_HEADING_SHIFT, ANSWER_PATH_PREFIX, AnswerDetailPage, type AnswerDetailPageProps, type AnswerLinkComponent, type AnswerLinkProps, AnswerRendererStrings, type AnswerStrings, AnswersPage, type AnswersPageProps, Button, type ButtonProps, CONCEPTS_PATH, CONCEPT_ILLUSTRATION_NOTICE, CONCEPT_PATH_PREFIX, CareersPostingOption, CareersSubmissionForm, type CareersSubmissionFormProps, type Concept, type ConceptCategory, ConceptDetailPage, type ConceptDetailPageProps, type ConceptDevice, type ConceptImage, type ConceptLinkComponent, type ConceptLinkProps, ConceptsPage, type ConceptsPageProps, ECOSYSTEM_PRODUCTS, EXPLORE_LOCALES, type ExploreLocale, type ExploreStrings, Input, Label, PUBLISHED_ANSWER_FIELDS, type PublishedAnswer, type PublishedAnswerSource, type PublishedAnswerTopic, Select, Textarea, WebsiteSwitcherProduct, answerPath, answerSourceHost, answerStrings, buttonVariants, conceptPath, formatAnswerDate, getAnswerBySlug, getConceptBySlug, isPublishedSourceUrl, isValidUrl, speechLocaleOf };