@burdenoff/website-sdk 2026.922.4 → 2026.922.5

package/dist/components/explore.d.mts

@@ -146,6 +146,8 @@ declare function summariseReferences(references: readonly ExploreReference[], or
  *   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.
  *
@@ -153,6 +155,26 @@ declare function summariseReferences(references: readonly ExploreReference[], or
  * 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, inlineImageOrigins, isInlineImageAllowed, logoUrlOf, productNamesByOrigin, referenceKindOf, summariseReferences };
+export { ExplorePage, type ExplorePageProps, type ExploreProvenance, type ExploreReferenceKind, answerPlainText, answerSpeechText, inlineImageOrigins, isInlineImageAllowed, logoUrlOf, productNamesByOrigin, referenceKindOf, summariseReferences };

package/dist/components/explore.d.ts

@@ -146,6 +146,8 @@ declare function summariseReferences(references: readonly ExploreReference[], or
  *   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.
  *
@@ -153,6 +155,26 @@ declare function summariseReferences(references: readonly ExploreReference[], or
  * 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, inlineImageOrigins, isInlineImageAllowed, logoUrlOf, productNamesByOrigin, referenceKindOf, summariseReferences };
+export { ExplorePage, type ExplorePageProps, type ExploreProvenance, type ExploreReferenceKind, answerPlainText, answerSpeechText, inlineImageOrigins, isInlineImageAllowed, logoUrlOf, productNamesByOrigin, referenceKindOf, summariseReferences };