pptx-react-viewer 2.17.0 → 2.19.0

package/dist/viewer/index.d.ts

@@ -185,11 +185,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 };
@@ -208,6 +215,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
@@ -1147,6 +1162,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
@@ -1187,6 +1218,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. */
@@ -1851,6 +1936,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;
@@ -1911,6 +2005,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). */
@@ -2321,6 +2428,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;
@@ -2522,6 +2635,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
@@ -2865,6 +3014,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.
@@ -3018,6 +3178,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;
@@ -3041,8 +3248,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. */
@@ -4954,7 +5191,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).
  */
@@ -5687,6 +5924,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
@@ -5733,6 +6018,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). */
@@ -6252,7 +6539,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. */
@@ -6547,6 +6834,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;
@@ -6749,6 +7048,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`).
  *
@@ -7763,6 +8082,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. */
@@ -8354,24 +8686,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.
+   *
+   * **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.
    *
-   * Each entry in the returned map is keyed by slide index and contains a
-   * standalone `Uint8Array` PPTX with only that slide.
+   * 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>>;
@@ -8721,6 +9067,91 @@ interface CollaborationConfig {
    */
   writeBackDebounceMs?: number;
 }
+//#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>;
+}
 /**
  * A font supplied by the host application. The package never ships fonts:
  * applications provide a licensed URL, data URL, or blob URL for their users.
@@ -8942,34 +9373,6 @@ interface ResizeState {
   lastWidth: number;
   lastHeight: number;
 }
-/**
- * Describes the position and value of a shape adjustment handle (yellow diamond).
- * Adjustment handles allow users to modify shape parameters like corner radius,
- * arrow width, etc. without a full resize.
- */
-interface ShapeAdjustmentHandleDescriptor {
-  key: string;
-  left: number;
-  top: number;
-  value: number;
-  cursor: string;
-}
-/**
- * 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
@@ -9448,6 +9851,28 @@ interface PowerPointViewerProps {
   onOpenFile?: () => void;
   /** Whether editing actions are enabled */
   canEdit?: boolean;
+  /**
+   * Recovery autosave: after an edit the deck is re-serialised (always as a
+   * plain, unencrypted package, because recovery has no password) and stashed
+   * in the shared IndexedDB store keyed by {@link filePath}. It is a crash-
+   * safety net and never replaces the user's real Save: the document stays
+   * dirty. On load, a newer snapshot is offered back through a recovery prompt.
+   *
+   * **The prop is a policy ceiling; the title-bar AutoSave toggle is the user's
+   * preference inside it.** `false` turns autosave off and makes the toggle
+   * inert (a user cannot switch on what the application forbade). `true` or
+   * omitted permits it, and the toggle decides, defaulting to on. Identical in
+   * all five bindings; see `resolveAutosaveActivation` in `pptx-viewer-shared`.
+   *
+   * @default true
+   */
+  autosave?: boolean;
+  /**
+   * Recovery cadence in milliseconds. An explicit value is a host policy and is
+   * honoured as given; omit it to follow the user's File > Options > Save >
+   * "Save AutoRecover information every N minutes" (two minutes by default).
+   */
+  autosaveIntervalMs?: number;
   /** Optional class name */
   className?: string;
   /**