@folienbaukasten/extension-toolkit 1.0.0

package/abi/shims/react.js

@@ -0,0 +1,18 @@
+// Injected into every theme pack in place of `react` (tools/pack-set.ts).
+// A pack must never bundle its own React: two copies in one page are two
+// renderers, and a platform component built by one cannot be rendered by the
+// other. The app publishes the live one on globalThis before it imports a
+// pack (src/sets/runtime.ts).
+const runtime = globalThis.__FBK_SET_RUNTIME__;
+if (!runtime) {
+  throw new Error('This theme was loaded without the Folien Baukasten set runtime.');
+}
+const React = runtime.react;
+export default React.default ?? React;
+export const {
+  Children, Fragment, StrictMode, Suspense, cloneElement, createContext,
+  createElement, forwardRef, isValidElement, lazy, memo, startTransition,
+  useCallback, useContext, useDebugValue, useDeferredValue, useEffect, useId,
+  useImperativeHandle, useInsertionEffect, useLayoutEffect, useMemo,
+  useReducer, useRef, useState, useSyncExternalStore, useTransition,
+} = React;

package/abi/types/charts/geometry.d.ts

@@ -0,0 +1,43 @@
+/** The inner plot rect — the data area, excluding axis labels. */
+export interface PlotArea {
+    x: number;
+    y: number;
+    w: number;
+    h: number;
+}
+/**
+ * Centre of category band `i` of `n`, as a fraction along the plot axis.
+ *
+ * Both renderers put a bar group AND a line's data point at the centre of
+ * its category band (ECharts' `boundaryGap: true`, which is the category
+ * default; Excel and PowerPoint do the same for line charts). Anything
+ * anchored to a category — a marker rule, a row in a side column — belongs
+ * here, not at `i / (n - 1)`, which is the edge-to-edge spacing a scatter
+ * plot would use and is off by half a band everywhere but the middle.
+ */
+export declare function bandCentre(i: number, n: number): number;
+/** Band centre in the chart box's own coordinates: along x for columns and
+ * lines, along y for horizontal bars (category axis inverted, so band 0 is
+ * at the top). */
+export declare function bandCentreX(plot: PlotArea, i: number, n: number): number;
+export declare function bandCentreY(plot: PlotArea, i: number, n: number): number;
+/**
+ * Where a value sits vertically, as a fraction of the chart box — only
+ * meaningful when the spec pins BOTH bounds, because otherwise each renderer
+ * picks its own "nice" axis maximum and the answer differs between them.
+ */
+export declare function valueY(plot: PlotArea, value: number, min: number, max: number): number;
+/**
+ * Minimum vertical distance between two end labels, as a fraction of the
+ * chart box. A 9pt label in a half-slide-tall chart is about this much.
+ */
+export declare const LABEL_MIN_GAP = 0.034;
+/**
+ * Pushes overlapping labels apart, top-first, preserving their order.
+ *
+ * Returns one offset per input (fraction of the chart box, negative is up),
+ * so a caller can apply them wherever its renderer takes an offset. Order is
+ * preserved deliberately: a label that has swapped places with its
+ * neighbour is worse than one sitting slightly off its line.
+ */
+export declare function spreadLabels(ys: number[], minGap?: number): number[];

package/abi/types/charts/option.d.ts

@@ -0,0 +1,15 @@
+import type { EChartsOption } from 'echarts';
+import type { ChartSpec } from '../deck/schema';
+import type { ChartTheme } from './theme';
+/**
+ * ChartSpec → ECharts option. Leans on ECharts defaults wherever the PPTX
+ * side can express the same look; everything themed comes from ChartTheme.
+ *
+ * Tooltips are always on: they only exist on hover, so the measure pass, the
+ * screenshots and the PDF never see them — a livelier preview for free. Entrance animation is opt-in via
+ * `animate`, because the PDF path reloads the page without the capture
+ * flags and would print mid-flight frames.
+ */
+export declare function buildChartOption(spec: ChartSpec, theme: ChartTheme, opts?: {
+    animate?: boolean;
+}): EChartsOption;

package/abi/types/charts/scale.d.ts

@@ -0,0 +1,14 @@
+/** PowerPoint's gap width (% of bar width) → share of the category band. */
+export declare function barFractionFromGapPct(gapPct: number): number;
+/** Share of the category band → PowerPoint's gap width. */
+export declare function gapPctFromBarFraction(fraction: number): number;
+/**
+ * Where the value axis starts under a `zero` baseline: pinned to 0 when the
+ * data is all on one side of it. With negative values present both
+ * renderers already straddle zero on their own, and pinning the minimum
+ * would clip the chart — so the answer is "let it scale".
+ *
+ * `auto` always returns undefined: it truncates the scale, which is the
+ * commonest way these charts mislead, so it has to be asked for.
+ */
+export declare function valueAxisMin(values: Array<number | null>, baseline: 'zero' | 'auto' | undefined): number | undefined;

package/abi/types/charts/theme.d.ts

@@ -0,0 +1,16 @@
+/** Chart-relevant theme tokens, resolved from CSS custom properties at
+ * runtime so theme.css stays the single source of truth. */
+export interface ChartTheme {
+    /** Series palette, '#rrggbb'. */
+    series: string[];
+    positive: string;
+    negative: string;
+    /** Waterfall totals. */
+    neutral: string;
+    /** The theme's accent, for the one series that carries the argument. */
+    accent: string;
+    fontFamily: string;
+    textColor: string;
+    mutedColor: string;
+}
+export declare function readChartTheme(): ChartTheme;

package/abi/types/charts/waterfall.d.ts

@@ -0,0 +1,35 @@
+export interface WaterfallSegments {
+    /** Invisible stack offset. */
+    base: (number | null)[];
+    increase: (number | null)[];
+    decrease: (number | null)[];
+    total: (number | null)[];
+    /**
+     * Label value per category — magnitudes, unsigned: PPTX stacked-chart
+     * labels come from the (positive) series values, so ECharts shows the
+     * same; the bar color conveys direction.
+     */
+    labels: number[];
+    /**
+     * Running total after each category — the height at which category i's
+     * bar hands over to i+1. Both renderers draw the connector line there
+     * (ECharts a custom series, PPTX a native `<c:serLines>`).
+     */
+    ends: number[];
+}
+/**
+ * How much of a category band the column fills. Shared so the preview and
+ * the .pptx put the same amount of air between bars: ECharts takes the
+ * fraction directly, PowerPoint takes the gap *between* bands.
+ */
+export declare const WF_BAR_FRACTION = 0.56;
+export declare const WF_GAP_WIDTH_PCT: number;
+/**
+ * How far the exporter nudges each bar label past the segment's top edge,
+ * as a fraction of the chart area (a `<c:manualLayout>` offset on the
+ * label, from its `inEnd` anchor). A fixed constant, not per-bar
+ * arithmetic: OOXML has no `outEnd` for stacked charts, and this is the
+ * declarative stand-in — ECharts says the same thing with position 'top'.
+ */
+export declare const WF_LABEL_RAISE = -0.04;
+export declare function computeWaterfall(rawDeltas: Array<number | null>, totalIndices?: number[]): WaterfallSegments;

package/abi/types/components/Block.d.ts

@@ -0,0 +1,31 @@
+import type { BlockSpec } from '../deck/schema';
+/**
+ * Content block, rendered as the theme's `card` or `callout` box style —
+ * `variant` selects which (DESIGN-SPEC.md §5.C). All look lives in
+ * theme.css, including which side the accent edge sits on: `callout` is
+ * left-edged in every theme because a left edge means "aside", while `card`
+ * follows the theme's signature side.
+ *
+ * `bullets` render as a real list under the body. Each item is its own
+ * tagged text node so the exporter measures one textbox per bullet — a
+ * single multi-line textbox would lose the marker geometry in PPTX.
+ *
+ * Fills its grid cell, so sibling blocks always share the same height —
+ * enforced by the layout, never by content.
+ *
+ * `path` is the spec's location inside the slide props (`"left"`,
+ * `"items.2.block"`), threaded in by the layout for inline editing — the
+ * component is the only place that knows whether `body` was a string or an
+ * array, so it is where the exact `data-edit` path must be stamped.
+ *
+ * The same path goes on the root as `data-item`: `data-edit` says "this
+ * node's text *is* that scalar", `data-item` says "this node *is* that whole
+ * component-shaped value". Freeform drag hit-tests against those nodes and
+ * the bake reads them to know where a component ends, so the attribute
+ * belongs on the element whose box is the component's visible extent — here
+ * the `.box`, not the inner padding wrapper.
+ */
+export declare function Block({ spec, path }: {
+    spec: BlockSpec;
+    path?: string;
+}): import("react").JSX.Element;

package/abi/types/components/BlockArrow.d.ts

@@ -0,0 +1,16 @@
+/**
+ * Slim right-pointing blade between the "while …" boxes: a solid isosceles
+ * triangle — width tapers from nothing at top/bottom to the apex at
+ * mid-height. Fills its container.
+ *
+ * PPTX: exported as the native `triangle` preset rotated 90° (see
+ * tools/export.ts), which is geometrically identical, so HTML and PPTX
+ * match by construction — the exporter reads the *computed* fill, so a set
+ * that retints the blade needs no export change.
+ *
+ * Colour: `--color-arrow`, falling back to the accent. It is connective
+ * tissue — it says "and then", it is not the point of the slide — so a set
+ * whose accent is loud can quiet it down without a component override. The
+ * fallback keeps the token optional for sets that do not care.
+ */
+export declare function BlockArrow(): import("react").JSX.Element;

package/abi/types/components/Card.d.ts

@@ -0,0 +1,25 @@
+import type { CardSpec } from '../deck/schema';
+/**
+ * One card of a card grid, rendered as the theme's `card` box style.
+ *
+ * All look lives in theme.css (.box / .box-edge / .box-inner and the
+ * .box-card* modifiers, DESIGN-SPEC.md §5.C). This component owns only
+ * structure and the export/edit tagging, so a theme restyles every card —
+ * including flipping the accent edge from top to left — without touching
+ * this file.
+ *
+ * Emphasis moves the edge color AND the fill together (§5.B2). The edge is
+ * always present: on a plain card it is muted, on an emphasis card it is the
+ * accent, so a row of cards says which one matters before it is read. That
+ * is why the edge is not conditional the way it used to be.
+ *
+ * The edge and the title separator are real elements rather than CSS
+ * borders, because measure-dom reads computed border and a per-side border
+ * would export as a full outline.
+ *
+ * Fills its grid cell, so sibling cards always share a height.
+ */
+export declare function Card({ spec, path }: {
+    spec: CardSpec;
+    path?: string;
+}): import("react").JSX.Element;

package/abi/types/components/ChartView.d.ts

@@ -0,0 +1,4 @@
+import type { ChartSpec } from '../deck/schema';
+export declare function ChartView({ spec }: {
+    spec: ChartSpec;
+}): import("react").JSX.Element;

package/abi/types/components/DriverTree.d.ts

@@ -0,0 +1,9 @@
+import type { DriverSpec } from '../deck/schema';
+export declare function DriverTree({ root, branches, rootPath, branchesPath, }: {
+    root: string;
+    branches: DriverSpec[];
+    /** `data-edit` paths for the two specs — passed separately because this
+     * component renders two independent props of its layout. */
+    rootPath?: string;
+    branchesPath?: string;
+}): import("react").JSX.Element;

package/abi/types/components/FindingsBanner.d.ts

@@ -0,0 +1,21 @@
+import type { FindingSpec } from '../deck/schema';
+/**
+ * Findings/recommendation banner: accent label segment on the left, light
+ * statement bar filling the rest. Square corners by design (per-corner radii
+ * cannot be exported). The text spans are tagged individually so their
+ * vertically-centered position is measured — the shapes carry no text of
+ * their own.
+ *
+ * The height is FIXED (--banner-height), not content-driven. A one-line and
+ * a two-line finding have to occupy the same band: when the banner grew with
+ * its text, the slide's bottom edge shifted between slides and the deck
+ * visibly breathed from one to the next. Both segments stretch to that
+ * height and center their text, so one line sits mid-band and two lines fill
+ * it.
+ *
+ * Text beyond two lines overflows rather than growing the band — deliberate,
+ * and the overflow check reports it. A finding that long belongs in the body.
+ */
+export declare function FindingsBanner({ spec }: {
+    spec: FindingSpec;
+}): import("react").JSX.Element;

package/abi/types/components/HarveyBall.d.ts

@@ -0,0 +1,12 @@
+import type { HarveyValue } from '../deck/schema';
+/**
+ * Harvey ball, rendered as inline SVG. Exported to PPTX as vector shapes:
+ * an ellipse outline plus (for partial values) a pie segment — see
+ * tools/export.ts. Stroke width is a shared constant with the exporter.
+ */
+export declare const HARVEY_STROKE_PX = 1.5;
+export declare const HARVEY_SIZE_PX = 20;
+export declare function HarveyBall({ value, size }: {
+    value: HarveyValue;
+    size?: number;
+}): import("react").JSX.Element;

package/abi/types/components/HeaderTitle.d.ts

@@ -0,0 +1,19 @@
+import type { ReactNode } from 'react';
+/**
+ * The action title, with one phrase optionally in the theme's highlight
+ * colour (`HeaderSpec.highlight`).
+ *
+ * Shared by every set's Header so the behaviour cannot drift between them,
+ * and so a set that never thought about highlighting still renders it.
+ *
+ * Export note: the highlighted phrase is a `<span>` inside the tagged text
+ * element, not a separate `data-pptx` node. measure-dom's `runsOf` walks one
+ * level of inline markup and emits a styled run per child, so the PPTX gets
+ * a single textbox with a coloured run — which is what a highlighted phrase
+ * has to be to keep wrapping with the sentence around it.
+ *
+ * A `highlight` that is not in the title is ignored rather than throwing:
+ * the model composes these, and a near-miss should cost the colour, not the
+ * slide.
+ */
+export declare function headerTitle(title: string, highlight?: string): ReactNode;

package/abi/types/components/InsightRail.d.ts

@@ -0,0 +1,13 @@
+import type { InsightSpec } from '../deck/schema';
+/**
+ * Takeaway strip: equal columns under a hairline rule, each an accent lead-in
+ * and one line of explanation. A lighter alternative to the FindingsBanner
+ * when a slide has several parallel takeaways rather than one statement.
+ *
+ * Rules and dividers are 1px `shape` divs (per-side borders export as full
+ * outlines); the columns are a grid so they stay equal regardless of length.
+ */
+export declare function InsightRail({ insights, path }: {
+    insights: InsightSpec[];
+    path?: string;
+}): import("react").JSX.Element;

package/abi/types/components/KpiTile.d.ts

@@ -0,0 +1,5 @@
+import type { KpiSpec } from '../deck/schema';
+export declare function KpiTile({ spec, path }: {
+    spec: KpiSpec;
+    path?: string;
+}): import("react").JSX.Element;

package/abi/types/components/Matrix.d.ts

@@ -0,0 +1,5 @@
+import type { MatrixSpec } from '../deck/schema';
+export declare function Matrix({ spec, path }: {
+    spec: MatrixSpec;
+    path?: string;
+}): import("react").JSX.Element;

package/abi/types/components/QuoteColumn.d.ts

@@ -0,0 +1,5 @@
+import type { QuoteColumnSpec } from '../deck/schema';
+export declare function QuoteColumn({ spec, path }: {
+    spec: QuoteColumnSpec;
+    path?: string;
+}): import("react").JSX.Element;

package/abi/types/components/SourceLine.d.ts

@@ -0,0 +1,6 @@
+/** Small source note placed below charts, images and tables. The `data-edit`
+ * path is constant because `source` sits at `props.source` in every layout
+ * that has one (same reasoning as `header.*` in the set chrome). */
+export declare function SourceLine({ text }: {
+    text: string;
+}): import("react").JSX.Element;

package/abi/types/components/Table.d.ts

@@ -0,0 +1,5 @@
+import type { TableSpec } from '../deck/schema';
+export declare function Table({ spec, path }: {
+    spec: TableSpec;
+    path?: string;
+}): import("react").JSX.Element;

package/abi/types/components/Timeline.d.ts

@@ -0,0 +1,5 @@
+import type { TimelineEventSpec } from '../deck/schema';
+export declare function Timeline({ events, path }: {
+    events: TimelineEventSpec[];
+    path?: string;
+}): import("react").JSX.Element;

package/abi/types/components/slide/ContentSlide.d.ts

@@ -0,0 +1,29 @@
+import type { ReactNode } from 'react';
+import type { DeckMeta, FindingSpec, HeaderSpec } from '../../deck/schema';
+import type { SetChrome } from '../../sets/types';
+/**
+ * The chrome every content slide shares: the active set's header, the body,
+ * then the optional findings banner and source line, then the set's footer.
+ * Layouts supply only the body, which is why the views are short.
+ *
+ * It exists as much for geometry as for reuse: the body goes into the
+ * `slide-body` region, whose height is the space left over between the
+ * reserved chrome bands (src/base.css). A body that hugs its content and one
+ * that stretches both live inside that region, so neither can displace the
+ * footer — the layouts cannot get this wrong, because they no longer place
+ * the chrome themselves.
+ *
+ * `chrome` arrives explicitly from the active set via `SlideViewProps` — not
+ * a React context — so defaults live at platform level and a set never
+ * imports another set.
+ */
+export declare function ContentSlide({ chrome, header, finding, source, meta, slideNumber, children, }: {
+    chrome: SetChrome;
+    /** Optional: the quote layout deliberately runs without an action title. */
+    header?: HeaderSpec;
+    finding?: FindingSpec;
+    source?: string;
+    meta: DeckMeta;
+    slideNumber: number;
+    children: ReactNode;
+}): import("react").JSX.Element;

package/abi/types/components/slide/MissingComponent.d.ts

@@ -0,0 +1,26 @@
+import type { DeckMeta } from '../../deck/schema';
+/**
+ * The placeholder shown where an extension component should be and its
+ * extension is not installed.
+ *
+ * Two callers render it: the `component` layout, whose whole body it fills,
+ * and a freeform `component` item whose slot names an extension kind. Both
+ * want the same three things, which is why this is a component rather than a
+ * copied block:
+ *
+ * - it carries no `data-pptx` tags but does carry `data-fallback-component`,
+ *   which is what makes the measurement pass refuse the export instead of
+ *   writing a silently blank PPTX region (src/export/measure-dom.ts)
+ * - it names the extension the way a person would, not by id, whenever the
+ *   deck's own metadata lets us say the name honestly
+ * - in the editor it carries the fix, because the Extensions dialog is one
+ *   click away from the slide that needs it
+ */
+export declare function MissingComponent({ kind, meta, compact, }: {
+    /** The namespaced kind the deck asked for. */
+    kind: string;
+    meta: DeckMeta;
+    /** Tighter padding and no button — for a freeform item, which is a box on
+     * a slide rather than the whole body. */
+    compact?: boolean;
+}): import("react").JSX.Element;

package/abi/types/components/slide/SlideFrame.d.ts

@@ -0,0 +1,20 @@
+import type { ReactNode } from 'react';
+/**
+ * Fixed 1280×720 canvas with safe-area margins; every layout renders inside
+ * one. The `slide-frame` class carries the platform's chrome-containment
+ * rules (src/base.css): the header and footer bands are reserved, so an
+ * oversized body clips instead of pushing the footer off the canvas.
+ *
+ * Platform-owned: sets style the frame through tokens but cannot replace it,
+ * so the containment contract holds for every set by construction.
+ */
+export declare function SlideFrame({ children, bleed, }: {
+    children: ReactNode;
+    /**
+     * Drop the safe-area margins so the body owns the canvas edge to edge
+     * (the `web` layout's full-bleed opener). The frame
+     * becomes the positioning context, because chrome that still has to sign a
+     * bleed slide has nowhere else to sit.
+     */
+    bleed?: boolean;
+}): import("react").JSX.Element;

package/abi/types/components/slide/SlotView.d.ts

@@ -0,0 +1,30 @@
+import type { SlotSpec } from '../../deck/layouts';
+import type { DeckMeta } from '../../deck/schema';
+import type { SetComponents } from '../../sets/types';
+/**
+ * Renders one slot (src/deck/layouts.ts, `SlotSpec`) — the shared "one piece
+ * of content" vocabulary behind a `split` side and a freeform `component`
+ * item. One renderer for both, so a kind cannot mean two different things
+ * depending on which layout reached it.
+ *
+ * `path` is the slot's own location in the slide props (`"left"`,
+ * `"items.2.content"`), and every payload hangs off it under the key the
+ * type declares: `${path}.block`, `${path}.events`, `${path}.columns.0`.
+ * The components stamp their own `data-item`/`data-edit` from that, so the
+ * inline editor addresses a block inside a freeform item exactly as it
+ * addresses one inside a split side.
+ *
+ * The wrappers carry `flex: 1` wherever the content has no height of its
+ * own (a chart in a zero-height box measures to nothing, which is the
+ * failure that ships a blank PPTX region). A grid item ignores `flex`, so
+ * this is inert for `split` and load-bearing for freeform, whose item box
+ * is a flex column sized by `area.h` as a floor.
+ */
+export declare function SlotView({ slot, path, meta, components, }: {
+    slot: SlotSpec;
+    path: string;
+    /** Only the `extension` kind needs these two — a slot that never names an
+     * extension renders without them. */
+    meta?: DeckMeta;
+    components?: SetComponents;
+}): import("react").JSX.Element | null;

package/abi/types/components/slide/registry.d.ts

@@ -0,0 +1,27 @@
+import type { ComponentType } from 'react';
+import type { SharedSlide } from '../../deck/layouts';
+import type { LayoutName, ResolvedSet, SlideViewProps, ThemeSet } from '../../sets/types';
+/**
+ * The platform's default view for every layout in the shared vocabulary.
+ * Typed against `SharedSlide`, so adding a layout without a default view is
+ * a compile error — this is where the old per-set registry exhaustiveness
+ * check now lives.
+ */
+export declare const platformDefaults: {
+    [L in LayoutName]: ComponentType<SlideViewProps<Extract<SharedSlide, {
+        layout: L;
+    }>>>;
+};
+/**
+ * Resolve a set's layout registry: platform defaults merged with the set's
+ * overrides. A missing override is not an error state — it is the normal
+ * case. Lives here rather than in the loader so the standalone template
+ * (which pins one set at build time and never sees the loader's glob) can
+ * resolve without pulling every set into its bundle.
+ */
+/**
+ * @param extensionComponents components from installed packs that provide
+ *   them (src/sets/loader.ts). Kinds are namespaced by pack id, so the set's
+ *   own components cannot collide with them; the set's win if one does.
+ */
+export declare function resolveSet(set: ThemeSet, extensionComponents?: ResolvedSet['components']): ResolvedSet;

package/abi/types/components/slide/views/AgendaSlideView.d.ts

@@ -0,0 +1,8 @@
+import type { SlideViewProps } from '../../../sets/types';
+import type { AgendaSlideSpec } from '../../../deck/layouts';
+/**
+ * Agenda / table of contents: equal-height rows, each an accent-colored
+ * two-digit number and the topic, separated by hairline dividers (1px tagged
+ * shapes, as in Footer — per-side borders would export as full outlines).
+ */
+export declare function AgendaSlideView({ slide, meta, slideNumber, chrome }: SlideViewProps<AgendaSlideSpec>): import("react").JSX.Element;

package/abi/types/components/slide/views/CardsSlideView.d.ts

@@ -0,0 +1,12 @@
+import type { SlideViewProps } from '../../../sets/types';
+import type { CardsSlideSpec } from '../../../deck/layouts';
+/**
+ * Card grid. Up to three cards sit in one row; four or more wrap into three
+ * columns, so a fourth card starts a second row rather than shrinking the
+ * first three past readability.
+ *
+ * The insight rail is body content, not chrome — it comments on the cards —
+ * so it shares the body region with them rather than sitting beside the
+ * findings banner.
+ */
+export declare function CardsSlideView({ slide, meta, slideNumber, chrome }: SlideViewProps<CardsSlideSpec>): import("react").JSX.Element;

package/abi/types/components/slide/views/ChaptersSlideView.d.ts

@@ -0,0 +1,11 @@
+import type { SlideViewProps } from '../../../sets/types';
+import type { ChaptersSlideSpec } from '../../../deck/layouts';
+/**
+ * Section divider: the chapters ahead as equal columns banded by a rule above
+ * and below, split by vertical hairlines. Rules and dividers are 1px `shape`
+ * divs (per-side borders export as full outlines).
+ *
+ * Carries no findings banner by design — a divider states the structure, it
+ * does not argue a point.
+ */
+export declare function ChaptersSlideView({ slide, meta, slideNumber, chrome, }: SlideViewProps<ChaptersSlideSpec>): import("react").JSX.Element;

package/abi/types/components/slide/views/ChartSlideView.d.ts

@@ -0,0 +1,3 @@
+import type { SlideViewProps } from '../../../sets/types';
+import type { ChartSlideSpec } from '../../../deck/layouts';
+export declare function ChartSlideView({ slide, meta, slideNumber, chrome }: SlideViewProps<ChartSlideSpec>): import("react").JSX.Element;

package/abi/types/components/slide/views/ComponentSlideView.d.ts

@@ -0,0 +1,19 @@
+import type { SlideViewProps } from '../../../sets/types';
+import type { ComponentSlideSpec } from '../../../deck/layouts';
+/**
+ * Host for an extension-supplied slide body: a
+ * `ContentSlide` whose single full-body slot is filled by the component the
+ * deck names. The component owns a box, never the slide — chrome, bands and
+ * the overflow contract stay platform-owned by construction.
+ *
+ * An unknown kind blanks only the body: correct chrome, correct slide
+ * number, the rest of the deck untouched, and a placeholder saying which
+ * extension is missing. The placeholder carries no `data-pptx` tags but a
+ * `data-fallback-component` marker, so the measurement pass refuses to
+ * export the deck rather than writing a silently blank PPTX region
+ * (src/export/measure-dom.ts — the FallbackSlide mechanism, one level down).
+ *
+ * In the editor the placeholder also carries the fix (see MissingComponent,
+ * which a freeform `component` item renders too).
+ */
+export declare function ComponentSlideView({ slide, meta, slideNumber, chrome, components, }: SlideViewProps<ComponentSlideSpec>): import("react").JSX.Element;

package/abi/types/components/slide/views/DriverTreeSlideView.d.ts

@@ -0,0 +1,3 @@
+import type { SlideViewProps } from '../../../sets/types';
+import type { DriverTreeSlideSpec } from '../../../deck/layouts';
+export declare function DriverTreeSlideView({ slide, meta, slideNumber, chrome, }: SlideViewProps<DriverTreeSlideSpec>): import("react").JSX.Element;

package/abi/types/components/slide/views/FreeformSlideView.d.ts

@@ -0,0 +1,3 @@
+import type { SlideViewProps } from '../../../sets/types';
+import type { FreeformSlideSpec } from '../../../deck/layouts';
+export declare function FreeformSlideView({ slide, meta, slideNumber, chrome, components, }: SlideViewProps<FreeformSlideSpec>): import("react").JSX.Element;

package/abi/types/components/slide/views/KpiSlideView.d.ts

@@ -0,0 +1,3 @@
+import type { SlideViewProps } from '../../../sets/types';
+import type { KpiSlideSpec } from '../../../deck/layouts';
+export declare function KpiSlideView({ slide, meta, slideNumber, chrome }: SlideViewProps<KpiSlideSpec>): import("react").JSX.Element;

package/abi/types/components/slide/views/MatrixSlideView.d.ts

@@ -0,0 +1,3 @@
+import type { SlideViewProps } from '../../../sets/types';
+import type { MatrixSlideSpec } from '../../../deck/layouts';
+export declare function MatrixSlideView({ slide, meta, slideNumber, chrome }: SlideViewProps<MatrixSlideSpec>): import("react").JSX.Element;

package/abi/types/components/slide/views/QuoteSlideView.d.ts

@@ -0,0 +1,3 @@
+import type { SlideViewProps } from '../../../sets/types';
+import type { QuoteSlideSpec } from '../../../deck/layouts';
+export declare function QuoteSlideView({ slide, meta, slideNumber, chrome }: SlideViewProps<QuoteSlideSpec>): import("react").JSX.Element;

package/abi/types/components/slide/views/QuotesSlideView.d.ts

@@ -0,0 +1,5 @@
+import type { SlideViewProps } from '../../../sets/types';
+import type { QuotesSlideSpec } from '../../../deck/layouts';
+/** Voice-of-customer evidence: equal columns, so a supporting and an opposing
+ * column always line up regardless of how many quotes each holds. */
+export declare function QuotesSlideView({ slide, meta, slideNumber, chrome }: SlideViewProps<QuotesSlideSpec>): import("react").JSX.Element;

package/abi/types/components/slide/views/SplitSlideView.d.ts

@@ -0,0 +1,3 @@
+import type { SlideViewProps } from '../../../sets/types';
+import type { SplitSlideSpec } from '../../../deck/layouts';
+export declare function SplitSlideView({ slide, meta, slideNumber, chrome }: SlideViewProps<SplitSlideSpec>): import("react").JSX.Element;

package/abi/types/components/slide/views/TableSlideView.d.ts

@@ -0,0 +1,3 @@
+import type { SlideViewProps } from '../../../sets/types';
+import type { TableSlideSpec } from '../../../deck/layouts';
+export declare function TableSlideView({ slide, meta, slideNumber, chrome }: SlideViewProps<TableSlideSpec>): import("react").JSX.Element;

package/abi/types/components/slide/views/TimelineSlideView.d.ts

@@ -0,0 +1,3 @@
+import type { SlideViewProps } from '../../../sets/types';
+import type { TimelineSlideSpec } from '../../../deck/layouts';
+export declare function TimelineSlideView({ slide, meta, slideNumber, chrome, }: SlideViewProps<TimelineSlideSpec>): import("react").JSX.Element;

package/abi/types/components/slide/views/TitleSlideView.d.ts

@@ -0,0 +1,7 @@
+import type { SlideViewProps } from '../../../sets/types';
+import type { TitleSlideSpec } from '../../../deck/layouts';
+/** The platform's default title view: accent bar, heading, subheading,
+ * author · date, and an optional title picture filling the right side
+ * (object-fit: cover). No footer. Ignores the spec's `eyebrow` and `chips`
+ * — sets with a place for them override this view (editorial does). */
+export declare function TitleSlideView({ slide }: SlideViewProps<TitleSlideSpec>): import("react").JSX.Element;

package/abi/types/components/slide/views/TwoBlockSlideView.d.ts

@@ -0,0 +1,3 @@
+import type { SlideViewProps } from '../../../sets/types';
+import type { TwoBlockSlideSpec } from '../../../deck/layouts';
+export declare function TwoBlockSlideView({ slide, meta, slideNumber, chrome }: SlideViewProps<TwoBlockSlideSpec>): import("react").JSX.Element;