@openpresentation/opf 0.10.1 → 0.11.1

package/dist/{chunk-D3GQIREP.js → chunk-LTSDDBNW.js}

@@ -3,7 +3,7 @@ var presentation = {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "$id": "https://openpresentation.org/schema/opf/v1",
   "title": "Presentation",
-  "description": "Open-source JSON format for describing PowerPoint presentations. Agents describe narratives, content, audience, reusable assets, and design \u2014 the engine handles OOXML complexity.\n\nFields that reference catalog records (narrative, language, tone, audience, purpose, design.theme / design.theme.id, design.colorScheme / design.colorScheme.id, design.fontScheme / design.fontScheme.id, Slide.layout, Chart.type, Organization.socials / Speaker.socials) resolve through the catalog system: inline 'catalogs.<kind>.records[]' on the document \u2192 'catalogs.<kind>.source' on the document \u2192 engine defaults \u2192 the default catalog at https://www.pptx.gallery/<kind>. Every reference resolves to the catalog record's 'id' field. When an OPF document omits a reference entirely, the engine falls back to engine defaults (see /spec/reference/engine-defaults.json for a reference example). The defaults file is engine configuration; it is not part of the OPF document contract and has no JSON Schema.\n\nMost catalog references accept the bare 'id' as a string for the common case (e.g. narrative = 'classic-story', design.colorScheme = 'cool-horizon'). Audience, purpose, tone, design, and language object forms use 'id' as a base catalog reference plus inline overrides. Asset references use 'asset:<id>' strings that point into the top-level assets registry.",
+  "description": "Open-source JSON format for describing PowerPoint presentations. Agents describe narratives, content, audience, reusable assets, and design \u2014 the engine handles OOXML complexity.\n\nFields that reference catalog records (narrative, language, tone, audience, purpose, design.theme / design.theme.id, design.colorScheme / design.colorScheme.id, design.fontScheme / design.fontScheme.id, Slide.layout, Chart.type, Organization.socials / Speaker.socials) resolve through the catalog system: inline 'catalogs.<kind>.records[]' on the document \u2192 'catalogs.<kind>.source' on the document \u2192 engine defaults \u2192 the default catalog at https://www.pptx.gallery/<kind>. Every reference resolves to the catalog record's 'id' field. When an OPF document omits a reference entirely, the engine falls back to engine defaults (see /spec/reference/engine-defaults.json for a reference example). The defaults file is engine configuration; it is not part of the OPF document contract and has no JSON Schema.\n\nMost catalog references accept the bare 'id' as a string for the common case (e.g. narrative = 'classic-story', design.colorScheme = 'cool-horizon'). Audience, purpose, tone, design, and language object forms use 'id' as a base catalog reference plus inline overrides. Asset references use 'asset:<id>' strings that point into the top-level assets registry, and content color fields (rich-text runs, styled table cells) accept hex values, color-scheme slot/role names, or 'var:<id>' references into the top-level variables map.",
   "type": "object",
   "required": [
     "slides"
@@ -284,6 +284,10 @@ var presentation = {
       "$ref": "#/$defs/Design",
       "description": "Optional design system covering theme, color scheme, font scheme, dimensions, background, logo, watermark, header, and footer applied to the deck. When omitted, engines use their default design configuration."
     },
+    "variables": {
+      "$ref": "#/$defs/Variables",
+      "description": "Optional named color variables for values the deck uses in more than one place or wants to name for intent (e.g. a risk red, a brand highlight). Content color fields reference entries as 'var:<id>' strings. Variables complement the color scheme: scheme slots and roles stay the primary vocabulary; variables cover deck-specific named colors that have no scheme slot."
+    },
     "narrative": {
       "oneOf": [
         {
@@ -658,6 +662,18 @@ Deck-level concerns that aren't part of the storyline (audience, tone, takeaway,
             "zh-Hans"
           ]
         },
+        "ooxmlLang": {
+          "type": "string",
+          "description": "Curated culture tag for OOXML text-run language attributes (a:rPr/@lang, a:endParaRPr/@lang), in the language-[Script-]REGION form Office recognizes (e.g. 'ja-JP', 'ar-SA', 'ms-MY', 'nb-NO', 'fil-PH', 'zh-CN'). Engines emit it instead of 'bcp47' when the document names the language by catalog id or by a tag without a region; a region-bearing tag written by the author is emitted as written. Curated rather than inferred so output does not depend on the runtime's locale data.",
+          "examples": [
+            "en-US",
+            "ja-JP",
+            "ar-SA",
+            "ms-MY",
+            "nb-NO",
+            "zh-CN"
+          ]
+        },
         "code": {
           "type": "string",
           "description": "ISO 639-3 or 639-2 language code carried for engines that prefer ISO codes.",
@@ -674,26 +690,32 @@ Deck-level concerns that aren't part of the storyline (audience, tone, takeaway,
             "ltr",
             "rtl"
           ],
-          "description": "Base text direction for the language."
+          "description": "Base text direction for the language. When omitted, engines derive it from the script: Arabic (Arab), Hebrew (Hebr), Syriac (Syrc), Thaana (Thaa), N'Ko (Nkoo), Adlam (Adlm), Samaritan (Samr), Mandaic (Mand) and Hanifi Rohingya (Rohg) are right-to-left; every other script is left-to-right. Bundled language records state it explicitly."
         },
         "script": {
           "type": "string",
-          "description": "ISO 15924 script code when the writing system should be explicit.",
+          "description": "ISO 15924 script code of the language's writing system. The script selects the OOXML font slot the language's text uses: East Asian scripts (Hans, Hant, Hani, Jpan, Kore, Hang, Hira, Kana, Bopo, Yiii) use the eastAsian slot; complex scripts (for example Arab, Hebr, Syrc, Thaa, Deva, Beng, Guru, Gujr, Orya, Taml, Telu, Knda, Mlym, Sinh, Thai, Laoo, Tibt, Mymr, Khmr, Mong) use the complexScript slot; every other script (Latn, Cyrl, Grek, Armn, Geor, Ethi, ...) uses the latin slot. When omitted, engines infer it from the BCP-47 tag. Bundled language records state it explicitly. See docs/programs/font-fidelity-everywhere/script-font-model.md.",
           "examples": [
             "Latn",
-            "Arab",
             "Cyrl",
+            "Grek",
+            "Arab",
+            "Hebr",
+            "Jpan",
+            "Kore",
             "Hans",
-            "Hant"
+            "Hant",
+            "Deva",
+            "Thai"
           ]
         },
         "fontScheme": {
           "type": "string",
-          "description": "Default font-scheme id for this language when targeting PowerPoint output."
+          "description": "Default font-scheme id for this language when targeting PowerPoint output. Resolves against catalogs.fontSchemes the same way design.fontScheme or design.fontScheme.id does. Its major/minor families fill the language's script slot (eastAsian or complexScript, chosen by 'script') unless the effective design font scheme sets that slot itself; the latin slot always follows the design font scheme."
         },
         "googleFontScheme": {
           "type": "string",
-          "description": "Default font-scheme id for this language when targeting Google Slides output."
+          "description": "Default font-scheme id for this language when targeting Google Slides output. Resolves against catalogs.fontSchemes the same way design.fontScheme or design.fontScheme.id does. Used in place of 'fontScheme' when resolving script fonts for Google Slides output."
         },
         "summary": {
           "type": "string",
@@ -882,7 +904,7 @@ Deck-level concerns that aren't part of the storyline (audience, tone, takeaway,
         },
         "socials": {
           "$ref": "#/$defs/Socials",
-          "description": "Optional social media handles or URLs for the organization."
+          "description": "Optional social media handles or URLs for the organization. The primary organization's socials render in header/footer zones that set socials: true; otherwise they are authoring metadata."
         }
       }
     },
@@ -968,7 +990,7 @@ Deck-level concerns that aren't part of the storyline (audience, tone, takeaway,
         },
         "socials": {
           "$ref": "#/$defs/Socials",
-          "description": "Optional social media handles or URLs for the speaker."
+          "description": "Optional social media handles or URLs for the speaker. Authoring metadata: no header/footer field renders speaker socials yet."
         }
       }
     },
@@ -1462,12 +1484,149 @@ Resolution order: inline catalogs.fontSchemes.records[] -> catalogs.fontSchemes.
                     "left",
                     "right"
                   ],
-                  "description": "Where the slide-level image sits relative to the content. 'background' is a full-bleed image behind the content."
+                  "description": "Where the slide-level image sits relative to the content. 'background' is a full-bleed image behind the content. The other positions give the image a band along that edge (see size) and compose headings and content in the rest of the slide."
+                },
+                "alt": {
+                  "type": "string",
+                  "description": "Alternative text for the slide-level image. Overrides the alt text of a referenced asset."
+                },
+                "fill": {
+                  "type": "string",
+                  "enum": [
+                    "crop",
+                    "fit"
+                  ],
+                  "description": "How the image fills its frame: 'crop' covers the frame from the center; 'fit' shows the whole image centered inside it. Overrides design.imageFill for this image. Default: design.imageFill, else 'crop'."
+                },
+                "size": {
+                  "type": "number",
+                  "minimum": 0.1,
+                  "maximum": 0.9,
+                  "description": "Share of the slide width (left/right) or height (top/bottom) given to the image band. Ignored for 'background'. Default 0.5."
+                },
+                "inset": {
+                  "type": "boolean",
+                  "description": "Place the frame inside the slide padding instead of edge to edge, like a card. Default false."
+                },
+                "aspectRatio": {
+                  "type": "number",
+                  "exclusiveMinimum": 0,
+                  "maximum": 10,
+                  "description": "Width-to-height ratio of the frame. The frame becomes the largest centered box with this ratio inside the band or slide, for example 2.39 for a cinematic letterbox or 0.5 for a phone-shaped frame. 'circle' always uses 1."
+                },
+                "shape": {
+                  "type": "string",
+                  "enum": [
+                    "rectangle",
+                    "rounded",
+                    "circle",
+                    "hexagon"
+                  ],
+                  "description": "Mask applied to the frame, exported as the picture's native preset geometry (rect, roundRect, ellipse, hexagon). 'circle' makes the frame square. Default 'rectangle'."
+                },
+                "cornerRadius": {
+                  "type": "number",
+                  "minimum": 0,
+                  "maximum": 0.5,
+                  "description": "Corner radius for shape 'rounded' as a fraction of the frame's shorter side. Default 0.16667, PowerPoint's roundRect default."
+                },
+                "border": {
+                  "type": "object",
+                  "additionalProperties": false,
+                  "required": [
+                    "color",
+                    "width"
+                  ],
+                  "properties": {
+                    "color": {
+                      "$ref": "#/$defs/ColorRef",
+                      "description": "Line color: a hex color, a color-scheme slot or role name, or a 'var:<id>' variable reference."
+                    },
+                    "width": {
+                      "type": "number",
+                      "minimum": 0,
+                      "maximum": 64,
+                      "description": "Line width in reference pixels at a 720-pixel short edge, centered on the frame outline like a native picture line. 0 removes the line."
+                    }
+                  },
+                  "description": "Solid line along the frame's shape. A thick dark border on a rounded portrait frame gives a device bezel."
+                },
+                "opacity": {
+                  "type": "number",
+                  "minimum": 0,
+                  "maximum": 1,
+                  "description": "Image opacity from 0 to 1, exported as a native alphaModFix. The border and overlay keep their own opacity. Default 1."
+                },
+                "recolor": {
+                  "oneOf": [
+                    {
+                      "type": "string",
+                      "const": "grayscale",
+                      "description": "Replace each pixel with its luminance, exported as native a:grayscl."
+                    },
+                    {
+                      "type": "object",
+                      "additionalProperties": false,
+                      "required": [
+                        "dark",
+                        "light"
+                      ],
+                      "properties": {
+                        "dark": {
+                          "$ref": "#/$defs/ColorRef",
+                          "description": "Color at luminance 0."
+                        },
+                        "light": {
+                          "$ref": "#/$defs/ColorRef",
+                          "description": "Color at luminance 1."
+                        }
+                      },
+                      "description": "Duotone: map each pixel's luminance linearly from dark to light, exported as native a:duotone."
+                    }
+                  ],
+                  "description": "Color treatment for the image pixels. Luminance uses Rec. 601 weights (0.299, 0.587, 0.114) on sRGB values."
+                },
+                "overlay": {
+                  "type": "object",
+                  "additionalProperties": false,
+                  "required": [
+                    "color",
+                    "opacity"
+                  ],
+                  "properties": {
+                    "color": {
+                      "$ref": "#/$defs/ColorRef",
+                      "description": "Overlay fill color."
+                    },
+                    "opacity": {
+                      "type": "number",
+                      "minimum": 0,
+                      "maximum": 1,
+                      "description": "Overlay fill opacity."
+                    },
+                    "edge": {
+                      "type": "string",
+                      "enum": [
+                        "top",
+                        "bottom",
+                        "left",
+                        "right"
+                      ],
+                      "description": "Cover only a band along this edge of the frame, for example a caption strip. Rectangle frames only; other shapes report unsupported-image-treatment and draw no overlay. Omit to cover the whole frame."
+                    },
+                    "size": {
+                      "type": "number",
+                      "minimum": 0.05,
+                      "maximum": 1,
+                      "description": "Band share of the frame for an edge overlay. Default 0.3."
+                    }
+                  },
+                  "description": "Solid scrim drawn over the image in the frame's shape, beneath headings and content, for example to keep overlaid text readable. Exported as a native shape above the picture."
                 }
               }
             }
           ],
-          "description": "Optional slide-level image treatment used by layouts that support a decorative or editorial image separate from content images."
+          "description": "Optional slide-level image, separate from content images. It applies to a slide that sets its own design.slideImage, and to slides whose layout declares slideImage: true or whose root image is the same source as a deck-level value. A root image with the same source becomes the slide image instead of a content item. Blur, shadows, soft edges, background removal and device artwork are not part of the treatment vocabulary; see docs/image-treatments.md."
         },
         "contentDirection": {
           "type": "string",
@@ -1815,7 +1974,7 @@ Resolution order: inline catalogs.fontSchemes.records[] -> catalogs.fontSchemes.
     },
     "FontScheme": {
       "type": "object",
-      "description": "Typography selections used by the design system. The pair fields (major, minor) and refinement fields (type, app, languageFamily) mirror font-scheme.schema.json (https://openpresentation.org/schema/opf-font-scheme/v1) so library records and inline OPF overrides are interchangeable on those fields.\n\nTwo parallel models are supported and may be mixed:\n- OOXML pairs (major, minor) - heading and body family names that round-trip directly to PowerPoint majorFont/minorFont entries.\n- Abstract roles (heading, body, accent, code) - OPF-specific Font objects the engine maps onto the OOXML pair when serializing. Convenient for inline overrides and for adding accent/code roles that don't have a direct OOXML slot; not part of the catalog record schema.\n\nIn design.fontScheme, 'id' resolves a fontSchemes catalog record as the base; pair and role overrides on the same object take precedence over the resolved scheme. The string shorthand on design.fontScheme is equivalent to setting only 'id'.",
+      "description": "Typography selections used by the design system. The pair fields (major, minor) and refinement fields (type, app, languageFamily) mirror font-scheme.schema.json (https://openpresentation.org/schema/opf-font-scheme/v1) so library records and inline OPF overrides are interchangeable on those fields.\n\nTwo parallel models are supported and may be mixed:\n- OOXML pairs (major, minor) - heading and body family names that round-trip directly to PowerPoint majorFont/minorFont entries.\n- Abstract roles (heading, body, accent, code) - OPF-specific Font objects the engine maps onto the OOXML pair when serializing. Convenient for inline overrides and for adding accent/code roles that don't have a direct OOXML slot. Catalog records may also carry 'code' (for example the consolas and courier-new records); heading, body and accent are not part of the catalog record schema.\n\nIn design.fontScheme, 'id' resolves a fontSchemes catalog record as the base; pair and role overrides on the same object take precedence over the resolved scheme. The string shorthand on design.fontScheme is equivalent to setting only 'id'.",
       "properties": {
         "id": {
           "type": "string",
@@ -1851,6 +2010,58 @@ Resolution order: inline catalogs.fontSchemes.records[] -> catalogs.fontSchemes.
             "Arial"
           ]
         },
+        "eastAsian": {
+          "type": "object",
+          "additionalProperties": false,
+          "minProperties": 1,
+          "description": "East Asian script fonts. Maps to the OOXML a:ea element of majorFont (major) and minorFont (minor), and to run-level a:ea. When set, they fill the eastAsian slot for every language; when omitted, the slot comes from this scheme's own major/minor when languageFamily is 'ea' and the scheme's languages list is empty or names the presentation language, then from the presentation language's font scheme for East Asian languages, and otherwise from the latin (major/minor) families. A missing 'major' or 'minor' falls back to the other.",
+          "properties": {
+            "major": {
+              "type": "string",
+              "description": "Heading (major) eastAsian font family \u2014 mirrors majorFont a:ea.",
+              "examples": [
+                "Noto Sans JP",
+                "Meiryo",
+                "Microsoft YaHei"
+              ]
+            },
+            "minor": {
+              "type": "string",
+              "description": "Body (minor) eastAsian font family \u2014 mirrors minorFont a:ea.",
+              "examples": [
+                "Noto Sans JP",
+                "Meiryo",
+                "Microsoft YaHei"
+              ]
+            }
+          }
+        },
+        "complexScript": {
+          "type": "object",
+          "additionalProperties": false,
+          "minProperties": 1,
+          "description": "Complex-script fonts (for example Arabic, Hebrew, Indic and Thai). Maps to the OOXML a:cs element of majorFont (major) and minorFont (minor), and to run-level a:cs. When set, they fill the complexScript slot for every language; when omitted, the slot comes from this scheme's own major/minor when languageFamily is 'cs' and the scheme's languages list is empty or names the presentation language, then from the presentation language's font scheme for complex-script languages, and otherwise from the latin (major/minor) families. A missing 'major' or 'minor' falls back to the other.",
+          "properties": {
+            "major": {
+              "type": "string",
+              "description": "Heading (major) complexScript font family \u2014 mirrors majorFont a:cs.",
+              "examples": [
+                "Noto Sans Arabic",
+                "Arial",
+                "Mangal"
+              ]
+            },
+            "minor": {
+              "type": "string",
+              "description": "Body (minor) complexScript font family \u2014 mirrors minorFont a:cs.",
+              "examples": [
+                "Noto Sans Arabic",
+                "Arial",
+                "Mangal"
+              ]
+            }
+          }
+        },
         "type": {
           "type": "string",
           "enum": [
@@ -1875,7 +2086,7 @@ Resolution order: inline catalogs.fontSchemes.records[] -> catalogs.fontSchemes.
             "ea",
             "cs"
           ],
-          "description": "OOXML font-language family this scheme is intended for: 'latin' for Latin-script content, 'ea' for East Asian scripts, 'cs' for Complex Scripts."
+          "description": "OOXML font-language family this scheme is intended for: 'latin' for Latin-script content, 'ea' for East Asian scripts, 'cs' for Complex Scripts. As the design font scheme, an 'ea' or 'cs' scheme also fills that script slot with its own major/minor families when its languages list is empty or names the presentation language."
         },
         "heading": {
           "$ref": "#/$defs/Font",
@@ -1891,7 +2102,7 @@ Resolution order: inline catalogs.fontSchemes.records[] -> catalogs.fontSchemes.
         },
         "code": {
           "$ref": "#/$defs/Font",
-          "description": "Abstract role: monospaced font used for code blocks. No direct OOXML slot."
+          "description": "Abstract role: monospaced font used for code blocks and inline code. No direct OOXML slot. Resolution: this override, then the resolved catalog record's 'code' (for example Consolas for the consolas scheme), then the engine fallback Roboto Mono. Heading and body families are never used as the code fallback."
         }
       }
     },
@@ -1982,6 +2193,109 @@ Resolution order: inline catalogs.fontSchemes.records[] -> catalogs.fontSchemes.
         "#0F172AFF"
       ]
     },
+    "ColorRef": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/HexColor"
+        },
+        {
+          "type": "string",
+          "enum": [
+            "accent1",
+            "accent2",
+            "accent3",
+            "accent4",
+            "accent5",
+            "accent6",
+            "dark1",
+            "dark2",
+            "light1",
+            "light2",
+            "hyperlink",
+            "followedHyperlink",
+            "primary",
+            "secondary",
+            "accent",
+            "background",
+            "surface",
+            "text",
+            "textSecondary"
+          ]
+        },
+        {
+          "type": "string",
+          "pattern": "^var:[a-z][a-z0-9-]*$"
+        }
+      ],
+      "description": "A color value or reference, enforced on styled table cell fill and text colors and on cell border colors. Three forms:\n- Literal hex: '#RGB', '#RRGGBB', or '#RRGGBBAA'.\n- Color-scheme name, resolved through the effective color scheme after design resolution: an OOXML slot ('accent1'-'accent6', 'dark1', 'dark2', 'light1', 'light2', 'hyperlink', 'followedHyperlink') or an abstract role ('primary', 'secondary', 'accent', 'background', 'surface', 'text', 'textSecondary'). Roles resolve through the same role-to-slot mapping engines already apply to color schemes.\n- Variable reference: 'var:<id>' into the top-level variables map.\n\nNames keep content theme-portable: re-theming the deck updates every named reference, where a literal hex stays frozen. Unknown 'var:' ids produce a validation warning, never an error, and engines fall back to their default text color. TextRun.color documents the same three forms but remains an open string so imported decks with unrecognized run colors stay valid; validators warn there instead of erroring.",
+      "examples": [
+        "#0F4C81",
+        "accent2",
+        "text",
+        "var:risk"
+      ]
+    },
+    "Variables": {
+      "type": "object",
+      "propertyNames": {
+        "pattern": "^[a-z][a-z0-9-]*$"
+      },
+      "additionalProperties": {
+        "$ref": "#/$defs/Variable"
+      },
+      "description": "Named color variables, keyed by stable kebab-case id. Content color fields reference entries as 'var:<id>' strings. Each value is a hex string shorthand or a Variable object.",
+      "examples": [
+        {
+          "risk": "#B42318",
+          "highlight": {
+            "type": "color",
+            "value": "#0F4C81",
+            "description": "Brand highlight for emphasized runs."
+          }
+        }
+      ]
+    },
+    "Variable": {
+      "oneOf": [
+        {
+          "$ref": "#/$defs/HexColor"
+        },
+        {
+          "type": "object",
+          "required": [
+            "type",
+            "value"
+          ],
+          "additionalProperties": false,
+          "properties": {
+            "type": {
+              "type": "string",
+              "enum": [
+                "color"
+              ],
+              "description": "Variable kind. Only 'color' is defined today; other kinds may be added when content surfaces exist to consume them."
+            },
+            "value": {
+              "$ref": "#/$defs/HexColor",
+              "description": "Hex color this variable resolves to."
+            },
+            "description": {
+              "type": "string",
+              "description": "Optional prose describing what the variable is for, surfaced by pickers and agents."
+            }
+          }
+        }
+      ],
+      "description": 'A single named variable. A hex string is shorthand for { "type": "color", "value": value }.',
+      "examples": [
+        "#B42318",
+        {
+          "type": "color",
+          "value": "#B42318",
+          "description": "Risk emphasis."
+        }
+      ]
+    },
     "BackgroundShortcut": {
       "oneOf": [
         {
@@ -2196,11 +2510,11 @@ Resolution order: inline catalogs.fontSchemes.records[] -> catalogs.fontSchemes.
           "properties": {
             "preset": {
               "type": "string",
-              "description": "Pattern preset or engine-defined pattern id.",
+              "description": "Pattern preset or engine-defined pattern id. DrawingML preset names (ECMA-376 ST_PresetPatternVal, for example pct5, ltHorz, wdUpDiag) are portable: PPTX export writes them as native pattern fills and import returns the same name. Engine-defined ids are renderer-specific; the legacy preview id diagStripe remains accepted and exports as wdUpDiag.",
               "examples": [
                 "pct5",
                 "ltHorz",
-                "diagStripe"
+                "wdUpDiag"
               ]
             },
             "foregroundColor": {
@@ -2322,7 +2636,7 @@ Resolution order: inline catalogs.fontSchemes.records[] -> catalogs.fontSchemes.
     },
     "HeaderFooterItem": {
       "type": "object",
-      "description": "One header/footer zone. Fields may be combined when the renderer supports it; otherwise renderers should prefer image, then text-like generated content.",
+      "description": "One header/footer zone. Every configured field renders; fields in one zone stack top to bottom in the order image, text, organization, section, slide number, date. Put a date and a slide number in different zones to keep each on the zone's single line.",
       "properties": {
         "text": {
           "type": "string",
@@ -2342,7 +2656,18 @@ Resolution order: inline catalogs.fontSchemes.records[] -> catalogs.fontSchemes.
         },
         "slideNumber": {
           "type": "boolean",
-          "description": "Whether to render the current slide number in this zone."
+          "description": "Whether to render the current slide number in this zone. PPTX export writes a native slide-number field when its value fits within one accepted text line; a value split across lines exports as static text with a diagnostic."
+        },
+        "slideNumberFormat": {
+          "type": "string",
+          "pattern": "[{]current[}]",
+          "description": 'Template for the slide number when slideNumber is true. {current} is the displayed slide number (a native PPTX field when its value fits within one accepted text line); {total} is the number of slides in the rendered or exported deck, written as fixed text because PowerPoint has no slide-count field. Other characters are literal. Defaults to "{current}".',
+          "examples": [
+            "{current}",
+            "{current} / {total}",
+            "A-{current}",
+            "Page {current} of {total}"
+          ]
         },
         "date": {
           "oneOf": [
@@ -2353,7 +2678,23 @@ Resolution order: inline catalogs.fontSchemes.records[] -> catalogs.fontSchemes.
               "type": "string"
             }
           ],
-          "description": "Whether to render the presentation date, or a literal date string to render."
+          "description": "true renders the current date: the renderer or exporter must be given an explicit ISO date by its host (core never reads a clock). PPTX export writes a native date field only for a supported dateFormat whose complete value fits within one accepted text line; otherwise it writes static text with a diagnostic. Native PowerPoint refresh and save/reopen compatibility require separate verification. A string is fixed: with dateFormat it must be an ISO YYYY-MM-DD date and is formatted; without dateFormat it is literal text rendered as written.",
+          "examples": [
+            true,
+            "2026-04-23",
+            "April 2026"
+          ]
+        },
+        "dateFormat": {
+          "type": "string",
+          "minLength": 1,
+          "description": `Date pattern for date. Tokens: yyyy (2026), yy (26), MMMM (April), MMM (Apr), MM (04), M (4), dd (09), d (9), EEEE (Thursday), EEE (Thu). Text in single quotes and other non-letter characters are literal. Month and weekday names are English, independent of host locale. Defaults to "M/d/yyyy" for a current date. PPTX export writes a native current-date field only when its complete value fits within one accepted text line and the pattern matches a PowerPoint en-US date field ('M/d/yyyy'; 'EEEE, MMMM d, yyyy'; 'd MMMM yyyy'; 'MMMM d, yyyy'; 'd-MMM-yy'; 'MMMM yy'; 'MMM-yy'). Other patterns and wrapped fields export as static text with a diagnostic. Full provenance can recover generated-date intent from unchanged supported wrapped dates on OPF reimport; the existing PPTX text remains static.`,
+          "examples": [
+            "MMM d, yyyy",
+            "yyyy-MM-dd",
+            "MMM yyyy",
+            "MMMM d, yyyy"
+          ]
         },
         "organization": {
           "type": "boolean",
@@ -2362,6 +2703,10 @@ Resolution order: inline catalogs.fontSchemes.records[] -> catalogs.fontSchemes.
         "section": {
           "type": "boolean",
           "description": "Whether to render the current slide section label."
+        },
+        "socials": {
+          "type": "boolean",
+          "description": "Whether to render the primary organization's social profiles from organization.socials, one line per platform in key order. A handle is formatted through the platform's socialPlatforms record (companyUrlPattern, else profileUrlPattern, else baseUrl, with handlePrefix stripped) and shown as that profile URL without its 'https://' scheme; a value that is already a URL is shown without an 'https://' scheme; an unknown platform key shows the raw value. Exporters link each line to its full URL when one exists. Speaker socials are not rendered by this field."
         }
       }
     },
@@ -2713,6 +3058,10 @@ Resolution order: inline catalogs.fontSchemes.records[] -> catalogs.fontSchemes.
         },
         "composition": {
           "$ref": "#/$defs/Composition"
+        },
+        "extensions": {
+          "type": "object",
+          "description": 'Custom data passthrough for agent workflows at slide scope; ignored by the engine but preserved across read/write round-trips. Use for review state, generation provenance, or authoring conventions such as { "authoring": { "locked": true } }.'
         }
       }
     },
@@ -2721,6 +3070,18 @@ Resolution order: inline catalogs.fontSchemes.records[] -> catalogs.fontSchemes.
       "description": "A content leaf or recursively composed group. A group contains blocks and optional composition; it cannot mix blocks with leaf payload fields. Groups may nest up to 32 levels.",
       "additionalProperties": false,
       "properties": {
+        "id": {
+          "type": "string",
+          "description": "Optional stable identifier for this payload, unique among slide and payload ids in the document. Use when another system needs to address the payload across edits \u2014 patch-style agent edits, comments, review state, or generation provenance. Identity survives reordering where array indexes do not.",
+          "examples": [
+            "kpi-adoption",
+            "churn-quote"
+          ]
+        },
+        "extensions": {
+          "type": "object",
+          "description": "Custom data passthrough for agent workflows at payload scope; ignored by the engine but preserved across read/write round-trips."
+        },
         "type": {
           "type": "string",
           "enum": [
@@ -3587,10 +3948,11 @@ Resolution order: inline catalogs.fontSchemes.records[] -> catalogs.fontSchemes.
             },
             "color": {
               "type": "string",
-              "description": "Run text color as a hex string.",
+              "description": "Run text color. Documented forms: a hex string ('#RGB', '#RRGGBB', '#RRGGBBAA'), a color-scheme slot or role name resolved through the effective color scheme ('accent2', 'text'), or a 'var:<id>' reference into the top-level variables map. Prefer names over hex so runs survive re-theming. Any other string stays schema-valid so imported decks keep validating: validators warn and renderers fall back to the theme text color.",
               "examples": [
                 "#0F172A",
-                "#1E40AF"
+                "accent2",
+                "var:risk"
               ]
             },
             "fontSize": {
@@ -3638,13 +4000,12 @@ Resolution order: inline catalogs.fontSchemes.records[] -> catalogs.fontSchemes.
       "properties": {
         "type": {
           "type": "string",
-          "description": "Chart type id. Resolves to the id of a chartTypes catalog record; renderers map that record through mappings.openxml and any renderer-specific mapping they understand.",
+          "description": "Chart type id. Resolves to the id of a chartTypes catalog record; renderers map that record through mappings.openxml and any renderer-specific mapping they understand. The bundled catalog covers the chart types Aspose.Slides officially supports; deprecated ids still resolve but validate with a warning naming their replacement.",
           "examples": [
-            "bar",
             "column",
+            "bar",
             "line",
             "pie",
-            "donut",
             "doughnut",
             "area",
             "scatter",
@@ -3652,7 +4013,7 @@ Resolution order: inline catalogs.fontSchemes.records[] -> catalogs.fontSchemes.
             "waterfall",
             "funnel",
             "treemap",
-            "combo"
+            "stacked-column-3x"
           ]
         },
         "data": {
@@ -3933,14 +4294,12 @@ Resolution order: inline catalogs.fontSchemes.records[] -> catalogs.fontSchemes.
       "additionalProperties": false,
       "properties": {
         "fill": {
-          "type": "string",
-          "pattern": "^#(?:[0-9a-fA-F]{3}|[0-9a-fA-F]{6}|[0-9a-fA-F]{8})$",
-          "description": "Explicit RGB or RGBA color. Eight-digit colors include alpha; #00000000 is transparent."
+          "$ref": "#/$defs/ColorRef",
+          "description": "Cell background: a hex color, a color-scheme slot or role name, or a 'var:<id>' variable reference. Eight-digit hex colors include alpha; #00000000 is transparent."
         },
         "color": {
-          "type": "string",
-          "pattern": "^#(?:[0-9a-fA-F]{3}|[0-9a-fA-F]{6}|[0-9a-fA-F]{8})$",
-          "description": "Default text color, overridden by individual rich run colors."
+          "$ref": "#/$defs/ColorRef",
+          "description": "Default text color, overridden by individual rich run colors. Accepts a hex color, a color-scheme slot or role name, or a 'var:<id>' variable reference."
         },
         "align": {
           "type": "string",
@@ -4021,9 +4380,8 @@ Resolution order: inline catalogs.fontSchemes.records[] -> catalogs.fontSchemes.
       ],
       "properties": {
         "color": {
-          "type": "string",
-          "pattern": "^#(?:[0-9a-fA-F]{3}|[0-9a-fA-F]{6}|[0-9a-fA-F]{8})$",
-          "description": "Explicit RGB or RGBA color. Eight-digit colors include alpha; #00000000 is transparent."
+          "$ref": "#/$defs/ColorRef",
+          "description": "Border color: a hex color, a color-scheme slot or role name, or a 'var:<id>' variable reference. Eight-digit hex colors include alpha; #00000000 is transparent."
         },
         "width": {
           "type": "number",
@@ -5170,7 +5528,7 @@ var chartType = {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "$id": "https://openpresentation.org/schema/opf-chart-type/v1",
   "title": "Chart Type",
-  "description": "Schema for chart-type records in the pptx.gallery catalog. Each record describes a named chart variant, its Open XML mapping, its series/category cardinality, the column structure of the underlying workbook, and a small sample dataset suitable for previews. Chart types are referenced from OPF chart content payloads; the engine resolves the reference against catalogs.chartTypes (inline) -> catalogs.chartTypes.source -> the default catalog at https://www.pptx.gallery/chart-types.",
+  "description": 'Schema for chart-type records in the pptx.gallery catalog. The bundled catalog holds one record per chart type that Aspose.Slides officially supports (see mappings.renderers["aspose-slides"].chartType). Each record describes a named chart variant, its Open XML mapping, its series/category cardinality, the column structure of the underlying workbook, and a small sample dataset suitable for previews. Chart types are referenced from OPF chart content payloads; the engine resolves the reference against catalogs.chartTypes (inline) -> catalogs.chartTypes.source -> the default catalog at https://www.pptx.gallery/chart-types.',
   "type": "object",
   "additionalProperties": false,
   "required": [
@@ -5191,11 +5549,11 @@ var chartType = {
       "description": "Stable slug used by OPF documents to reference this chart type. Lowercase kebab-case. Chart type ids may start with a digit (e.g., '100pct-stacked-column', '3d-column') to mirror conventional chart naming.",
       "examples": [
         "column",
-        "clustered-column",
-        "stacked-column",
+        "bar",
+        "stacked-column-3x",
         "doughnut",
-        "bullet-column",
-        "100pct-stacked-column"
+        "treemap",
+        "100pct-stacked-column-3x"
       ]
     },
     "name": {
@@ -5203,9 +5561,9 @@ var chartType = {
       "description": "Stable display/programmatic name for this chart type.",
       "examples": [
         "COLUMN",
-        "CLUSTERED_COLUMN",
+        "STACKED_COLUMN_3X",
         "DOUGHNUT",
-        "BULLET_COLUMN"
+        "TREEMAP"
       ]
     },
     "label": {
@@ -5213,9 +5571,9 @@ var chartType = {
       "description": "Human-readable label shown in chart pickers.",
       "examples": [
         "Column",
-        "Clustered Column",
+        "Stacked Column",
         "Doughnut",
-        "Bullet Column"
+        "Treemap"
       ]
     },
     "summary": {
@@ -5237,6 +5595,10 @@ var chartType = {
       "$ref": "#/$defs/ChartTypeMappings",
       "description": "Canonical and optional renderer-specific mappings used by engines to render this chart type."
     },
+    "deprecation": {
+      "$ref": "#/$defs/ChartTypeDeprecation",
+      "description": "Present when this chart type is deprecated. Deprecated records stay resolvable so existing documents keep validating, but pickers and default listings exclude them, validators warn when a document references them, and they are removed in the release named by `removal`."
+    },
     "group": {
       "type": "string",
       "description": "Top-level grouping in the chart picker (column, bar, line, area, pie, radar, etc.).",
@@ -5473,6 +5835,35 @@ var chartType = {
     }
   },
   "$defs": {
+    "ChartTypeDeprecation": {
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "replacedBy"
+      ],
+      "properties": {
+        "replacedBy": {
+          "type": "string",
+          "pattern": "^[a-z0-9][a-z0-9-]*$",
+          "description": "Id of the non-deprecated chart type that documents should reference instead.",
+          "examples": [
+            "column",
+            "stacked-column-3x"
+          ]
+        },
+        "reason": {
+          "type": "string",
+          "description": "Why the record is deprecated."
+        },
+        "removal": {
+          "type": "string",
+          "description": "Package version in which the record is scheduled for removal from the bundled catalog.",
+          "examples": [
+            "0.12.0"
+          ]
+        }
+      }
+    },
     "ChartTypeMappings": {
       "type": "object",
       "additionalProperties": false,
@@ -5486,11 +5877,18 @@ var chartType = {
         },
         "renderers": {
           "type": "object",
-          "description": "Optional renderer-specific mappings. Keys are renderer ids; values are intentionally opaque to OPF.",
+          "description": 'Optional renderer-specific mappings. Keys are renderer ids; values are intentionally opaque to OPF. The bundled catalog records the matching Aspose.Slides ChartType enumeration member under the "aspose-slides" key, e.g. {"aspose-slides": {"chartType": "StackedColumn"}}.',
           "additionalProperties": {
             "type": "object",
             "additionalProperties": true
-          }
+          },
+          "examples": [
+            {
+              "aspose-slides": {
+                "chartType": "ClusteredColumn"
+              }
+            }
+          ]
         }
       }
     },
@@ -6171,13 +6569,25 @@ var language = {
         "zh-Hans"
       ]
     },
+    "ooxmlLang": {
+      "type": "string",
+      "description": "Curated culture tag for OOXML text-run language attributes (a:rPr/@lang, a:endParaRPr/@lang), in the language-[Script-]REGION form Office recognizes (e.g. 'ja-JP', 'ar-SA', 'ms-MY', 'nb-NO', 'fil-PH', 'zh-CN'). Engines emit it instead of 'bcp47' when the document names the language by catalog id or by a tag without a region; a region-bearing tag written by the author is emitted as written. Curated rather than inferred so output does not depend on the runtime's locale data.",
+      "examples": [
+        "en-US",
+        "ja-JP",
+        "ar-SA",
+        "ms-MY",
+        "nb-NO",
+        "zh-CN"
+      ]
+    },
     "direction": {
       "type": "string",
       "enum": [
         "ltr",
         "rtl"
       ],
-      "description": "Base text direction for the language.",
+      "description": "Base text direction for the language. When omitted, engines derive it from the script: Arabic (Arab), Hebrew (Hebr), Syriac (Syrc), Thaana (Thaa), N'Ko (Nkoo), Adlam (Adlm), Samaritan (Samr), Mandaic (Mand) and Hanifi Rohingya (Rohg) are right-to-left; every other script is left-to-right. Bundled language records state it explicitly.",
       "examples": [
         "ltr",
         "rtl"
@@ -6185,18 +6595,24 @@ var language = {
     },
     "script": {
       "type": "string",
-      "description": "ISO 15924 script code when the writing system should be explicit.",
+      "description": "ISO 15924 script code of the language's writing system. The script selects the OOXML font slot the language's text uses: East Asian scripts (Hans, Hant, Hani, Jpan, Kore, Hang, Hira, Kana, Bopo, Yiii) use the eastAsian slot; complex scripts (for example Arab, Hebr, Syrc, Thaa, Deva, Beng, Guru, Gujr, Orya, Taml, Telu, Knda, Mlym, Sinh, Thai, Laoo, Tibt, Mymr, Khmr, Mong) use the complexScript slot; every other script (Latn, Cyrl, Grek, Armn, Geor, Ethi, ...) uses the latin slot. When omitted, engines infer it from the BCP-47 tag. Bundled language records state it explicitly. See docs/programs/font-fidelity-everywhere/script-font-model.md.",
       "examples": [
         "Latn",
-        "Arab",
         "Cyrl",
+        "Grek",
+        "Arab",
+        "Hebr",
+        "Jpan",
+        "Kore",
         "Hans",
-        "Hant"
+        "Hant",
+        "Deva",
+        "Thai"
       ]
     },
     "fontScheme": {
       "type": "string",
-      "description": "Default font-scheme id for this language when targeting PowerPoint output. Resolves against catalogs.fontSchemes the same way design.fontScheme or design.fontScheme.id does.",
+      "description": "Default font-scheme id for this language when targeting PowerPoint output. Resolves against catalogs.fontSchemes the same way design.fontScheme or design.fontScheme.id does. Its major/minor families fill the language's script slot (eastAsian or complexScript, chosen by 'script') unless the effective design font scheme sets that slot itself; the latin slot always follows the design font scheme.",
       "examples": [
         "aptos",
         "microsoft-yahei",
@@ -6205,7 +6621,7 @@ var language = {
     },
     "googleFontScheme": {
       "type": "string",
-      "description": "Default font-scheme id for this language when targeting Google Slides output. Resolves against catalogs.fontSchemes the same way design.fontScheme or design.fontScheme.id does.",
+      "description": "Default font-scheme id for this language when targeting Google Slides output. Resolves against catalogs.fontSchemes the same way design.fontScheme or design.fontScheme.id does. Used in place of 'fontScheme' when resolving script fonts for Google Slides output.",
       "examples": [
         "roboto",
         "noto-sans",
@@ -6539,6 +6955,96 @@ var fontScheme = {
         "Microsoft YaHei"
       ]
     },
+    "code": {
+      "type": "object",
+      "description": "Optional monospaced font for code blocks and inline code. It has the same shape as the OPF FontScheme 'code' role, so a record and an inline design.fontScheme override are interchangeable. OOXML has no code slot, so exporters write this family on code runs. When neither design.fontScheme nor the resolved record defines 'code', engines fall back to Roboto Mono.",
+      "required": [
+        "family"
+      ],
+      "properties": {
+        "family": {
+          "type": "string",
+          "description": "Monospaced font family name.",
+          "examples": [
+            "Consolas",
+            "Courier New"
+          ]
+        },
+        "weight": {
+          "type": "number",
+          "description": "Numeric font weight (e.g., 400 for regular, 700 for bold)."
+        },
+        "style": {
+          "type": "string",
+          "enum": [
+            "normal",
+            "italic"
+          ],
+          "description": "Font style."
+        },
+        "letterSpacing": {
+          "type": "number",
+          "description": "Letter spacing (tracking) in ems."
+        }
+      },
+      "examples": [
+        {
+          "family": "Consolas"
+        }
+      ]
+    },
+    "eastAsian": {
+      "type": "object",
+      "additionalProperties": false,
+      "minProperties": 1,
+      "description": "East Asian script fonts. Maps to the OOXML a:ea element of majorFont (major) and minorFont (minor), and to run-level a:ea. When set, they fill the eastAsian slot for every language; when omitted, the slot comes from this scheme's own major/minor when languageFamily is 'ea' and the scheme's languages list is empty or names the presentation language, then from the presentation language's font scheme for East Asian languages, and otherwise from the latin (major/minor) families. A missing 'major' or 'minor' falls back to the other.",
+      "properties": {
+        "major": {
+          "type": "string",
+          "description": "Heading (major) eastAsian font family \u2014 mirrors majorFont a:ea.",
+          "examples": [
+            "Noto Sans JP",
+            "Meiryo",
+            "Microsoft YaHei"
+          ]
+        },
+        "minor": {
+          "type": "string",
+          "description": "Body (minor) eastAsian font family \u2014 mirrors minorFont a:ea.",
+          "examples": [
+            "Noto Sans JP",
+            "Meiryo",
+            "Microsoft YaHei"
+          ]
+        }
+      }
+    },
+    "complexScript": {
+      "type": "object",
+      "additionalProperties": false,
+      "minProperties": 1,
+      "description": "Complex-script fonts (for example Arabic, Hebrew, Indic and Thai). Maps to the OOXML a:cs element of majorFont (major) and minorFont (minor), and to run-level a:cs. When set, they fill the complexScript slot for every language; when omitted, the slot comes from this scheme's own major/minor when languageFamily is 'cs' and the scheme's languages list is empty or names the presentation language, then from the presentation language's font scheme for complex-script languages, and otherwise from the latin (major/minor) families. A missing 'major' or 'minor' falls back to the other.",
+      "properties": {
+        "major": {
+          "type": "string",
+          "description": "Heading (major) complexScript font family \u2014 mirrors majorFont a:cs.",
+          "examples": [
+            "Noto Sans Arabic",
+            "Arial",
+            "Mangal"
+          ]
+        },
+        "minor": {
+          "type": "string",
+          "description": "Body (minor) complexScript font family \u2014 mirrors minorFont a:cs.",
+          "examples": [
+            "Noto Sans Arabic",
+            "Arial",
+            "Mangal"
+          ]
+        }
+      }
+    },
     "type": {
       "type": "string",
       "enum": [
@@ -6563,7 +7069,7 @@ var fontScheme = {
         "ea",
         "cs"
       ],
-      "description": "OOXML font-language family this scheme is intended for: 'latin' for Latin-script content, 'ea' for East Asian scripts, 'cs' for Complex Scripts."
+      "description": "OOXML font-language family this scheme is intended for: 'latin' for Latin-script content, 'ea' for East Asian scripts, 'cs' for Complex Scripts. As the design font scheme, an 'ea' or 'cs' scheme also fills that script slot with its own major/minor families when its languages list is empty or names the presentation language."
     },
     "languages": {
       "type": "array",