@openpresentation/opf 0.18.3 → 0.19.0

package/dist/{chunk-2PEWUUBR.js → chunk-R5T4H4ZV.js}

@@ -1201,7 +1201,7 @@ var presentation = {
             "center",
             "right"
           ],
-          "description": "Default horizontal alignment for title placeholders in resolved layouts. Effective value: the slide's design, then the deck's design, then the layout record's design.titleAlignment, then the engine default."
+          "description": "Default horizontal alignment for the title heading area in resolved layouts. Effective value: the slide's design, then the deck's design, then the theme's design.titleAlignment, then the layout record's design.titleAlignment, then the engine default."
         },
         "contentAlignment": {
           "type": "string",
@@ -1210,11 +1210,11 @@ var presentation = {
             "center",
             "right"
           ],
-          "description": "Default horizontal alignment for body/content regions in resolved layouts. Effective value: the slide's design, then the deck's design, then the layout record's design.contentAlignment, then the engine default. A cover's tag and subtitle follow titleAlignment unless the slide's own design sets contentAlignment."
+          "description": "Default horizontal alignment for body/content regions in resolved layouts. Effective value: the slide's design, then the deck's design, then the theme's design.contentAlignment, then the layout record's design.contentAlignment, then the engine default. A cover's tag and subtitle follow titleAlignment unless the slide's own design sets contentAlignment."
         },
         "contentBox": {
           "type": "boolean",
-          "description": "Whether body/content regions are rendered inside a visible card or surface. Effective value: the slide's design, then the deck's design, then the layout record's design.contentBox, then the engine default."
+          "description": "Whether body/content regions are rendered inside a visible card or surface. Effective value: the slide's design, then the deck's design, then the theme's design.contentBox, then the layout record's design.contentBox, then the engine default."
         },
         "contentDirection": {
           "type": "string",
@@ -1222,7 +1222,7 @@ var presentation = {
             "horizontal",
             "vertical"
           ],
-          "description": "Axis along which parallel body content is arranged. Sets the root arrangement mode of blocks and root payloads when no composition.mode is set on the slide or on its layout record: 'vertical' is column, 'horizontal' is row. Precedence: composition.mode (the slide's own, else the layout record's geometry contract), then the effective value (slide design, then deck design, then the layout record's design.contentDirection), then automatic selection. A layout that carries a composition.mode keeps its grid or direction whatever this value says. Promoted regions (left, top:left, ...) keep their explicit geometry and nested groups keep their own composition."
+          "description": "Axis along which parallel body content is arranged: 'vertical' is a column, 'horizontal' a row. Effective value: the slide's design, then the deck's design, then the theme's design.contentDirection, then the layout record's design.contentDirection. On a slide with a template layout (OPF 0.19) it turns every flowing region of the slide into one row or one column, below the slide's own composition.mode, columns and weights, which arrange its first primary flowing region. On an automatic slide (and a 0.18 record) it sets the root arrangement mode when no composition.mode is set on the slide or on its layout record. Promoted regions (left, top:left, ...) keep their explicit geometry and nested groups keep their own composition."
         },
         "chartPrimary": {
           "type": "string",
@@ -1233,7 +1233,7 @@ var presentation = {
             "left",
             "right"
           ],
-          "description": "Where the primary chart sits relative to supporting content. Effective value: slide design, then deck design, then the layout record's design.chartPrimary. When the slide has no promoted regions and no composition.mode of its own, and its root nodes mix at least one chart with other content, the first chart becomes a primary track and the other nodes form one synthetic sub-grid: 'left'/'right' is a two-track row and 'top'/'bottom' a two-track column, weighted 3:2 in favor of the chart; explicit root columns and weights are ignored while it applies. 'none' (the default) keeps the ordinary automatic grid with equal weight. It is shorthand for a placeholder group (layout.schema.json PlaceholderGroup): the slide composes exactly as on a layout record whose root composition is that weighted row or column and whose placeholders are the chart and one automatic group of the other content, and while it applies it replaces the layout record's own placeholder groups as well."
+          "description": "Where the primary chart sits relative to supporting content. Effective value: slide design, then deck design, then the layout record's design.chartPrimary. It applies to automatic slides only; a template layout says the same with its regions (chart-beside). When the slide has no promoted regions and no composition.mode of its own, and its root nodes mix at least one chart with other content, the first chart becomes a primary track and the other nodes form one synthetic sub-grid: 'left'/'right' is a two-track row and 'top'/'bottom' a two-track column, weighted 3:2 in favor of the chart; explicit root columns and weights are ignored while it applies. 'none' (the default) keeps the ordinary automatic grid with equal weight. Automatic composition builds direct content groups; template regions remain authoritative."
         },
         "imageFit": {
           "type": "string",
@@ -1242,7 +1242,7 @@ var presentation = {
             "contain",
             "stretch"
           ],
-          "description": "Default fit of image blocks (and Slide.image) that set no fit of their own: 'cover' fills the frame and crops what overflows around the block's focus, 'contain' shows the whole picture centered in the frame, 'stretch' scales it to the frame exactly. Effective value: the slide's design, then the deck's design, then the layout record's design.imageFit, then 'cover'. Backgrounds set their own fit."
+          "description": "Default fit of image blocks (and Slide.image) that set no fit of their own: 'cover' fills the frame and crops what overflows around the block's focus, 'contain' shows the whole picture centered in the frame, 'stretch' scales it to the frame exactly. Effective value: the slide's design, then the deck's design, then the theme's design.imageFit, then the layout record's design.imageFit, then 'cover'. Backgrounds set their own fit."
         },
         "listBullet": {
           "type": "string",
@@ -1250,7 +1250,11 @@ var presentation = {
             "character",
             "image"
           ],
-          "description": "Marker style for items and bullets lists. Effective value: the slide's design, then the deck's design, then the layout record's design.listBullet, then 'character'. 'character' (the default) draws the glyph marker. 'image' draws the primary organization's icon logo (or the organization and shape design.logo names; the onDark value on dark backgrounds) as a picture bullet: a square of the marker's font size whose bottom sits on the marker baseline, so list geometry does not change. Without a logo the glyph is drawn and the engine reports unresolved-content at this field."
+          "description": "Marker style for items and bullets lists. Effective value: the slide's design, then the deck's design, then the theme's design.listBullet, then the layout record's design.listBullet, then 'character'. 'character' (the default) draws the glyph marker. 'image' draws the primary organization's icon logo (or the organization and shape design.logo names; the onDark value on dark backgrounds) as a picture bullet: a square of the marker's font size whose bottom sits on the marker baseline, so list geometry does not change. Without a logo the glyph is drawn and the engine reports unresolved-content at this field."
+        },
+        "mirror": {
+          "type": "boolean",
+          "description": "Draw the slide's template layout mirrored (OPF 0.19): each row's cells and the column sizes reversed, so a 'beside' layout puts its picture, chart or table at the end. Logical: a right-to-left deck mirrors on top. Binding and reading order do not change. Effective value: the slide's design, then the deck's design, then the layout record's design.mirror, then false. Slides without a template layout ignore it."
         }
       }
     },
@@ -2754,13 +2758,12 @@ var presentation = {
         },
         "layout": {
           "$ref": "#/$defs/CatalogReference",
-          "description": "Optional layout: a layouts reference, a bare id ('title-subtitle') or 'name:id' ('acme:hero'). When omitted, the slide is composed with no layout record: engines arrange title, subtitle, tag and content automatically, a slide with no body payload is a cover (vertically centered), and design hints apply; there is no finding. A reference that resolves nowhere is the warning opf/unresolved-reference (and the 'unresolved-reference' diagnostic of resolveSlideContext), the slide composes automatically, and a strict export fails. A layout never changes what a slide contains, and engines never substitute a different layout.",
+          "description": "Optional layout: a layouts reference, a bare id ('pillars') or 'name:id' ('acme:hero'), or 'auto'. When omitted or 'auto', the slide is composed with no layout record: engines arrange title, subtitle, tag and content automatically, a slide with no body payload is a cover (vertically centered), and design hints apply; there is no finding. 'auto' is reserved, so no catalog may define a layout of that id, and opf format drops it. A layout is a grid template (layout.schema.json): the slide's content stays flat and binds to the layout's regions by reading order, role and kind, a block may pin itself to a region with 'region', and an empty region collapses. A reference that resolves nowhere is the warning opf/unresolved-reference (and the 'unresolved-reference' diagnostic of resolveSlideContext), the slide composes automatically, and a strict export fails. A layout id of the 0.18 default catalog that 0.19 no longer has is such a reference: 0.19 has no migration path for layouts. A layout never changes what a slide contains, and engines never substitute a different layout.",
           "examples": [
-            "title",
-            "title-subtitle",
-            "text-2x",
-            "chart-3x",
-            "blank",
+            "cover",
+            "pillars",
+            "chart-beside",
+            "auto",
             "acme:hero"
           ]
         },
@@ -2776,7 +2779,7 @@ var presentation = {
               }
             }
           ],
-          "description": "Slide-level title content. When the resolved layout exposes a 'title' placeholder, the engine renders this value there. Use a string for plain text or TextRun[] for inline rich text (a colored word, bold, a link, a citation or footnote marker); the heading keeps its size and fitting rules either way, and run colors resolve like body text.",
+          "description": "Slide-level title content. A v2 layout renders this in its title heading area, or an implicit heading row when that area is absent. Use a string for plain text or TextRun[] for inline rich text (a colored word, bold, a link, a citation or footnote marker); the heading keeps its size and fitting rules either way, and run colors resolve like body text.",
           "examples": [
             "Quarterly Review",
             "Why Now",
@@ -2802,7 +2805,7 @@ var presentation = {
               }
             }
           ],
-          "description": "Slide-level subtitle or supporting line. When the resolved layout exposes a 'subtitle' placeholder, the engine renders this value there. Use a string for plain text or TextRun[] for inline rich text (a colored word, bold, a link, a citation or footnote marker); the heading keeps its size and fitting rules either way, and run colors resolve like body text.",
+          "description": "Slide-level subtitle or supporting line. A v2 layout renders this in its subtitle area when present, otherwise in the title heading group. Use a string for plain text or TextRun[] for inline rich text (a colored word, bold, a link, a citation or footnote marker); the heading keeps its size and fitting rules either way, and run colors resolve like body text.",
           "examples": [
             "Prepared for the board",
             "Three signals changed this quarter"
@@ -2820,7 +2823,7 @@ var presentation = {
               }
             }
           ],
-          "description": "Small slide-level label or badge. When the resolved layout exposes a 'tag' placeholder, the engine renders this value there. Use a string for plain text or TextRun[] for inline rich text (a colored word, bold, a link, a citation or footnote marker); the heading keeps its size and fitting rules either way, and run colors resolve like body text.",
+          "description": "Small slide-level label or badge. A v2 layout renders this before the title in its title heading group; tag is not a separate layout area. Use a string for plain text or TextRun[] for inline rich text (a colored word, bold, a link, a citation or footnote marker); the heading keeps its size and fitting rules either way, and run colors resolve like body text.",
           "examples": [
             "Intro",
             "Confidential",
@@ -2878,7 +2881,7 @@ var presentation = {
         },
         "image": {
           "$ref": "#/$defs/Asset",
-          "description": "Shorthand for one image block: the picture composes as body content, like { type: 'image', image: value }, with the effective design.imageFit. A layout's image placeholder may place it along an edge (placement). For fit, focus, treatments or an explicit placement use an image block in blocks; for a full-slide picture behind the content use design.background. Presence of this field infers type 'image'."
+          "description": "Shorthand for one image block: the picture composes as body content, like { type: 'image', image: value }, with the effective design.imageFit. A v2 layout binds it to a compatible body region; a region's bleed setting may extend its outer edges to the slide edge. For fit, focus, treatments or an explicit placement use an image block in blocks; for a full-slide picture behind the content use design.background. Presence of this field infers type 'image'."
         },
         "video": {
           "$ref": "#/$defs/Asset",
@@ -3139,6 +3142,15 @@ var presentation = {
           "type": "object",
           "description": "Custom data passthrough for agent workflows at payload scope; ignored by the engine but preserved across read/write round-trips."
         },
+        "region": {
+          "type": "string",
+          "pattern": "^[a-z][a-z0-9-]*$",
+          "description": "Pin a root block (slides.N.blocks.I) to a region of the slide's template layout by name (OPF 0.19). The block goes to that region when the region exists, accepts the block's kind and has room; otherwise the pin is ignored with a warning (opf/region-unknown, opf/region-kind or opf/region-full) and the block is placed by its kind. Blocks without a pin are bound by reading order, role and kind. A pin on a nested block, or on a slide without a template layout, has no effect.",
+          "examples": [
+            "notes",
+            "metrics"
+          ]
+        },
         "type": {
           "type": "string",
           "enum": [
@@ -3240,6 +3252,23 @@ var presentation = {
             ]
           ]
         },
+        "columns": {
+          "oneOf": [
+            {
+              "const": "auto"
+            },
+            {
+              "type": "integer",
+              "minimum": 1,
+              "maximum": 3
+            }
+          ],
+          "description": "Lay the payload's `items` or `bullets` out in columns (OPF 0.19). 'auto' tries 1, 2 then 3 equal columns at the starting text size and uses the first count at which the list fits, as long as a column stays at least a quarter of the slide wide; when none fits, the largest allowed count shrinks towards minFontSize. 1, 2 or 3 fixes the count. Column breaks fall between items (a nested item stays with its parent) and keep the columns as even as possible; numbering continues and reading order runs column by column. A lone list in a layout region with listColumns: 'auto' behaves as 'auto'.",
+          "examples": [
+            "auto",
+            2
+          ]
+        },
         "image": {
           "$ref": "#/$defs/Asset",
           "description": "Source for an image item.",
@@ -3690,6 +3719,27 @@ var presentation = {
               ]
             }
           }
+        },
+        {
+          "if": {
+            "required": [
+              "columns"
+            ]
+          },
+          "then": {
+            "anyOf": [
+              {
+                "required": [
+                  "items"
+                ]
+              },
+              {
+                "required": [
+                  "bullets"
+                ]
+              }
+            ]
+          }
         }
       ]
     },
@@ -5520,17 +5570,22 @@ var presentation = {
               "layouts": {
                 "two-column": {
                   "name": "Two column",
-                  "placeholders": [
-                    {
-                      "type": "title"
+                  "areas": [
+                    "title title",
+                    "primary secondary"
+                  ],
+                  "regions": {
+                    "primary": {
+                      "accepts": [
+                        "text"
+                      ]
                     },
-                    {
-                      "type": "text"
-                    },
-                    {
-                      "type": "text"
+                    "secondary": {
+                      "accepts": [
+                        "text"
+                      ]
                     }
-                  ]
+                  }
                 }
               }
             },
@@ -5587,10 +5642,8 @@ var presentation = {
             "layouts": {
               "hero": {
                 "name": "Hero",
-                "placeholders": [
-                  {
-                    "type": "title"
-                  }
+                "areas": [
+                  "title"
                 ]
               }
             }
@@ -5599,14 +5652,18 @@ var presentation = {
             "layouts": {
               "q4-special": {
                 "name": "Q4 special",
-                "placeholders": [
-                  {
-                    "type": "title"
-                  },
-                  {
-                    "type": "chart"
+                "areas": [
+                  "title",
+                  "chart"
+                ],
+                "regions": {
+                  "chart": {
+                    "accepts": [
+                      "chart"
+                    ],
+                    "flow": "none"
                   }
-                ]
+                }
               }
             }
           }
@@ -5623,7 +5680,7 @@ var presentation = {
         },
         "layouts": {
           "$ref": "#/$defs/CatalogRecords",
-          "description": "Layout records keyed by id, each with the fields of https://openpresentation.org/schema/opf-layout/v1. Referenced from Slide.layout."
+          "description": "Layout records keyed by id, each with the fields of https://openpresentation.org/schema/opf-layout/v2. Referenced from Slide.layout."
         },
         "themes": {
           "$ref": "#/$defs/CatalogRecords",
@@ -5715,7 +5772,7 @@ var presentation = {
     "Composition": {
       "type": "object",
       "additionalProperties": false,
-      "description": "Portable dynamic composition. Slide fields override the resolved layout. Nested groups (content groups here, placeholder groups in a layout record) arrange their children independently, inheriting only minFontSize and overflow. Explicit promoted regions retain their positions.",
+      "description": "Automatic slide and content-group arrangement. Nested content groups arrange their children independently, inheriting only minFontSize and overflow. Explicit promoted regions retain their positions. A v2 layout defines its grid through areas, tracks and regions; its composition supports gap, padding, minFontSize and overflow rather than mode, columns or weights.",
       "properties": {
         "mode": {
           "type": "string",
@@ -6321,6 +6378,66 @@ var theme = {
         "standard"
       ]
     },
+    "design": {
+      "type": "object",
+      "additionalProperties": false,
+      "description": "The theme's design defaults (OPF 0.19), so a house style such as boxed content or centred titles is set once: the keys and values of the deck's design for titleAlignment, contentAlignment, contentBox, contentDirection, imageFit and listBullet. Per key the slide's design wins, then the deck's design, then this, then the layout record's design, then the engine default.",
+      "properties": {
+        "titleAlignment": {
+          "type": "string",
+          "enum": [
+            "left",
+            "center",
+            "right"
+          ],
+          "description": "As design.titleAlignment of a deck."
+        },
+        "contentAlignment": {
+          "type": "string",
+          "enum": [
+            "left",
+            "center",
+            "right"
+          ],
+          "description": "As design.contentAlignment of a deck."
+        },
+        "contentBox": {
+          "type": "boolean",
+          "description": "As design.contentBox of a deck."
+        },
+        "contentDirection": {
+          "type": "string",
+          "enum": [
+            "horizontal",
+            "vertical"
+          ],
+          "description": "As design.contentDirection of a deck."
+        },
+        "imageFit": {
+          "type": "string",
+          "enum": [
+            "cover",
+            "contain",
+            "stretch"
+          ],
+          "description": "As design.imageFit of a deck."
+        },
+        "listBullet": {
+          "type": "string",
+          "enum": [
+            "character",
+            "image"
+          ],
+          "description": "As design.listBullet of a deck."
+        }
+      },
+      "examples": [
+        {
+          "contentBox": true,
+          "titleAlignment": "left"
+        }
+      ]
+    },
     "tags": {
       "type": "array",
       "items": {
@@ -6402,48 +6519,51 @@ var theme = {
 };
 var layout = {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "https://openpresentation.org/schema/opf-layout/v1",
+  "$id": "https://openpresentation.org/schema/opf-layout/v2",
   "title": "Slide Layout",
-  "description": "Schema for slide-layout records. Each record describes a semantic slide layout: what regions it exposes, what content kinds those regions are intended to hold, how they are arranged (composition) and its design hints. Documents reference a layout from Slide.layout; a slide without a layout, or whose layout resolves nowhere, composes automatically.\n\nA document references a record as a bare id or 'name:id' and resolves it in its own catalogs groups first, then in the catalog the host registered for the group's source; engines never fetch a catalog. A published record file carries '$schema' and 'id'; the copy a document embeds under catalogs.<group>.<kind>.<id> carries neither (the key is the id) and no 'x-*' display metadata.",
+  "description": "Schema for slide-layout records (OPF 0.19). A layout is a grid template: 'areas' names the cells of a grid in the notation of CSS grid-template-areas, 'columns' and 'rows' size its tracks, and 'regions' says, for every body area, which content kinds it takes and how several blocks share it. Slide content stays flat: engines bind a slide's blocks to the regions by reading order, role and kind (bindRegions in @openpresentation/opf), a block may pin itself to a region with 'region', and an empty region collapses into a neighbour. Built-in and custom layouts are records of this one schema; a custom layout is embedded under catalogs.custom.layouts or shipped in a catalog. Documents reference a layout from Slide.layout; a slide without a layout, with layout 'auto', or whose layout resolves nowhere composes automatically.\n\nA document references a record as a bare id or 'name:id' and resolves it in its own catalogs groups first, then in the catalog the host registered for the group's source; engines never fetch a catalog. A published record file carries '$schema' and 'id'; the copy a document embeds under catalogs.<group>.<kind>.<id> carries neither (the key is the id) and no 'x-*' display metadata.",
   "type": "object",
   "required": [
     "$schema",
     "id",
-    "name"
+    "name",
+    "areas"
   ],
   "properties": {
     "$schema": {
       "type": "string",
-      "const": "https://openpresentation.org/schema/opf-layout/v1",
-      "description": "Identifies a published record file as a layout record. Required in a published file; an embedded copy omits it."
+      "const": "https://openpresentation.org/schema/opf-layout/v2",
+      "description": "Identifies a published record file as a layout template. Required in a published file; an embedded copy omits it."
     },
     "id": {
       "type": "string",
       "pattern": "^[a-z][a-z0-9-]*$",
-      "description": "The layout's id in its catalog, lowercase kebab-case. Required in a published record file; a document references the record by it (a bare id, or 'name:id' for a named group) and embeds it keyed by it, without this field.",
+      "description": "The layout's id in its catalog, lowercase kebab-case. Required in a published record file; a document references the record by it (a bare id, or 'name:id' for a named group) and embeds it keyed by it, without this field. 'auto' is reserved: Slide.layout 'auto' is automatic composition, so no catalog may define a layout of that id.",
       "examples": [
-        "title",
-        "title-subtitle",
-        "chart-1x",
-        "image-focus"
-      ]
+        "cover",
+        "pillars",
+        "chart-beside",
+        "roadmap-split"
+      ],
+      "not": {
+        "const": "auto"
+      }
     },
     "name": {
       "type": "string",
-      "description": "Human-readable layout name shown in layout pickers.",
+      "description": "Human-readable layout name, shown in layout pickers and as the PowerPoint layout name.",
       "examples": [
-        "Title",
-        "Title Subtitle",
-        "Chart 1x",
-        "Image Bleed"
+        "Cover",
+        "Pillars",
+        "Chart beside"
       ]
     },
     "summary": {
       "type": "string",
       "description": "One-sentence positioning of the layout \u2014 when to reach for it.",
       "examples": [
-        "Slide title aligned left over a single content area \u2014 flexible workhorse layout.",
-        "Title plus a single chart on the left and supporting copy on the right."
+        "Two to six ideas of equal weight, as cards.",
+        "A chart with the takeaway beside it."
       ]
     },
     "description": {
@@ -6455,14 +6575,92 @@ var layout = {
     },
     "design": {
       "$ref": "#/$defs/DesignHints",
-      "description": "The layout's design hints, with the same keys and values as the deck's design and a slide's design (a slide overrides exactly what its layout sets, by the same name). An absent key means the layout has no opinion. Every key is applied from the record as the lowest-precedence default, per key: the slide's design, then the deck's design, then this record's design, then the engine default, so a layout value nobody overrides is honored without copying it anywhere (a layout's composition.mode still ranks above contentDirection). Composition, the renderer and the PPTX exporter all read the one result."
+      "description": "The layout's design defaults, with the same keys and values as the deck's design and a slide's design (a slide overrides exactly what its layout sets, by the same name). An absent key means the layout has no opinion. Per key the slide's design wins, then the deck's design, then the resolved theme's design, then this record's design, then the engine default. Composition, the renderer and the PPTX exporter all read the one result."
     },
-    "placeholders": {
+    "areas": {
       "type": "array",
+      "minItems": 1,
+      "maxItems": 12,
       "items": {
-        "$ref": "#/$defs/PlaceholderEntry"
+        "type": "string"
       },
-      "description": `Ordered regions the layout exposes. This is the single source of truth for what the layout holds: the content kind, the number of body regions and whether it has a title, subtitle or tag are derived from it (layoutContent in @openpresentation/opf, which counts the leaves of placeholder groups), never stored separately. The engine fills 'title', 'subtitle' and 'tag' placeholders from Slide.title, Slide.subtitle and Slide.tag. The other placeholders are content-kind regions that composition uses to size the body and that pickers use to match layouts. An entry may instead be a placeholder group ({ "type": "group", "composition", "placeholders" }) that arranges its own regions inside one cell of this record's composition, so a record can say 'two stacked panels beside a chart' once; groups nest at most three levels. Slide content stays flat: its body payloads fill the leaf regions in reading order (depth first, in array order). Slide content itself lives either in root payload fields, blocks or promoted region keys on Slide. Chrome (slide number, footer, date) is not included here; it is owned by Design.header / Design.footer.`
+      "description": "The grid, in the notation of CSS grid-template-areas: each string is a row, each word a cell, and a name repeated over adjacent cells spans them; '.' is an empty cell. Words are lowercase names ([a-z][a-z0-9-]*) or '.', separated by spaces, and every row has the same number of words (at most 12 rows and 12 columns). A name's cells must form one filled rectangle. 'title' and 'subtitle' are heading areas: 'title' holds the slide's heading group (tag, title and subtitle, stacked) and a 'subtitle' area takes the subtitle out of it; they have no regions entry, and a 'subtitle' area needs a 'title' area. A layout with no 'title' area gets an implicit auto row on top for a slide that has headings. Every other name is a body region and needs an entry in 'regions'. The grid rules a schema cannot express are the validate finding opf/layout-template.",
+      "examples": [
+        [
+          "title",
+          "body"
+        ],
+        [
+          "title title",
+          "timeline notes",
+          "timeline metrics"
+        ]
+      ]
+    },
+    "columns": {
+      "type": "array",
+      "minItems": 1,
+      "maxItems": 12,
+      "items": {
+        "type": "number",
+        "exclusiveMinimum": 0,
+        "maximum": 100
+      },
+      "description": "Relative column widths, one per cell of a row; the columns share the content width in proportion, separated by the gap. Omitted: all 1. Columns are numbers only.",
+      "examples": [
+        [
+          1,
+          1
+        ],
+        [
+          3,
+          2
+        ]
+      ]
+    },
+    "rows": {
+      "type": "array",
+      "minItems": 1,
+      "maxItems": 12,
+      "items": {
+        "oneOf": [
+          {
+            "type": "number",
+            "exclusiveMinimum": 0,
+            "maximum": 100
+          },
+          {
+            "const": "auto"
+          }
+        ]
+      },
+      "description": "Relative row heights, one per string of 'areas'. 'auto' is the height the row's content needs at the starting text size (at most half the content box; areas that span several rows do not size it); the numeric rows share the rest in proportion. An auto row whose areas are all empty has no height. Omitted: all 1.",
+      "examples": [
+        [
+          "auto",
+          1
+        ],
+        [
+          "auto",
+          1,
+          "auto"
+        ]
+      ]
+    },
+    "regions": {
+      "type": "object",
+      "propertyNames": {
+        "pattern": "^[a-z][a-z0-9-]*$"
+      },
+      "additionalProperties": {
+        "$ref": "#/$defs/Region"
+      },
+      "description": "One entry per body area, keyed by the area's name. Region names may not be 'title', 'subtitle', 'tag', 'auto' or one of the promoted-region words ('left', 'center', 'right', 'top', 'middle', 'bottom'), so a Markdown block's region= option stays unambiguous. Region rules the schema cannot express (an area without a region, a region without an area, a reserved name) are the validate finding opf/layout-region."
+    },
+    "overflowRegion": {
+      "type": "string",
+      "pattern": "^[a-z][a-z0-9-]*$",
+      "description": "The region where content that no region accepts goes, whatever its 'accepts', while it has room; content beyond every region's room is drawn there too, with the warning opf/layout-unplaced. Omitted: the first primary region (in reading order) whose flow is not 'none'."
     },
     "tags": {
       "type": "array",
@@ -6494,7 +6692,7 @@ var layout = {
           "format": "uri",
           "description": "Main preview image (PNG/JPG). Used as the primary visual in picker UIs and previews of the record.",
           "examples": [
-            "https://example.com/layouts/title-subtitle.png"
+            "https://example.com/layouts/cover.png"
           ]
         },
         "thumbnailSrc": {
@@ -6502,7 +6700,7 @@ var layout = {
           "format": "uri",
           "description": "Smaller thumbnail preview suited to dense grid views.",
           "examples": [
-            "https://example.com/layouts/title-subtitle.thumbnail.png"
+            "https://example.com/layouts/cover.thumbnail.png"
           ]
         },
         "vectorSrc": {
@@ -6510,254 +6708,115 @@ var layout = {
           "format": "uri",
           "description": "SVG / vector preview for crisp scaling at any size.",
           "examples": [
-            "https://www.pptx.gallery/layout-previews/title-subtitle.svg"
+            "https://www.pptx.gallery/layout-previews/cover.svg"
           ]
         }
       }
     },
     "composition": {
+      "type": "object",
+      "description": "Only 'gap', 'padding', 'minFontSize' and 'overflow', with their 0.18 meaning. A template's regions replace composition.mode, columns and weights.",
       "$ref": "#/$defs/Composition"
     }
   },
   "$defs": {
-    "PlaceholderEntry": {
-      "description": "One entry of a layout's placeholders: a region (Placeholder) or, when its type is 'group', a placeholder group (PlaceholderGroup).",
-      "if": {
-        "type": "object",
-        "required": [
-          "type"
-        ],
-        "properties": {
-          "type": {
-            "const": "group"
-          }
-        }
-      },
-      "then": {
-        "$ref": "#/$defs/PlaceholderGroup"
-      },
-      "else": {
-        "$ref": "#/$defs/Placeholder"
-      }
-    },
-    "PlaceholderGroup": {
+    "Region": {
       "type": "object",
       "additionalProperties": false,
       "required": [
-        "type",
-        "placeholders"
+        "accepts"
       ],
-      "description": "A placeholder group: regions arranged by their own composition inside one cell of the record's composition, the way a content group (a block with blocks) arranges its children. Slide content fills the group's leaf regions in reading order, as part of one flat sequence for the whole record. A group holds body regions and groups only (no title, subtitle or tag, and no placement), and groups nest at most three levels inside a record: this is the first. Groups draw nothing of their own and have no slide path; design.chartPrimary is shorthand for a record whose root holds the chart and one group of the other content.",
+      "description": "One body region of a layout: which content it takes and how several blocks share it.",
       "properties": {
-        "type": {
-          "const": "group",
-          "description": "Marks the entry as a placeholder group."
-        },
-        "composition": {
-          "$ref": "#/$defs/Composition",
-          "description": "How the group arranges its regions, with the semantics of a content group's composition: only minFontSize and overflow inherit from the enclosing composition; padding defaults to 0 and gap is a fraction of the group's short edge. Omitted, the group arranges its regions automatically."
-        },
-        "placeholders": {
-          "type": "array",
-          "minItems": 1,
-          "items": {
-            "$ref": "#/$defs/PlaceholderGroupEntry2"
-          },
-          "description": "The group's regions and nested groups, in reading order."
-        }
-      }
-    },
-    "PlaceholderGroupEntry2": {
-      "description": "An entry of a first-level group: a region (GroupedPlaceholder) or a second-level group (PlaceholderGroup2).",
-      "if": {
-        "type": "object",
-        "required": [
-          "type"
-        ],
-        "properties": {
-          "type": {
-            "const": "group"
-          }
-        }
-      },
-      "then": {
-        "$ref": "#/$defs/PlaceholderGroup2"
-      },
-      "else": {
-        "$ref": "#/$defs/GroupedPlaceholder"
-      }
-    },
-    "PlaceholderGroup2": {
-      "type": "object",
-      "additionalProperties": false,
-      "required": [
-        "type",
-        "placeholders"
-      ],
-      "description": "A placeholder group nested in another (the second level). Same fields as PlaceholderGroup.",
-      "properties": {
-        "type": {
-          "const": "group",
-          "description": "Marks the entry as a placeholder group."
-        },
-        "composition": {
-          "$ref": "#/$defs/Composition",
-          "description": "How the group arranges its regions; see PlaceholderGroup.composition."
-        },
-        "placeholders": {
+        "accepts": {
           "type": "array",
           "minItems": 1,
+          "uniqueItems": true,
           "items": {
-            "$ref": "#/$defs/PlaceholderGroupEntry3"
+            "type": "string",
+            "enum": [
+              "text",
+              "list",
+              "image",
+              "video",
+              "chart",
+              "table",
+              "code",
+              "metric",
+              "quote",
+              "timeline",
+              "group"
+            ]
           },
-          "description": "The group's regions and nested groups, in reading order."
-        }
-      }
-    },
-    "PlaceholderGroupEntry3": {
-      "description": "An entry of a second-level group: a region (GroupedPlaceholder) or a third-level group (PlaceholderGroup3).",
-      "if": {
-        "type": "object",
-        "required": [
-          "type"
-        ],
-        "properties": {
-          "type": {
-            "const": "group"
-          }
-        }
-      },
-      "then": {
-        "$ref": "#/$defs/PlaceholderGroup3"
-      },
-      "else": {
-        "$ref": "#/$defs/GroupedPlaceholder"
-      }
-    },
-    "PlaceholderGroup3": {
-      "type": "object",
-      "additionalProperties": false,
-      "required": [
-        "type",
-        "placeholders"
-      ],
-      "description": "The innermost placeholder group (the third level): it holds regions only, never another group.",
-      "properties": {
-        "type": {
-          "const": "group",
-          "description": "Marks the entry as a placeholder group."
-        },
-        "composition": {
-          "$ref": "#/$defs/Composition",
-          "description": "How the group arranges its regions; see PlaceholderGroup.composition."
+          "description": "Content kinds the region takes: the body content kinds, and 'group' for a content group of any content. A group is also accepted where every one of its leaf kinds is.",
+          "examples": [
+            [
+              "text",
+              "list"
+            ],
+            [
+              "image",
+              "video"
+            ]
+          ]
         },
-        "placeholders": {
-          "type": "array",
-          "minItems": 1,
-          "items": {
-            "$ref": "#/$defs/GroupedPlaceholder"
-          },
-          "description": "The group's regions, in reading order."
-        }
-      }
-    },
-    "GroupedPlaceholder": {
-      "type": "object",
-      "additionalProperties": false,
-      "required": [
-        "type"
-      ],
-      "description": "A region inside a placeholder group: a body content kind only. Headings ('title', 'subtitle', 'tag') stay at the record's top level, and only a top-level image placeholder may carry a placement.",
-      "properties": {
-        "type": {
+        "role": {
           "type": "string",
           "enum": [
-            "text",
-            "list",
-            "image",
-            "video",
-            "chart",
-            "table",
-            "code",
-            "metric",
-            "quote",
-            "timeline"
+            "primary",
+            "secondary",
+            "media",
+            "supporting"
           ],
-          "description": "The content kind of the region, from the one OPF content-kind vocabulary (see Placeholder.type)."
-        }
-      }
-    },
-    "Placeholder": {
-      "type": "object",
-      "required": [
-        "type"
-      ],
-      "description": "A single region inside a slide layout. Title, subtitle, and tag placeholders bind to the corresponding Slide fields; every other placeholder describes the content kind that region holds. The array order in the surrounding 'placeholders' field preserves layout region order.",
-      "if": {
-        "required": [
-          "placement"
-        ]
-      },
-      "then": {
-        "properties": {
-          "type": {
-            "const": "image"
-          }
-        }
-      },
-      "properties": {
-        "type": {
+          "description": "Which content the region wants first. Binding gives a picture (image, video) to a media region first, then primary, secondary, supporting; every other kind to a primary region first, then secondary, supporting, media; of two equal regions the first in reading order fills first. A supporting region receives content only when no primary or secondary region that accepts it has room, or by a pin. Default 'primary'."
+        },
+        "flow": {
           "type": "string",
           "enum": [
-            "title",
-            "subtitle",
-            "tag",
-            "text",
-            "list",
-            "image",
-            "video",
-            "chart",
-            "table",
-            "code",
-            "metric",
-            "quote",
-            "timeline"
+            "none",
+            "grid",
+            "column",
+            "auto"
           ],
-          "description": "The content kind of the region. This is the one OPF content-kind vocabulary: the same words name a slide's payload fields (text, items, image, video, chart, table, code, metric, quote, timeline). 'title', 'subtitle' and 'tag' are the heading kinds and bind to Slide.title, Slide.subtitle and Slide.tag. 'text' holds text and bullets; 'list' holds items. 'image' is filled by an image payload and 'video' by a video payload. 'metric', 'quote', 'timeline', 'chart', 'table' and 'code' are filled by the payload of the same name; a metric region shows the metric payload with its optional label, description, unit, delta, trend and sentiment."
+          "description": "How several blocks share the region: 'none' one block fills it; 'grid' by count (1 fills, 2 side by side, 3 in a row, 4 as 2 x 2, 5 as 3 + 2, 6 as 3 x 2, 7 to 12 in four columns; rows and columns swap in a portrait region; a short last row is centred); 'column' stacked with equal heights; 'auto' a grid when every block is short and a column when any block is long (more than 6 estimated lines in its grid cell at the starting size). design.contentDirection turns every flowing region into one row or one column. Default 'auto'."
         },
-        "placement": {
-          "$ref": "#/$defs/ImagePlacement",
-          "description": "Image placeholders only. Bleeds the slide's image for this region to one slide edge, as an image block's placement does: the n-th image placeholder (counting the image regions of placeholder groups too, in reading order) places the slide's n-th top-level image (Slide.image or an image block in blocks) unless that block sets its own placement. Only a top-level image placeholder may carry a placement; a region inside a placeholder group cannot bleed to a slide edge. The headings and the other content compose in the rest of the slide."
-        }
-      }
-    },
-    "ImagePlacement": {
-      "type": "object",
-      "additionalProperties": false,
-      "required": [
-        "edge"
-      ],
-      "description": "The same object as ImagePlacement in opf.schema.json: a band along one slide edge for the image, edge to edge, with the rest of the slide left to the headings and the other content.",
-      "properties": {
-        "edge": {
+        "max": {
+          "type": "integer",
+          "minimum": 1,
+          "maximum": 12,
+          "description": "Blocks the region holds on one slide. Default 1 for flow 'none' (which requires 1), else 6. Content beyond every region's room is drawn in the overflow region with the warning opf/layout-unplaced, and paginate moves it to a continuation slide."
+        },
+        "bleed": {
+          "type": "boolean",
+          "description": "The region's outer edges that lie on the content box's edge extend to the slide edge, as a placed image does. A bled region is never drawn as a card. Default false."
+        },
+        "listColumns": {
+          "oneOf": [
+            {
+              "const": "auto"
+            },
+            {
+              "const": 1
+            }
+          ],
+          "description": "'auto': a list in the region that does not fit its cell at the starting size (a lone list, or one of several blocks) flows into up to three columns before it shrinks, as a list payload's columns: 'auto'. Default 1."
+        },
+        "anchor": {
           "type": "string",
           "enum": [
-            "left",
-            "right",
             "top",
+            "middle",
             "bottom"
           ],
-          "description": "The slide edge the image bleeds to. In a right-to-left deck 'left' is the start side, drawn at the right."
-        },
-        "size": {
-          "type": "number",
-          "minimum": 0.1,
-          "maximum": 0.9,
-          "description": "Share of the slide width (left, right) or height (top, bottom) given to the band. Default 0.5."
+          "description": "Vertical position of the region's content when it is shorter than the region. Default 'top'."
         },
-        "inset": {
-          "type": "boolean",
-          "description": "Draw the frame inside the slide padding on every side of the band instead of edge to edge. Default false."
+        "empty": {
+          "type": "string",
+          "enum": [
+            "collapse",
+            "keep"
+          ],
+          "description": "What the region does on a slide that gives it no content: 'collapse' (default) joins its cells to a neighbouring area that shares the full length of one of its edges and is not itself empty; 'keep' leaves the space."
         }
       }
     },
@@ -6773,7 +6832,7 @@ var layout = {
             "center",
             "right"
           ],
-          "description": "Horizontal alignment of the title placeholder."
+          "description": "Horizontal alignment of the title heading area."
         },
         "contentAlignment": {
           "type": "string",
@@ -6794,7 +6853,7 @@ var layout = {
             "horizontal",
             "vertical"
           ],
-          "description": "Axis along which parallel body content is arranged: 'vertical' is a column, 'horizontal' a row. Composition applies it when neither the slide nor this layout's composition sets a mode, below the slide's and the deck's design.contentDirection and above automatic selection."
+          "description": "Axis along which parallel body content is arranged: 'vertical' is a column, 'horizontal' a row. On a layout slide it turns every flowing region into one row or one column; the slide's own composition.mode, columns and weights rank above it."
         },
         "chartPrimary": {
           "type": "string",
@@ -6805,7 +6864,7 @@ var layout = {
             "left",
             "right"
           ],
-          "description": "Where the primary chart sits relative to the other body content. Composition applies it below the slide's and the deck's design.chartPrimary, with the semantics described there. It is shorthand for a placeholder group: a record can state the same structure explicitly as a root row or column of the chart and one PlaceholderGroup of the other regions, weighted 3:2."
+          "description": "Where the primary chart sits relative to supporting content on automatic slides. Template layouts express this arrangement with their regions; chartPrimary does not override a template."
         },
         "imageFit": {
           "type": "string",
@@ -6823,30 +6882,18 @@ var layout = {
             "image"
           ],
           "description": "Marker style of lists: 'character' draws the glyph, 'image' draws the deck's icon logo as a picture bullet."
+        },
+        "mirror": {
+          "type": "boolean",
+          "description": "Draw the layout mirrored: each row's cells and the column sizes reversed, so a 'beside' layout puts its picture, chart or table at the end. Logical: a right-to-left deck mirrors on top. Binding and reading order do not change."
         }
       }
     },
     "Composition": {
       "type": "object",
       "additionalProperties": false,
-      "description": "Portable dynamic composition. Slide fields override the resolved layout. Nested groups (placeholder groups here, content groups in a slide) arrange their children independently, inheriting only minFontSize and overflow. Explicit promoted regions retain their positions.",
+      "description": "A template's composition: only gap, padding, minFontSize and overflow, with their 0.18 meaning. A slide's composition overrides them; a slide's composition.mode, columns and weights arrange its first primary flowing region.",
       "properties": {
-        "mode": {
-          "type": "string",
-          "enum": [
-            "auto",
-            "grid",
-            "row",
-            "column"
-          ],
-          "description": "auto chooses a grid from available space and content; grid uses columns; row and column use one horizontal or vertical track."
-        },
-        "columns": {
-          "type": "integer",
-          "minimum": 1,
-          "maximum": 12,
-          "description": "Column count for grid. In auto mode this caps the number of columns."
-        },
         "gap": {
           "type": "number",
           "minimum": 0,
@@ -6859,17 +6906,6 @@ var layout = {
           "maximum": 0.2,
           "description": "Inset as a fraction of the container short edge. Default 0.08 on a slide, 0 inside a group."
         },
-        "weights": {
-          "type": "array",
-          "minItems": 1,
-          "maxItems": 12,
-          "items": {
-            "type": "number",
-            "exclusiveMinimum": 0,
-            "maximum": 100
-          },
-          "description": "Relative track sizes: columns for row/grid/auto, rows for column. Omitted tracks have weight 1; extra weights are ignored."
-        },
         "minFontSize": {
           "type": "number",
           "minimum": 8,
@@ -6892,12 +6928,12 @@ 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: display metadata for chart pickers (name, group, expected series, complexity) and the Open XML mapping a picker can describe. One record per chart type that Aspose.Slides officially supports (see mappings.renderers["aspose-slides"].chartType), plus the column-and-line combination 'combo'. A document's chart.type is an engine vocabulary validated directly; engines never look a chart-type record up. pptx.gallery publishes these records and @openpresentation/opf/catalog ships them as catalogDisplay.chartTypes.`,
+  "description": `Schema for chart-type records: display metadata for chart pickers (name, group, expected series, complexity) and the Open XML mapping a picker can describe. One record per chart type that Aspose.Slides officially supports (see mappings.renderers["aspose-slides"].chartType), plus the column-and-line combination 'combo'. A document's chart.type is an engine vocabulary validated directly; engines never look a chart-type record up. pptx.gallery publishes these records and @openpresentation/gallery ships them as catalogDisplay.chartTypes.`,
   "type": "object",
   "additionalProperties": false,
   "patternProperties": {
     "^x-": {
-      "description": "Publisher extension member, such as the `x-gallery` presentation metadata that pptx.gallery adds to the records it publishes. Engines and validators ignore top-level `x-*` members, and the pinned snapshot in spec/catalogs never carries them."
+      "description": "Publisher extension member, such as the `x-gallery` presentation metadata that pptx.gallery adds to the records it publishes. Engines and validators ignore top-level `x-*` members, and the pinned snapshot in @openpresentation/gallery never carries them."
     }
   },
   "required": [
@@ -7370,7 +7406,7 @@ var socialPlatform = {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "$id": "https://openpresentation.org/schema/opf-social-platform/v1",
   "title": "Social Platform",
-  "description": "Schema for social-platform records: display metadata for authoring UIs (name, brand color, handle example) alongside the URL patterns. The keys of a Socials object are an engine vocabulary validated directly; engines link a handle with the patterns in spec/reference/engine-vocabularies.json and never look a social-platform record up. pptx.gallery publishes these records and @openpresentation/opf/catalog ships them as catalogDisplay.socialPlatforms.",
+  "description": "Schema for social-platform records: display metadata for authoring UIs (name, brand color, handle example) alongside the URL patterns. The keys of a Socials object are an engine vocabulary validated directly; engines link a handle with the patterns in spec/reference/engine-vocabularies.json and never look a social-platform record up. pptx.gallery publishes these records and @openpresentation/gallery ships them as catalogDisplay.socialPlatforms.",
   "type": "object",
   "required": [
     "$schema",
@@ -7544,7 +7580,7 @@ var language = {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "$id": "https://openpresentation.org/schema/opf-language/v1",
   "title": "Language",
-  "description": "Schema for language records: display metadata for the language pickers of authoring tools (name, ISO code, the default font schemes a picker suggests). The document's 'language' is an engine vocabulary, a BCP-47 tag validated directly; engines never look a language record up, and their script, direction, OOXML tag and default script fonts come from spec/reference/engine-vocabularies.json. pptx.gallery publishes these records and @openpresentation/opf/catalog ships them as catalogDisplay.languages.",
+  "description": "Schema for language records: display metadata for the language pickers of authoring tools (name, ISO code, the default font schemes a picker suggests). The document's 'language' is an engine vocabulary, a BCP-47 tag validated directly; engines never look a language record up, and their script, direction, OOXML tag and default script fonts come from spec/reference/engine-vocabularies.json. pptx.gallery publishes these records and @openpresentation/gallery ships them as catalogDisplay.languages.",
   "type": "object",
   "required": [
     "$schema",