@openpresentation/opf 0.15.1 → 0.17.0

package/dist/spec/schemas/opf.schema.json

@@ -36,7 +36,7 @@
           "minItems": 1
         }
       ],
-      "description": "Organization associated with the presentation, usually the presenting company. Array form supports hosts, partners, clients, and sponsors. The primary organization (Organization.role 'primary', else the first item) supplies the default deck logo, the 'organization' and 'socials' header/footer fields and the 'organization.<field>' built-in variables; the others are available by id as 'organization.<id>.<field>' and are not drawn automatically."
+      "description": "Organization associated with the presentation, usually the presenting company. Array form supports hosts, partners, clients, and sponsors. The primary organization (Organization.role 'primary', else the first item) supplies the default deck logo, the 'socials' header/footer field and the 'organization.<field>' built-in variables; the others are available by id as 'organization.<id>.<field>' and are not drawn automatically."
     },
     "speaker": {
       "oneOf": [
@@ -47,7 +47,7 @@
           "minItems": 1
         }
       ],
-      "description": "Person presenting the deck. Array form supports panels and multi-speaker decks. The first speaker is the primary speaker: the built-in variables 'speaker.<field>' and the 'speaker' header/footer field read it, 'speakers' lists every name, and 'speaker.<id>.<field>' addresses one by id. A speaker is drawn nowhere else."
+      "description": "Person presenting the deck. Array form supports panels and multi-speaker decks. The first speaker is the primary speaker: the built-in variables 'speaker.<field>' read it, 'speakers' lists every name, and 'speaker.<id>.<field>' addresses one by id. A speaker is drawn nowhere else."
     },
     "author": {
       "oneOf": [
@@ -494,7 +494,7 @@
     },
     "Organization": {
       "type": "object",
-      "description": "An organization associated with the presentation, typically the presenting company, but also hosts, partners, clients, or sponsors. The primary organization (role 'primary', else the first one) supplies the default deck logo (unless design.logo overrides it), the 'organization' header/footer field (its name) and the 'socials' field (its socials). Every field is also a built-in variable ('{{organization.name}}', 'var:organization.logo', 'organization.<id>.<field>'). Nothing else about an organization is drawn automatically. See docs/templates-and-variables.md.",
+      "description": "An organization associated with the presentation, typically the presenting company, but also hosts, partners, clients, or sponsors. The primary organization (role 'primary', else the first one) supplies the default deck logo (unless design.logo overrides it) and the 'socials' header/footer field (its socials). Every field is also a built-in variable ('{{organization.name}}', 'var:organization.logo', 'organization.<id>.<field>'). Nothing else about an organization is drawn automatically. See docs/templates-and-variables.md.",
       "required": ["id", "name"],
       "properties": {
         "id": {
@@ -505,7 +505,7 @@
         },
         "name": {
           "type": "string",
-          "description": "Display name. Drawn by the 'organization' header/footer field for the primary organization; the built-in variable 'organization.name' (or 'organization.<id>.name') carries it into any string.",
+          "description": "Display name. The built-in variable 'organization.name' (primary organization) or 'organization.<id>.name' carries it into any string, such as a header or footer text of '{{organization.name}}'.",
           "examples": ["Acme Corp", "DevConf 2026", "Beta Industries"]
         },
         "legalName": {
@@ -547,7 +547,7 @@
         "role": {
           "type": "string",
           "enum": ["primary", "partner", "client", "sponsor", "host"],
-          "description": "Role of the organization relative to the presentation. Only 'primary' has behavior: it selects the primary organization (deck logo, 'organization' and 'socials' header/footer fields, and the 'organization.<field>' built-ins). When no organization has role 'primary', the first one is primary. 'partner', 'client', 'sponsor' and 'host' are descriptive labels that change nothing."
+          "description": "Role of the organization relative to the presentation. Only 'primary' has behavior: it selects the primary organization (deck logo, the 'socials' header/footer field, and the 'organization.<field>' built-ins). When no organization has role 'primary', the first one is primary. 'partner', 'client', 'sponsor' and 'host' are descriptive labels that change nothing."
         },
         "socials": {
           "$ref": "#/$defs/Socials",
@@ -557,7 +557,7 @@
     },
     "Speaker": {
       "type": "object",
-      "description": "A person presenting the deck. A speaker is drawn only through built-in variables ('{{speaker.name}}' inside any string, 'var:speaker.photo' as a whole image field) and the 'speaker' header/footer field (the first speaker's name and title). No layout, cover or bio slide places a speaker on its own. See docs/templates-and-variables.md.",
+      "description": "A person presenting the deck. A speaker is drawn only through built-in variables ('{{speaker.name}}' inside any string, a header or footer text included, and 'var:speaker.photo' as a whole image field). No layout, cover or bio slide places a speaker on its own. See docs/templates-and-variables.md.",
       "required": ["id", "name"],
       "properties": {
         "id": {
@@ -568,12 +568,12 @@
         },
         "name": {
           "type": "string",
-          "description": "Display name. Built-in variable 'speaker.name' (first speaker) or 'speaker.<id>.name'; the first speaker's name is also drawn by the 'speaker' header/footer field and every name is listed by 'speakers'.",
+          "description": "Display name. Built-in variable 'speaker.name' (first speaker) or 'speaker.<id>.name'; every name is listed by 'speakers'.",
           "examples": ["Alice Chen", "Bob Lee", "Dr. Carla Diaz"]
         },
         "title": {
           "type": "string",
-          "description": "Role or title. Built-in variable 'speaker.title'; the 'speaker' header/footer field draws it after the name ('Alice Chen, VP of Engineering').",
+          "description": "Role or title. Built-in variable 'speaker.title' (or 'speaker.<id>.title'), for example in a footer text of '{{speaker.name}}, {{speaker.title}}'.",
           "examples": ["VP of Engineering", "Founder & CEO", "Chief Product Officer", "Senior Staff Engineer"]
         },
         "photo": {
@@ -715,7 +715,7 @@
             { "$ref": "#/$defs/HeaderFooter" }
           ],
           "description": "Repeated header furniture rendered outside the main slide content. Use false to suppress an inherited header.",
-          "examples": [false, { "left": { "section": true }, "right": { "image": "asset:acme-logo" } }]
+          "examples": [false, { "left": { "text": "{{slide.section}}" }, "right": { "image": "asset:acme-logo" } }]
         },
         "footer": {
           "oneOf": [
@@ -725,7 +725,7 @@
           "description": "Repeated footer furniture rendered outside the main slide content. Use false to suppress an inherited footer.",
           "examples": [
             false,
-            { "left": { "image": "asset:acme-logo" }, "center": { "text": "Confidential" }, "right": { "slideNumber": true } }
+            { "left": { "image": "asset:acme-logo" }, "center": { "text": "Confidential" }, "right": { "text": "{{slide.number}}" } }
           ]
         },
         "titleAlignment": {
@@ -750,7 +750,7 @@
         "chartPrimary": {
           "type": "string",
           "enum": ["none", "top", "bottom", "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."
+          "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."
         },
         "imageFit": {
           "type": "string",
@@ -1027,7 +1027,7 @@
       "additionalProperties": {
         "$ref": "#/$defs/Variable"
       },
-      "description": "Named variables, keyed by stable kebab-case id. A variable is a typed, named value the deck declares once and uses in many places: a color ('var:<id>' in color fields, the original use), or content that fills a template (text, number, date, image, url, list). Content is referenced inline as '{{<id>}}' inside any string, or whole as 'var:<id>' in a field of the matching type; '\\{{' writes a literal '{{'. A hex string is shorthand for a color variable. A variable with no 'value' is unfilled: expected in a template (root 'template': true), an error in a normal deck. Engines resolve variables with resolveVariables() before composing, rendering or exporting, so a template plus its values previews and exports exactly like the equivalent hand-written deck. Read-only built-in variables come from the deck's own metadata and use dotted names that a user id can never take: 'deck.name', 'deck.description', 'deck.author', 'speaker.name|title|email|phone|bio|photo' (first speaker), 'speakers' (every speaker's name, a list), 'organization.name|legalName|tagline|domain|email|phone|logo' (primary organization), and 'speaker.<id>.<field>' / 'organization.<id>.<field>' by id. They are written the same two ways ('{{speaker.name}}', 'var:speaker.photo'), are never declared, and an unknown built-in path is a validation error; a known one with no source value resolves to nothing with a warning. The id 'speakers' is reserved. See docs/templates-and-variables.md.",
+      "description": "Named variables, keyed by stable kebab-case id. A variable is a typed, named value the deck declares once and uses in many places: a color ('var:<id>' in color fields, the original use), or content that fills a template (text, number, date, image, url, list). Content is referenced inline as '{{<id>}}' inside any string, or whole as 'var:<id>' in a field of the matching type; '\\{{' writes a literal '{{'. A hex string is shorthand for a color variable. A variable with no 'value' is unfilled: expected in a template (root 'template': true), an error in a normal deck. Engines resolve variables with resolveVariables() before composing, rendering or exporting, so a template plus its values previews and exports exactly like the equivalent hand-written deck. Read-only built-in variables come from the deck's own metadata and use dotted names that a user id can never take: 'deck.name', 'deck.description', 'deck.author', 'speaker.name|title|email|phone|bio|photo' (first speaker), 'speakers' (every speaker's name, a list), 'organization.name|legalName|tagline|domain|email|phone|logo' (primary organization), and 'speaker.<id>.<field>' / 'organization.<id>.<field>' by id. They are written the same two ways ('{{speaker.name}}', 'var:speaker.photo'), are never declared, and an unknown built-in path is a validation error; a known one with no source value resolves to nothing with a warning. The id 'speakers' is reserved. Three built-ins are slide-scoped and written only as inline tokens: '{{slide.number}}' (the displayed slide number after pagination), '{{slide.section}}' (the slide's section) and '{{deck.slideCount}}' (the number of slides after pagination). resolveVariables() leaves them as written; they resolve per slide as it is composed (resolveSlideVariables(), and header/footer text in layoutFurniture()), so every 'slide.' name is reserved and 'var:slide.*' or 'var:deck.slideCount' is a validation error. See docs/templates-and-variables.md.",
       "examples": [
         {
           "risk": "#B42318",
@@ -1835,7 +1835,8 @@
     },
     "HeaderFooterItem": {
       "type": "object",
-      "description": "One header/footer zone. Every configured field renders; fields in one zone stack top to bottom in the order logo, image, text, organization, speaker, socials, section, slide number, date. Put a date and a slide number in different zones to keep each on the zone's single line.",
+      "description": "One header/footer zone. Every configured field renders; fields in one zone stack top to bottom in the order logo, image, text, socials, date. Generated values such as the slide number, the slide count, the section, the organization or the speaker are variables inside text ('{{slide.number}} / {{deck.slideCount}}', '{{organization.name}}'), so one text writes several values in the author's order; a line break is '\\n'. Put a date and a slide number in different zones to keep each on the zone's single line. See docs/templates-and-variables.md.",
+      "additionalProperties": false,
       "properties": {
         "logo": {
           "type": "boolean",
@@ -1843,24 +1844,14 @@
         },
         "text": {
           "type": "string",
-          "description": "Literal text rendered in this zone.",
-          "examples": ["Confidential", "Q4 Business Review"]
+          "description": "Text rendered in this zone. Variables resolve inside it like any string: deck-wide ones ('{{organization.name}}', '{{speaker.name}}, {{speaker.title}}', '{{customer}}') before composition, and the slide-scoped built-ins '{{slide.number}}', '{{slide.section}}' and '{{deck.slideCount}}' for each slide as it is laid out. Each '{{slide.number}}' is a live slide-number field: PPTX export writes it as a native field when its value fits within one accepted text line, and as static text with a diagnostic otherwise. '{{deck.slideCount}}' is fixed text, because PowerPoint has no slide-count field. Write '\\{{' for literal braces.",
+          "examples": ["Confidential", "Q4 Business Review", "{{slide.number}} / {{deck.slideCount}}", "{{organization.name}}\n{{slide.section}}"]
         },
         "image": {
           "$ref": "#/$defs/Asset",
           "description": "Generic image rendered in this zone, such as a logo, partner mark, certification badge, or icon.",
           "examples": ["asset:acme-logo", "./assets/footer-badge.svg"]
         },
-        "slideNumber": {
-          "type": "boolean",
-          "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": [
             { "type": "boolean" },
@@ -1875,18 +1866,6 @@
           "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",
-          "description": "Whether to render the primary organization's name from organization (role 'primary', else the first organization)."
-        },
-        "speaker": {
-          "type": "boolean",
-          "description": "Whether to render the primary (first) speaker's name and title from speaker, joined as 'Ada Lovelace, CTO' (just the name when the speaker has no title). It is generated text: without a named speaker the engine reports unresolved-content at this field. PPTX export writes it as static text and import restores the flag from the file's furniture provenance."
-        },
-        "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."
@@ -1969,12 +1948,12 @@
         "items": {
           "type": "array",
           "items": { "$ref": "#/$defs/ListItem" },
-          "description": "Full-slide generic list payload. Presence of this field infers type 'list'. At slide root, multiple content payload kinds with no explicit type, blocks, or regions are accepted as shorthand for layout-agnostic blocks."
+          "description": "Full-slide structured list payload. Presence of this field infers type 'list'. Entries are strings, TextRun[] or objects with `text`, optional `description` (supporting detail under the entry), `level` and `start`. Use `items` when entries share a shape (features, steps, options, risks) or any entry needs a `description`; use `bullets` for plain talking points. Both draw the same marker, nesting and numbering; they differ in the inferred kind and in `description`, which only `items` accepts. At slide root, multiple content payload kinds with no explicit type, blocks, or regions are accepted as shorthand for layout-agnostic blocks, so `items` next to `text` or `bullets` composes as separate blocks side by side."
         },
         "bullets": {
           "type": "array",
           "items": { "$ref": "#/$defs/BulletItem" },
-          "description": "Full-slide text-style bullet payload. Presence of this field infers type 'text'."
+          "description": "Full-slide prose bullet payload: short talking points, each standing alone. Presence of this field infers type 'text', so it may sit beside `text` in one payload. Entries are strings, TextRun[] or objects with `text`, `level` and `start`; there is no `description` (use `items` for entries with supporting detail)."
         },
         "numbering": {
           "$ref": "#/$defs/NumberingSpec",
@@ -2187,7 +2166,7 @@
         },
         "section": {
           "type": "string",
-          "description": "PowerPoint-style slide section label. Consecutive slides with the same value belong to the same section in presenter view, outlines, and PowerPoint section-aware exports.",
+          "description": "PowerPoint-style slide section label. Consecutive slides with the same value belong to the same section in presenter view, outlines, and PowerPoint section-aware exports. Also the slide-scoped built-in variable '{{slide.section}}', for example in a header text.",
           "examples": ["Intro", "Problem", "Solution", "Ask", "Appendix"]
         },
         "hidden": {
@@ -2244,7 +2223,7 @@
         "items": {
           "type": "array",
           "items": { "$ref": "#/$defs/ListItem" },
-          "description": "Generic list payload. Each item is either a plain string, a TextRun[] rich text sequence, or a ListItem object. List nesting uses item.level rather than nested content payloads.",
+          "description": "Structured list payload (type 'list'). Each item is either a plain string, a TextRun[] rich text sequence, or a ListItem object with optional `description`. List nesting uses item.level rather than nested content payloads. Use `items` when entries share a shape or any entry needs a `description`; use `bullets` for plain talking points. Both draw the same marker, nesting and numbering. A block or region holds `items` or `bullets`, never both, and `items` cannot sit beside `text`.",
           "examples": [[
             "Sub-second agent latency",
             ["Drop-in compatible with ", { "text": "OpenAI tool-calling", "bold": true }],
@@ -2257,7 +2236,7 @@
         "bullets": {
           "type": "array",
           "items": { "$ref": "#/$defs/BulletItem" },
-          "description": "Text-style bullet payload. Presence of this field infers type 'text'.",
+          "description": "Prose bullet payload: short talking points, each standing alone. Presence of this field infers type 'text', so it may sit beside `text` in one payload. Entries have no `description`; use `items` for entries with supporting detail.",
           "examples": [["Sub-second agent latency", "Drop-in compatible with OpenAI tool-calling", "SOC 2 Type II"]]
         },
         "numbering": {
@@ -3313,6 +3292,11 @@
         "fields": {
           "$ref": "#/$defs/DatasetFields",
           "description": "Dataset tables only: the dataset columns to show, by name and in order. Absent shows every column. An unknown name is a 'dataset-field-unknown' error."
+        },
+        "alt": {
+          "type": "string",
+          "description": "Text alternative for the table: what it shows (the point and the key numbers), not 'a table'. The preview exposes it as the table's accessible name (role group with aria-label; the cells stay readable) and the PowerPoint export writes it as the table frame's alternative text (descr); import reads it back. An empty string hides a purely decorative table, with the same meaning as an empty Asset alt. The alt is a summary read before the cells, which stay readable, so it is most useful for a large or dense table; validate does not require one and does not report a missing one.",
+          "examples": ["North America grew 46% to $18.1M in Q4, ahead of EMEA at 40%."]
         }
       }
     },
@@ -3849,7 +3833,7 @@
     "Composition": {
       "type": "object",
       "additionalProperties": false,
-      "description": "Portable dynamic composition. Slide fields override the resolved layout. Nested groups arrange their children independently, inheriting only minFontSize and overflow. Explicit promoted regions retain their positions.",
+      "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.",
       "properties": {
         "mode": {
           "type": "string",

package/dist/types.d.ts

@@ -1,7 +1,7 @@
-export { P as Presentation } from './presentation-CDKQVkyI.js';
-export { C as CatalogKind } from './catalog-refs-BSfGELpt.js';
+export { P as Presentation } from './presentation-fb8CZmRq.js';
+export { c as CatalogKind } from './catalog-refs-C4K4y-vh.js';
 export { SchemaName } from './schemas.js';
-export { a as Finding, d as FindingCategory, e as FindingFix, f as FindingFocus, b as FindingLocation, F as FindingReport, c as FindingSeverity, g as FindingSuggestion, J as JsonPatchOperation, V as ValidationIssue } from './finding-CT_f_vbD.js';
+export { F as Finding, a as FindingCategory, b as FindingFix, c as FindingFocus, d as FindingLocation, e as FindingReport, f as FindingSeverity, g as FindingSuggestion, J as JsonPatchOperation, V as ValidationIssue } from './finding-CDQ_wH8j.js';
 import './json-BFSdESOE.js';
 
 /**
@@ -326,9 +326,9 @@ interface Layout {
     description?: string;
     design?: DesignHints;
     /**
-     * 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), 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. Slide content itself lives either in root payload fields or promoted region keys on Slide. Chrome (slide number, footer, date) is not included here; it is owned by Design.header / Design.footer.
+     * 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.
      */
-    placeholders?: Placeholder[];
+    placeholders?: PlaceholderEntry[];
     /**
      * Free-form labels for filtering and search.
      */
@@ -375,7 +375,7 @@ interface DesignHints {
      */
     contentDirection?: ("horizontal" | "vertical");
     /**
-     * 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.
+     * 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.
      */
     chartPrimary?: ("none" | "top" | "bottom" | "left" | "right");
     /**
@@ -388,38 +388,16 @@ interface DesignHints {
     listBullet?: ("character" | "image");
 }
 /**
- * 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.
+ * One entry of a layout's placeholders: a region (Placeholder) or, when its type is 'group', a placeholder group (PlaceholderGroup).
  *
  * This interface was referenced by `Layout`'s JSON-Schema
- * via the `definition` "Placeholder".
+ * via the `definition` "PlaceholderEntry".
  */
-interface Placeholder {
-    /**
-     * 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.
-     */
-    type: ("title" | "subtitle" | "tag" | "text" | "list" | "image" | "video" | "chart" | "table" | "code" | "metric" | "quote" | "timeline");
-    placement?: ImagePlacement;
+interface PlaceholderEntry {
     [k: string]: unknown;
 }
 /**
- * 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 places the slide's n-th top-level image (Slide.image or an image block in blocks) unless that block sets its own placement. The headings and the other content compose in the rest of the slide.
- */
-interface ImagePlacement {
-    /**
-     * The slide edge the image bleeds to. In a right-to-left deck 'left' is the start side, drawn at the right.
-     */
-    edge: ("left" | "right" | "top" | "bottom");
-    /**
-     * Share of the slide width (left, right) or height (top, bottom) given to the band. Default 0.5.
-     */
-    size?: number;
-    /**
-     * Draw the frame inside the slide padding on every side of the band instead of edge to edge. Default false.
-     */
-    inset?: boolean;
-}
-/**
- * Portable dynamic composition. Slide fields override the resolved layout. Nested groups arrange their children independently, inheriting only minFontSize and overflow. Explicit promoted regions retain their positions.
+ * 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.
  *
  * This interface was referenced by `Layout`'s JSON-Schema
  * via the `definition` "Composition".

package/dist/{validation-types-BOcY9GTs.d.ts → validation-types-iZbXfES6.d.ts}

@@ -1,6 +1,6 @@
-import { a as Catalog } from './catalog-refs-BSfGELpt.js';
-import { T as TextMeasurement } from './composition-D2tghM82.js';
-import { c as FindingSeverity, F as FindingReport } from './finding-CT_f_vbD.js';
+import { b as Catalog } from './catalog-refs-C4K4y-vh.js';
+import { T as TextMeasurement } from './composition-BbZ_9C-c.js';
+import { f as FindingSeverity, e as FindingReport } from './finding-CDQ_wH8j.js';
 import { J as JsonPrimitive } from './json-BFSdESOE.js';
 
 /**
@@ -134,9 +134,18 @@ interface BuiltinVariableInfo {
     kind: VariableKind;
     /** Short label for pickers, such as "Speaker name". */
     label: string;
-    /** The value the document gives it, when it has one (a string, an Asset or the list of names). */
+    /**
+     * `deck` for a value read once from the document; `slide` for `slide.number`, `slide.section` and
+     * `deck.slideCount`, which vary per slide and resolve as each slide is composed (inline tokens only).
+     */
+    scope: "deck" | "slide";
+    /** The value the document gives it, when it has one (a string, an Asset or the list of names). Never set for a slide-scoped built-in. */
     value?: unknown;
-    /** True when the document has a source value for it. Unavailable built-ins resolve to nothing. */
+    /**
+     * True when the document has a source value for it. Unavailable built-ins resolve to nothing. A slide-scoped
+     * built-in is available when every slide gives it a value: always for `slide.number` and `deck.slideCount`, and
+     * for `slide.section` when at least one slide has a section.
+     */
     available: boolean;
     /** Every place the document uses it. */
     uses: VariableUse[];
@@ -144,7 +153,8 @@ interface BuiltinVariableInfo {
 /**
  * The built-in variables of a deck, for pickers and agents: the generic names (`deck.*`, `speaker.*`, `speakers`,
  * `organization.*`) first, then the id-addressed ones (`speaker.<id>.*`, `organization.<id>.*`) of each speaker and
- * organization that has an id. Each carries its kind, current source value and where the document uses it.
+ * organization that has an id, then the slide-scoped `slide.number`, `slide.section` and `deck.slideCount` (scope
+ * `slide`, no value). Each carries its kind, current source value and where the document uses it.
  */
 declare function listBuiltinVariables(presentation: unknown): BuiltinVariableInfo[];
 
@@ -203,7 +213,8 @@ interface Contract {
 /**
  * What the layout rules read from a fonts handle (the object `loadFonts()` of the renderer returns): the host's
  * measured text widths. Without one, composition uses core's portable estimate. A function receives the zero-based
- * slide index, so a host can supply a script-aware measurement per slide.
+ * slide index, so a host can supply a script-aware measurement per slide. A measurement with `forScripts` (a script
+ * planner, such as the renderer's) is asked for each slide's script-aware measurement, the one the engines measure with.
  */
 interface ValidateFonts {
     textMeasurement?: TextMeasurement | ((slideIndex: number) => TextMeasurement | undefined);
@@ -273,4 +284,4 @@ interface ValidationReport extends FindingReport {
     unfilledVariables?: string[];
 }
 
-export { variableDeclarations as A, type BuiltinVariableInfo as B, type Contract as C, DEFAULT_VARIABLE_DATE_FORMAT as D, OPFVariableError as O, type ResolveVariablesOptions as R, type ValidateOptions as V, type ValidationReport as a, type ResolveVariablesResult as b, VARIABLE_KINDS as c, type ValidateFonts as d, type ValidationCategory as e, type ValidationChecks as f, type ValidationRuleCost as g, type ValidationRuleInfo as h, type ValidationThresholds as i, type VariableDeclaration as j, type VariableDiagnostic as k, type VariableDiagnosticCode as l, type VariableDiagnosticSeverity as m, type VariableInfo as n, type VariableKind as o, type VariableUse as p, type VariableUseForm as q, type VariableValues as r, coerceVariableValue as s, formatVariableNumber as t, hasContentVariables as u, isTemplate as v, listBuiltinVariables as w, listVariables as x, resolveVariables as y, validationCategories as z };
+export { variableDeclarations as A, type BuiltinVariableInfo as B, type Contract as C, DEFAULT_VARIABLE_DATE_FORMAT as D, OPFVariableError as O, type ResolveVariablesOptions as R, VARIABLE_KINDS as V, type ResolveVariablesResult as a, type ValidateFonts as b, type ValidateOptions as c, type ValidationCategory as d, type ValidationChecks as e, type ValidationReport as f, type ValidationRuleCost as g, type ValidationRuleInfo as h, type ValidationThresholds as i, type VariableDeclaration as j, type VariableDiagnostic as k, type VariableDiagnosticCode as l, type VariableDiagnosticSeverity as m, type VariableInfo as n, type VariableKind as o, type VariableUse as p, type VariableUseForm as q, type VariableValues as r, coerceVariableValue as s, formatVariableNumber as t, hasContentVariables as u, isTemplate as v, listBuiltinVariables as w, listVariables as x, resolveVariables as y, validationCategories as z };

package/dist/validator.d.ts

@@ -1,13 +1,13 @@
-import { a as CatalogRecordKind } from './catalog-schemas-CinPh5WA.js';
-import { a as Finding } from './finding-CT_f_vbD.js';
-import { P as Presentation } from './presentation-CDKQVkyI.js';
-import { i as ValidationThresholds, h as ValidationRuleInfo, a as ValidationReport, V as ValidateOptions } from './validation-types-BOcY9GTs.js';
-export { C as Contract, d as ValidateFonts, e as ValidationCategory, f as ValidationChecks, g as ValidationRuleCost, z as validationCategories } from './validation-types-BOcY9GTs.js';
-import './catalog-refs-BSfGELpt.js';
+import { a as CatalogRecordKind } from './catalog-schemas-g7RFQBdc.js';
+import { F as Finding } from './finding-CDQ_wH8j.js';
+import { P as Presentation } from './presentation-fb8CZmRq.js';
+import { i as ValidationThresholds, h as ValidationRuleInfo, f as ValidationReport, c as ValidateOptions } from './validation-types-iZbXfES6.js';
+export { C as Contract, b as ValidateFonts, d as ValidationCategory, e as ValidationChecks, g as ValidationRuleCost, z as validationCategories } from './validation-types-iZbXfES6.js';
+import './catalog-refs-C4K4y-vh.js';
 import './schemas.js';
 import './json-BFSdESOE.js';
-import './composition-D2tghM82.js';
-import './chart-data-BnNqgnC-.js';
+import './composition-BbZ_9C-c.js';
+import './chart-data-DTxdRRT1.js';
 
 /**
  * The series palette opf-render and opf-pptx draw charts with (`CHART_COLORS`), in series order. A host with

package/dist/validator.js

@@ -1,5 +1,5 @@
-export { DEFAULT_CHART_PALETTE, DEFAULT_VALIDATION_THRESHOLDS, OPFValidationError, assertValid, assertValidCatalogRecord, findValidationRule, validate, validateCatalogRecord, validationCategories, validationRules } from './chunk-QDI75P2M.js';
-export { promotedRegionKeys } from './chunk-O744SXXA.js';
+export { DEFAULT_CHART_PALETTE, DEFAULT_VALIDATION_THRESHOLDS, OPFValidationError, assertValid, assertValidCatalogRecord, findValidationRule, validate, validateCatalogRecord, validationCategories, validationRules } from './chunk-NLNYNBTS.js';
+export { promotedRegionKeys } from './chunk-CW7GEAV3.js';
 import './chunk-TRDXRRQK.js';
 import './chunk-SPFV27O5.js';
-import './chunk-2CJPC4HI.js';
+import './chunk-RA64UQKI.js';

package/dist/yaml.d.ts

@@ -1,9 +1,9 @@
-import { a as Catalog } from './catalog-refs-BSfGELpt.js';
-import { P as Presentation } from './presentation-CDKQVkyI.js';
-import { V as ValidateOptions, a as ValidationReport } from './validation-types-BOcY9GTs.js';
-import { a as Finding, b as FindingLocation } from './finding-CT_f_vbD.js';
-import './composition-D2tghM82.js';
-import './chart-data-BnNqgnC-.js';
+import { b as Catalog } from './catalog-refs-C4K4y-vh.js';
+import { P as Presentation } from './presentation-fb8CZmRq.js';
+import { c as ValidateOptions, f as ValidationReport } from './validation-types-iZbXfES6.js';
+import { F as Finding, d as FindingLocation } from './finding-CDQ_wH8j.js';
+import './composition-BbZ_9C-c.js';
+import './chart-data-DTxdRRT1.js';
 import './json-BFSdESOE.js';
 
 /** A finding located in the YAML source: `yaml/<rule>` syntax and dialect errors (category `format`) and the OPF findings of the parsed deck. */