executable-stories-react 0.1.16 → 0.2.0

package/dist/index.d.cts

@@ -1,8 +1,10 @@
 import * as react from 'react';
-import { ReactNode } from 'react';
-import * as executable_stories_formatters from 'executable-stories-formatters';
-import { ReportDocMermaid, ReportDocCode, ReportDocSection, ReportDocCustom, StoryReport, ReportSummary as ReportSummary$1, ReportFeature as ReportFeature$1, ReportScenario as ReportScenario$1, ReportStep, ReportDocEntry, ReportDocNote, ReportDocTag, ReportDocKv, ReportDocTable, ReportDocLink, ReportDocScreenshot } from 'executable-stories-formatters';
-export { StoryReport, ReportDocEntry as StoryReportDocEntry, ReportFeature as StoryReportFeature, ReportScenario as StoryReportScenario, ReportStep as StoryReportStep, ReportSummary as StoryReportSummary } from 'executable-stories-formatters';
+import { ReactNode, Ref } from 'react';
+import * as executable_stories_core from 'executable-stories-core';
+import { ReportDocMermaid, ReportDocCode, ReportDocSection, ReportDocCustom, StoryReport, ReportSummary as ReportSummary$1, ReportAttachment, ReportFeature as ReportFeature$1, ReportScenario as ReportScenario$1, ReportStep, ReportDocEntry, ReportDocNote, ReportDocTag, ReportDocKv, ReportDocTable, ReportDocLink, ReportDocScreenshot, ReportDocVideo, ReportDocHtml } from 'executable-stories-core';
+export { StoryReport, ReportDocEntry as StoryReportDocEntry, ReportFeature as StoryReportFeature, ReportScenario as StoryReportScenario, ReportStep as StoryReportStep, ReportSummary as StoryReportSummary } from 'executable-stories-core';
+import { OtelSpan } from 'executable-stories-core/types/otel';
+import * as mermaid from 'mermaid';
 import { z } from 'zod';
 
 /**
@@ -11,6 +13,7 @@ import { z } from 'zod';
  * Used at the boundary where a StoryReport is parsed: the consumer hands us
  * an unknown value (file contents, fetch body, prop) and we return a Result.
  */
+
 type Result<T, E = ReportParseError> = {
     ok: true;
     data: T;
@@ -82,11 +85,43 @@ interface ReportSummaryViewProps {
 }
 declare function ReportSummaryView({ summary, className, ariaLabel }: ReportSummaryViewProps): react.JSX.Element;
 
+/**
+ * Run metadata line (started, duration, version, git SHA, CI) — the React
+ * equivalent of the report's `.meta-info` block. Reads the top-level StoryReport
+ * fields from context.
+ */
+declare function ReportMeta(): react.JSX.Element | null;
+
+/**
+ * Renders scenario attachments. Base64 images embed inline; everything else
+ * becomes a labelled data-URI download link. Mirrors the report's attachments
+ * block (which also inlines images and links other media).
+ */
+declare function ReportAttachments({ attachments }: {
+    attachments: ReportAttachment[];
+}): react.JSX.Element | null;
+
+/**
+ * OTel trace waterfall. Collapsed by default (native <details>, no JS) so it
+ * renders in both the static and interactive reports. Each span is a row with a
+ * depth-indented name and a bar positioned/sized by its time window.
+ */
+declare function ReportTrace({ spans }: {
+    spans: readonly OtelSpan[] | undefined;
+}): react.JSX.Element | null;
+
 declare function ReportFeatureList(): react.JSX.Element;
 
 interface ReportFeatureProps {
     feature: ReportFeature$1;
 }
+/**
+ * Feature group — the report's `.feature` card: a header bar with the feature
+ * title + mono source path and ✓/✗/○ status counts on the right, over a stack
+ * of scenario cards. Kept a semantic <section> (a region), not a shadcn Card
+ * div, so it stays a landmark and doesn't collide with the scenario cards'
+ * `[data-slot="card"]`.
+ */
 declare function ReportFeature({ feature }: ReportFeatureProps): react.JSX.Element;
 
 interface ReportScenarioListProps {
@@ -96,8 +131,14 @@ declare function ReportScenarioList({ feature }: ReportScenarioListProps): react
 
 interface ReportScenarioProps {
     scenario: ReportScenario$1;
+    /**
+     * Omit the card's own title row (status badge + tags still render). Use when
+     * the surrounding page already shows the scenario title as its heading — e.g.
+     * the Astro detail page, where Starlight renders the title as the page `h1`.
+     */
+    hideTitle?: boolean;
 }
-declare function ReportScenario({ scenario }: ReportScenarioProps): react.JSX.Element;
+declare function ReportScenario({ scenario, hideTitle }: ReportScenarioProps): react.JSX.Element;
 
 interface ReportStepsProps {
     scenario: ReportScenario$1;
@@ -114,7 +155,7 @@ declare function ReportDocEntries({ entries }: ReportDocEntriesProps): react.JSX
 
 declare function DocEntry({ entry }: {
     entry: ReportDocEntry;
-}): react.JSX.Element | undefined;
+}): react.JSX.Element;
 
 declare function DocNote({ entry }: {
     entry: ReportDocNote;
@@ -145,24 +186,98 @@ declare function DocSection({ entry }: {
 }): react.JSX.Element;
 
 /**
- * Renders mermaid source as a semantic <pre data-mermaid> by default.
+ * The raw mermaid source as a semantic `<pre data-mermaid>`. This is the
+ * default render and the universal fallback: AI agents, screen readers, and
+ * no-JS views all get the readable source. `<MermaidDiagram>` upgrades this to
+ * a drawn diagram on the client.
+ */
+declare function MermaidSource({ entry, ref }: {
+    entry: ReportDocMermaid;
+    ref?: Ref<HTMLElement>;
+}): react.JSX.Element;
+/**
+ * Renders mermaid source as a semantic `<pre data-mermaid>` by default.
  *
- * AI agents and screen readers get the raw source. To render the diagram
- * visually, supply a `renderers.mermaid` prop with a client-only component
- * (e.g., one that dynamically imports the mermaid library on mount).
+ * To draw the diagram, supply a `renderers.mermaid` prop — e.g. the shipped
+ * `MermaidDiagram` (`renderers={{ mermaid: (e) => <MermaidDiagram entry={e} /> }}`).
  */
 declare function DocMermaid({ entry }: {
     entry: ReportDocMermaid;
 }): react.JSX.Element;
 
+type MermaidApi = typeof mermaid.default;
+type MermaidLoader = () => Promise<MermaidApi>;
+
+/**
+ * Client renderer for `story.mermaid(...)` entries. Dynamically imports the
+ * installed `mermaid` package and draws the diagram to inline SVG, falling back
+ * to the readable source on the server / before load / on error.
+ *
+ * Opt in via `<Report renderers={{ mermaid: (e) => <MermaidDiagram entry={e} /> }} />`.
+ * Requires `mermaid` to be installed (an optional peer dependency). Pass `load`
+ * to override how mermaid is obtained (the standalone report island injects a
+ * CDN loader via `MermaidView` directly).
+ */
+declare function MermaidDiagram({ entry, load }: {
+    entry: ReportDocMermaid;
+    load?: MermaidLoader;
+}): react.JSX.Element;
+
 declare function DocScreenshot({ entry }: {
     entry: ReportDocScreenshot;
 }): react.JSX.Element;
 
+/**
+ * Renders a video doc entry. Video bytes are large and never inlined; `path` is
+ * a URL or a path that resolves alongside the report. Both `path` and `poster`
+ * are adapter-supplied, so they go through the same scheme allow-list as the
+ * DocHtml iframe src (no `javascript:`/`data:` URLs reach the DOM).
+ */
+declare function DocVideo({ entry }: {
+    entry: ReportDocVideo;
+}): react.JSX.Element;
+
+/**
+ * Renders an embedded-HTML doc entry inside a SANDBOXED iframe. All embedded
+ * HTML is untrusted, so the frame is `sandbox="allow-scripts"` only (no
+ * allow-same-origin) — embedded scripts run (charts work) but can't touch the
+ * report DOM, cookies, or storage. Inline `content` → srcdoc (keeps the report
+ * self-contained); `url`/`path` → src (scheme-validated).
+ */
+declare function DocHtml({ entry }: {
+    entry: ReportDocHtml;
+}): react.JSX.Element;
+
 declare function DocCustom({ entry }: {
     entry: ReportDocCustom;
 }): react.JSX.Element;
 
+type ExplorerStatus = "passed" | "failed" | "skipped" | "pending";
+interface ExplorerScenario {
+    id: string;
+    title: string;
+    status: ExplorerStatus;
+    tags: string[];
+    /** Source file / feature label shown on the right. */
+    feature: string;
+    /** Resolved href to the scenario detail page. */
+    href: string;
+}
+interface ScenarioExplorerProps {
+    scenarios: ExplorerScenario[];
+    summary?: {
+        total: number;
+        passed: number;
+        failed: number;
+    };
+}
+/**
+ * Scenario Explorer surface — a shadcn `Command` palette rendered inline. cmdk
+ * filters by the item value (title + feature + tags) as you type; the status
+ * pills pre-filter the list. Each row is a real `<a>` to the detail page.
+ */
+declare function ScenarioExplorer({ scenarios, summary }: ScenarioExplorerProps): react.JSX.Element;
+
 declare function useCustomRenderers(): CustomRenderers;
 declare function useBuiltinRenderers(): BuiltinRenderers;
 
@@ -176,7 +291,7 @@ interface ReportSchemaErrorProps {
 }
 declare function ReportSchemaError({ error }: ReportSchemaErrorProps): react.JSX.Element;
 
-declare function useReport(): executable_stories_formatters.StoryReport;
+declare function useReport(): executable_stories_core.StoryReport;
 
 /**
  * parseStoryReport — boundary validator. Accepts unknown input (file contents,
@@ -185,9 +300,17 @@ declare function useReport(): executable_stories_formatters.StoryReport;
 
 declare function parseStoryReport(input: unknown): Result<StoryReport>;
 
+/**
+ * The supported StoryReport schema major version, factored out of
+ * story-report.schema.ts so the client island can do a cheap version check
+ * WITHOUT importing the Zod schema module (which evaluates z.fromJSONSchema at
+ * module load and pulls ~315kb of zod + locales into the bundle).
+ */
+declare const STORY_REPORT_SCHEMA_MAJOR: 1;
+
 /**
  * StoryReport runtime Zod schema, derived from the canonical JSON Schema
- * at executable-stories-formatters/schemas/story-report-v1.json.
+ * at executable-stories-core/schemas/story-report-v1.json.
  *
  * Uses z.fromJSONSchema (experimental in Zod 4.x). If the API changes upstream,
  * only this file needs updating — the rest of the package consumes
@@ -197,6 +320,5 @@ declare function parseStoryReport(input: unknown): Result<StoryReport>;
  */
 
 declare const storyReportSchema: z.ZodType<unknown, unknown, z.core.$ZodTypeInternals<unknown, unknown>>;
-declare const STORY_REPORT_SCHEMA_MAJOR: 1;
 
-export { type BuiltinRenderers, type CustomRenderer, type CustomRenderers, DocCode, DocCustom, DocEntry, DocKv, DocLink, DocMermaid, DocNote, DocScreenshot, DocSection, DocTable, DocTag, Report, ReportDocEntries, type ReportDocEntriesProps, ReportEmpty, type ReportEmptyProps, ReportFeature, ReportFeatureList, type ReportFeatureProps, type ReportParseError, type ReportParseErrorCode, type ReportProps, ReportRoot, type ReportRootProps, ReportScenario, ReportScenarioList, type ReportScenarioListProps, type ReportScenarioProps, ReportSchemaError, type ReportSchemaErrorProps, ReportStepItem, ReportSteps, type ReportStepsProps, ReportSummary, type ReportSummaryProps, ReportSummaryView, type ReportSummaryViewProps, type Result, STORY_REPORT_SCHEMA_MAJOR, err, ok, parseStoryReport, storyReportSchema, useBuiltinRenderers, useCustomRenderers, useReport };
+export { type BuiltinRenderers, type CustomRenderer, type CustomRenderers, DocCode, DocCustom, DocEntry, DocHtml, DocKv, DocLink, DocMermaid, DocNote, DocScreenshot, DocSection, DocTable, DocTag, DocVideo, type ExplorerScenario, type ExplorerStatus, MermaidDiagram, MermaidSource, Report, ReportAttachments, ReportDocEntries, type ReportDocEntriesProps, ReportEmpty, type ReportEmptyProps, ReportFeature, ReportFeatureList, type ReportFeatureProps, ReportMeta, type ReportParseError, type ReportParseErrorCode, type ReportProps, ReportRoot, type ReportRootProps, ReportScenario, ReportScenarioList, type ReportScenarioListProps, type ReportScenarioProps, ReportSchemaError, type ReportSchemaErrorProps, ReportStepItem, ReportSteps, type ReportStepsProps, ReportSummary, type ReportSummaryProps, ReportSummaryView, type ReportSummaryViewProps, ReportTrace, type Result, STORY_REPORT_SCHEMA_MAJOR, ScenarioExplorer, type ScenarioExplorerProps, err, ok, parseStoryReport, storyReportSchema, useBuiltinRenderers, useCustomRenderers, useReport };

package/dist/index.d.ts

@@ -1,8 +1,10 @@
 import * as react from 'react';
-import { ReactNode } from 'react';
-import * as executable_stories_formatters from 'executable-stories-formatters';
-import { ReportDocMermaid, ReportDocCode, ReportDocSection, ReportDocCustom, StoryReport, ReportSummary as ReportSummary$1, ReportFeature as ReportFeature$1, ReportScenario as ReportScenario$1, ReportStep, ReportDocEntry, ReportDocNote, ReportDocTag, ReportDocKv, ReportDocTable, ReportDocLink, ReportDocScreenshot } from 'executable-stories-formatters';
-export { StoryReport, ReportDocEntry as StoryReportDocEntry, ReportFeature as StoryReportFeature, ReportScenario as StoryReportScenario, ReportStep as StoryReportStep, ReportSummary as StoryReportSummary } from 'executable-stories-formatters';
+import { ReactNode, Ref } from 'react';
+import * as executable_stories_core from 'executable-stories-core';
+import { ReportDocMermaid, ReportDocCode, ReportDocSection, ReportDocCustom, StoryReport, ReportSummary as ReportSummary$1, ReportAttachment, ReportFeature as ReportFeature$1, ReportScenario as ReportScenario$1, ReportStep, ReportDocEntry, ReportDocNote, ReportDocTag, ReportDocKv, ReportDocTable, ReportDocLink, ReportDocScreenshot, ReportDocVideo, ReportDocHtml } from 'executable-stories-core';
+export { StoryReport, ReportDocEntry as StoryReportDocEntry, ReportFeature as StoryReportFeature, ReportScenario as StoryReportScenario, ReportStep as StoryReportStep, ReportSummary as StoryReportSummary } from 'executable-stories-core';
+import { OtelSpan } from 'executable-stories-core/types/otel';
+import * as mermaid from 'mermaid';
 import { z } from 'zod';
 
 /**
@@ -11,6 +13,7 @@ import { z } from 'zod';
  * Used at the boundary where a StoryReport is parsed: the consumer hands us
  * an unknown value (file contents, fetch body, prop) and we return a Result.
  */
+
 type Result<T, E = ReportParseError> = {
     ok: true;
     data: T;
@@ -82,11 +85,43 @@ interface ReportSummaryViewProps {
 }
 declare function ReportSummaryView({ summary, className, ariaLabel }: ReportSummaryViewProps): react.JSX.Element;
 
+/**
+ * Run metadata line (started, duration, version, git SHA, CI) — the React
+ * equivalent of the report's `.meta-info` block. Reads the top-level StoryReport
+ * fields from context.
+ */
+declare function ReportMeta(): react.JSX.Element | null;
+
+/**
+ * Renders scenario attachments. Base64 images embed inline; everything else
+ * becomes a labelled data-URI download link. Mirrors the report's attachments
+ * block (which also inlines images and links other media).
+ */
+declare function ReportAttachments({ attachments }: {
+    attachments: ReportAttachment[];
+}): react.JSX.Element | null;
+
+/**
+ * OTel trace waterfall. Collapsed by default (native <details>, no JS) so it
+ * renders in both the static and interactive reports. Each span is a row with a
+ * depth-indented name and a bar positioned/sized by its time window.
+ */
+declare function ReportTrace({ spans }: {
+    spans: readonly OtelSpan[] | undefined;
+}): react.JSX.Element | null;
+
 declare function ReportFeatureList(): react.JSX.Element;
 
 interface ReportFeatureProps {
     feature: ReportFeature$1;
 }
+/**
+ * Feature group — the report's `.feature` card: a header bar with the feature
+ * title + mono source path and ✓/✗/○ status counts on the right, over a stack
+ * of scenario cards. Kept a semantic <section> (a region), not a shadcn Card
+ * div, so it stays a landmark and doesn't collide with the scenario cards'
+ * `[data-slot="card"]`.
+ */
 declare function ReportFeature({ feature }: ReportFeatureProps): react.JSX.Element;
 
 interface ReportScenarioListProps {
@@ -96,8 +131,14 @@ declare function ReportScenarioList({ feature }: ReportScenarioListProps): react
 
 interface ReportScenarioProps {
     scenario: ReportScenario$1;
+    /**
+     * Omit the card's own title row (status badge + tags still render). Use when
+     * the surrounding page already shows the scenario title as its heading — e.g.
+     * the Astro detail page, where Starlight renders the title as the page `h1`.
+     */
+    hideTitle?: boolean;
 }
-declare function ReportScenario({ scenario }: ReportScenarioProps): react.JSX.Element;
+declare function ReportScenario({ scenario, hideTitle }: ReportScenarioProps): react.JSX.Element;
 
 interface ReportStepsProps {
     scenario: ReportScenario$1;
@@ -114,7 +155,7 @@ declare function ReportDocEntries({ entries }: ReportDocEntriesProps): react.JSX
 
 declare function DocEntry({ entry }: {
     entry: ReportDocEntry;
-}): react.JSX.Element | undefined;
+}): react.JSX.Element;
 
 declare function DocNote({ entry }: {
     entry: ReportDocNote;
@@ -145,24 +186,98 @@ declare function DocSection({ entry }: {
 }): react.JSX.Element;
 
 /**
- * Renders mermaid source as a semantic <pre data-mermaid> by default.
+ * The raw mermaid source as a semantic `<pre data-mermaid>`. This is the
+ * default render and the universal fallback: AI agents, screen readers, and
+ * no-JS views all get the readable source. `<MermaidDiagram>` upgrades this to
+ * a drawn diagram on the client.
+ */
+declare function MermaidSource({ entry, ref }: {
+    entry: ReportDocMermaid;
+    ref?: Ref<HTMLElement>;
+}): react.JSX.Element;
+/**
+ * Renders mermaid source as a semantic `<pre data-mermaid>` by default.
  *
- * AI agents and screen readers get the raw source. To render the diagram
- * visually, supply a `renderers.mermaid` prop with a client-only component
- * (e.g., one that dynamically imports the mermaid library on mount).
+ * To draw the diagram, supply a `renderers.mermaid` prop — e.g. the shipped
+ * `MermaidDiagram` (`renderers={{ mermaid: (e) => <MermaidDiagram entry={e} /> }}`).
  */
 declare function DocMermaid({ entry }: {
     entry: ReportDocMermaid;
 }): react.JSX.Element;
 
+type MermaidApi = typeof mermaid.default;
+type MermaidLoader = () => Promise<MermaidApi>;
+
+/**
+ * Client renderer for `story.mermaid(...)` entries. Dynamically imports the
+ * installed `mermaid` package and draws the diagram to inline SVG, falling back
+ * to the readable source on the server / before load / on error.
+ *
+ * Opt in via `<Report renderers={{ mermaid: (e) => <MermaidDiagram entry={e} /> }} />`.
+ * Requires `mermaid` to be installed (an optional peer dependency). Pass `load`
+ * to override how mermaid is obtained (the standalone report island injects a
+ * CDN loader via `MermaidView` directly).
+ */
+declare function MermaidDiagram({ entry, load }: {
+    entry: ReportDocMermaid;
+    load?: MermaidLoader;
+}): react.JSX.Element;
+
 declare function DocScreenshot({ entry }: {
     entry: ReportDocScreenshot;
 }): react.JSX.Element;
 
+/**
+ * Renders a video doc entry. Video bytes are large and never inlined; `path` is
+ * a URL or a path that resolves alongside the report. Both `path` and `poster`
+ * are adapter-supplied, so they go through the same scheme allow-list as the
+ * DocHtml iframe src (no `javascript:`/`data:` URLs reach the DOM).
+ */
+declare function DocVideo({ entry }: {
+    entry: ReportDocVideo;
+}): react.JSX.Element;
+
+/**
+ * Renders an embedded-HTML doc entry inside a SANDBOXED iframe. All embedded
+ * HTML is untrusted, so the frame is `sandbox="allow-scripts"` only (no
+ * allow-same-origin) — embedded scripts run (charts work) but can't touch the
+ * report DOM, cookies, or storage. Inline `content` → srcdoc (keeps the report
+ * self-contained); `url`/`path` → src (scheme-validated).
+ */
+declare function DocHtml({ entry }: {
+    entry: ReportDocHtml;
+}): react.JSX.Element;
+
 declare function DocCustom({ entry }: {
     entry: ReportDocCustom;
 }): react.JSX.Element;
 
+type ExplorerStatus = "passed" | "failed" | "skipped" | "pending";
+interface ExplorerScenario {
+    id: string;
+    title: string;
+    status: ExplorerStatus;
+    tags: string[];
+    /** Source file / feature label shown on the right. */
+    feature: string;
+    /** Resolved href to the scenario detail page. */
+    href: string;
+}
+interface ScenarioExplorerProps {
+    scenarios: ExplorerScenario[];
+    summary?: {
+        total: number;
+        passed: number;
+        failed: number;
+    };
+}
+/**
+ * Scenario Explorer surface — a shadcn `Command` palette rendered inline. cmdk
+ * filters by the item value (title + feature + tags) as you type; the status
+ * pills pre-filter the list. Each row is a real `<a>` to the detail page.
+ */
+declare function ScenarioExplorer({ scenarios, summary }: ScenarioExplorerProps): react.JSX.Element;
+
 declare function useCustomRenderers(): CustomRenderers;
 declare function useBuiltinRenderers(): BuiltinRenderers;
 
@@ -176,7 +291,7 @@ interface ReportSchemaErrorProps {
 }
 declare function ReportSchemaError({ error }: ReportSchemaErrorProps): react.JSX.Element;
 
-declare function useReport(): executable_stories_formatters.StoryReport;
+declare function useReport(): executable_stories_core.StoryReport;
 
 /**
  * parseStoryReport — boundary validator. Accepts unknown input (file contents,
@@ -185,9 +300,17 @@ declare function useReport(): executable_stories_formatters.StoryReport;
 
 declare function parseStoryReport(input: unknown): Result<StoryReport>;
 
+/**
+ * The supported StoryReport schema major version, factored out of
+ * story-report.schema.ts so the client island can do a cheap version check
+ * WITHOUT importing the Zod schema module (which evaluates z.fromJSONSchema at
+ * module load and pulls ~315kb of zod + locales into the bundle).
+ */
+declare const STORY_REPORT_SCHEMA_MAJOR: 1;
+
 /**
  * StoryReport runtime Zod schema, derived from the canonical JSON Schema
- * at executable-stories-formatters/schemas/story-report-v1.json.
+ * at executable-stories-core/schemas/story-report-v1.json.
  *
  * Uses z.fromJSONSchema (experimental in Zod 4.x). If the API changes upstream,
  * only this file needs updating — the rest of the package consumes
@@ -197,6 +320,5 @@ declare function parseStoryReport(input: unknown): Result<StoryReport>;
  */
 
 declare const storyReportSchema: z.ZodType<unknown, unknown, z.core.$ZodTypeInternals<unknown, unknown>>;
-declare const STORY_REPORT_SCHEMA_MAJOR: 1;
 
-export { type BuiltinRenderers, type CustomRenderer, type CustomRenderers, DocCode, DocCustom, DocEntry, DocKv, DocLink, DocMermaid, DocNote, DocScreenshot, DocSection, DocTable, DocTag, Report, ReportDocEntries, type ReportDocEntriesProps, ReportEmpty, type ReportEmptyProps, ReportFeature, ReportFeatureList, type ReportFeatureProps, type ReportParseError, type ReportParseErrorCode, type ReportProps, ReportRoot, type ReportRootProps, ReportScenario, ReportScenarioList, type ReportScenarioListProps, type ReportScenarioProps, ReportSchemaError, type ReportSchemaErrorProps, ReportStepItem, ReportSteps, type ReportStepsProps, ReportSummary, type ReportSummaryProps, ReportSummaryView, type ReportSummaryViewProps, type Result, STORY_REPORT_SCHEMA_MAJOR, err, ok, parseStoryReport, storyReportSchema, useBuiltinRenderers, useCustomRenderers, useReport };
+export { type BuiltinRenderers, type CustomRenderer, type CustomRenderers, DocCode, DocCustom, DocEntry, DocHtml, DocKv, DocLink, DocMermaid, DocNote, DocScreenshot, DocSection, DocTable, DocTag, DocVideo, type ExplorerScenario, type ExplorerStatus, MermaidDiagram, MermaidSource, Report, ReportAttachments, ReportDocEntries, type ReportDocEntriesProps, ReportEmpty, type ReportEmptyProps, ReportFeature, ReportFeatureList, type ReportFeatureProps, ReportMeta, type ReportParseError, type ReportParseErrorCode, type ReportProps, ReportRoot, type ReportRootProps, ReportScenario, ReportScenarioList, type ReportScenarioListProps, type ReportScenarioProps, ReportSchemaError, type ReportSchemaErrorProps, ReportStepItem, ReportSteps, type ReportStepsProps, ReportSummary, type ReportSummaryProps, ReportSummaryView, type ReportSummaryViewProps, ReportTrace, type Result, STORY_REPORT_SCHEMA_MAJOR, ScenarioExplorer, type ScenarioExplorerProps, err, ok, parseStoryReport, storyReportSchema, useBuiltinRenderers, useCustomRenderers, useReport };