pptx-react-viewer 2.17.0 → 2.19.0

package/dist/internals.d.ts

@@ -183,11 +183,18 @@ interface XmlObject {
   [child: string]: XmlObject | XmlObject[] | string | undefined;
 }
 /**
- * Shape lock attributes from `p:cNvSpPr / a:spLocks`.
+ * Lock attributes from an element's non-visual properties node.
  *
  * When a flag is `true` the corresponding user interaction is disabled
  * in the editor (e.g. `noRotation` prevents free rotation of the shape).
  *
+ * One bag covers every family, but the families are NOT interchangeable in
+ * the file: `a:spLocks` (`CT_ShapeLocking`), `a:picLocks`, `a:cxnSpLocks`,
+ * `a:grpSpLocks` (`CT_GroupLocking`) and `a:graphicFrameLocks`
+ * (`CT_GraphicalObjectFrameLocking`) each declare their own attribute subset.
+ * `runtime/shape-lock-containers` holds that table and is what decides which
+ * of these fields may be written for a given element.
+ *
  * @example
  * ```ts
  * const locks: PptxShapeLocks = { noMove: true, noResize: true };
@@ -206,6 +213,14 @@ interface PptxShapeLocks {
   noAdjustHandles?: boolean;
   noChangeArrowheads?: boolean;
   noChangeShapeType?: boolean;
+  /**
+   * `a:graphicFrameLocks/@noDrilldown`: forbids selecting the individual
+   * parts inside a graphic frame (a chart series, a SmartArt node). Declared
+   * ONLY by `CT_GraphicalObjectFrameLocking`, so it is written for tables,
+   * charts, SmartArt, OLE objects and graphic-frame media, and never onto
+   * `a:spLocks` / `a:picLocks` / `a:cxnSpLocks` / `a:grpSpLocks`.
+   */
+  noDrilldown?: boolean;
   /**
    * Text-box flag from `p:cNvSpPr/@txBox`. Not a lock in the strict sense,
    * but it lives on the same non-visual-properties node as `a:spLocks`, so
@@ -1145,6 +1160,22 @@ interface ShapeStyle {
   fontRefIdx?: string;
   /** Raw XML colour child of `<a:fontRef>`. */
   fontRefColorXml?: XmlObject;
+  /**
+   * The fill `<a:fillRef>` resolved to, recorded ONLY when the shape's own
+   * `spPr` authored no fill at all, so the reference is what paints it.
+   *
+   * Its absence therefore means "the fill is the shape's own", and its
+   * presence plus an unchanged flat fill means "still purely inherited": see
+   * `authored-shape-style.ts`, the shape-scope twin of `TextStyle`'s
+   * `inheritedRunStyle`.
+   */
+  inheritedFillStyle?: ShapeStyle;
+  /**
+   * The outline `<a:lnRef>` resolved to, recorded before `spPr/a:ln` was
+   * layered on top. A property that still equals this baseline was never
+   * authored on the shape and must not be written back as if it were.
+   */
+  inheritedLineStyle?: ShapeStyle;
 }
 //#endregion
 //#region src/core/types/text.d.ts
@@ -1185,6 +1216,60 @@ interface ShapeStyle {
 interface TextStyle {
   /** Original `a:rPr` XML retained by projections that share the shape-text model. */
   runPropertiesXml?: XmlObject;
+  /**
+   * The properties this run's OWN `a:rPr` authored, and nothing else.
+   *
+   * A run style is assembled as
+   * `{...inheritedRunStyle, ...authoredRunStyle}`, so the flat style is a
+   * fully RESOLVED view: it cannot say whether `fontSize: 60` came from the
+   * run, from the shape's `a:lstStyle`, from the layout placeholder, from the
+   * master `p:txStyles` or from the theme. Omission is meaningful in OOXML
+   * (§21.1.2.3), so a writer that re-emits the resolved view converts every
+   * inherited value into an authored one and the deck stops being
+   * theme-driven after one save.
+   *
+   * This is the run-scope twin of {@link TextSegment.paragraphProperties},
+   * which is parsed strictly from the paragraph's own `a:pPr` for the same
+   * reason. Present only for runs that came from a parsed deck; absent for
+   * SDK-built text, where the flat style IS the only description and must be
+   * written out in full.
+   */
+  authoredRunStyle?: TextStyle;
+  /**
+   * The resolved inheritance baseline {@link authoredRunStyle} was layered
+   * on top of (shape `a:lstStyle` -> placeholder -> layout -> master
+   * `p:txStyles` -> theme -> `p:defaultTextStyle`).
+   *
+   * Kept alongside the authored half because the two answer different
+   * questions. The authored half says "the source pinned this"; the baseline
+   * says "this value is what inheritance already produces", which is how an
+   * EDIT is told apart from an inherited value: an editor mutates the flat
+   * style without knowing about either field, so a property that now differs
+   * from the baseline was either authored or edited and must be written,
+   * while one that still matches can be left to inherit.
+   *
+   * Holds a reference to the per-paragraph baseline object rather than a
+   * copy, so carrying it costs one pointer per run.
+   */
+  inheritedRunStyle?: TextStyle;
+  /**
+   * Snapshot of the ELEMENT-scope paragraph geometry (alignment, margins,
+   * indent, line and paragraph spacing, tab stops, rtl, line-break flags) as
+   * the load pipeline resolved it.
+   *
+   * Present only on an `element.textStyle` that came from a parsed deck, and
+   * populated only with the geometry keys. It exists so the save path can
+   * answer one question it otherwise cannot: has the user CHANGED the body's
+   * alignment or indent, or is the value simply what the shape's
+   * `a:lstStyle`, its layout placeholder and the master already produce?
+   * Element-level text panels (`textAdvancedPatch`, `alignPatch` and friends
+   * in `pptx-viewer-shared`) write `element.textStyle` and never touch
+   * `segment.paragraphProperties`, so a diff against this snapshot is the
+   * only way to tell an edit from an inheritance artefact.
+   *
+   * @see element-paragraph-geometry.ts
+   */
+  resolvedParagraphGeometry?: TextStyle;
   fontFamily?: string;
   fontSize?: number;
   /** When true, renderer should shrink text to fit the shape bounds. */
@@ -1849,6 +1934,15 @@ interface PptxElementBase {
   shapeId?: string;
   /** Element name from `cNvPr/@name`. Used for morph transition matching via the `!!` naming convention. */
   name?: string;
+  /**
+   * `p:nvSpPr/p:nvPr/p:ph/@type` (lower-cased) when the shape is a placeholder:
+   * `title`, `ctrtitle`, `body`, `subtitle`, `ftr`, `dt`, `sldnum`, ...
+   *
+   * Captured on load so consumers can tell a footer placeholder from a text box
+   * without re-walking `rawXml`. Absent on non-placeholder shapes and on
+   * SDK-created elements.
+   */
+  placeholderType?: string;
   x: number;
   y: number;
   width: number;
@@ -1909,6 +2003,19 @@ interface PptxTextProperties {
   }>;
   /** Placeholder prompt text inherited from layout/master (e.g. "Click to add title"). Shown as a greyed-out hint when the shape has no user-entered text. */
   promptText?: string;
+  /**
+   * The string {@link text} was INHERITED from, when this is a header / footer /
+   * date / slide-number placeholder whose own body the file leaves empty.
+   *
+   * PowerPoint keeps the footer string on the slide master and writes each
+   * slide's copy of the `ftr` placeholder empty, so the empty body means
+   * "render the master's footer here". Rendering needs the resolved string, but
+   * SAVING it into the slide would pin that slide to today's master text and
+   * silently detach it from the Header & Footer dialog. The save writer
+   * therefore leaves the authored empty body alone while `text` still equals
+   * this value, and writes a genuine per-slide override once it does not.
+   */
+  inheritedPlaceholderText?: string;
   /** Linked text box chain ID from `a:bodyPr > a:linkedTxbx/@id` or `a:txbx > a:linkedTxbx/@id`. Text overflows from one linked frame to the next. */
   linkedTxbxId?: number;
   /** Sequence number within a linked text box chain (0-based). */
@@ -2319,6 +2426,12 @@ interface PptxChartLineStyle {
 }
 /** Marker symbol types for line/scatter chart data points. */
 type PptxChartMarkerSymbol = 'circle' | 'dash' | 'diamond' | 'dot' | 'none' | 'picture' | 'plus' | 'square' | 'star' | 'triangle' | 'x' | 'auto';
+/**
+ * `ST_ScatterStyle` (ECMA-376 §21.2.3.40): how a scatter chart joins its points.
+ * `line`/`lineMarker` connect them with straight segments, `smooth`/
+ * `smoothMarker` with a bezier, `marker`/`none` not at all.
+ */
+type PptxChartScatterStyle = 'none' | 'line' | 'lineMarker' | 'marker' | 'smooth' | 'smoothMarker';
 /** Shape properties extracted from c:spPr for chart formatting. */
 interface PptxChartShapeProps {
   fillColor?: string;
@@ -2520,6 +2633,42 @@ interface PptxChartTreemapOptions {
 interface PptxChartSeries {
   name: string;
   values: number[];
+  /**
+   * Per-series x values from `c:ser/c:xVal` (scatter and bubble series only).
+   *
+   * Every `CT_ScatterSer` / `CT_BubbleSer` carries its OWN `c:xVal`, so two
+   * series in one scatter chart routinely plot against different x ranges (the
+   * normal case for measurement data). Reading the x values off the first
+   * series and reusing them everywhere plotted every series against series 1's
+   * x axis. Absent for category-axis chart kinds, where
+   * {@link PptxChartData.categories} is the x axis.
+   */
+  xValues?: number[];
+  /**
+   * Per-series bubble sizes from `c:ser/c:bubbleSize` (bubble series only),
+   * aligned index-for-index with {@link values}.
+   *
+   * `CT_BubbleSer` carries x, y AND size, so a one-series bubble chart is fully
+   * specified. Absent when the source omits `c:bubbleSize`.
+   */
+  bubbleSizes?: number[];
+  /**
+   * Series-level data-label content flags from `c:ser/c:dLbls`.
+   *
+   * PowerPoint writes the flags a user picks in "Format Data Labels" onto the
+   * SERIES, and leaves the chart-type-level `c:dLbls` all-zero, so reading only
+   * the chart-level group reports "show nothing" for a chart that visibly shows
+   * percentages. These override {@link PptxChartStyle.dataLabels}.
+   */
+  dataLabelOptions?: PptxChartDataLabelOptions;
+  /**
+   * Whether the series line is explicitly suppressed
+   * (`c:ser/c:spPr/a:ln/a:noFill`). Line-drawn kinds (line, scatter, radar)
+   * use this to decide whether to draw a connecting line at all; a marker-only
+   * scatter is authored as `scatterStyle="lineMarker"` PLUS this flag, never by
+   * changing the scatter style.
+   */
+  lineNoFill?: boolean;
   /**
    * Blank-value mask aligned index-for-index with {@link values}: `true` marks
    * a category whose numeric cache point (`c:numCache/c:pt`) was absent or
@@ -2863,6 +3012,17 @@ interface PptxChartData {
    * default), so only horizontal bar charts need to carry the field.
    */
   barDirection?: PptxChartBarDirection;
+  /**
+   * Scatter presentation mode (`c:scatterChart/c:scatterStyle/@val`).
+   *
+   * `lineMarker` (PowerPoint's own default for every scatter it writes) and
+   * `smoothMarker` draw a connecting line; `marker` and `none` do not. Whether
+   * the MARKERS appear is decided separately by `c:marker/c:symbol`, and
+   * whether the LINE appears is further gated by
+   * {@link PptxChartSeries.lineNoFill} - PowerPoint expresses "markers only" as
+   * `lineMarker` plus an `a:ln/a:noFill`, not as `marker`.
+   */
+  scatterStyle?: PptxChartScatterStyle;
   /**
    * Bar/column gap between category clusters as a percentage of bar width
    * (`c:gapWidth/@val`, 0 through 500). Absent uses the renderer default.
@@ -3016,6 +3176,53 @@ interface PptxChartData {
  * // => { brightness: 20, contrast: -10, grayscale: true } satisfies PptxImageEffects
  * ```
  */
+/**
+ * One `a14:foregroundMark` / `a14:backgroundMark` polyline hint recorded while
+ * the user painted over the picture in PowerPoint's "Remove Background" mode.
+ * Coordinates are 0..1 fractions of the image.
+ */
+interface PptxBackgroundRemovalMark {
+  x1: number;
+  y1: number;
+  x2: number;
+  y2: number;
+}
+/**
+ * PowerPoint "Remove Background" state (`a14:backgroundRemoval`).
+ *
+ * The four edges are the RETAINED rectangle as 0..1 fractions of the image
+ * (OOXML stores them as per-100000 relative units), and the mark lists are the
+ * segmentation hints the user painted.
+ *
+ * **This is edit-time metadata, not a render instruction.** PowerPoint bakes the
+ * removal into the bitmap referenced by the main `a:blip/@r:embed` and keeps the
+ * pristine original in `a14:imgLayer/@r:embed`. Verified against PowerPoint COM:
+ * a slide exported with and without this element is byte-identical. A renderer
+ * that clips to the retained rectangle would clip an image whose background has
+ * already been removed.
+ *
+ * @example
+ * ```ts
+ * const removal: PptxBackgroundRemoval = { top: 0.12, bottom: 0.88, left: 0.07, right: 0.93 };
+ * // => retains the middle of the image; the marks list stays empty
+ * ```
+ */
+interface PptxBackgroundRemoval {
+  /** Top edge of the retained rectangle (0..1 fraction of the image height). */
+  top: number;
+  /** Bottom edge of the retained rectangle (0..1 fraction of the image height). */
+  bottom: number;
+  /** Left edge of the retained rectangle (0..1 fraction of the image width). */
+  left: number;
+  /** Right edge of the retained rectangle (0..1 fraction of the image width). */
+  right: number;
+  /** Strokes marking regions the user forced to be foreground. */
+  foregroundMarks?: PptxBackgroundRemovalMark[];
+  /** Strokes marking regions the user forced to be background. */
+  backgroundMarks?: PptxBackgroundRemovalMark[];
+  /** Original effect XML, retained for lossless re-emission. */
+  rawXml?: XmlObject;
+}
 interface PptxImageEffects {
   /** Brightness adjustment (-100 to 100). */
   brightness?: number;
@@ -3039,8 +3246,38 @@ interface PptxImageEffects {
   };
   /** Artistic effect name (blur, pencilGrayscale, paintStrokes, etc.). */
   artisticEffect?: string;
-  /** Artistic effect radius/amount. */
+  /** Artistic effect radius/amount, normalised to 0..100. */
   artisticRadius?: number;
+  /**
+   * Every numeric attribute of the source `a14:artistic*` element, raw and
+   * un-normalised (`trans`, `pencilSize`, `crackSpacing`, …). The attribute set
+   * differs per effect, so this is the lossless companion to the single
+   * {@link PptxImageEffects.artisticRadius} number.
+   */
+  artisticParams?: Record<string, number>;
+  /**
+   * Name of the artistic effect ALREADY baked into the image data, which a
+   * renderer must not apply a second time. Set from the `a14` blip extension,
+   * which PowerPoint writes alongside a pre-rendered bitmap (see
+   * {@link PptxBackgroundRemoval}), and normally equal to
+   * {@link PptxImageEffects.artisticEffect}.
+   *
+   * It records the NAME rather than a boolean so that picking a different
+   * effect in this library's inspector (which patches `artisticEffect` alone)
+   * still renders: the two names then differ.
+   */
+  artisticPrerenderedEffect?: string;
+  /**
+   * PowerPoint "Remove Background" state (`a14:backgroundRemoval`). Edit-time
+   * metadata: the removal is already baked into the image data.
+   */
+  backgroundRemoval?: PptxBackgroundRemoval;
+  /**
+   * `a14:imgLayer/@r:embed` — relationship id of the PRISTINE original image
+   * the baked effects were derived from (PowerPoint stores it as an HD Photo
+   * `.wdp` part, which browsers cannot decode).
+   */
+  originalImageRelId?: string;
   /** Alpha modulation fixed: non-negative percentage (100 means unchanged opacity). */
   alphaModFix?: number;
   /** Original alpha modulation fixed node, including foreign attributes. */
@@ -4952,7 +5189,7 @@ interface UnknownPptxElement extends PptxElementBase {
 /**
  * A single element on a PPTX slide.
  *
- * This is a **discriminated union** — narrow on `element.type` to access
+ * This is a **discriminated union**: narrow on `element.type` to access
  * variant-specific properties like `imageData` (image/picture), `pathData`
  * (shape), or `textSegments` (text/shape).
  */
@@ -5695,6 +5932,54 @@ interface PptxEmbeddedFontList {
   rawXml?: XmlObject;
 }
 //#endregion
+//#region src/core/types/comment-mentions.d.ts
+/**
+ * A single `@`-mention inside a modern comment body.
+ *
+ * Offsets index into the comment's FLATTENED plain text: every `a:t` value
+ * below `p188:txBody` concatenated, with paragraphs joined by `\n`. That is the
+ * same string `PptxComment.text` carries, so an edit to `text` invalidates
+ * every offset after the edit point and the serializer re-bases them.
+ *
+ * The markup Office uses for a mention is `CT_Mention` (documented for the
+ * SpreadsheetML `2018/threadedcomments` part): `mentionpersonId`, `mentionId`,
+ * `startIndex` and `length`. The PowerPoint `2018/8/main` schema does not
+ * publish a mention element at all, so `rawXml` is retained and re-emitted
+ * attribute-for-attribute: a producer that spells the attributes differently
+ * still round-trips.
+ *
+ * @example
+ * ```ts
+ * const mention: PptxCommentMention = {
+ *   personId: "{2CB2E9D0-D392-EB21-5D46-FBA34C1295E6}",
+ *   authorName: "Bob Example",
+ *   startIndex: 3,
+ *   length: 11,
+ * };
+ * // => "Hi Bob Example can you check this".slice(3, 14) === "Bob Example"
+ * ```
+ */
+interface PptxCommentMention {
+  /** `mentionId`: GUID identifying this mention instance. */
+  id?: string;
+  /** `mentionpersonId`: the `p188:author` id of the mentioned person. */
+  personId: string;
+  /** Display name resolved from the author list at parse time, when known. */
+  authorName?: string;
+  /** Character offset of the mentioned span in the flattened plain text. */
+  startIndex: number;
+  /** Character length of the mentioned span. */
+  length: number;
+  /**
+   * `uri` of the `p188:ext` this mention list was read from. Undefined means
+   * the list is a direct child of `p188:cm`, which is where it is written for
+   * newly authored mentions.
+   */
+  containerUri?: string;
+  /** Original `p188:mention` node, retained for unknown-attribute preservation. */
+  rawXml?: XmlObject;
+}
+//#endregion
 //#region src/core/types/metadata.d.ts
 /**
  * A slide comment — may be a legacy positional comment or a modern
@@ -5741,6 +6026,8 @@ interface PptxComment {
   title?: string;
   /** Modern threaded comment support (p15:threadingInfo). */
   threadId?: string;
+  /** `@`-mentions, indexed into `text` (see {@link PptxCommentMention}). */
+  mentions?: PptxCommentMention[];
   /** Replies to this comment (for modern threaded comments). */
   replies?: PptxComment[];
   /** ID of the element this comment is associated with (if any). */
@@ -6260,7 +6547,7 @@ interface PptxTheme {
  * // => "morph" — one of 40+ transition effects
  * ```
  */
-type PptxTransitionType = 'none' | 'cut' | 'fade' | 'push' | 'wipe' | 'split' | 'randomBar' | 'blinds' | 'checker' | 'circle' | 'comb' | 'cover' | 'diamond' | 'dissolve' | 'plus' | 'pull' | 'random' | 'strips' | 'uncover' | 'wedge' | 'wheel' | 'zoom' | 'newsflash' | 'morph' | 'conveyor' | 'doors' | 'ferris' | 'flash' | 'flythrough' | 'gallery' | 'glitter' | 'honeycomb' | 'pan' | 'prism' | 'reveal' | 'ripple' | 'shred' | 'switch' | 'vortex' | 'warp' | 'wheelReverse' | 'window' | 'cube' | 'flip' | 'rotate' | 'orbit' | 'fallOver' | 'drape' | 'curtains' | 'wind' | 'prestige' | 'fracture' | 'crush' | 'peelOff' | 'pageCurlDouble' | 'pageCurlSingle' | 'airplane' | 'origami';
+type PptxTransitionType = 'none' | 'cut' | 'fade' | 'push' | 'wipe' | 'split' | 'randomBar' | 'blinds' | 'checker' | 'circle' | 'comb' | 'cover' | 'diamond' | 'dissolve' | 'plus' | 'pull' | 'random' | 'strips' | 'uncover' | 'wedge' | 'wheel' | 'zoom' | 'newsflash' | 'morph' | 'conveyor' | 'doors' | 'ferris' | 'flash' | 'flythrough' | 'gallery' | 'glitter' | 'honeycomb' | 'pan' | 'prism' | 'reveal' | 'ripple' | 'shred' | 'switch' | 'vortex' | 'warp' | 'wheelReverse' | 'window' | 'cube' | 'flip' | 'rotate' | 'box' | 'orbit' | 'fallOver' | 'drape' | 'curtains' | 'wind' | 'prestige' | 'fracture' | 'crush' | 'peelOff' | 'pageCurlDouble' | 'pageCurlSingle' | 'airplane' | 'origami';
 /** Split orientation from OOXML `@_orient`. */
 type PptxSplitOrientation = 'horz' | 'vert';
 /** Schema-defined `ST_TransitionSpeed` values. */
@@ -6555,6 +6842,18 @@ interface PptxSlideBackgroundPattern {
 interface PptxSlide {
   id: string;
   rId: string;
+  /**
+   * `p:sldIdLst/p:sldId/@id` (ST_SlideId, 256..2147483647): the numeric key
+   * that sections (`p14:sldIdLst/p14:sldId/@id`) and section/summary zooms
+   * name slides by.
+   *
+   * It lives in `presentation.xml`, NOT in the slide part, so it cannot be
+   * recovered from `rawXml`. Without it on the model, code that writes a
+   * section's membership has nothing correct to write and falls back to the
+   * slide NUMBER, which is 1-based and therefore never matches a real deck's
+   * ids: the section reloads with no slides in it.
+   */
+  slideId?: string;
   sourceSlideId?: string;
   /** Optional author-supplied slide name (set via `SlideBuilder.setName`). */
   name?: string;
@@ -6757,6 +7056,26 @@ interface PptxPresentationProperties {
   /** Kiosk auto-restart interval in milliseconds (from `p:kiosk/@restart`). Only meaningful when showType is "kiosk". */
   kioskRestartTime?: number;
 }
+/**
+ * Slide dimensions from `p:sldSz` (CT_SlideSize, ECMA-376 §19.2.1.39).
+ *
+ * @example
+ * ```ts
+ * const size: PptxSlideSize = { widthEmu: 9144000, heightEmu: 6858000, type: 'screen4x3' };
+ * // => satisfies PptxSlideSize
+ * ```
+ */
+interface PptxSlideSize {
+  /** `@cx` in EMU. Omitted or non-positive values leave the loaded width alone. */
+  widthEmu?: number;
+  /** `@cy` in EMU. Omitted or non-positive values leave the loaded height alone. */
+  heightEmu?: number;
+  /**
+   * `@type` (ST_SlideSizeType). The schema default is `custom`, which is
+   * why PowerPoint omits the attribute for a non-preset size.
+   */
+  type?: string;
+}
 /**
  * A named custom slide show (`p:custShowLst / p:custShow`).
  *
@@ -7771,6 +8090,19 @@ interface PptxHandlerSaveOptions {
   customerData?: PptxCustomerData[];
   /** Photo album metadata to save back to `p:photoAlbum`. */
   photoAlbum?: PptxPhotoAlbum;
+  /**
+   * Slide dimensions to write back to `p:sldSz`.
+   *
+   * Omitting the option preserves the load-time dimensions verbatim, which
+   * is why an edit made through a viewer's Slide Size control has to reach
+   * the save call: nothing else in the pipeline can observe it.
+   *
+   * PowerPoint derives `Presentation.PageSetup.SlideSize` from `@cx`/`@cy`
+   * alone (verified by COM: an A4-typed `p:sldSz` carrying 4:3 dimensions
+   * still reports `ppSlideSizeCustom`), so `type` is written for fidelity
+   * but the dimensions are what actually decide the reported preset.
+   */
+  slideSize?: PptxSlideSize;
   /** East Asian line-break settings to save back to `p:kinsoku`. */
   kinsoku?: PptxKinsoku | null;
   /** Write-protection verifier. Set to `null` to remove, `undefined` to preserve existing. */
@@ -8362,24 +8694,38 @@ declare class PptxHandlerCore {
     name?: string;
   }>>;
   /**
-   * Export selected slides as individual PPTX files.
+   * Export selected slides to a vector or raster format, keyed by slide index.
    *
-   * Each entry in the returned map is keyed by slide index and contains a
-   * standalone `Uint8Array` PPTX with only that slide.
+   * **This does not produce PPTX files.** The previous version of this comment
+   * said each entry was "a standalone PPTX with only that slide", named the
+   * option `slideIndexes` (the real field is `slideIndices`), and wrote the
+   * bytes to `slide_N.pptx`. None of that was ever true: the runtime has
+   * always taken a `format` of `svg` / `png` / `pdf`. Per-slide PPTX
+   * extraction is a different operation and is not implemented here.
+   *
+   * Only `svg` works without a host-supplied backend, and it works fully:
+   * the headless {@link SvgExporter} renders it with no DOM. `png` and `pdf`
+   * THROW, because this package carries no rasteriser; use a viewer binding's
+   * browser export pipeline, or override `exportSlides` on the runtime with
+   * your own backend.
    *
    * @param slides  - Full slide array.
-   * @param options - Export options (slide indexes, format, etc.).
-   * @returns A `Map<slideIndex, Uint8Array>` of exported files.
+   * @param options - Export options (`format`, `slideIndices`, `width`, ...).
+   * @returns A `Map<slideIndex, Uint8Array>` of exported files. Hidden slides
+   *   are omitted unless `options.includeHidden` is set, so the map can be
+   *   smaller than `options.slideIndices`.
+   * @throws {Error} when `options.format` is `png` or `pdf`.
    *
    * @example
    * ```ts
    * const exports = await handler.exportSlides(data.slides, {
-   *   slideIndexes: [0, 2],
+   *   format: 'svg',
+   *   slideIndices: [0, 2],
    * });
    * for (const [idx, bytes] of exports) {
-   *   await fs.writeFile(`slide_${idx}.pptx`, Buffer.from(bytes));
+   *   await fs.writeFile(`slide_${idx}.svg`, Buffer.from(bytes));
    * }
-   * // => Map<number, Uint8Array> — one standalone .pptx per exported slide
+   * // => Map<number, Uint8Array>: one SVG document per exported slide
    * ```
    */
   exportSlides(slides: PptxSlide[], options: PptxExportOptions): Promise<Map<number, Uint8Array>>;
@@ -8829,6 +9175,91 @@ interface MorphTransitionPlan {
 //#region src/render/text-case-transform.d.ts
 type ChangeCaseMode = 'sentence' | 'lower' | 'upper' | 'capitalize' | 'toggle';
 //#endregion
+//#region src/render/shape-adjustment-model.d.ts
+/**
+ * `shape-adjustment-model`: the vocabulary the adjust-handle modules share.
+ *
+ * The `a:ahLst` work is split three ways for the repo's file-size budget:
+ * `shape-adjustment-probe` measures the geometry, `shape-adjustment-handles`
+ * derives the handles from those measurements, and `shape-adjustment-solver`
+ * turns a pointer position back into guide values. All three need these types
+ * and the one rule that operates purely on them, so they live here and the
+ * dependency graph stays a DAG rather than a cycle.
+ *
+ * @module render/shape-adjustment-model
+ */
+/**
+ * How a pointer position becomes a guide value, captured once when the gesture
+ * starts so `pointermove` stays pure arithmetic.
+ */
+interface ShapeAdjustmentSolver {
+  /** `linear`: the handle slides. `angular`: it swings about {@link centerX}. */
+  kind: 'linear' | 'angular';
+  /** Handle position in element-local px at {@link startValue}. */
+  anchorX: number;
+  anchorY: number;
+  /** Element-local px the handle travels per ONE unit of guide value. */
+  dirX: number;
+  dirY: number;
+  /** Pivot for an angular handle (the shape centre). */
+  centerX: number;
+  centerY: number;
+  /** The guide value the anchor was measured at. */
+  startValue: number;
+  /** Guide-space bounds, taken from the preset's own `pin` clamp. */
+  min: number;
+  max: number;
+}
+/** One guide a handle drives. */
+interface AdjustmentAxisSolver {
+  key: string;
+  solver: ShapeAdjustmentSolver;
+}
+/** Descriptor for one draggable adjustment handle (the amber diamond). */
+interface ShapeAdjustmentHandleDescriptor {
+  /** The `a:avLst` guide name this handle writes (`adj`, `adj1`, ...). */
+  key: string;
+  /** Handle x offset in element-local px (origin = element top-left). */
+  left: number;
+  /** Handle y offset in element-local px. */
+  top: number;
+  /**
+   * Current adjustment value in GUIDE units, not a 0-1 fraction. Most presets
+   * range 0..50000 or 0..100000 and the angular ones run to 21,600,000.
+   */
+  value: number;
+  cursor: string;
+  /**
+   * How this handle's drag resolves, measured off the preset geometry: one
+   * entry per `a:avLst` guide it drives (callouts drive two). Absent only for
+   * a caller that built a descriptor by hand.
+   */
+  solvers?: AdjustmentAxisSolver[];
+}
+/** Live drag state captured when an adjustment gesture starts. */
+interface ShapeAdjustmentDragState {
+  elementId: string;
+  key: string;
+  shapeType: string;
+  startClientX: number;
+  startClientY: number;
+  startAdjustment: number;
+  startWidth: number;
+  startHeight: number;
+  moved: boolean;
+  /** Copied from the descriptor the gesture started on. */
+  solvers?: AdjustmentAxisSolver[];
+  /**
+   * The element's whole `a:avLst` map at gesture start.
+   *
+   * A binding writes `shapeAdjustments` as one object, so a drag that sent
+   * only the guide it changed would DELETE every other authored adjustment on
+   * a multi-adjust preset (a `quadArrow` would lose two of its three the first
+   * time one was touched).
+   */
+  startAdjustments?: Record<string, number>;
+}
+//#endregion
 //#region src/render/collaboration-text-codec.d.ts
 /**
  * collaboration-text-codec.ts: TextSegment[] <-> Y.Text delta codec used by the
@@ -8947,6 +9378,12 @@ interface CompareResult {
   changedCount: number;
   unchangedCount: number;
 }
+interface SlideSizeEmu {
+  widthEmu: number;
+  heightEmu: number;
+  /** ST_SlideSizeType token, or `''` for a size with no preset. */
+  type: string;
+}
 //#endregion
 //#region src/render/mobile-viewport.d.ts
 /**
@@ -9068,6 +9505,31 @@ interface FontEmbeddingDescriptor {
   /** Present only when `interactive` is false. */
   disabledReasonKey?: string;
 }
+/** Everything a binding needs to render the recovery dialog, and nothing else. */
+interface AutosaveRecoveryPrompt {
+  /** IndexedDB key the snapshot is stored under (the deck's file path/name). */
+  readonly filePath: string;
+  /** When the snapshot was written (epoch ms). */
+  readonly timestamp: number;
+  /** Snapshot size in bytes. */
+  readonly size: number;
+  /** Whole minutes since it was written, floored at 0. */
+  readonly ageMinutes: number;
+  readonly titleKey: string;
+  readonly messageKey: string;
+  /** `size` is pre-formatted here because byte units are not translated. */
+  readonly messageParams: {
+    readonly file: string;
+    readonly size: string;
+  };
+  /** Relative age, reusing the existing autosave age keys. */
+  readonly ageKey: string;
+  readonly ageParams: {
+    readonly count: number;
+  };
+  readonly restoreKey: string;
+  readonly discardKey: string;
+}
 //#endregion
 //#region src/render/master-view.d.ts
 /** Which part the master view is currently pointed at. */
@@ -9217,13 +9679,25 @@ interface ViewerProofingOptions {
   checkSpellingAsYouType: boolean;
   hideSpellingErrors: boolean;
 }
+/**
+ * File > Options > Save.
+ *
+ * Font embedding deliberately has NO entry here. It is owned by the File >
+ * Fonts panel, whose toggle is the one the save path reads (see
+ * `render/font-embedding`: `describeFontEmbedding` decides the toggle's start
+ * position and whether it can do anything at all, `embeddedFontSaveOptions`
+ * turns it into the `PptxHandler.save()` slice). This group used to carry a
+ * second `embedFonts` boolean, plus an `embedAllFontCharacters` companion, and
+ * neither was read by anything: the pane moved a switch that changed no saved
+ * byte, while the panel next door moved the real one. Two switches for one
+ * setting, one of them lying, is worse than one switch in a less
+ * PowerPoint-shaped place.
+ */
 interface ViewerSaveOptions {
   autoSave: boolean;
   autoRecoverIntervalMinutes: number;
   keepLastAutoRecoveredVersion: boolean;
   defaultExportFormat: DefaultExportFormat;
-  embedFonts: boolean;
-  embedAllFontCharacters: boolean;
   cacheRetentionDays: number;
   clearCacheOnClose: boolean;
 }
@@ -9442,22 +9916,6 @@ interface ResizeState {
   lastWidth: number;
   lastHeight: number;
 }
-/**
- * Tracks the state of an ongoing shape adjustment handle drag.
- * Used when the user drags the yellow diamond handle to alter
- * shape-specific parameters (e.g. corner radius on a rounded rectangle).
- */
-interface ShapeAdjustmentDragState {
-  elementId: string;
-  key: string;
-  shapeType: string;
-  startClientX: number;
-  startClientY: number;
-  startAdjustment: number;
-  startWidth: number;
-  startHeight: number;
-  moved: boolean;
-}
 /**
  * A snapshot of editor state captured for undo/redo history.
  * Contains the full slide deck state at a point in time so that
@@ -9760,6 +10218,8 @@ interface ToolbarProps {
   onToggleVersionHistory?: () => void;
   onOpenPasswordProtection?: () => void;
   onOpenDocumentProperties?: () => void;
+  /** Design > Slide Size: reveal the inspector card that owns the slide size. */
+  onOpenSlideSize?: () => void;
   onOpenFontEmbedding?: () => void;
   onOpenDigitalSignatures?: () => void;
   onEnterMasterView: () => void;
@@ -9885,7 +10345,7 @@ interface SlideCanvasProps {
   /** Called when the user presses mouse down on empty canvas space. */
   onCanvasMouseDown?: (e: React$1.MouseEvent) => void;
   onResizePointerDown: (elementId: string, e: React$1.MouseEvent, handle: string) => void;
-  onAdjustmentPointerDown: (elementId: string, e: React$1.MouseEvent) => void;
+  onAdjustmentPointerDown: (elementId: string, e: React$1.MouseEvent, descriptor: ShapeAdjustmentHandleDescriptor) => void;
   /** Commit a new rotation (degrees) when the on-canvas rotate handle is dragged. */
   onRotate?: (elementId: string, rotationDeg: number) => void;
   onInlineEditChange: (text: string) => void;
@@ -10000,10 +10460,37 @@ interface UseAutosaveInput {
   filePath: string | undefined;
   /** Serialise current editor state to a Uint8Array. */
   serializeSlides: () => Promise<Uint8Array | null>;
-  /** Autosave interval in seconds (default 120). */
+  /**
+   * Autosave interval in seconds.
+   *
+   * @deprecated Pass {@link intervalMs} instead. Seconds cannot express the
+   * short cadence a host may legitimately ask for, and the shared clamp it went
+   * through raised anything under 10s back to 10s, so an explicit host policy
+   * was silently overruled. Ignored when `intervalMs` is given.
+   */
   intervalSeconds?: number;
-  /** Whether autosave is enabled. */
+  /**
+   * Autosave interval in milliseconds, already resolved by the shared
+   * `resolveAutosaveIntervalMs` (host prop > File > Options > Save AutoRecover
+   * cadence > 120s default). Wins over {@link intervalSeconds}.
+   */
+  intervalMs?: number;
+  /**
+   * Whether autosave is enabled: the resolved `active` from the shared
+   * `resolveAutosaveActivation`, NOT the raw title-bar toggle.
+   */
   enabled?: boolean;
+  /**
+   * The values a snapshot is built from, read fresh on each tick.
+   *
+   * `isDirty` stays true from the first edit until the user performs a real
+   * save, so on its own it makes the timer re-serialize and rewrite an
+   * identical deck every N seconds forever. Vue, Svelte and Vanilla never had
+   * that problem because they debounce on the slides array being reassigned;
+   * this is the same trigger, and `shouldWriteAutosaveSnapshot` writes
+   * whenever it is unsure. Omit it and every tick writes, as before.
+   */
+  getChangeSources?: () => readonly unknown[];
 }
 interface UseAutosaveResult {
   /** Current autosave status for display in the StatusBar. */
@@ -10575,6 +11062,8 @@ interface UsePresentationModeInput {
   onToggleToolbar?: () => void;
   /** Open the All Slides navigator (Ctrl+S). */
   onShowAllSlides?: () => void;
+  /** Show or hide live captions (PowerPoint's bare J). */
+  onToggleSubtitles?: () => void;
   /** Called to persist rehearsal timings into slide transitions. */
   onSaveRehearsalTimings?: (timings: Record<number, number>) => void;
   /** Whether to loop continuously (kiosk or explicit loop setting). */
@@ -10951,6 +11440,15 @@ interface ViewerCoreState {
   /** Width and height of the slide canvas in CSS pixels. */
   canvasSize: CanvasSize;
   setCanvasSize: React$1.Dispatch<React$1.SetStateAction<CanvasSize>>;
+  /**
+   * `p:sldSz` in EMU, seeded from the loaded deck and updated by Design >
+   * Slide Size. It is what a save persists: the pixel `canvasSize` above
+   * cannot round-trip a preset (Ledger's 12179300 EMU is 1278.5px, and the
+   * integer pixel it rounds to costs the deck its `ppSlideSizeLedgerPaper`
+   * identity). `undefined` until a deck loads or the user picks a preset.
+   */
+  slideSizeEmu: SlideSizeEmu | undefined;
+  setSlideSizeEmu: React$1.Dispatch<React$1.SetStateAction<SlideSizeEmu | undefined>>;
   /** Zero-based index of the currently active (visible) slide. */
   activeSlideIndex: number;
   setActiveSlideIndex: React$1.Dispatch<React$1.SetStateAction<number>>;
@@ -11230,6 +11728,8 @@ interface UseLoadContentInput {
   setTemplateElementsBySlideId: React.Dispatch<React.SetStateAction<Record<string, PptxElement[]>>>;
   mediaDataUrls: Map<string, string>;
   setCanvasSize: React.Dispatch<React.SetStateAction<CanvasSize>>;
+  /** Seeds the EMU `p:sldSz` that a save persists (see `ViewerCoreState.slideSizeEmu`). */
+  setSlideSizeEmu: React.Dispatch<React.SetStateAction<SlideSizeEmu | undefined>>;
   setHeaderFooter: React.Dispatch<React.SetStateAction<PptxHeaderFooter>>;
   setLayoutOptions: React.Dispatch<React.SetStateAction<Array<{
     path: string;
@@ -11240,6 +11740,12 @@ interface UseLoadContentInput {
   setTableStyleMap: React.Dispatch<React.SetStateAction<ParsedTableStyleMap | undefined>>;
   setThemeOptions: React.Dispatch<React.SetStateAction<PptxThemeOption[]>>;
   setCustomShows: React.Dispatch<React.SetStateAction<PptxCustomShow[]>>;
+  /**
+   * Seeds the running show from `p:showPr/p:custShow/@id`, so a deck authored
+   * to open into a custom show plays that subset instead of the whole deck.
+   * A later manual pick still wins: this only fires on load.
+   */
+  setActiveCustomShowId: React.Dispatch<React.SetStateAction<string | null>>;
   setSections: React.Dispatch<React.SetStateAction<PptxSection[]>>;
   setPresentationProperties: React.Dispatch<React.SetStateAction<PptxPresentationProperties>>;
   setNotesMaster: React.Dispatch<React.SetStateAction<PptxNotesMaster | undefined>>;
@@ -11273,7 +11779,7 @@ interface UseLoadContentInput {
 interface UseLoadContentResult {
   handlerRef: React.MutableRefObject<PptxHandler | null>;
 }
-declare function useLoadContent({ content, clearSelection, history, setSlides, setTemplateElementsBySlideId, mediaDataUrls, setCanvasSize, setHeaderFooter, setLayoutOptions, setSlideMasters, setTheme, setTableStyleMap, setThemeOptions, setCustomShows, setSections, setPresentationProperties, setNotesMaster, setHandoutMaster, setNotesCanvasSize, setCustomProperties, setTagCollections, setCoreProperties, setAppProperties, setEmbeddedFonts, setActiveSlideIndex, setHasMacros, setHasDigitalSignatures, setDigitalSignatureCount, setGuides, setLoading, setError, setIsDirty, setIsEncrypted, onContentApplied }: UseLoadContentInput): UseLoadContentResult;
+declare function useLoadContent({ content, clearSelection, history, setSlides, setTemplateElementsBySlideId, mediaDataUrls, setCanvasSize, setSlideSizeEmu, setHeaderFooter, setLayoutOptions, setSlideMasters, setTheme, setTableStyleMap, setThemeOptions, setCustomShows, setActiveCustomShowId, setSections, setPresentationProperties, setNotesMaster, setHandoutMaster, setNotesCanvasSize, setCustomProperties, setTagCollections, setCoreProperties, setAppProperties, setEmbeddedFonts, setActiveSlideIndex, setHasMacros, setHasDigitalSignatures, setDigitalSignatureCount, setGuides, setLoading, setError, setIsDirty, setIsEncrypted, onContentApplied }: UseLoadContentInput): UseLoadContentResult;
 //#endregion
 //#region src/viewer/hooks/useElementOperations.d.ts
 /**
@@ -11354,6 +11860,12 @@ interface SectionOperations {
   moveSectionUp: (sectionId: string) => void;
   moveSectionDown: (sectionId: string) => void;
   moveSlidesToSection: (slideIndexes: number[], targetSectionId: string) => void;
+  /**
+   * Flip `section.collapsed`, the `p14:section/@collapsed` flag core already
+   * round-trips. React alone kept collapse in component-local state, so the
+   * one binding that could not persist a collapsed section was this one.
+   */
+  toggleSectionCollapse: (sectionId: string) => void;
 }
 declare function useSectionOperations(input: UseSectionOperationsInput): SectionOperations;
 //#endregion
@@ -11424,7 +11936,7 @@ interface CanvasInteractionHandlers {
   handleElementContextMenu: (elementId: string, e: React.MouseEvent) => void;
   handleCanvasMouseDown: (e: React.MouseEvent) => void;
   handleResizePointerDown: (elementId: string, e: React.MouseEvent, handle: string) => void;
-  handleAdjustmentPointerDown: (elementId: string, e: React.MouseEvent) => void;
+  handleAdjustmentPointerDown: (elementId: string, e: React.MouseEvent, descriptor: ShapeAdjustmentHandleDescriptor) => void;
   /** Commit a new rotation (degrees) for an element from the on-canvas rotate handle. */
   handleRotate: (elementId: string, rotationDeg: number) => void;
   /** Commit an inline (on-canvas) SmartArt node edit through the element-update path. */
@@ -11688,6 +12200,8 @@ interface UseExportHandlersInput {
   appProperties: Record<string, unknown> | null;
   customProperties: Array<Record<string, unknown>>;
   tagCollections: Array<Record<string, unknown>>;
+  /** The slide masters and their layouts; see `UseExportSaveAsInput`. */
+  slideMasters: PptxSlideMaster[];
   notesMaster: Record<string, unknown> | undefined;
   handoutMaster: Record<string, unknown> | undefined;
   guides: Array<{
@@ -11700,6 +12214,12 @@ interface UseExportHandlersInput {
   theme: PptxTheme | undefined;
   /** Slide canvas size in CSS pixels, carried into the deck-JSON export. */
   canvasSize: CanvasSize;
+  /**
+   * The EMU `p:sldSz` the viewer holds. Save-As builds its own save options
+   * rather than reusing `useSerialize`, so without this a Slide Size edit
+   * reached Save and not Save As (or the backstage Save, which routes here).
+   */
+  slideSizeEmu?: SlideSizeEmu | undefined;
   password?: string;
 }
 interface ExportHandlersResult {
@@ -12075,6 +12595,16 @@ interface UseSerializeInput {
   /** Separated master/layout (template) elements, merged back at save time. */
   templateElementsBySlideId: Record<string, PptxElement[]>;
   activeSlideIndex: number;
+  /** The pixel canvas the raw Slide Size W/H inputs edit. */
+  canvasSize: CanvasSize;
+  /**
+   * The EMU `p:sldSz` the viewer is holding (seeded on load, replaced by a
+   * preset/orientation pick). Passed with `canvasSize` to
+   * `resolveSlideSizeSelection`, which keeps the EMU whenever the two still
+   * agree so a preset survives the save, and takes the pixels when the user
+   * has typed into the raw inputs.
+   */
+  slideSizeEmu?: SlideSizeEmu | undefined;
   guides: Array<{
     id: string;
     axis: 'h' | 'v';
@@ -12092,6 +12622,19 @@ interface UseSerializeInput {
   appProperties: PptxAppProperties | undefined;
   customProperties: PptxCustomProperty[];
   tagCollections: PptxTagCollection[];
+  /**
+   * The slide masters and their layouts, as View > Slide Master left them.
+   *
+   * Required, not optional: this was the one save option React never passed,
+   * and core rewrites a master or layout part only for the ones the caller
+   * hands back. Every master-view edit therefore showed on screen and was
+   * dropped by the save - a deleted master shape came back on reload, and a
+   * master background reverted to white. The other four bindings pass it.
+   * Core compares each part against the element list parsed at load and
+   * rewrites only what actually changed, so passing the whole array on every
+   * save costs an untouched deck nothing.
+   */
+  slideMasters: PptxSlideMaster[];
   notesMaster: PptxNotesMaster | undefined;
   handoutMaster: PptxHandoutMaster | undefined;
   handlerRef: React$1.RefObject<PptxHandler | null>;
@@ -12125,9 +12668,26 @@ interface UseRecoveryDetectionInput {
   loading: boolean;
   error: string | null;
   slideCount: number;
-  openVersionHistory: () => void;
+  /**
+   * Whether the host permits autosave (the shared `resolveAutosaveActivation`
+   * ceiling). A host that passed `autosave={false}` is never offered snapshots
+   * an earlier configuration left behind. Defaults to true.
+   */
+  autosaveAllowed?: boolean;
+  /** Load the recovered bytes into the viewer. */
+  onRestore?: (bytes: Uint8Array) => void;
+  /** Legacy behaviour: also open the Version History panel when one is found. */
+  openVersionHistory?: () => void;
+}
+interface UseRecoveryDetectionResult {
+  /** What the dialog should say, or null when there is nothing to offer. */
+  prompt: AutosaveRecoveryPrompt | null;
+  /** Accept: load the snapshot and close. */
+  restore: () => void;
+  /** Decline: drop the snapshot and close. */
+  discard: () => void;
 }
-declare function useRecoveryDetection(input: UseRecoveryDetectionInput): void;
+declare function useRecoveryDetection(input: UseRecoveryDetectionInput): UseRecoveryDetectionResult;
 //#endregion
 //#region src/viewer/hooks/usePresentationSetup.d.ts
 interface UsePresentationSetupInput {
@@ -12158,6 +12718,12 @@ interface UsePresentationSetupInput {
   promptKeepInkAnnotations?: boolean;
   /** Options > Advanced > "Show popup toolbar" (default true). */
   popupToolbarEnabled?: boolean;
+  /**
+   * Show or hide live captions. PowerPoint toggles them on a bare `J` during a
+   * show, and the shared slide-show keymap resolves that key for every binding;
+   * without this callback the key is mapped and then lands nowhere.
+   */
+  onToggleSubtitles?: () => void;
 }
 interface PresentationSetupResult {
   presentation: UsePresentationModeResult;
@@ -12241,15 +12807,18 @@ declare function useIOHandlers(input: UseIOHandlersInput): IOHandlersResult;
 interface UseContentLifecycleInput {
   content: ArrayBuffer | Uint8Array | null;
   filePath: string | undefined;
-  /** AutoSave toggle state; when false the recovery autosave timer is off. */
+  /**
+   * Whether autosave actually runs: the resolved `active` from the shared
+   * `resolveAutosaveActivation` (host `autosave` prop as a ceiling, title-bar
+   * toggle as the preference inside it), not the raw toggle.
+   */
   autosaveEnabled?: boolean;
   /**
-   * AutoRecover cadence in seconds, from
-   * `resolveAutosaveIntervalSeconds(File > Options > Save)`. React was the only
-   * binding that never passed one (vanilla, svelte and angular all resolve it),
-   * so the option's number field moved and the timer kept its 120s default.
+   * The resolved cadence in milliseconds, from the shared
+   * `resolveAutosaveIntervalMs` (host `autosaveIntervalMs` prop > File >
+   * Options > Save AutoRecover cadence > 120s default).
    */
-  autosaveIntervalSeconds?: number;
+  autosaveIntervalMs?: number;
   /**
    * File > Fonts > "Embed fonts in the file". Forwarded to `useSerialize`, so
    * turning it off actually strips the embedded font data on the next save.
@@ -12305,13 +12874,22 @@ interface UseViewerIntegrationInput {
   gridSpacingPx: number;
   content: ArrayBuffer | Uint8Array | null;
   filePath: string | undefined;
-  /** AutoSave toggle state from the title bar. */
+  /**
+   * Whether autosave actually runs: the shared `resolveAutosaveActivation`
+   * verdict (host `autosave` prop as a ceiling, title-bar toggle inside it).
+   */
   autosaveEnabled: boolean;
   /**
-   * AutoRecover cadence in seconds, resolved from File > Options > Save.
-   * Optional: omitting it keeps `useAutosave`'s 120s default.
+   * Whether the host permits autosave at all. Only the recovery prompt needs
+   * this separately from `autosaveEnabled`: a user who merely switched the
+   * toggle off should still be offered a snapshot from before the crash.
    */
-  autosaveIntervalSeconds?: number;
+  autosaveAllowed?: boolean;
+  /**
+   * The resolved cadence in milliseconds (shared `resolveAutosaveIntervalMs`).
+   * Optional: omitting it keeps the shared 120s AutoRecover default.
+   */
+  autosaveIntervalMs?: number;
   canEdit: boolean;
   mode: ViewerState['mode'];
   slides: PptxSlide[];
@@ -12342,6 +12920,8 @@ interface ViewerIntegrationResult {
   handleEnterPresenterView: AnnotationHandlersResult['handleEnterPresenterView'];
   handleEnterRehearsalMode: AnnotationHandlersResult['handleEnterRehearsalMode'];
   autosaveStatus: AutosaveStatus;
+  /** The crash-recovery prompt (shared descriptor) plus its accept/decline actions. */
+  recovery: UseRecoveryDetectionResult;
   isEncryptedDialogOpen: boolean;
   setIsEncryptedDialogOpen: Dispatch<SetStateAction<boolean>>;
   /** The loaded core handler, exposed for the AI bridge (`getHandler`). */
@@ -12643,6 +13223,13 @@ interface UseExportSaveAsInput {
   appProperties: Record<string, unknown> | null;
   customProperties: Array<Record<string, unknown>>;
   tagCollections: Array<Record<string, unknown>>;
+  /**
+   * The slide masters and their layouts, as View > Slide Master left them.
+   * Save As builds its own options rather than reusing `useSerialize`, so it
+   * needs the same array: without it a master-view edit reached Save and not
+   * Save As. (For a long while it reached neither.)
+   */
+  slideMasters: PptxSlideMaster[];
   notesMaster: Record<string, unknown> | undefined;
   handoutMaster: Record<string, unknown> | undefined;
   guides: Array<{
@@ -12655,6 +13242,8 @@ interface UseExportSaveAsInput {
   theme: PptxTheme | undefined;
   /** Slide canvas size in CSS pixels, carried into the deck-JSON export. */
   canvasSize: CanvasSize;
+  /** The EMU `p:sldSz` the viewer holds; see `UseExportHandlersInput`. */
+  slideSizeEmu?: SlideSizeEmu | undefined;
   modalControls: ExportModalControls;
   password?: string;
 }
@@ -12722,6 +13311,13 @@ interface UseKeyboardShortcutsInput {
   onUngroup?: () => void;
   /** Show or hide the keyboard-shortcut reference ("?"). */
   onToggleShortcuts?: () => void;
+  /**
+   * Open or close the find bar (Ctrl/Cmd+F). Left unwired by the default
+   * shell, where `useFindReplace` owns the find state and resolves the same
+   * chord against the same shared keymap; the case exists so the switch stays
+   * exhaustive and so a host driving this hook directly can handle it.
+   */
+  onFind?: () => void;
   /** Navigate to previous visible slide (edit mode, no selection). */
   onPrevSlide?: () => void;
   /** Navigate to next visible slide (edit mode, no selection). */
@@ -12880,6 +13476,8 @@ interface UsePresentationKeyboardInput {
   onToggleToolbar?: () => void;
   /** Open the All Slides navigator (Ctrl+S). */
   onShowAllSlides?: () => void;
+  /** Show or hide live captions (J). */
+  onToggleSubtitles?: () => void;
   onToggleBlackScreen?: () => void;
   onToggleWhiteScreen?: () => void;
   rehearsing: boolean;