@openpresentation/opf 0.13.0 → 0.15.1

package/dist/types.d.ts

@@ -1,4 +1,1125 @@
-export { P as Presentation } from './presentation-mG-IYErQ.js';
-export { A as Audience, C as CatalogKind, e as ChartType, f as ColorScheme, F as FontScheme, L as Language, g as Layout, N as Narrative, P as Purpose, S as SocialPlatform, T as Theme, h as Tone } from './catalogs-ywCamd8C.js';
-export { a as SchemaName } from './schemas-BbPonsTz.js';
-export { V as ValidationIssue, e as ValidationResult } from './validator-CIylxoIm.js';
+export { P as Presentation } from './presentation-CDKQVkyI.js';
+export { C as CatalogKind } from './catalog-refs-BSfGELpt.js';
+export { SchemaName } from './schemas.js';
+export { a as Finding, d as FindingCategory, e as FindingFix, f as FindingFocus, b as FindingLocation, F as FindingReport, c as FindingSeverity, g as FindingSuggestion, J as JsonPatchOperation, V as ValidationIssue } from './finding-CT_f_vbD.js';
+import './json-BFSdESOE.js';
+
+/**
+ * Schema for audience records. Each record names an audience archetype (e.g. 'executive', 'engineering-team', 'investor') and carries seniority, technical-fluency, decision-power, and attention-budget hints used by AI-driven generation. Documents reference an audience from 'audience', which also accepts free-form text.
+ *
+ * A document references a record as a bare id or 'name:id' and resolves it in its own catalogs groups first, then in the catalog the host registered for the group's source; engines never fetch a catalog. A published record file carries '$schema' and 'id'; the copy a document embeds under catalogs.<group>.<kind>.<id> carries neither (the key is the id) and no 'x-*' display metadata.
+ */
+interface Audience {
+    /**
+     * Identifies a published record file as a audience record. Required in a published file; an embedded copy omits it.
+     */
+    $schema: "https://openpresentation.org/schema/opf-audience/v1";
+    /**
+     * The audience's id in its catalog, lowercase kebab-case. Required in a published record file; a document references the record by it (a bare id, or 'name:id' for a named group) and embeds it keyed by it, without this field.
+     */
+    id: string;
+    /**
+     * Human-readable audience name shown in pickers.
+     */
+    name: string;
+    /**
+     * One-sentence positioning of the audience — who they are and what they care about.
+     */
+    summary?: string;
+    /**
+     * Longer prose describing the audience archetype and how to address them.
+     */
+    description?: string;
+    /**
+     * Typical seniority level of the audience. Engines use this as a hint for default depth and pacing.
+     */
+    seniority?: ("ic" | "manager" | "director" | "vp" | "c-suite" | "mixed");
+    /**
+     * Typical technical fluency of the audience. AI generation uses this to decide whether to expand or assume technical terminology.
+     */
+    technicalFluency?: ("low" | "medium" | "high" | "mixed");
+    /**
+     * Whether the audience is expected to be informed, to advise, or to actually decide. Shapes the strength of the closing ask.
+     */
+    decisionPower?: ("informational" | "advisory" | "decision-maker");
+    /**
+     * Realistic upper bound on this audience's focused attention for a single presentation, in minutes. Used as a hint when comparing against duration and the resolved narrative's duration range.
+     */
+    attentionBudgetMinutes?: number;
+    /**
+     * Soft cross-link: ids of narratives in the same catalog that work well for this audience. Used by picker UIs to suggest narratives once an audience is chosen. Never resolved, embedded or validated as references.
+     */
+    recommendedNarratives?: string[];
+    /**
+     * Soft cross-link: ids of tones in the same catalog that work well for this audience. Never resolved, embedded or validated as references.
+     */
+    recommendedTones?: string[];
+    /**
+     * Free-form labels for filtering and search.
+     */
+    tags?: string[];
+    /**
+     * Visual previews of the record, used by picker UIs and inline rendering. All sub-fields are optional.
+     */
+    preview?: {
+        /**
+         * Main preview image (PNG/JPG).
+         */
+        src?: string;
+        /**
+         * Smaller thumbnail preview suited to dense grid views.
+         */
+        thumbnailSrc?: string;
+        /**
+         * SVG / vector preview for crisp scaling at any size.
+         */
+        vectorSrc?: string;
+        [k: string]: unknown;
+    };
+    [k: string]: unknown;
+}
+
+/**
+ * Schema for purpose records. Each record names a presentation objective such as informing, aligning, persuading, driving a decision, or selling. Documents reference a purpose from 'purpose', which also accepts free-form text and inline Purpose objects.
+ *
+ * A document references a record as a bare id or 'name:id' and resolves it in its own catalogs groups first, then in the catalog the host registered for the group's source; engines never fetch a catalog. A published record file carries '$schema' and 'id'; the copy a document embeds under catalogs.<group>.<kind>.<id> carries neither (the key is the id) and no 'x-*' display metadata.
+ */
+interface Purpose {
+    /**
+     * Identifies a published record file as a purpose record. Required in a published file; an embedded copy omits it.
+     */
+    $schema: "https://openpresentation.org/schema/opf-purpose/v1";
+    /**
+     * The purpose's id in its catalog, lowercase kebab-case. Required in a published record file; a document references the record by it (a bare id, or 'name:id' for a named group) and embeds it keyed by it, without this field.
+     */
+    id: string;
+    /**
+     * Human-readable purpose name shown in pickers.
+     */
+    name: string;
+    /**
+     * One-sentence positioning of the purpose — what this deck is trying to accomplish.
+     */
+    summary?: string;
+    /**
+     * Longer prose describing when to use this purpose and how it should shape a deck.
+     */
+    description?: string;
+    /**
+     * Desired audience outcome after the presentation.
+     */
+    outcome?: string;
+    /**
+     * Observable signals that the deck accomplished this purpose.
+     */
+    successCriteria?: string[];
+    /**
+     * Soft cross-link: ids of narratives in the same catalog that work well for this purpose. Never resolved, embedded or validated as references.
+     */
+    recommendedNarratives?: string[];
+    /**
+     * Soft cross-link: ids of tones in the same catalog that work well for this purpose. Never resolved, embedded or validated as references.
+     */
+    recommendedTones?: string[];
+    /**
+     * Free-form labels for filtering and search.
+     */
+    tags?: string[];
+    /**
+     * Visual previews of the record, used by picker UIs and inline rendering. All sub-fields are optional.
+     */
+    preview?: {
+        /**
+         * Main preview image (PNG/JPG).
+         */
+        src?: string;
+        /**
+         * Smaller thumbnail preview suited to dense grid views.
+         */
+        thumbnailSrc?: string;
+        /**
+         * SVG / vector preview for crisp scaling at any size.
+         */
+        vectorSrc?: string;
+        [k: string]: unknown;
+    };
+    [k: string]: unknown;
+}
+
+/**
+ * Schema for tone records. Each record names a presentation tone (e.g. 'formal', 'casual', 'inspirational') and carries voice cues, anti-patterns, and sample phrases that AI-driven generation uses to shape output. Documents reference a tone from 'tone'.
+ *
+ * A document references a record as a bare id or 'name:id' and resolves it in its own catalogs groups first, then in the catalog the host registered for the group's source; engines never fetch a catalog. A published record file carries '$schema' and 'id'; the copy a document embeds under catalogs.<group>.<kind>.<id> carries neither (the key is the id) and no 'x-*' display metadata.
+ */
+interface Tone {
+    /**
+     * Identifies a published record file as a tone record. Required in a published file; an embedded copy omits it.
+     */
+    $schema: "https://openpresentation.org/schema/opf-tone/v1";
+    /**
+     * The tone's id in its catalog, lowercase kebab-case. Required in a published record file; a document references the record by it (a bare id, or 'name:id' for a named group) and embeds it keyed by it, without this field.
+     */
+    id: string;
+    /**
+     * Human-readable tone name shown in pickers.
+     */
+    name: string;
+    /**
+     * One-sentence positioning of the tone — when to reach for it.
+     */
+    summary?: string;
+    /**
+     * Longer prose describing the tone and the kinds of decks it suits.
+     */
+    description?: string;
+    /**
+     * Short directives that shape AI generation toward this tone. Phrased as imperatives, e.g. 'use second-person', 'favor short sentences', 'lead with the recommendation'.
+     */
+    voiceCues?: string[];
+    /**
+     * Anti-patterns that AI generation should not produce when this tone is active.
+     */
+    avoid?: string[];
+    /**
+     * Short example phrases that exemplify this tone. Used by picker UIs and as few-shot examples for AI generation.
+     */
+    samplePhrases?: string[];
+    /**
+     * Soft cross-link: ids of narratives in the same catalog this tone pairs well with. Used by picker UIs to suggest narratives once a tone is chosen. Never resolved, embedded or validated as references.
+     */
+    recommendedNarratives?: string[];
+    /**
+     * Free-form labels for filtering and search.
+     */
+    tags?: string[];
+    /**
+     * Visual previews of the record, used by picker UIs and inline rendering. All sub-fields are optional.
+     */
+    preview?: {
+        /**
+         * Main preview image (PNG/JPG).
+         */
+        src?: string;
+        /**
+         * Smaller thumbnail preview suited to dense grid views.
+         */
+        thumbnailSrc?: string;
+        /**
+         * SVG / vector preview for crisp scaling at any size.
+         */
+        vectorSrc?: string;
+        [k: string]: unknown;
+    };
+    [k: string]: unknown;
+}
+
+/**
+ * PowerPoint theme-controlled slide background slot from the active color scheme. These are slots, not assumptions about actual colors: light1 is usually white and dark1 is usually black by convention, but the color scheme controls the real values.
+ *
+ * This interface was referenced by `Theme`'s JSON-Schema
+ * via the `definition` "ThemeBackgroundSlot".
+ */
+type ThemeBackgroundSlot = ("light1" | "light2" | "dark1" | "dark2");
+/**
+ * Schema for theme records. Each theme is a small, named bundle that pairs a color scheme, a font scheme, a default theme-controlled background, and a slide size. Documents reference a theme from design.theme; design.colorScheme, design.fontScheme, design.background and design.dimensions take precedence over the resolved theme. The theme's own colorScheme and fontScheme references resolve in the theme's group first, so a catalog's theme finds that catalog's schemes.
+ *
+ * A document references a record as a bare id or 'name:id' and resolves it in its own catalogs groups first, then in the catalog the host registered for the group's source; engines never fetch a catalog. A published record file carries '$schema' and 'id'; the copy a document embeds under catalogs.<group>.<kind>.<id> carries neither (the key is the id) and no 'x-*' display metadata.
+ */
+interface Theme {
+    /**
+     * Identifies a published record file as a theme record. Required in a published file; an embedded copy omits it.
+     */
+    $schema: "https://openpresentation.org/schema/opf-theme/v1";
+    /**
+     * The theme's id in its catalog, lowercase kebab-case. Required in a published record file; a document references the record by it (a bare id, or 'name:id' for a named group) and embeds it keyed by it, without this field.
+     */
+    id: string;
+    /**
+     * Human-readable theme name shown in pickers.
+     */
+    name: string;
+    /**
+     * One-sentence positioning of the theme — when to reach for it.
+     */
+    summary?: string;
+    /**
+     * Longer prose describing what the theme looks and feels like and the kinds of decks it suits.
+     */
+    description?: string;
+    /**
+     * The theme's default colour scheme: a reference (a bare id or 'name:id') resolved like design.colorScheme, but in the theme's own catalogs group first.
+     */
+    colorScheme?: string;
+    /**
+     * The theme's default font scheme: a reference (a bare id or 'name:id') resolved like design.fontScheme, but in the theme's own catalogs group first.
+     */
+    fontScheme?: string;
+    background?: ThemeBackground;
+    /**
+     * Default slide size for this theme. Accepts the same preset values as design.dimensions.preset.
+     */
+    dimensions?: ("16:9" | "4:3" | "16:10" | "1:1" | "4:5" | "9:16" | "letter" | "a4" | "widescreen" | "standard");
+    /**
+     * Free-form labels for filtering and search.
+     */
+    tags?: string[];
+    /**
+     * Visual previews of the record, used by picker UIs and inline rendering. All sub-fields are optional; engines fall back gracefully when previews aren't available.
+     */
+    preview?: {
+        /**
+         * Main preview image (PNG/JPG). Used as the primary visual in picker UIs and previews of the record.
+         */
+        src?: string;
+        /**
+         * Smaller thumbnail preview suited to dense grid views.
+         */
+        thumbnailSrc?: string;
+        /**
+         * SVG / vector preview for crisp scaling at any size.
+         */
+        vectorSrc?: string;
+        [k: string]: unknown;
+    };
+    [k: string]: unknown;
+}
+/**
+ * Theme-controlled PowerPoint slide background. The slot is resolved through the active color scheme and remains theme-aware.
+ *
+ * This interface was referenced by `Theme`'s JSON-Schema
+ * via the `definition` "ThemeBackground".
+ */
+interface ThemeBackground {
+    /**
+     * Theme-controlled background fill.
+     */
+    type: "theme";
+    slot: ThemeBackgroundSlot;
+    [k: string]: unknown;
+}
+
+/**
+ * Schema for slide-layout records. Each record describes a semantic slide layout: what regions it exposes, what content kinds those regions are intended to hold, how they are arranged (composition) and its design hints. Documents reference a layout from Slide.layout; a slide without a layout, or whose layout resolves nowhere, composes automatically.
+ *
+ * A document references a record as a bare id or 'name:id' and resolves it in its own catalogs groups first, then in the catalog the host registered for the group's source; engines never fetch a catalog. A published record file carries '$schema' and 'id'; the copy a document embeds under catalogs.<group>.<kind>.<id> carries neither (the key is the id) and no 'x-*' display metadata.
+ */
+interface Layout {
+    /**
+     * Identifies a published record file as a layout record. Required in a published file; an embedded copy omits it.
+     */
+    $schema: "https://openpresentation.org/schema/opf-layout/v1";
+    /**
+     * The layout's id in its catalog, lowercase kebab-case. Required in a published record file; a document references the record by it (a bare id, or 'name:id' for a named group) and embeds it keyed by it, without this field.
+     */
+    id: string;
+    /**
+     * Human-readable layout name shown in layout pickers.
+     */
+    name: string;
+    /**
+     * One-sentence positioning of the layout — when to reach for it.
+     */
+    summary?: string;
+    /**
+     * Longer prose describing the layout structure and ideal use cases.
+     */
+    description?: string;
+    design?: DesignHints;
+    /**
+     * Ordered regions the layout exposes. This is the single source of truth for what the layout holds: the content kind, the number of body regions and whether it has a title, subtitle or tag are derived from it (layoutContent in @openpresentation/opf), never stored separately. The engine fills 'title', 'subtitle' and 'tag' placeholders from Slide.title, Slide.subtitle and Slide.tag. The other placeholders are content-kind regions that composition uses to size the body and that pickers use to match layouts. Slide content itself lives either in root payload fields or promoted region keys on Slide. Chrome (slide number, footer, date) is not included here; it is owned by Design.header / Design.footer.
+     */
+    placeholders?: Placeholder[];
+    /**
+     * Free-form labels for filtering and search.
+     */
+    tags?: string[];
+    /**
+     * Visual previews of the record, used by picker UIs and inline rendering. All sub-fields are optional; engines fall back gracefully when previews aren't available.
+     */
+    preview?: {
+        /**
+         * Main preview image (PNG/JPG). Used as the primary visual in picker UIs and previews of the record.
+         */
+        src?: string;
+        /**
+         * Smaller thumbnail preview suited to dense grid views.
+         */
+        thumbnailSrc?: string;
+        /**
+         * SVG / vector preview for crisp scaling at any size.
+         */
+        vectorSrc?: string;
+        [k: string]: unknown;
+    };
+    composition?: Composition;
+    [k: string]: unknown;
+}
+/**
+ * The layout's design hints, with the same keys and values as the deck's design and a slide's design (a slide overrides exactly what its layout sets, by the same name). An absent key means the layout has no opinion. Every key is applied from the record as the lowest-precedence default, per key: the slide's design, then the deck's design, then this record's design, then the engine default, so a layout value nobody overrides is honored without copying it anywhere (a layout's composition.mode still ranks above contentDirection). Composition, the renderer and the PPTX exporter all read the one result.
+ */
+interface DesignHints {
+    /**
+     * Horizontal alignment of the title placeholder.
+     */
+    titleAlignment?: ("left" | "center" | "right");
+    /**
+     * Horizontal alignment of the body regions.
+     */
+    contentAlignment?: ("left" | "center" | "right");
+    /**
+     * Whether the body regions are drawn inside a visible card or surface.
+     */
+    contentBox?: boolean;
+    /**
+     * Axis along which parallel body content is arranged: 'vertical' is a column, 'horizontal' a row. Composition applies it when neither the slide nor this layout's composition sets a mode, below the slide's and the deck's design.contentDirection and above automatic selection.
+     */
+    contentDirection?: ("horizontal" | "vertical");
+    /**
+     * Where the primary chart sits relative to the other body content. Composition applies it below the slide's and the deck's design.chartPrimary, with the semantics described there.
+     */
+    chartPrimary?: ("none" | "top" | "bottom" | "left" | "right");
+    /**
+     * Default fit of the slide's image blocks: 'cover' fills the frame and crops around focus, 'contain' shows the whole picture, 'stretch' scales it to the frame.
+     */
+    imageFit?: ("cover" | "contain" | "stretch");
+    /**
+     * Marker style of lists: 'character' draws the glyph, 'image' draws the deck's icon logo as a picture bullet.
+     */
+    listBullet?: ("character" | "image");
+}
+/**
+ * A single region inside a slide layout. Title, subtitle, and tag placeholders bind to the corresponding Slide fields; every other placeholder describes the content kind that region holds. The array order in the surrounding 'placeholders' field preserves layout region order.
+ *
+ * This interface was referenced by `Layout`'s JSON-Schema
+ * via the `definition` "Placeholder".
+ */
+interface Placeholder {
+    /**
+     * The content kind of the region. This is the one OPF content-kind vocabulary: the same words name a slide's payload fields (text, items, image, video, chart, table, code, metric, quote, timeline). 'title', 'subtitle' and 'tag' are the heading kinds and bind to Slide.title, Slide.subtitle and Slide.tag. 'text' holds text and bullets; 'list' holds items. 'image' is filled by an image payload and 'video' by a video payload. 'metric', 'quote', 'timeline', 'chart', 'table' and 'code' are filled by the payload of the same name; a metric region shows the metric payload with its optional label, description, unit, delta, trend and sentiment.
+     */
+    type: ("title" | "subtitle" | "tag" | "text" | "list" | "image" | "video" | "chart" | "table" | "code" | "metric" | "quote" | "timeline");
+    placement?: ImagePlacement;
+    [k: string]: unknown;
+}
+/**
+ * Image placeholders only. Bleeds the slide's image for this region to one slide edge, as an image block's placement does: the n-th image placeholder places the slide's n-th top-level image (Slide.image or an image block in blocks) unless that block sets its own placement. The headings and the other content compose in the rest of the slide.
+ */
+interface ImagePlacement {
+    /**
+     * The slide edge the image bleeds to. In a right-to-left deck 'left' is the start side, drawn at the right.
+     */
+    edge: ("left" | "right" | "top" | "bottom");
+    /**
+     * Share of the slide width (left, right) or height (top, bottom) given to the band. Default 0.5.
+     */
+    size?: number;
+    /**
+     * Draw the frame inside the slide padding on every side of the band instead of edge to edge. Default false.
+     */
+    inset?: boolean;
+}
+/**
+ * Portable dynamic composition. Slide fields override the resolved layout. Nested groups arrange their children independently, inheriting only minFontSize and overflow. Explicit promoted regions retain their positions.
+ *
+ * This interface was referenced by `Layout`'s JSON-Schema
+ * via the `definition` "Composition".
+ */
+interface Composition {
+    /**
+     * auto chooses a grid from available space and content; grid uses columns; row and column use one horizontal or vertical track.
+     */
+    mode?: ("auto" | "grid" | "row" | "column");
+    /**
+     * Column count for grid. In auto mode this caps the number of columns.
+     */
+    columns?: number;
+    /**
+     * Space between cells as a fraction of the container short edge (canvas at slide root). Default 0.03333333333333333.
+     */
+    gap?: number;
+    /**
+     * Inset as a fraction of the container short edge. Default 0.08 on a slide, 0 inside a group.
+     */
+    padding?: number;
+    /**
+     * Relative track sizes: columns for row/grid/auto, rows for column. Omitted tracks have weight 1; extra weights are ignored.
+     *
+     * @minItems 1
+     * @maxItems 12
+     */
+    weights?: [number] | [number, number] | [number, number, number] | [number, number, number, number] | [number, number, number, number, number] | [number, number, number, number, number, number] | [number, number, number, number, number, number, number] | [number, number, number, number, number, number, number, number] | [number, number, number, number, number, number, number, number, number] | [number, number, number, number, number, number, number, number, number, number] | [number, number, number, number, number, number, number, number, number, number, number] | [number, number, number, number, number, number, number, number, number, number, number, number];
+    /**
+     * Minimum readable text size in reference pixels at a 720-pixel canvas short edge. Default 16. Overflow is diagnosed when text cannot fit at this size.
+     */
+    minFontSize?: number;
+    /**
+     * warn returns diagnostics for content that does not fit; error rejects layout. Content is never silently removed. Default warn.
+     */
+    overflow?: ("warn" | "error");
+}
+
+/**
+ * Schema for chart-type records: display metadata for chart pickers (name, group, expected series, complexity) and the Open XML mapping a picker can describe. One record per chart type that Aspose.Slides officially supports (see mappings.renderers["aspose-slides"].chartType), plus the column-and-line combination 'combo'. A document's chart.type is an engine vocabulary validated directly; engines never look a chart-type record up. pptx.gallery publishes these records and @openpresentation/opf/catalog ships them as catalogDisplay.chartTypes.
+ */
+interface ChartType {
+    /**
+     * Identifies this record as a chart type in the open presentation catalog.
+     */
+    $schema: "https://openpresentation.org/schema/opf-chart-type/v1";
+    /**
+     * The chart-type value (`chart.type`) this record describes. Lowercase kebab-case; it may start with a digit (e.g., '100pct-stacked-column') to mirror conventional chart naming.
+     */
+    id: string;
+    /**
+     * Human-readable name of the chart type, as a chart picker shows it.
+     */
+    name: string;
+    /**
+     * One-sentence positioning: when to reach for this chart variant.
+     */
+    summary?: string;
+    /**
+     * Longer prose describing the chart and ideal use cases.
+     */
+    description?: string;
+    mappings: ChartTypeMappings;
+    /**
+     * Top-level grouping in the chart picker.
+     */
+    group?: string;
+    /**
+     * Display ordering hint within the chart group.
+     */
+    groupSort?: number;
+    /**
+     * Shape of the underlying data: a flat series ('simple'), one with engine-side calculation ('calculated'), parent-child rows ('hierarchical'), or pre-normalized rows ('normalized'). The editor offers only 'simple' types as switch targets for a chart's existing data.
+     */
+    complexity?: ("simple" | "calculated" | "hierarchical" | "normalized");
+    /**
+     * Number of data series this chart type expects: exactly that many, except that a stacked or percent-stacked type and a combination (composition 'mixed', such as combo) expect at least that many. The editor offers a type that expects more than one series only for data with a fitting number of value columns; a one-series type fits one value column, and column, bar, line, area and radar types fit any number.
+     */
+    series?: number;
+    /**
+     * Free-form labels for filtering and search.
+     */
+    tags?: string[];
+    /**
+     * Visual previews of the record, used by picker UIs and inline rendering. All sub-fields are optional; engines fall back gracefully when previews aren't available.
+     */
+    preview?: {
+        /**
+         * Main preview image (PNG/JPG). Used as the primary visual in picker UIs and previews of the record.
+         */
+        src?: string;
+        /**
+         * Smaller thumbnail preview suited to dense grid views.
+         */
+        thumbnailSrc?: string;
+        /**
+         * SVG / vector preview for crisp scaling at any size.
+         */
+        vectorSrc?: string;
+        [k: string]: unknown;
+    };
+    /**
+     * Publisher extension member, such as the `x-gallery` presentation metadata that pptx.gallery adds to the records it publishes. Engines and validators ignore top-level `x-*` members, and the pinned snapshot in spec/catalogs never carries them.
+     *
+     * This interface was referenced by `ChartType`'s JSON-Schema definition
+     * via the `patternProperty` "^x-".
+     */
+    [k: string]: {
+        [k: string]: unknown;
+    } | "https://openpresentation.org/schema/opf-chart-type/v1" | string | ChartTypeMappings | number | "simple" | "calculated" | "hierarchical" | "normalized" | string[] | {
+        /**
+         * Main preview image (PNG/JPG). Used as the primary visual in picker UIs and previews of the record.
+         */
+        src?: string;
+        /**
+         * Smaller thumbnail preview suited to dense grid views.
+         */
+        thumbnailSrc?: string;
+        /**
+         * SVG / vector preview for crisp scaling at any size.
+         */
+        vectorSrc?: string;
+        [k: string]: unknown;
+    } | undefined;
+}
+/**
+ * Canonical and optional renderer-specific mappings used by engines to render this chart type.
+ */
+interface ChartTypeMappings {
+    openxml: OpenXmlChartMapping;
+    /**
+     * Optional renderer-specific mappings. Keys are renderer ids; values are intentionally opaque to OPF. The bundled catalog records the matching Aspose.Slides ChartType enumeration member under the "aspose-slides" key, e.g. {"aspose-slides": {"chartType": "StackedColumn"}}; a mixed composition names the ChartType it starts from and the series type it switches series to, e.g. {"chartType": "ClusteredColumn", "lineSeriesType": "LineWithMarkers"}.
+     */
+    renderers?: {
+        [k: string]: {
+            [k: string]: unknown;
+        };
+    };
+}
+/**
+ * Canonical mapping to Open XML chart structures.
+ */
+interface OpenXmlChartMapping {
+    /**
+     * Primary Open XML chart element or extension chart element, such as 'barChart', 'lineChart', 'pieChart', 'treemapChart', or 'waterfallChart'.
+     */
+    element?: string;
+    /**
+     * Bar direction for Open XML barChart mappings.
+     */
+    barDir?: ("bar" | "col");
+    /**
+     * Open XML chart grouping value when the chart family supports grouping.
+     */
+    grouping?: ("standard" | "clustered" | "stacked" | "percentStacked");
+    /**
+     * Whether the chart type expects visible data markers.
+     */
+    marker?: boolean;
+    /**
+     * Open XML radarStyle value for radarChart mappings.
+     */
+    radarStyle?: ("standard" | "marker" | "filled");
+    /**
+     * Open XML scatterStyle value for scatterChart mappings.
+     */
+    scatterStyle?: ("line" | "lineMarker" | "marker" | "smooth" | "smoothMarker");
+    /**
+     * Whether the chart maps to one standard chart element, multiple combined chart elements, or an Open XML extension chart.
+     */
+    composition?: ("single" | "mixed" | "extension");
+    /**
+     * Optional Open XML extension namespace or element hint for extension charts.
+     */
+    extension?: string;
+    /**
+     * Open XML chart elements used by mixed/composite chart types.
+     */
+    series?: OpenXmlChartMapping1[];
+    /**
+     * Short implementation note for mappings that need renderer interpretation.
+     */
+    notes?: string;
+}
+/**
+ * This interface was referenced by `ChartType`'s JSON-Schema
+ * via the `definition` "OpenXmlChartMapping".
+ */
+interface OpenXmlChartMapping1 {
+    /**
+     * Primary Open XML chart element or extension chart element, such as 'barChart', 'lineChart', 'pieChart', 'treemapChart', or 'waterfallChart'.
+     */
+    element?: string;
+    /**
+     * Bar direction for Open XML barChart mappings.
+     */
+    barDir?: ("bar" | "col");
+    /**
+     * Open XML chart grouping value when the chart family supports grouping.
+     */
+    grouping?: ("standard" | "clustered" | "stacked" | "percentStacked");
+    /**
+     * Whether the chart type expects visible data markers.
+     */
+    marker?: boolean;
+    /**
+     * Open XML radarStyle value for radarChart mappings.
+     */
+    radarStyle?: ("standard" | "marker" | "filled");
+    /**
+     * Open XML scatterStyle value for scatterChart mappings.
+     */
+    scatterStyle?: ("line" | "lineMarker" | "marker" | "smooth" | "smoothMarker");
+    /**
+     * Whether the chart maps to one standard chart element, multiple combined chart elements, or an Open XML extension chart.
+     */
+    composition?: ("single" | "mixed" | "extension");
+    /**
+     * Optional Open XML extension namespace or element hint for extension charts.
+     */
+    extension?: string;
+    /**
+     * Open XML chart elements used by mixed/composite chart types.
+     */
+    series?: OpenXmlChartMapping1[];
+    /**
+     * Short implementation note for mappings that need renderer interpretation.
+     */
+    notes?: string;
+}
+
+/**
+ * Schema for narrative records. A narrative is a plan: a named story arc (e.g. 'problem-solution', 'scqa') as an ordered list of beats, each saying what its slide must do. A document points at one with the string 'narrative' and links its slides to beats with 'slides[].beat'; a narrative the document defines itself is a record in catalogs.custom.narratives. Core validate warns about a 'slides[].beat' id the resolved narrative does not define (opf/unknown-beat) and about a root 'duration' outside this record's 'duration' range (opf/duration-outside-narrative), and reports a beat no slide references (opf/unused-beat).
+ *
+ * A document references a record as a bare id or 'name:id' and resolves it in its own catalogs groups first, then in the catalog the host registered for the group's source; engines never fetch a catalog. A published record file carries '$schema' and 'id'; the copy a document embeds under catalogs.<group>.<kind>.<id> carries neither (the key is the id) and no 'x-*' display metadata.
+ */
+interface Narrative {
+    /**
+     * Identifies a published record file as a narrative record. Required in a published file; an embedded copy omits it.
+     */
+    $schema: "https://openpresentation.org/schema/opf-narrative/v1";
+    /**
+     * The narrative's id in its catalog, lowercase kebab-case. Required in a published record file; a document references the record by it (a bare id, or 'name:id' for a named group) and embeds it keyed by it, without this field.
+     */
+    id: string;
+    /**
+     * Human-readable template name, e.g. 'Problem → Solution'.
+     */
+    name: string;
+    /**
+     * One-sentence description of when and why to use this narrative.
+     */
+    summary?: string;
+    /**
+     * Longer prose describing the narrative arc and ideal use cases. Used by AI-driven generation to seed deck-level direction.
+     */
+    description?: string;
+    /**
+     * Audiences this narrative works well for, e.g. ['executive', 'investor', 'customer'].
+     */
+    audienceFit?: string[];
+    /**
+     * Typical talk length this narrative suits, as a range in minutes. A deck's own target is the root 'duration' (one number); core validate warns when that target lies outside this range, and when 'min' is greater than 'max'.
+     */
+    duration?: {
+        /**
+         * Shortest talk length, in minutes, this narrative suits.
+         */
+        min?: number;
+        /**
+         * Longest talk length, in minutes, this narrative suits.
+         */
+        max?: number;
+    };
+    /**
+     * Free-form labels for filtering and search, e.g. ['business', 'pitch', 'internal'].
+     */
+    tags?: string[];
+    /**
+     * Visual previews of the record, used by picker UIs and inline rendering. All sub-fields are optional; engines fall back gracefully when previews aren't available.
+     */
+    preview?: {
+        /**
+         * Main preview image (PNG/JPG). Used as the primary visual in picker UIs and previews of the record.
+         */
+        src?: string;
+        /**
+         * Smaller thumbnail preview suited to dense grid views.
+         */
+        thumbnailSrc?: string;
+        /**
+         * SVG / vector preview for crisp scaling at any size.
+         */
+        vectorSrc?: string;
+        [k: string]: unknown;
+    };
+    /**
+     * Ordered list of beats that make up the narrative arc.
+     *
+     * @minItems 1
+     */
+    beats: [Beat, ...(Beat)[]];
+    [k: string]: unknown;
+}
+/**
+ * A single narrative beat — a labeled segment of the story arc with a specific dramatic purpose. One beat is one slide: 'type' is that slide's Slide.type and 'layout' is its Slide.layout, so a planner copies them straight into a skeleton deck. Split a heavy beat into several beats rather than giving it several slides.
+ *
+ * This interface was referenced by `Narrative`'s JSON-Schema
+ * via the `definition` "Beat".
+ */
+interface Beat {
+    /**
+     * Stable slug used by Slide.beat to reference this beat. Lowercase kebab-case.
+     */
+    id: string;
+    /**
+     * Human-readable beat name, e.g. 'The Problem'.
+     */
+    name: string;
+    /**
+     * Curator-written prose that explains what this beat should accomplish.
+     */
+    description?: string;
+    /**
+     * Short author-facing instruction for the beat — typically one phrase. Complements 'description' with a concise directive.
+     */
+    instructions?: string;
+    /**
+     * Default content kind for the beat's slide: the same values as Slide.type. Helps engines and planners choose a layout when only the beat is known.
+     */
+    type?: ("text" | "list" | "image" | "video" | "chart" | "table" | "code" | "metric" | "quote" | "timeline");
+    /**
+     * Suggested layout id for the beat's slide, e.g. 'section-divider', 'title-slide', 'text-left'. Resolves the same way as Slide.layout — against catalogs.layouts and the default catalog at https://www.pptx.gallery/layouts.
+     */
+    layout?: string;
+    /**
+     * Optional speaker or thinking cues for the beat: questions the slide should answer. A planner or author turns them into the slide's notes; no engine copies them there on its own.
+     */
+    thoughtCues?: string[];
+    [k: string]: unknown;
+}
+
+/**
+ * Schema for social-platform records: display metadata for authoring UIs (name, brand color, handle example) alongside the URL patterns. The keys of a Socials object are an engine vocabulary validated directly; engines link a handle with the patterns in spec/reference/engine-vocabularies.json and never look a social-platform record up. pptx.gallery publishes these records and @openpresentation/opf/catalog ships them as catalogDisplay.socialPlatforms.
+ */
+interface SocialPlatform {
+    /**
+     * Identifies this record as a social-platform entry in the openpresentation.org catalog.
+     */
+    $schema: "https://openpresentation.org/schema/opf-social-platform/v1";
+    /**
+     * The social platform's key, as written in a Socials object. Lowercase kebab-case.
+     */
+    id: string;
+    /**
+     * Human-readable platform name shown in pickers and footers.
+     */
+    name: string;
+    /**
+     * One-sentence positioning of the platform — what it's used for and who's on it.
+     */
+    summary?: string;
+    /**
+     * Longer prose describing the platform and any rendering conventions (e.g., handle prefixes, distributed instances).
+     */
+    description?: string;
+    /**
+     * Canonical base URL of the platform — used as the prefix when normalizing handles to full URLs.
+     */
+    baseUrl?: string;
+    /**
+     * URL pattern for individual member profiles. Use '{handle}' as the placeholder for the handle (with the prefix already stripped).
+     */
+    profileUrlPattern?: string;
+    /**
+     * Optional URL pattern for organization / company pages, when the platform distinguishes them from member profiles. Use '{handle}' as the placeholder.
+     */
+    companyUrlPattern?: string;
+    /**
+     * Conventional prefix character displayed before the handle (e.g. '@' for X / Mastodon / Threads / TikTok). Empty string when no prefix is used. Renderers strip it before substituting into URL patterns.
+     */
+    handlePrefix?: string;
+    /**
+     * Example handle in its conventional rendered form, used by picker UIs and validation hints.
+     */
+    handleExample?: string;
+    /**
+     * Brand color (hex) for branded icon chips, link styling, or section accents in authoring UIs. Catalog metadata: engines do not draw it.
+     */
+    brandColor?: string;
+    /**
+     * Free-form labels for filtering and search.
+     */
+    tags?: string[];
+    /**
+     * Visual previews of the record, used by picker UIs and inline rendering. All sub-fields are optional; engines fall back gracefully when previews aren't available.
+     */
+    preview?: {
+        /**
+         * Main preview image (PNG/JPG).
+         */
+        src?: string;
+        /**
+         * Smaller thumbnail preview suited to dense grid views.
+         */
+        thumbnailSrc?: string;
+        /**
+         * SVG / vector preview for crisp scaling at any size.
+         */
+        vectorSrc?: string;
+        [k: string]: unknown;
+    };
+    [k: string]: unknown;
+}
+
+/**
+ * Schema for language records: display metadata for the language pickers of authoring tools (name, ISO code, the default font schemes a picker suggests). The document's 'language' is an engine vocabulary, a BCP-47 tag validated directly; engines never look a language record up, and their script, direction, OOXML tag and default script fonts come from spec/reference/engine-vocabularies.json. pptx.gallery publishes these records and @openpresentation/opf/catalog ships them as catalogDisplay.languages.
+ */
+interface Language {
+    /**
+     * Identifies this record as a language in the openpresentation.org catalog.
+     */
+    $schema: "https://openpresentation.org/schema/opf-language/v1";
+    /**
+     * The record's id in the gallery's language catalog, lowercase kebab-case. Documents name a language by its BCP-47 tag ('bcp47'), never by this id.
+     */
+    id: string;
+    /**
+     * Human-readable language name.
+     */
+    name: string;
+    /**
+     * ISO 639-3 (or 639-2) three-letter language code. Carried for engines that prefer ISO codes.
+     */
+    code?: string;
+    /**
+     * BCP-47 language tag for this record. Use 'en-GB' for UK English; 'en-UK' is not a valid BCP-47 region form.
+     */
+    bcp47: string;
+    /**
+     * Curated culture tag for OOXML text-run language attributes (a:rPr/@lang, a:endParaRPr/@lang), in the language-[Script-]REGION form Office recognizes (e.g. 'ja-JP', 'ar-SA', 'ms-MY', 'nb-NO', 'fil-PH', 'zh-CN'). Engines emit it instead of 'bcp47' for a tag without a region; a region-bearing tag written by the author is emitted as written. Display metadata here: engines take the curated tag from their language vocabulary. Curated rather than inferred so output does not depend on the runtime's locale data.
+     */
+    ooxmlLang?: string;
+    /**
+     * Base text direction for the language. When omitted, engines derive it from the script: Arabic (Arab), Hebrew (Hebr), Syriac (Syrc), Thaana (Thaa), N'Ko (Nkoo), Adlam (Adlm), Samaritan (Samr), Mandaic (Mand) and Hanifi Rohingya (Rohg) are right-to-left; every other script is left-to-right. The engine language vocabulary (spec/reference/engine-vocabularies.json) states it for the tags it knows.
+     */
+    direction?: ("ltr" | "rtl");
+    /**
+     * ISO 15924 script code of the language's writing system. The script selects the OOXML font slot the language's text uses: East Asian scripts (Hans, Hant, Hani, Jpan, Kore, Hang, Hira, Kana, Bopo, Yiii) use the eastAsian slot; complex scripts (for example Arab, Hebr, Syrc, Thaa, Deva, Beng, Guru, Gujr, Orya, Taml, Telu, Knda, Mlym, Sinh, Thai, Laoo, Tibt, Mymr, Khmr, Mong) use the complexScript slot; every other script (Latn, Cyrl, Grek, Armn, Geor, Ethi, ...) uses the latin slot. When omitted, engines infer it from the BCP-47 tag. The engine language vocabulary (spec/reference/engine-vocabularies.json) states it for the tags it knows. See docs/programs/font-fidelity-everywhere/script-font-model.md.
+     */
+    script?: string;
+    /**
+     * The font-scheme id a picker suggests for this language when targeting PowerPoint output. Display metadata: engines take a language's default script fonts from their own vocabulary.
+     */
+    fontScheme?: string;
+    /**
+     * The font-scheme id a picker suggests for this language when targeting Google Slides output. Display metadata.
+     */
+    googleFontScheme?: string;
+    /**
+     * One-sentence note about coverage or font defaults.
+     */
+    summary?: string;
+    /**
+     * Longer prose describing the language record and any font-pairing rationale.
+     */
+    description?: string;
+    /**
+     * Free-form labels for filtering and search.
+     */
+    tags?: string[];
+    /**
+     * Visual previews of the record, used by picker UIs and inline rendering. All sub-fields are optional; engines fall back gracefully when previews aren't available.
+     */
+    preview?: {
+        /**
+         * Main preview image (PNG/JPG). Used as the primary visual in picker UIs and previews of the record.
+         */
+        src?: string;
+        /**
+         * Smaller thumbnail preview suited to dense grid views.
+         */
+        thumbnailSrc?: string;
+        /**
+         * SVG / vector preview for crisp scaling at any size.
+         */
+        vectorSrc?: string;
+        [k: string]: unknown;
+    };
+    [k: string]: unknown;
+}
+
+/**
+ * Schema for color-scheme records. Each scheme is a named palette with the twelve PowerPoint color slots (six accents, two darks, two lights, plus hyperlink and followed-hyperlink), suitable for being mapped directly into OOXML theme XML. Documents reference a scheme from design.colorScheme (or design.colorScheme.id) and from a theme's colorScheme; slot overrides on design.colorScheme take precedence over the resolved scheme.
+ *
+ * The slot fields here mirror the inline-override fields on the in-document ColorScheme type (in opf.schema.json), so records and inline OPF overrides are interchangeable.
+ *
+ * A document references a record as a bare id or 'name:id' and resolves it in its own catalogs groups first, then in the catalog the host registered for the group's source; engines never fetch a catalog. A published record file carries '$schema' and 'id'; the copy a document embeds under catalogs.<group>.<kind>.<id> carries neither (the key is the id) and no 'x-*' display metadata.
+ */
+interface ColorScheme {
+    /**
+     * Identifies a published record file as a colour scheme record. Required in a published file; an embedded copy omits it.
+     */
+    $schema: "https://openpresentation.org/schema/opf-color-scheme/v1";
+    /**
+     * The colour scheme's id in its catalog, lowercase kebab-case. Required in a published record file; a document references the record by it (a bare id, or 'name:id' for a named group) and embeds it keyed by it, without this field.
+     */
+    id: string;
+    /**
+     * Human-readable scheme name shown in pickers.
+     */
+    name: string;
+    /**
+     * One-sentence positioning of the palette — what mood it evokes and where to use it.
+     */
+    summary?: string;
+    /**
+     * Longer prose describing the palette and its intended use.
+     */
+    description?: string;
+    /**
+     * Accent 1 color (hex). Mirrors the OOXML accent1 slot.
+     */
+    accent1?: string;
+    /**
+     * Accent 2 color (hex). Mirrors the OOXML accent2 slot.
+     */
+    accent2?: string;
+    /**
+     * Accent 3 color (hex). Mirrors the OOXML accent3 slot.
+     */
+    accent3?: string;
+    /**
+     * Accent 4 color (hex). Mirrors the OOXML accent4 slot.
+     */
+    accent4?: string;
+    /**
+     * Accent 5 color (hex). Mirrors the OOXML accent5 slot.
+     */
+    accent5?: string;
+    /**
+     * Accent 6 color (hex). Mirrors the OOXML accent6 slot.
+     */
+    accent6?: string;
+    /**
+     * Dark 1 color (hex). Typically the deepest neutral; OOXML dark1.
+     */
+    dark1?: string;
+    /**
+     * Dark 2 color (hex). Secondary dark; OOXML dark2.
+     */
+    dark2?: string;
+    /**
+     * Light 1 color (hex). Typically the slide canvas; OOXML lt1.
+     */
+    light1?: string;
+    /**
+     * Light 2 color (hex). Secondary light surface; OOXML lt2.
+     */
+    light2?: string;
+    /**
+     * Hyperlink color (hex). OOXML hlink.
+     */
+    hyperlink?: string;
+    /**
+     * Followed-hyperlink color (hex). OOXML folHlink.
+     */
+    followedHyperlink?: string;
+    /**
+     * Free-form labels for filtering and search.
+     */
+    tags?: string[];
+    /**
+     * Visual previews of the record, used by picker UIs and inline rendering. All sub-fields are optional; engines fall back gracefully when previews aren't available.
+     */
+    preview?: {
+        /**
+         * Main preview image (PNG/JPG). Used as the primary visual in picker UIs and previews of the record.
+         */
+        src?: string;
+        /**
+         * Smaller thumbnail preview suited to dense grid views.
+         */
+        thumbnailSrc?: string;
+        /**
+         * SVG / vector preview for crisp scaling at any size.
+         */
+        vectorSrc?: string;
+        [k: string]: unknown;
+    };
+    [k: string]: unknown;
+}
+
+/**
+ * Schema for font-scheme records. Each scheme pairs a major (heading) and minor (body) font family in the OOXML majorFont/minorFont sense, scoped to a target app (powerpoint or google-slides) and a language family (Latin, East Asian, or Complex Script). Documents reference a scheme from design.fontScheme (or design.fontScheme.id), from a theme's fontScheme and from a language's fontScheme / googleFontScheme. Role overrides on design.fontScheme (heading, body, accent, code), each a font family name, take precedence over the resolved scheme.
+ *
+ * A document references a record as a bare id or 'name:id' and resolves it in its own catalogs groups first, then in the catalog the host registered for the group's source; engines never fetch a catalog. A published record file carries '$schema' and 'id'; the copy a document embeds under catalogs.<group>.<kind>.<id> carries neither (the key is the id) and no 'x-*' display metadata.
+ */
+interface FontScheme {
+    /**
+     * Identifies a published record file as a font scheme record. Required in a published file; an embedded copy omits it.
+     */
+    $schema: "https://openpresentation.org/schema/opf-font-scheme/v1";
+    /**
+     * The font scheme's id in its catalog, lowercase kebab-case. Required in a published record file; a document references the record by it (a bare id, or 'name:id' for a named group) and embeds it keyed by it, without this field.
+     */
+    id: string;
+    /**
+     * Human-readable scheme name shown in pickers.
+     */
+    name: string;
+    /**
+     * Heading (major) font family — mirrors the OOXML majorFont entry.
+     */
+    major: string;
+    /**
+     * Body (minor) font family — mirrors the OOXML minorFont entry.
+     */
+    minor: string;
+    /**
+     * Optional monospaced font family name for code blocks and for inline code runs (TextRun.code). It has the same shape as the OPF FontScheme 'code' role, so a record and an inline design.fontScheme override are interchangeable. OOXML has no code slot, so exporters write this family on code runs. When neither design.fontScheme nor the resolved record defines 'code', engines fall back to Roboto Mono.
+     */
+    code?: string;
+    /**
+     * East Asian script fonts. Maps to the OOXML a:ea element of majorFont (major) and minorFont (minor), and to run-level a:ea. When set, they fill the eastAsian slot for every language; when omitted, the slot comes from this scheme's own major/minor when languageFamily is 'ea' and the scheme's languages list is empty or names the presentation language, then from the presentation language's font scheme for East Asian languages, and otherwise from the latin (major/minor) families. A missing 'major' or 'minor' falls back to the other.
+     */
+    eastAsian?: {
+        /**
+         * Heading (major) eastAsian font family — mirrors majorFont a:ea.
+         */
+        major?: string;
+        /**
+         * Body (minor) eastAsian font family — mirrors minorFont a:ea.
+         */
+        minor?: string;
+    };
+    /**
+     * Complex-script fonts (for example Arabic, Hebrew, Indic and Thai). Maps to the OOXML a:cs element of majorFont (major) and minorFont (minor), and to run-level a:cs. When set, they fill the complexScript slot for every language; when omitted, the slot comes from this scheme's own major/minor when languageFamily is 'cs' and the scheme's languages list is empty or names the presentation language, then from the presentation language's font scheme for complex-script languages, and otherwise from the latin (major/minor) families. A missing 'major' or 'minor' falls back to the other.
+     */
+    complexScript?: {
+        /**
+         * Heading (major) complexScript font family — mirrors majorFont a:cs.
+         */
+        major?: string;
+        /**
+         * Body (minor) complexScript font family — mirrors minorFont a:cs.
+         */
+        minor?: string;
+    };
+    /**
+     * High-level typographic class of the scheme.
+     */
+    type?: ("sans-serif" | "serif" | "monospace");
+    /**
+     * Target application this font pairing is intended for. Metadata for pickers and catalog filters: no engine changes its output by it.
+     */
+    app?: ("powerpoint" | "google-slides");
+    /**
+     * Font-language family this scheme is intended for: 'latin' for Latin-script content, 'ea' (or 'eastAsian', the same value) for East Asian scripts, 'cs' (or 'complexScript', the same value) for Complex Scripts. The long names match the 'eastAsian' and 'complexScript' slot keys; the short names match the OOXML a:ea and a:cs elements; core reads both spellings as one value. As the design font scheme, an 'ea'/'eastAsian' or 'cs'/'complexScript' scheme also fills that script slot with its own major/minor families when its languages list is empty or names the presentation language.
+     */
+    languageFamily?: ("latin" | "ea" | "cs" | "eastAsian" | "complexScript");
+    /**
+     * Optional list of BCP-47 language tags this scheme is curated for. Useful for picker UIs that group fonts by language coverage. As the design font scheme, an 'ea' or 'cs' scheme fills its script slot only when this list is empty or names the presentation language: an entry matches a tag with the same language subtag (and the same script, when the entry names one).
+     */
+    languages?: string[];
+    /**
+     * Short specimen string used by picker UIs to preview the scheme.
+     */
+    textSample?: string;
+    /**
+     * One-sentence positioning of the font pairing.
+     */
+    summary?: string;
+    /**
+     * Longer prose describing the font scheme and where it shines.
+     */
+    description?: string;
+    /**
+     * Free-form labels for filtering and search.
+     */
+    tags?: string[];
+    /**
+     * Visual previews of the record, used by picker UIs and inline rendering. All sub-fields are optional; engines fall back gracefully when previews aren't available.
+     */
+    preview?: {
+        /**
+         * Main preview image (PNG/JPG). Used as the primary visual in picker UIs and previews of the record.
+         */
+        src?: string;
+        /**
+         * Smaller thumbnail preview suited to dense grid views.
+         */
+        thumbnailSrc?: string;
+        /**
+         * SVG / vector preview for crisp scaling at any size.
+         */
+        vectorSrc?: string;
+        [k: string]: unknown;
+    };
+    [k: string]: unknown;
+}
+
+export type { Audience, ChartType, ColorScheme, FontScheme, Language, Layout, Narrative, Purpose, SocialPlatform, Theme, Tone };