@openpresentation/opf 0.1.0 → 0.2.2

package/dist/schemas.d.ts

@@ -1,8 +1,8 @@
 declare const presentation: {
     readonly $schema: "https://json-schema.org/draft/2020-12/schema";
     readonly $id: "https://openpresentation.org/schema/opf/v1";
-    readonly title: "OPF — Open Presentation Format";
-    readonly description: "Open-source JSON format for describing PowerPoint presentations. Agents describe narratives, content, audience, reusable assets, and design — the engine handles OOXML complexity.\n\nFields that reference catalog records (narrative, language, tone, audience, purpose, design.theme / design.theme.id, design.colorScheme / design.colorScheme.id, design.fontScheme / design.fontScheme.id, Slide.layout, Chart.type, Organization.socials / Speaker.socials) resolve through the catalog system: inline 'catalogs.<kind>.records[]' on the document → 'catalogs.<kind>.source' on the document → engine defaults → the default catalog at https://www.pptx.gallery/<kind>. Every reference resolves to the catalog record's 'id' field. When an OPF document omits a reference entirely, the engine falls back to engine defaults (see /spec/reference/engine-defaults.json for a reference example). The defaults file is engine configuration; it is not part of the OPF document contract and has no JSON Schema.\n\nMost catalog references accept the bare 'id' as a string for the common case (e.g. narrative = 'classic-story', design.colorScheme = 'cool-horizon'). Audience, purpose, tone, design, and language object forms use 'id' as a base catalog reference plus inline overrides. Asset references use 'asset:<id>' strings that point into the top-level assets registry.";
+    readonly title: "Presentation";
+    readonly description: "Open-source JSON format for describing PowerPoint presentations. Agents describe narratives, content, audience, reusable assets, and design — the engine handles OOXML complexity.\n\nFields that reference catalog records (narrative, language, tone, audience, purpose, design.theme / design.theme.id, design.colorScheme / design.colorScheme.id, design.fontScheme / design.fontScheme.id, Slide.layout, Chart.type, Organization.socials / Speaker.socials) resolve through the catalog system: inline 'catalogs.<kind>.records[]' on the document → 'catalogs.<kind>.source' on the document → engine defaults → the default catalog at https://www.pptx.gallery/<kind>. Every reference resolves to the catalog record's 'id' field. When an OPF document omits a reference entirely, the engine falls back to engine defaults (see /spec/reference/engine-defaults.json for a reference example). The defaults file is engine configuration; it is not part of the OPF document contract and has no JSON Schema.\n\nMost catalog references accept the bare 'id' as a string for the common case (e.g. narrative = 'classic-story', design.colorScheme = 'cool-horizon'). Audience, purpose, tone, design, and language object forms use 'id' as a base catalog reference plus inline overrides. Asset references use 'asset:<id>' strings that point into the top-level assets registry.";
     readonly type: "object";
     readonly required: ["slides"];
     readonly additionalProperties: false;
@@ -15,11 +15,11 @@ declare const presentation: {
         readonly name: {
             readonly type: "string";
             readonly description: "Display name of the presentation for GUI/TUI lists, library/search indexing, OS-level metadata, and default export filenames. This is deck identity, not slide content. Use slides[].title and slides[].subtitle for text that should appear on presented slides.";
-            readonly examples: ["Q4 2026 Business Review", "Series B Pitch — Acme", "The Future of Agentic Workflows"];
+            readonly examples: ["Q4 2026 Business Review", "Series B Pitch — Acme", "The Future of Agentic Workflows"];
         };
         readonly description: {
             readonly type: "string";
-            readonly description: "Free-form prose describing what this presentation is about. Used by agents and humans as a deck-level summary; complements purpose (the goal) and narrative (the structured storyline). Round-trips to OOXML 'docProps/core.xml' as '<dc:description>' (PowerPoint surfaces this as the 'Comments' field in File → Properties).";
+            readonly description: "Free-form prose describing what this presentation is about. Used by agents and humans as a deck-level summary; complements purpose (the goal) and narrative (the structured storyline). Round-trips to OOXML 'docProps/core.xml' as '<dc:description>' (PowerPoint surfaces this as the 'Comments' field in File → Properties).";
             readonly examples: ["Quarterly business review covering revenue, product, and hiring milestones for the executive team."];
         };
         readonly filename: {
@@ -65,17 +65,21 @@ declare const presentation: {
             readonly examples: ["Bob Lee", ["Bob Lee", "Carla Diaz"]];
         };
         readonly audience: {
-            readonly type: "array";
-            readonly items: {
-                readonly oneOf: [{
-                    readonly type: "string";
-                }, {
-                    readonly $ref: "#/$defs/Audience";
-                }];
-            };
-            readonly minItems: 1;
-            readonly description: "Intended audiences for the presentation. Each item accepts either:\n- A string shorthand: free-form description ('Series B investors'), an audiences catalog id ('executives'), an HTTPS URL, or a 'pkg:' reference.\n- An inline Audience object for custom audience metadata or catalog-backed overrides. Object form mirrors https://openpresentation.org/schema/opf-audience/v1 without '$schema'.\n\nResolution order for catalog ids and references: inline catalogs.audiences.records[] → catalogs.audiences.source → default catalog at https://www.pptx.gallery/audiences.";
-            readonly examples: [["executives"], ["board", "c-suite"], ["Series B investors", "https://acme.com/decks/audiences/acme-board.json"], [{
+            readonly oneOf: [{
+                readonly type: "string";
+            }, {
+                readonly type: "array";
+                readonly items: {
+                    readonly oneOf: [{
+                        readonly type: "string";
+                    }, {
+                        readonly $ref: "#/$defs/Audience";
+                    }];
+                };
+                readonly minItems: 1;
+            }];
+            readonly description: "Intended audiences for the presentation. Accepts either:\n- A single string shorthand: free-form description ('Series B investors'), an audiences catalog id ('executives'), an HTTPS URL, or a 'pkg:' reference.\n- An array of string shorthands and/or inline Audience objects for custom audience metadata or catalog-backed overrides. Object form mirrors https://openpresentation.org/schema/opf-audience/v1 without '$schema'.\n\nResolution order for catalog ids and references: inline catalogs.audiences.records[] → catalogs.audiences.source → default catalog at https://www.pptx.gallery/audiences.";
+            readonly examples: ["executives", "Biology Students and Wildlife Enthusiasts", ["executives"], ["board", "c-suite"], ["Series B investors", "https://acme.com/decks/audiences/acme-board.json"], [{
                 readonly id: "executives";
                 readonly attentionBudgetMinutes: 20;
             }, {
@@ -91,7 +95,7 @@ declare const presentation: {
             }, {
                 readonly $ref: "#/$defs/Purpose";
             }];
-            readonly description: "Primary goal of the presentation. Accepts either:\n- A string shorthand: free-form goal ('Raise a Series B round of $30M'), a purposes catalog id ('decide', 'align'), an HTTPS URL, or a 'pkg:' reference.\n- An inline Purpose object for custom purpose metadata or catalog-backed overrides. Object form mirrors https://openpresentation.org/schema/opf-purpose/v1 without '$schema'.\n\nResolution order for catalog ids and references: inline catalogs.purposes.records[] → catalogs.purposes.source → default catalog at https://www.pptx.gallery/purposes.";
+            readonly description: "Primary goal of the presentation. Accepts either:\n- A string shorthand: free-form goal ('Raise a Series B round of $30M'), a purposes catalog id ('decide', 'align'), an HTTPS URL, or a 'pkg:' reference.\n- An inline Purpose object for custom purpose metadata or catalog-backed overrides. Object form mirrors https://openpresentation.org/schema/opf-purpose/v1 without '$schema'.\n\nResolution order for catalog ids and references: inline catalogs.purposes.records[] → catalogs.purposes.source → default catalog at https://www.pptx.gallery/purposes.";
             readonly examples: ["Raise a Series B round of $30M", "align", "educate", "https://acme.com/decks/purposes/fundraise.json", "pkg:@acme/decks/purposes/fundraise", {
                 readonly id: "decide";
                 readonly outcome: "Approve the Q4 hiring plan";
@@ -106,7 +110,7 @@ declare const presentation: {
             }, {
                 readonly $ref: "#/$defs/Language";
             }];
-            readonly description: "Language for the presentation content. Accepts either:\n- A string shorthand: a BCP-47 language tag ('en-US', 'en-GB', 'ja-JP', 'fr'), a languages catalog id ('english', 'japanese'), an HTTPS URL, or a 'pkg:' reference.\n- An inline Language object for custom language metadata or catalog-backed overrides. Object form mirrors https://openpresentation.org/schema/opf-language/v1 without '$schema'.\n\nResolution order for catalog ids and references: inline catalogs.languages.records[] → catalogs.languages.source → default catalog at https://www.pptx.gallery/languages.";
+            readonly description: "Language for the presentation content. Accepts either:\n- A string shorthand: a BCP-47 language tag ('en-US', 'en-GB', 'ja-JP', 'fr'), a languages catalog id ('english', 'japanese'), an HTTPS URL, or a 'pkg:' reference.\n- An inline Language object for custom language metadata or catalog-backed overrides. Object form mirrors https://openpresentation.org/schema/opf-language/v1 without '$schema'.\n\nResolution order for catalog ids and references: inline catalogs.languages.records[] → catalogs.languages.source → default catalog at https://www.pptx.gallery/languages.";
             readonly examples: ["en-US", "en-GB", "es-MX", "ja-JP", "fr", "english", "japanese", "https://acme.com/decks/languages/en-acme.json", "pkg:@acme/decks/languages/en-acme", {
                 readonly id: "english";
                 readonly bcp47: "en-US";
@@ -125,7 +129,7 @@ declare const presentation: {
             }, {
                 readonly $ref: "#/$defs/Tone";
             }];
-            readonly description: "Desired tone for the presentation. Accepts either:\n- A string shorthand: a tones catalog id ('formal'), an HTTPS URL, or a 'pkg:' reference.\n- An inline Tone object for custom tone metadata or catalog-backed overrides. Object form mirrors https://openpresentation.org/schema/opf-tone/v1 without '$schema'.\n\nResolution order for catalog ids and references: inline catalogs.tones.records[] → catalogs.tones.source → default catalog at https://www.pptx.gallery/tones.";
+            readonly description: "Desired tone for the presentation. Accepts either:\n- A string shorthand: a tones catalog id ('formal'), an HTTPS URL, or a 'pkg:' reference.\n- An inline Tone object for custom tone metadata or catalog-backed overrides. Object form mirrors https://openpresentation.org/schema/opf-tone/v1 without '$schema'.\n\nResolution order for catalog ids and references: inline catalogs.tones.records[] → catalogs.tones.source → default catalog at https://www.pptx.gallery/tones.";
             readonly examples: ["formal", "casual", "inspirational", "technical", "persuasive", "https://acme.com/decks/tones/acme-voice.json", "pkg:@acme/decks/tones/acme-voice", {
                 readonly id: "formal";
                 readonly voiceCues: ["Use precise, concise language."];
@@ -170,7 +174,7 @@ declare const presentation: {
             }, {
                 readonly $ref: "#/$defs/Narrative";
             }];
-            readonly description: "Structured storyline describing the deck's arc and beats. Resolves to the 'id' of a 'narratives' catalog record.\n\nAccepts two forms:\n- String shorthand for the common case: 'narrative = \"classic-story\"'. Accepts a bare id (lowercase kebab-case), an HTTPS URL pointing at a record file, or a 'pkg:' reference to a locally-installed package.\n- Object form for inline overrides or fully custom narratives: 'narrative = { id: \"classic-story\", beats: [...] }'. The object shape mirrors https://openpresentation.org/schema/opf-narrative/v1 (sans '$schema'), so a library record and an inline narrative are interchangeable.\n\nResolution order: inline catalogs.narratives.records[] → catalogs.narratives.source → default catalog at https://www.pptx.gallery/narratives. Unknown ids produce a validation warning, not an error.\n\nDeck-level concerns that aren't part of the storyline (audience, tone, takeaway, duration) live as siblings on the presentation root rather than inside the narrative object.";
+            readonly description: "Structured storyline describing the deck's arc and beats. Resolves to the 'id' of a 'narratives' catalog record.\n\nAccepts two forms:\n- String shorthand for the common case: 'narrative = \"classic-story\"'. Accepts a bare id (lowercase kebab-case), an HTTPS URL pointing at a record file, or a 'pkg:' reference to a locally-installed package.\n- Object form for inline overrides or fully custom narratives: 'narrative = { id: \"classic-story\", beats: [...] }'. The object shape mirrors https://openpresentation.org/schema/opf-narrative/v1 (sans '$schema'), so a library record and an inline narrative are interchangeable.\n\nResolution order: inline catalogs.narratives.records[] → catalogs.narratives.source → default catalog at https://www.pptx.gallery/narratives. Unknown ids produce a validation warning, not an error.\n\nDeck-level concerns that aren't part of the storyline (audience, tone, takeaway, duration) live as siblings on the presentation root rather than inside the narrative object.";
             readonly examples: ["classic-story", "problem-solution", "scqa", "pitch-deck", {
                 readonly id: "custom-pitch";
                 readonly name: "Custom Pitch";
@@ -528,7 +532,7 @@ declare const presentation: {
         };
         readonly Organization: {
             readonly type: "object";
-            readonly description: "An organization associated with the presentation — typically the presenting company, but also hosts, partners, clients, or sponsors. Surfaced on cover slides, footers, and brand bars; the primary organization's logo is the default deck logo unless overridden by design.logo.";
+            readonly description: "An organization associated with the presentation — typically the presenting company, but also hosts, partners, clients, or sponsors. Surfaced on cover slides, footers, and brand bars; the primary organization's logo is the default deck logo unless overridden by design.logo.";
             readonly required: ["id", "name"];
             readonly properties: {
                 readonly id: {
@@ -639,7 +643,7 @@ declare const presentation: {
         };
         readonly Socials: {
             readonly type: "object";
-            readonly description: "Social media handles or URLs, keyed by platform id from the 'socialPlatforms' catalog. Each value is a string — either a full URL or a platform handle (e.g., '@acme'). The catalog record for each platform carries the URL pattern, handle prefix, brand color, and themed icons used by renderers.\n\nKeys resolve to the 'id' of a 'socialPlatforms' catalog record. Resolution order: inline catalogs.socialPlatforms.records[] → catalogs.socialPlatforms.source → default catalog at https://www.pptx.gallery/social-platforms. Unknown platform keys render with engine fallbacks (the raw value as text). Used both for organization and speaker records.";
+            readonly description: "Social media handles or URLs, keyed by platform id from the 'socialPlatforms' catalog. Each value is a string — either a full URL or a platform handle (e.g., '@acme'). The catalog record for each platform carries the URL pattern, handle prefix, brand color, and themed icons used by renderers.\n\nKeys resolve to the 'id' of a 'socialPlatforms' catalog record. Resolution order: inline catalogs.socialPlatforms.records[] → catalogs.socialPlatforms.source → default catalog at https://www.pptx.gallery/social-platforms. Unknown platform keys render with engine fallbacks (the raw value as text). Used both for organization and speaker records.";
             readonly additionalProperties: {
                 readonly type: "string";
                 readonly description: "Handle or URL for the platform identified by the property key.";
@@ -660,7 +664,7 @@ declare const presentation: {
         };
         readonly Narrative: {
             readonly type: "object";
-            readonly description: "Structured storyline used by AI to shape generated content. Mirrors the OPF Narrative Template record at https://openpresentation.org/schema/opf-narrative/v1 (sans '$schema'), so a library record and an inline narrative are interchangeable.\n\nNarrative declares the deck's intended story arc; slides may opt into beats via Slide.beat. The narrative does not constrain slide structure — validators warn on drift (orphan slides, unused beats) but never error. Slides are the source of truth; narrative is intent that travels with the deck.\n\nWhen 'id' matches a record in the resolved 'narratives' catalog, the inline fields override matching fields on the catalog record (beats merge by beat 'id'). When 'id' doesn't match, this object defines a fully custom inline narrative.\n\nDeck-level concerns that aren't part of the storyline (audience, tone, takeaway, duration) live as siblings on the presentation root rather than inside this object.";
+            readonly description: "Structured storyline used by AI to shape generated content. Mirrors the OPF Narrative Template record at https://openpresentation.org/schema/opf-narrative/v1 (sans '$schema'), so a library record and an inline narrative are interchangeable.\n\nNarrative declares the deck's intended story arc; slides may opt into beats via Slide.beat. The narrative does not constrain slide structure — validators warn on drift (orphan slides, unused beats) but never error. Slides are the source of truth; narrative is intent that travels with the deck.\n\nWhen 'id' matches a record in the resolved 'narratives' catalog, the inline fields override matching fields on the catalog record (beats merge by beat 'id'). When 'id' doesn't match, this object defines a fully custom inline narrative.\n\nDeck-level concerns that aren't part of the storyline (audience, tone, takeaway, duration) live as siblings on the presentation root rather than inside this object.";
             readonly properties: {
                 readonly id: {
                     readonly type: "string";
@@ -671,7 +675,7 @@ declare const presentation: {
                 readonly name: {
                     readonly type: "string";
                     readonly description: "Human-readable narrative name.";
-                    readonly examples: ["Classic Story", "Problem → Solution", "SCQA", "Founder Pitch"];
+                    readonly examples: ["Classic Story", "Problem → Solution", "SCQA", "Founder Pitch"];
                 };
                 readonly summary: {
                     readonly type: "string";
@@ -744,7 +748,7 @@ declare const presentation: {
         };
         readonly NarrativeBeat: {
             readonly type: "object";
-            readonly description: "A single narrative beat — a labeled segment of the story arc with a specific dramatic purpose (e.g. 'hook', 'problem', 'evidence', 'ask'). Slides reference beats via Slide.beat. Beats may also carry slide-blueprint hints (slideType, layoutHint, thoughtCues, instructions) that guide the assigned slide.\n\nMirrors the Beat definition in narrative.schema.json (https://openpresentation.org/schema/opf-narrative/v1) so library entries and inline OPF beats are interchangeable.";
+            readonly description: "A single narrative beat — a labeled segment of the story arc with a specific dramatic purpose (e.g. 'hook', 'problem', 'evidence', 'ask'). Slides reference beats via Slide.beat. Beats may also carry slide-blueprint hints (slideType, layoutHint, thoughtCues, instructions) that guide the assigned slide.\n\nMirrors the Beat definition in narrative.schema.json (https://openpresentation.org/schema/opf-narrative/v1) so library entries and inline OPF beats are interchangeable.";
             readonly required: ["id", "name"];
             readonly properties: {
                 readonly id: {
@@ -765,7 +769,7 @@ declare const presentation: {
                 };
                 readonly instructions: {
                     readonly type: "string";
-                    readonly description: "Short author-facing instruction for the beat — typically one phrase. Complements 'description' with a concise directive.";
+                    readonly description: "Short author-facing instruction for the beat — typically one phrase. Complements 'description' with a concise directive.";
                     readonly examples: ["Capture audience attention", "Introduce problem", "Detail implementation", "Inspire & conclude"];
                 };
                 readonly slideCount: {
@@ -780,7 +784,7 @@ declare const presentation: {
                 };
                 readonly layoutHint: {
                     readonly type: "string";
-                    readonly description: "Suggested layout id for the beat's opening slide. Resolves the same way as Slide.layout — against catalogs.layouts and the default catalog at https://www.pptx.gallery/layouts.";
+                    readonly description: "Suggested layout id for the beat's opening slide. Resolves the same way as Slide.layout — against catalogs.layouts and the default catalog at https://www.pptx.gallery/layouts.";
                     readonly examples: ["section-divider", "title-slide", "title-left", "two-column", "text-left"];
                 };
                 readonly thoughtCues: {
@@ -1192,12 +1196,12 @@ declare const presentation: {
                 };
                 readonly major: {
                     readonly type: "string";
-                    readonly description: "Heading (major) font family — mirrors the OOXML majorFont entry. Pairs with 'minor'.";
+                    readonly description: "Heading (major) font family — mirrors the OOXML majorFont entry. Pairs with 'minor'.";
                     readonly examples: ["Aptos Display", "Calibri", "Microsoft YaHei", "Arial Black"];
                 };
                 readonly minor: {
                     readonly type: "string";
-                    readonly description: "Body (minor) font family — mirrors the OOXML minorFont entry. Pairs with 'major'.";
+                    readonly description: "Body (minor) font family — mirrors the OOXML minorFont entry. Pairs with 'major'.";
                     readonly examples: ["Aptos", "Calibri", "Microsoft YaHei", "Arial"];
                 };
                 readonly type: {
@@ -1634,7 +1638,7 @@ declare const presentation: {
                 };
                 readonly layout: {
                     readonly type: "string";
-                    readonly description: "Optional slide layout reference. Resolves to the 'id' of a 'layouts' catalog record. When omitted, engines infer a layout from the slide's root payload or promoted region keys. Accepts a bare id (lowercase kebab-case, e.g. 'title-subtitle'), an HTTPS URL pointing at a record file, or a 'pkg:' reference. Free-form custom layout names that don't resolve through any catalog fall through to engine-defined layouts.\n\nResolution order: inline catalogs.layouts.records[] → catalogs.layouts.source → default catalog at https://www.pptx.gallery/layouts.";
+                    readonly description: "Optional slide layout reference. Resolves to the 'id' of a 'layouts' catalog record. When omitted, engines infer a layout from the slide's root payload or promoted region keys. Accepts a bare id (lowercase kebab-case, e.g. 'title-subtitle'), an HTTPS URL pointing at a record file, or a 'pkg:' reference. Free-form custom layout names that don't resolve through any catalog fall through to engine-defined layouts.\n\nResolution order: inline catalogs.layouts.records[] → catalogs.layouts.source → default catalog at https://www.pptx.gallery/layouts.";
                     readonly examples: ["title", "title-subtitle", "text-2x", "chart-3x", "image-bleed", "blank", "https://acme.com/decks/layouts/cover.json", "pkg:@acme/decks/layouts/cover"];
                 };
                 readonly title: {
@@ -1668,7 +1672,7 @@ declare const presentation: {
                     readonly items: {
                         readonly $ref: "#/$defs/ListItem";
                     };
-                    readonly description: "Full-slide generic list payload. Presence of this field infers type 'list'.";
+                    readonly 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.";
                 };
                 readonly bullets: {
                     readonly type: "array";
@@ -1728,7 +1732,7 @@ declare const presentation: {
                     readonly items: {
                         readonly $ref: "#/$defs/ContentPayload";
                     };
-                    readonly description: "Layout-agnostic content blocks rendered together as a composed payload when exact placement is unspecified.";
+                    readonly description: "Layout-agnostic content blocks rendered together as a composed payload when exact placement is unspecified. At slide root, multiple content payload kinds with no explicit type, blocks, or regions are accepted as shorthand for equivalent blocks.";
                 };
                 readonly design: {
                     readonly $ref: "#/$defs/Design";
@@ -2568,7 +2572,7 @@ declare const presentation: {
         };
         readonly Catalogs: {
             readonly type: "object";
-            readonly description: "Catalog overrides for the in-document references. Every property is optional. The default catalog for a kind lives at https://www.pptx.gallery/<kind> (e.g. https://www.pptx.gallery/narratives, https://www.pptx.gallery/themes). For each kind, declaring a 'source' replaces the default registry and/or 'records' adds inline records that take precedence over anything fetched from a source.\n\nResolution order for any reference (e.g. narrative, design.theme): inline catalogs.<kind>.records[] → catalogs.<kind>.source → default catalog at https://www.pptx.gallery/<kind>. Every reference resolves to the catalog record's 'id' field. References that are themselves URLs or 'pkg:' references skip the catalog lookup and resolve directly.";
+            readonly description: "Catalog overrides for the in-document references. Every property is optional. The default catalog for a kind lives at https://www.pptx.gallery/<kind> (e.g. https://www.pptx.gallery/narratives, https://www.pptx.gallery/themes). For each kind, declaring a 'source' replaces the default registry and/or 'records' adds inline records that take precedence over anything fetched from a source.\n\nResolution order for any reference (e.g. narrative, design.theme): inline catalogs.<kind>.records[] → catalogs.<kind>.source → default catalog at https://www.pptx.gallery/<kind>. Every reference resolves to the catalog record's 'id' field. References that are themselves URLs or 'pkg:' references skip the catalog lookup and resolve directly.";
             readonly properties: {
                 readonly narratives: {
                     readonly $ref: "#/$defs/CatalogEntry";
@@ -2652,7 +2656,7 @@ declare const presentation: {
 declare const audience: {
     readonly $schema: "https://json-schema.org/draft/2020-12/schema";
     readonly $id: "https://openpresentation.org/schema/opf-audience/v1";
-    readonly title: "OPF Audience";
+    readonly title: "Audience";
     readonly description: "Schema for audience records in the pptx.gallery library. Each record names an audience archetype (e.g. 'executives', 'engineering-team', 'investors') and carries seniority, technical-fluency, decision-power, and attention-budget hints used by AI-driven generation. Audiences are referenced from OPF documents via audience; the engine resolves the reference against catalogs.audiences (inline) → catalogs.audiences.source → the default catalog at https://www.pptx.gallery/audiences. The audience field also accepts free-form strings; this catalog is for engine-aware audience archetypes that carry generation hints.";
     readonly type: "object";
     readonly required: ["$schema", "id", "name"];
@@ -2753,7 +2757,7 @@ declare const audience: {
 declare const purpose: {
     readonly $schema: "https://json-schema.org/draft/2020-12/schema";
     readonly $id: "https://openpresentation.org/schema/opf-purpose/v1";
-    readonly title: "OPF Purpose";
+    readonly title: "Purpose";
     readonly description: "Schema for purpose records in the pptx.gallery library. Each record names a presentation objective such as informing, aligning, persuading, driving a decision, or selling. Purposes are referenced from OPF documents via purpose; the engine resolves the reference against catalogs.purposes (inline) → catalogs.purposes.source → the default catalog at https://www.pptx.gallery/purposes. The purpose field also accepts free-form strings and inline Purpose objects.";
     readonly type: "object";
     readonly required: ["$schema", "id", "name"];
@@ -2841,7 +2845,7 @@ declare const purpose: {
 declare const tone: {
     readonly $schema: "https://json-schema.org/draft/2020-12/schema";
     readonly $id: "https://openpresentation.org/schema/opf-tone/v1";
-    readonly title: "OPF Tone";
+    readonly title: "Tone";
     readonly description: "Schema for tone records in the pptx.gallery library. Each record names a presentation tone (e.g. 'formal', 'casual', 'inspirational') and carries voice cues, anti-patterns, and sample phrases that AI-driven generation uses to shape output. Tones are referenced from OPF documents via tone; the engine resolves the reference against catalogs.tones (inline) → catalogs.tones.source → the default catalog at https://www.pptx.gallery/tones.";
     readonly type: "object";
     readonly required: ["$schema", "id", "name"];
@@ -2938,7 +2942,7 @@ declare const tone: {
 declare const theme: {
     readonly $schema: "https://json-schema.org/draft/2020-12/schema";
     readonly $id: "https://openpresentation.org/schema/opf-theme/v1";
-    readonly title: "OPF Theme";
+    readonly title: "Theme";
     readonly description: "Schema for theme records in the pptx.gallery library. Each theme is a small, named bundle that pairs a color scheme, a font scheme, a default theme-controlled background, and a slide size. Themes are referenced from OPF documents via design.theme or design.theme.id; the engine resolves the reference against catalogs.themes (inline) → catalogs.themes.source → the default catalog at https://www.pptx.gallery/themes. Inline overrides on design.colorScheme / design.fontScheme / design.background / design.dimensions take precedence over a resolved theme.";
     readonly type: "object";
     readonly required: ["$schema", "id", "name"];
@@ -3047,7 +3051,7 @@ declare const theme: {
 declare const layout: {
     readonly $schema: "https://json-schema.org/draft/2020-12/schema";
     readonly $id: "https://openpresentation.org/schema/opf-layout/v1";
-    readonly title: "OPF Slide Layout";
+    readonly title: "Slide Layout";
     readonly description: "Schema for slide-layout records in the pptx.gallery library. Each record describes a semantic slide layout — what regions it exposes and what content kinds those regions are intended to hold. Layouts are referenced from OPF documents via Slide.layout; the engine resolves the reference against catalogs.layouts (inline) → catalogs.layouts.source → the default catalog at https://www.pptx.gallery/layouts. Free-form custom layout names that don't resolve through any catalog fall through to engine-defined layouts.";
     readonly type: "object";
     readonly required: ["$schema", "id", "name"];
@@ -3211,7 +3215,7 @@ declare const layout: {
 declare const chartType: {
     readonly $schema: "https://json-schema.org/draft/2020-12/schema";
     readonly $id: "https://openpresentation.org/schema/opf-chart-type/v1";
-    readonly title: "OPF Chart Type";
+    readonly title: "Chart Type";
     readonly description: "Schema for chart-type records in the pptx.gallery catalog. Each record describes a named chart variant, its Open XML mapping, its series/category cardinality, the column structure of the underlying workbook, and a small sample dataset suitable for previews. Chart types are referenced from OPF chart content payloads; the engine resolves the reference against catalogs.chartTypes (inline) -> catalogs.chartTypes.source -> the default catalog at https://www.pptx.gallery/chart-types.";
     readonly type: "object";
     readonly additionalProperties: false;
@@ -3517,7 +3521,7 @@ declare const chartType: {
 declare const narrative: {
     readonly $schema: "https://json-schema.org/draft/2020-12/schema";
     readonly $id: "https://openpresentation.org/schema/opf-narrative/v1";
-    readonly title: "OPF Narrative Template";
+    readonly title: "Narrative Template";
     readonly description: "Schema for narrative template files in the openpresentation.org catalog. Each template describes a named story arc (e.g. 'problem-solution', 'scqa') as an ordered list of beats. Templates are referenced from OPF documents via narrative — either as a bare id string (e.g. 'classic-story') or as an inline object whose shape matches this schema (sans '$schema').";
     readonly type: "object";
     readonly required: ["$schema", "id", "name", "beats"];
@@ -3663,8 +3667,8 @@ declare const narrative: {
 declare const socialPlatform: {
     readonly $schema: "https://json-schema.org/draft/2020-12/schema";
     readonly $id: "https://openpresentation.org/schema/opf-social-platform/v1";
-    readonly title: "OPF Social Platform";
-    readonly description: "Schema for social-platform records in the pptx.gallery library. Each record describes a single social-media platform — its base URL, profile-URL pattern, handle prefix, brand color, and themed icons. Records are referenced from OPF documents indirectly: the property keys of any Socials object (Organization.socials, Speaker.socials) match record ids, and renderers use the catalog record to format URLs and pick icons. The engine resolves references against catalogs.socialPlatforms (inline) → catalogs.socialPlatforms.source → the default catalog at https://www.pptx.gallery/social-platforms.";
+    readonly title: "Social Platform";
+    readonly description: "Schema for social-platform records in the pptx.gallery library. Each record describes a single social-media platform — its base URL, profile-URL pattern, handle prefix, brand color, and themed icons. Records are referenced from OPF documents indirectly: the property keys of any Socials object (Organization.socials, Speaker.socials) match record ids, and renderers use the catalog record to format URLs and pick icons. The engine resolves references against catalogs.socialPlatforms (inline) → catalogs.socialPlatforms.source → the default catalog at https://www.pptx.gallery/social-platforms.";
     readonly type: "object";
     readonly required: ["$schema", "id", "name"];
     readonly properties: {
@@ -3676,7 +3680,7 @@ declare const socialPlatform: {
         readonly id: {
             readonly type: "string";
             readonly pattern: "^[a-z][a-z0-9-]*$";
-            readonly description: "Stable slug used by OPF documents to reference this platform — appears as a property key on Socials objects. Lowercase kebab-case.";
+            readonly description: "Stable slug used by OPF documents to reference this platform — appears as a property key on Socials objects. Lowercase kebab-case.";
             readonly examples: ["linkedin", "x", "github", "youtube", "instagram", "facebook", "tiktok", "threads", "mastodon", "bluesky"];
         };
         readonly name: {
@@ -3686,7 +3690,7 @@ declare const socialPlatform: {
         };
         readonly summary: {
             readonly type: "string";
-            readonly description: "One-sentence positioning of the platform — what it's used for and who's on it.";
+            readonly description: "One-sentence positioning of the platform — what it's used for and who's on it.";
             readonly examples: ["Professional social network for individuals and companies.", "Real-time microblog for news, opinions, and discussion."];
         };
         readonly description: {
@@ -3697,7 +3701,7 @@ declare const socialPlatform: {
         readonly baseUrl: {
             readonly type: "string";
             readonly format: "uri";
-            readonly description: "Canonical base URL of the platform — used as the prefix when normalizing handles to full URLs.";
+            readonly description: "Canonical base URL of the platform — used as the prefix when normalizing handles to full URLs.";
             readonly examples: ["https://linkedin.com", "https://x.com", "https://github.com", "https://youtube.com"];
         };
         readonly profileUrlPattern: {
@@ -3774,7 +3778,7 @@ declare const socialPlatform: {
 declare const language: {
     readonly $schema: "https://json-schema.org/draft/2020-12/schema";
     readonly $id: "https://openpresentation.org/schema/opf-language/v1";
-    readonly title: "OPF Language";
+    readonly title: "Language";
     readonly description: "Schema for language records in the pptx.gallery library. Each record names a presentation language, carries a BCP-47 language tag, and pairs it with sensible default font schemes for PowerPoint and Google Slides output. Languages are referenced from OPF documents via language; the engine resolves the reference against catalogs.languages (inline) → catalogs.languages.source → the default catalog at https://www.pptx.gallery/languages. The presentation language field also accepts BCP-47 tags directly or inline Language objects for engine-aware language records that carry default-font hints.";
     readonly type: "object";
     readonly required: ["$schema", "id", "name", "bcp47"];
@@ -3873,7 +3877,7 @@ declare const language: {
 declare const colorScheme: {
     readonly $schema: "https://json-schema.org/draft/2020-12/schema";
     readonly $id: "https://openpresentation.org/schema/opf-color-scheme/v1";
-    readonly title: "OPF Color Scheme";
+    readonly title: "Color Scheme";
     readonly description: "Schema for color-scheme records in the pptx.gallery library. Each scheme is a named palette with the twelve PowerPoint color slots (six accents, two darks, two lights, plus hyperlink and followed-hyperlink), suitable for being mapped directly into OOXML theme XML. Color schemes are referenced from OPF documents via design.colorScheme or design.colorScheme.id; the engine resolves the reference against catalogs.colorSchemes (inline) -> catalogs.colorSchemes.source -> the default catalog at https://www.pptx.gallery/color-schemes. Slot overrides on design.colorScheme take precedence over the resolved scheme.\n\nThe slot fields here mirror the inline-override fields on the in-document ColorScheme type (in opf.schema.json), so library entries and inline OPF overrides are interchangeable.";
     readonly type: "object";
     readonly required: ["$schema", "id", "name"];
@@ -4001,7 +4005,7 @@ declare const colorScheme: {
 declare const fontScheme: {
     readonly $schema: "https://json-schema.org/draft/2020-12/schema";
     readonly $id: "https://openpresentation.org/schema/opf-font-scheme/v1";
-    readonly title: "OPF Font Scheme";
+    readonly title: "Font Scheme";
     readonly description: "Schema for font-scheme records in the pptx.gallery library. Each scheme pairs a major (heading) and minor (body) font family in the OOXML majorFont/minorFont sense, scoped to a target app (PowerPoint or Google Slides) and a language family (Latin, East Asian, or Complex Script). Font schemes are referenced from OPF documents via design.fontScheme or design.fontScheme.id; the engine resolves the reference against catalogs.fontSchemes (inline) → catalogs.fontSchemes.source → the default catalog at https://www.pptx.gallery/font-schemes. Role overrides on design.fontScheme (heading, body, accent, code) take precedence over the resolved scheme.";
     readonly type: "object";
     readonly required: ["$schema", "id", "name", "major", "minor"];
@@ -4108,8 +4112,8 @@ declare const schemas: {
     readonly presentation: {
         readonly $schema: "https://json-schema.org/draft/2020-12/schema";
         readonly $id: "https://openpresentation.org/schema/opf/v1";
-        readonly title: "OPF — Open Presentation Format";
-        readonly description: "Open-source JSON format for describing PowerPoint presentations. Agents describe narratives, content, audience, reusable assets, and design — the engine handles OOXML complexity.\n\nFields that reference catalog records (narrative, language, tone, audience, purpose, design.theme / design.theme.id, design.colorScheme / design.colorScheme.id, design.fontScheme / design.fontScheme.id, Slide.layout, Chart.type, Organization.socials / Speaker.socials) resolve through the catalog system: inline 'catalogs.<kind>.records[]' on the document → 'catalogs.<kind>.source' on the document → engine defaults → the default catalog at https://www.pptx.gallery/<kind>. Every reference resolves to the catalog record's 'id' field. When an OPF document omits a reference entirely, the engine falls back to engine defaults (see /spec/reference/engine-defaults.json for a reference example). The defaults file is engine configuration; it is not part of the OPF document contract and has no JSON Schema.\n\nMost catalog references accept the bare 'id' as a string for the common case (e.g. narrative = 'classic-story', design.colorScheme = 'cool-horizon'). Audience, purpose, tone, design, and language object forms use 'id' as a base catalog reference plus inline overrides. Asset references use 'asset:<id>' strings that point into the top-level assets registry.";
+        readonly title: "Presentation";
+        readonly description: "Open-source JSON format for describing PowerPoint presentations. Agents describe narratives, content, audience, reusable assets, and design — the engine handles OOXML complexity.\n\nFields that reference catalog records (narrative, language, tone, audience, purpose, design.theme / design.theme.id, design.colorScheme / design.colorScheme.id, design.fontScheme / design.fontScheme.id, Slide.layout, Chart.type, Organization.socials / Speaker.socials) resolve through the catalog system: inline 'catalogs.<kind>.records[]' on the document → 'catalogs.<kind>.source' on the document → engine defaults → the default catalog at https://www.pptx.gallery/<kind>. Every reference resolves to the catalog record's 'id' field. When an OPF document omits a reference entirely, the engine falls back to engine defaults (see /spec/reference/engine-defaults.json for a reference example). The defaults file is engine configuration; it is not part of the OPF document contract and has no JSON Schema.\n\nMost catalog references accept the bare 'id' as a string for the common case (e.g. narrative = 'classic-story', design.colorScheme = 'cool-horizon'). Audience, purpose, tone, design, and language object forms use 'id' as a base catalog reference plus inline overrides. Asset references use 'asset:<id>' strings that point into the top-level assets registry.";
         readonly type: "object";
         readonly required: ["slides"];
         readonly additionalProperties: false;
@@ -4122,11 +4126,11 @@ declare const schemas: {
             readonly name: {
                 readonly type: "string";
                 readonly description: "Display name of the presentation for GUI/TUI lists, library/search indexing, OS-level metadata, and default export filenames. This is deck identity, not slide content. Use slides[].title and slides[].subtitle for text that should appear on presented slides.";
-                readonly examples: ["Q4 2026 Business Review", "Series B Pitch — Acme", "The Future of Agentic Workflows"];
+                readonly examples: ["Q4 2026 Business Review", "Series B Pitch — Acme", "The Future of Agentic Workflows"];
             };
             readonly description: {
                 readonly type: "string";
-                readonly description: "Free-form prose describing what this presentation is about. Used by agents and humans as a deck-level summary; complements purpose (the goal) and narrative (the structured storyline). Round-trips to OOXML 'docProps/core.xml' as '<dc:description>' (PowerPoint surfaces this as the 'Comments' field in File → Properties).";
+                readonly description: "Free-form prose describing what this presentation is about. Used by agents and humans as a deck-level summary; complements purpose (the goal) and narrative (the structured storyline). Round-trips to OOXML 'docProps/core.xml' as '<dc:description>' (PowerPoint surfaces this as the 'Comments' field in File → Properties).";
                 readonly examples: ["Quarterly business review covering revenue, product, and hiring milestones for the executive team."];
             };
             readonly filename: {
@@ -4172,17 +4176,21 @@ declare const schemas: {
                 readonly examples: ["Bob Lee", ["Bob Lee", "Carla Diaz"]];
             };
             readonly audience: {
-                readonly type: "array";
-                readonly items: {
-                    readonly oneOf: [{
-                        readonly type: "string";
-                    }, {
-                        readonly $ref: "#/$defs/Audience";
-                    }];
-                };
-                readonly minItems: 1;
-                readonly description: "Intended audiences for the presentation. Each item accepts either:\n- A string shorthand: free-form description ('Series B investors'), an audiences catalog id ('executives'), an HTTPS URL, or a 'pkg:' reference.\n- An inline Audience object for custom audience metadata or catalog-backed overrides. Object form mirrors https://openpresentation.org/schema/opf-audience/v1 without '$schema'.\n\nResolution order for catalog ids and references: inline catalogs.audiences.records[] → catalogs.audiences.source → default catalog at https://www.pptx.gallery/audiences.";
-                readonly examples: [["executives"], ["board", "c-suite"], ["Series B investors", "https://acme.com/decks/audiences/acme-board.json"], [{
+                readonly oneOf: [{
+                    readonly type: "string";
+                }, {
+                    readonly type: "array";
+                    readonly items: {
+                        readonly oneOf: [{
+                            readonly type: "string";
+                        }, {
+                            readonly $ref: "#/$defs/Audience";
+                        }];
+                    };
+                    readonly minItems: 1;
+                }];
+                readonly description: "Intended audiences for the presentation. Accepts either:\n- A single string shorthand: free-form description ('Series B investors'), an audiences catalog id ('executives'), an HTTPS URL, or a 'pkg:' reference.\n- An array of string shorthands and/or inline Audience objects for custom audience metadata or catalog-backed overrides. Object form mirrors https://openpresentation.org/schema/opf-audience/v1 without '$schema'.\n\nResolution order for catalog ids and references: inline catalogs.audiences.records[] → catalogs.audiences.source → default catalog at https://www.pptx.gallery/audiences.";
+                readonly examples: ["executives", "Biology Students and Wildlife Enthusiasts", ["executives"], ["board", "c-suite"], ["Series B investors", "https://acme.com/decks/audiences/acme-board.json"], [{
                     readonly id: "executives";
                     readonly attentionBudgetMinutes: 20;
                 }, {
@@ -4198,7 +4206,7 @@ declare const schemas: {
                 }, {
                     readonly $ref: "#/$defs/Purpose";
                 }];
-                readonly description: "Primary goal of the presentation. Accepts either:\n- A string shorthand: free-form goal ('Raise a Series B round of $30M'), a purposes catalog id ('decide', 'align'), an HTTPS URL, or a 'pkg:' reference.\n- An inline Purpose object for custom purpose metadata or catalog-backed overrides. Object form mirrors https://openpresentation.org/schema/opf-purpose/v1 without '$schema'.\n\nResolution order for catalog ids and references: inline catalogs.purposes.records[] → catalogs.purposes.source → default catalog at https://www.pptx.gallery/purposes.";
+                readonly description: "Primary goal of the presentation. Accepts either:\n- A string shorthand: free-form goal ('Raise a Series B round of $30M'), a purposes catalog id ('decide', 'align'), an HTTPS URL, or a 'pkg:' reference.\n- An inline Purpose object for custom purpose metadata or catalog-backed overrides. Object form mirrors https://openpresentation.org/schema/opf-purpose/v1 without '$schema'.\n\nResolution order for catalog ids and references: inline catalogs.purposes.records[] → catalogs.purposes.source → default catalog at https://www.pptx.gallery/purposes.";
                 readonly examples: ["Raise a Series B round of $30M", "align", "educate", "https://acme.com/decks/purposes/fundraise.json", "pkg:@acme/decks/purposes/fundraise", {
                     readonly id: "decide";
                     readonly outcome: "Approve the Q4 hiring plan";
@@ -4213,7 +4221,7 @@ declare const schemas: {
                 }, {
                     readonly $ref: "#/$defs/Language";
                 }];
-                readonly description: "Language for the presentation content. Accepts either:\n- A string shorthand: a BCP-47 language tag ('en-US', 'en-GB', 'ja-JP', 'fr'), a languages catalog id ('english', 'japanese'), an HTTPS URL, or a 'pkg:' reference.\n- An inline Language object for custom language metadata or catalog-backed overrides. Object form mirrors https://openpresentation.org/schema/opf-language/v1 without '$schema'.\n\nResolution order for catalog ids and references: inline catalogs.languages.records[] → catalogs.languages.source → default catalog at https://www.pptx.gallery/languages.";
+                readonly description: "Language for the presentation content. Accepts either:\n- A string shorthand: a BCP-47 language tag ('en-US', 'en-GB', 'ja-JP', 'fr'), a languages catalog id ('english', 'japanese'), an HTTPS URL, or a 'pkg:' reference.\n- An inline Language object for custom language metadata or catalog-backed overrides. Object form mirrors https://openpresentation.org/schema/opf-language/v1 without '$schema'.\n\nResolution order for catalog ids and references: inline catalogs.languages.records[] → catalogs.languages.source → default catalog at https://www.pptx.gallery/languages.";
                 readonly examples: ["en-US", "en-GB", "es-MX", "ja-JP", "fr", "english", "japanese", "https://acme.com/decks/languages/en-acme.json", "pkg:@acme/decks/languages/en-acme", {
                     readonly id: "english";
                     readonly bcp47: "en-US";
@@ -4232,7 +4240,7 @@ declare const schemas: {
                 }, {
                     readonly $ref: "#/$defs/Tone";
                 }];
-                readonly description: "Desired tone for the presentation. Accepts either:\n- A string shorthand: a tones catalog id ('formal'), an HTTPS URL, or a 'pkg:' reference.\n- An inline Tone object for custom tone metadata or catalog-backed overrides. Object form mirrors https://openpresentation.org/schema/opf-tone/v1 without '$schema'.\n\nResolution order for catalog ids and references: inline catalogs.tones.records[] → catalogs.tones.source → default catalog at https://www.pptx.gallery/tones.";
+                readonly description: "Desired tone for the presentation. Accepts either:\n- A string shorthand: a tones catalog id ('formal'), an HTTPS URL, or a 'pkg:' reference.\n- An inline Tone object for custom tone metadata or catalog-backed overrides. Object form mirrors https://openpresentation.org/schema/opf-tone/v1 without '$schema'.\n\nResolution order for catalog ids and references: inline catalogs.tones.records[] → catalogs.tones.source → default catalog at https://www.pptx.gallery/tones.";
                 readonly examples: ["formal", "casual", "inspirational", "technical", "persuasive", "https://acme.com/decks/tones/acme-voice.json", "pkg:@acme/decks/tones/acme-voice", {
                     readonly id: "formal";
                     readonly voiceCues: ["Use precise, concise language."];
@@ -4277,7 +4285,7 @@ declare const schemas: {
                 }, {
                     readonly $ref: "#/$defs/Narrative";
                 }];
-                readonly description: "Structured storyline describing the deck's arc and beats. Resolves to the 'id' of a 'narratives' catalog record.\n\nAccepts two forms:\n- String shorthand for the common case: 'narrative = \"classic-story\"'. Accepts a bare id (lowercase kebab-case), an HTTPS URL pointing at a record file, or a 'pkg:' reference to a locally-installed package.\n- Object form for inline overrides or fully custom narratives: 'narrative = { id: \"classic-story\", beats: [...] }'. The object shape mirrors https://openpresentation.org/schema/opf-narrative/v1 (sans '$schema'), so a library record and an inline narrative are interchangeable.\n\nResolution order: inline catalogs.narratives.records[] → catalogs.narratives.source → default catalog at https://www.pptx.gallery/narratives. Unknown ids produce a validation warning, not an error.\n\nDeck-level concerns that aren't part of the storyline (audience, tone, takeaway, duration) live as siblings on the presentation root rather than inside the narrative object.";
+                readonly description: "Structured storyline describing the deck's arc and beats. Resolves to the 'id' of a 'narratives' catalog record.\n\nAccepts two forms:\n- String shorthand for the common case: 'narrative = \"classic-story\"'. Accepts a bare id (lowercase kebab-case), an HTTPS URL pointing at a record file, or a 'pkg:' reference to a locally-installed package.\n- Object form for inline overrides or fully custom narratives: 'narrative = { id: \"classic-story\", beats: [...] }'. The object shape mirrors https://openpresentation.org/schema/opf-narrative/v1 (sans '$schema'), so a library record and an inline narrative are interchangeable.\n\nResolution order: inline catalogs.narratives.records[] → catalogs.narratives.source → default catalog at https://www.pptx.gallery/narratives. Unknown ids produce a validation warning, not an error.\n\nDeck-level concerns that aren't part of the storyline (audience, tone, takeaway, duration) live as siblings on the presentation root rather than inside the narrative object.";
                 readonly examples: ["classic-story", "problem-solution", "scqa", "pitch-deck", {
                     readonly id: "custom-pitch";
                     readonly name: "Custom Pitch";
@@ -4635,7 +4643,7 @@ declare const schemas: {
             };
             readonly Organization: {
                 readonly type: "object";
-                readonly description: "An organization associated with the presentation — typically the presenting company, but also hosts, partners, clients, or sponsors. Surfaced on cover slides, footers, and brand bars; the primary organization's logo is the default deck logo unless overridden by design.logo.";
+                readonly description: "An organization associated with the presentation — typically the presenting company, but also hosts, partners, clients, or sponsors. Surfaced on cover slides, footers, and brand bars; the primary organization's logo is the default deck logo unless overridden by design.logo.";
                 readonly required: ["id", "name"];
                 readonly properties: {
                     readonly id: {
@@ -4746,7 +4754,7 @@ declare const schemas: {
             };
             readonly Socials: {
                 readonly type: "object";
-                readonly description: "Social media handles or URLs, keyed by platform id from the 'socialPlatforms' catalog. Each value is a string — either a full URL or a platform handle (e.g., '@acme'). The catalog record for each platform carries the URL pattern, handle prefix, brand color, and themed icons used by renderers.\n\nKeys resolve to the 'id' of a 'socialPlatforms' catalog record. Resolution order: inline catalogs.socialPlatforms.records[] → catalogs.socialPlatforms.source → default catalog at https://www.pptx.gallery/social-platforms. Unknown platform keys render with engine fallbacks (the raw value as text). Used both for organization and speaker records.";
+                readonly description: "Social media handles or URLs, keyed by platform id from the 'socialPlatforms' catalog. Each value is a string — either a full URL or a platform handle (e.g., '@acme'). The catalog record for each platform carries the URL pattern, handle prefix, brand color, and themed icons used by renderers.\n\nKeys resolve to the 'id' of a 'socialPlatforms' catalog record. Resolution order: inline catalogs.socialPlatforms.records[] → catalogs.socialPlatforms.source → default catalog at https://www.pptx.gallery/social-platforms. Unknown platform keys render with engine fallbacks (the raw value as text). Used both for organization and speaker records.";
                 readonly additionalProperties: {
                     readonly type: "string";
                     readonly description: "Handle or URL for the platform identified by the property key.";
@@ -4767,7 +4775,7 @@ declare const schemas: {
             };
             readonly Narrative: {
                 readonly type: "object";
-                readonly description: "Structured storyline used by AI to shape generated content. Mirrors the OPF Narrative Template record at https://openpresentation.org/schema/opf-narrative/v1 (sans '$schema'), so a library record and an inline narrative are interchangeable.\n\nNarrative declares the deck's intended story arc; slides may opt into beats via Slide.beat. The narrative does not constrain slide structure — validators warn on drift (orphan slides, unused beats) but never error. Slides are the source of truth; narrative is intent that travels with the deck.\n\nWhen 'id' matches a record in the resolved 'narratives' catalog, the inline fields override matching fields on the catalog record (beats merge by beat 'id'). When 'id' doesn't match, this object defines a fully custom inline narrative.\n\nDeck-level concerns that aren't part of the storyline (audience, tone, takeaway, duration) live as siblings on the presentation root rather than inside this object.";
+                readonly description: "Structured storyline used by AI to shape generated content. Mirrors the OPF Narrative Template record at https://openpresentation.org/schema/opf-narrative/v1 (sans '$schema'), so a library record and an inline narrative are interchangeable.\n\nNarrative declares the deck's intended story arc; slides may opt into beats via Slide.beat. The narrative does not constrain slide structure — validators warn on drift (orphan slides, unused beats) but never error. Slides are the source of truth; narrative is intent that travels with the deck.\n\nWhen 'id' matches a record in the resolved 'narratives' catalog, the inline fields override matching fields on the catalog record (beats merge by beat 'id'). When 'id' doesn't match, this object defines a fully custom inline narrative.\n\nDeck-level concerns that aren't part of the storyline (audience, tone, takeaway, duration) live as siblings on the presentation root rather than inside this object.";
                 readonly properties: {
                     readonly id: {
                         readonly type: "string";
@@ -4778,7 +4786,7 @@ declare const schemas: {
                     readonly name: {
                         readonly type: "string";
                         readonly description: "Human-readable narrative name.";
-                        readonly examples: ["Classic Story", "Problem → Solution", "SCQA", "Founder Pitch"];
+                        readonly examples: ["Classic Story", "Problem → Solution", "SCQA", "Founder Pitch"];
                     };
                     readonly summary: {
                         readonly type: "string";
@@ -4851,7 +4859,7 @@ declare const schemas: {
             };
             readonly NarrativeBeat: {
                 readonly type: "object";
-                readonly description: "A single narrative beat — a labeled segment of the story arc with a specific dramatic purpose (e.g. 'hook', 'problem', 'evidence', 'ask'). Slides reference beats via Slide.beat. Beats may also carry slide-blueprint hints (slideType, layoutHint, thoughtCues, instructions) that guide the assigned slide.\n\nMirrors the Beat definition in narrative.schema.json (https://openpresentation.org/schema/opf-narrative/v1) so library entries and inline OPF beats are interchangeable.";
+                readonly description: "A single narrative beat — a labeled segment of the story arc with a specific dramatic purpose (e.g. 'hook', 'problem', 'evidence', 'ask'). Slides reference beats via Slide.beat. Beats may also carry slide-blueprint hints (slideType, layoutHint, thoughtCues, instructions) that guide the assigned slide.\n\nMirrors the Beat definition in narrative.schema.json (https://openpresentation.org/schema/opf-narrative/v1) so library entries and inline OPF beats are interchangeable.";
                 readonly required: ["id", "name"];
                 readonly properties: {
                     readonly id: {
@@ -4872,7 +4880,7 @@ declare const schemas: {
                     };
                     readonly instructions: {
                         readonly type: "string";
-                        readonly description: "Short author-facing instruction for the beat — typically one phrase. Complements 'description' with a concise directive.";
+                        readonly description: "Short author-facing instruction for the beat — typically one phrase. Complements 'description' with a concise directive.";
                         readonly examples: ["Capture audience attention", "Introduce problem", "Detail implementation", "Inspire & conclude"];
                     };
                     readonly slideCount: {
@@ -4887,7 +4895,7 @@ declare const schemas: {
                     };
                     readonly layoutHint: {
                         readonly type: "string";
-                        readonly description: "Suggested layout id for the beat's opening slide. Resolves the same way as Slide.layout — against catalogs.layouts and the default catalog at https://www.pptx.gallery/layouts.";
+                        readonly description: "Suggested layout id for the beat's opening slide. Resolves the same way as Slide.layout — against catalogs.layouts and the default catalog at https://www.pptx.gallery/layouts.";
                         readonly examples: ["section-divider", "title-slide", "title-left", "two-column", "text-left"];
                     };
                     readonly thoughtCues: {
@@ -5299,12 +5307,12 @@ declare const schemas: {
                     };
                     readonly major: {
                         readonly type: "string";
-                        readonly description: "Heading (major) font family — mirrors the OOXML majorFont entry. Pairs with 'minor'.";
+                        readonly description: "Heading (major) font family — mirrors the OOXML majorFont entry. Pairs with 'minor'.";
                         readonly examples: ["Aptos Display", "Calibri", "Microsoft YaHei", "Arial Black"];
                     };
                     readonly minor: {
                         readonly type: "string";
-                        readonly description: "Body (minor) font family — mirrors the OOXML minorFont entry. Pairs with 'major'.";
+                        readonly description: "Body (minor) font family — mirrors the OOXML minorFont entry. Pairs with 'major'.";
                         readonly examples: ["Aptos", "Calibri", "Microsoft YaHei", "Arial"];
                     };
                     readonly type: {
@@ -5741,7 +5749,7 @@ declare const schemas: {
                     };
                     readonly layout: {
                         readonly type: "string";
-                        readonly description: "Optional slide layout reference. Resolves to the 'id' of a 'layouts' catalog record. When omitted, engines infer a layout from the slide's root payload or promoted region keys. Accepts a bare id (lowercase kebab-case, e.g. 'title-subtitle'), an HTTPS URL pointing at a record file, or a 'pkg:' reference. Free-form custom layout names that don't resolve through any catalog fall through to engine-defined layouts.\n\nResolution order: inline catalogs.layouts.records[] → catalogs.layouts.source → default catalog at https://www.pptx.gallery/layouts.";
+                        readonly description: "Optional slide layout reference. Resolves to the 'id' of a 'layouts' catalog record. When omitted, engines infer a layout from the slide's root payload or promoted region keys. Accepts a bare id (lowercase kebab-case, e.g. 'title-subtitle'), an HTTPS URL pointing at a record file, or a 'pkg:' reference. Free-form custom layout names that don't resolve through any catalog fall through to engine-defined layouts.\n\nResolution order: inline catalogs.layouts.records[] → catalogs.layouts.source → default catalog at https://www.pptx.gallery/layouts.";
                         readonly examples: ["title", "title-subtitle", "text-2x", "chart-3x", "image-bleed", "blank", "https://acme.com/decks/layouts/cover.json", "pkg:@acme/decks/layouts/cover"];
                     };
                     readonly title: {
@@ -5775,7 +5783,7 @@ declare const schemas: {
                         readonly items: {
                             readonly $ref: "#/$defs/ListItem";
                         };
-                        readonly description: "Full-slide generic list payload. Presence of this field infers type 'list'.";
+                        readonly 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.";
                     };
                     readonly bullets: {
                         readonly type: "array";
@@ -5835,7 +5843,7 @@ declare const schemas: {
                         readonly items: {
                             readonly $ref: "#/$defs/ContentPayload";
                         };
-                        readonly description: "Layout-agnostic content blocks rendered together as a composed payload when exact placement is unspecified.";
+                        readonly description: "Layout-agnostic content blocks rendered together as a composed payload when exact placement is unspecified. At slide root, multiple content payload kinds with no explicit type, blocks, or regions are accepted as shorthand for equivalent blocks.";
                     };
                     readonly design: {
                         readonly $ref: "#/$defs/Design";
@@ -6675,7 +6683,7 @@ declare const schemas: {
             };
             readonly Catalogs: {
                 readonly type: "object";
-                readonly description: "Catalog overrides for the in-document references. Every property is optional. The default catalog for a kind lives at https://www.pptx.gallery/<kind> (e.g. https://www.pptx.gallery/narratives, https://www.pptx.gallery/themes). For each kind, declaring a 'source' replaces the default registry and/or 'records' adds inline records that take precedence over anything fetched from a source.\n\nResolution order for any reference (e.g. narrative, design.theme): inline catalogs.<kind>.records[] → catalogs.<kind>.source → default catalog at https://www.pptx.gallery/<kind>. Every reference resolves to the catalog record's 'id' field. References that are themselves URLs or 'pkg:' references skip the catalog lookup and resolve directly.";
+                readonly description: "Catalog overrides for the in-document references. Every property is optional. The default catalog for a kind lives at https://www.pptx.gallery/<kind> (e.g. https://www.pptx.gallery/narratives, https://www.pptx.gallery/themes). For each kind, declaring a 'source' replaces the default registry and/or 'records' adds inline records that take precedence over anything fetched from a source.\n\nResolution order for any reference (e.g. narrative, design.theme): inline catalogs.<kind>.records[] → catalogs.<kind>.source → default catalog at https://www.pptx.gallery/<kind>. Every reference resolves to the catalog record's 'id' field. References that are themselves URLs or 'pkg:' references skip the catalog lookup and resolve directly.";
                 readonly properties: {
                     readonly narratives: {
                         readonly $ref: "#/$defs/CatalogEntry";
@@ -6759,7 +6767,7 @@ declare const schemas: {
     readonly audience: {
         readonly $schema: "https://json-schema.org/draft/2020-12/schema";
         readonly $id: "https://openpresentation.org/schema/opf-audience/v1";
-        readonly title: "OPF Audience";
+        readonly title: "Audience";
         readonly description: "Schema for audience records in the pptx.gallery library. Each record names an audience archetype (e.g. 'executives', 'engineering-team', 'investors') and carries seniority, technical-fluency, decision-power, and attention-budget hints used by AI-driven generation. Audiences are referenced from OPF documents via audience; the engine resolves the reference against catalogs.audiences (inline) → catalogs.audiences.source → the default catalog at https://www.pptx.gallery/audiences. The audience field also accepts free-form strings; this catalog is for engine-aware audience archetypes that carry generation hints.";
         readonly type: "object";
         readonly required: ["$schema", "id", "name"];
@@ -6860,7 +6868,7 @@ declare const schemas: {
     readonly purpose: {
         readonly $schema: "https://json-schema.org/draft/2020-12/schema";
         readonly $id: "https://openpresentation.org/schema/opf-purpose/v1";
-        readonly title: "OPF Purpose";
+        readonly title: "Purpose";
         readonly description: "Schema for purpose records in the pptx.gallery library. Each record names a presentation objective such as informing, aligning, persuading, driving a decision, or selling. Purposes are referenced from OPF documents via purpose; the engine resolves the reference against catalogs.purposes (inline) → catalogs.purposes.source → the default catalog at https://www.pptx.gallery/purposes. The purpose field also accepts free-form strings and inline Purpose objects.";
         readonly type: "object";
         readonly required: ["$schema", "id", "name"];
@@ -6948,7 +6956,7 @@ declare const schemas: {
     readonly tone: {
         readonly $schema: "https://json-schema.org/draft/2020-12/schema";
         readonly $id: "https://openpresentation.org/schema/opf-tone/v1";
-        readonly title: "OPF Tone";
+        readonly title: "Tone";
         readonly description: "Schema for tone records in the pptx.gallery library. Each record names a presentation tone (e.g. 'formal', 'casual', 'inspirational') and carries voice cues, anti-patterns, and sample phrases that AI-driven generation uses to shape output. Tones are referenced from OPF documents via tone; the engine resolves the reference against catalogs.tones (inline) → catalogs.tones.source → the default catalog at https://www.pptx.gallery/tones.";
         readonly type: "object";
         readonly required: ["$schema", "id", "name"];
@@ -7045,7 +7053,7 @@ declare const schemas: {
     readonly theme: {
         readonly $schema: "https://json-schema.org/draft/2020-12/schema";
         readonly $id: "https://openpresentation.org/schema/opf-theme/v1";
-        readonly title: "OPF Theme";
+        readonly title: "Theme";
         readonly description: "Schema for theme records in the pptx.gallery library. Each theme is a small, named bundle that pairs a color scheme, a font scheme, a default theme-controlled background, and a slide size. Themes are referenced from OPF documents via design.theme or design.theme.id; the engine resolves the reference against catalogs.themes (inline) → catalogs.themes.source → the default catalog at https://www.pptx.gallery/themes. Inline overrides on design.colorScheme / design.fontScheme / design.background / design.dimensions take precedence over a resolved theme.";
         readonly type: "object";
         readonly required: ["$schema", "id", "name"];
@@ -7154,7 +7162,7 @@ declare const schemas: {
     readonly layout: {
         readonly $schema: "https://json-schema.org/draft/2020-12/schema";
         readonly $id: "https://openpresentation.org/schema/opf-layout/v1";
-        readonly title: "OPF Slide Layout";
+        readonly title: "Slide Layout";
         readonly description: "Schema for slide-layout records in the pptx.gallery library. Each record describes a semantic slide layout — what regions it exposes and what content kinds those regions are intended to hold. Layouts are referenced from OPF documents via Slide.layout; the engine resolves the reference against catalogs.layouts (inline) → catalogs.layouts.source → the default catalog at https://www.pptx.gallery/layouts. Free-form custom layout names that don't resolve through any catalog fall through to engine-defined layouts.";
         readonly type: "object";
         readonly required: ["$schema", "id", "name"];
@@ -7318,7 +7326,7 @@ declare const schemas: {
     readonly chartType: {
         readonly $schema: "https://json-schema.org/draft/2020-12/schema";
         readonly $id: "https://openpresentation.org/schema/opf-chart-type/v1";
-        readonly title: "OPF Chart Type";
+        readonly title: "Chart Type";
         readonly description: "Schema for chart-type records in the pptx.gallery catalog. Each record describes a named chart variant, its Open XML mapping, its series/category cardinality, the column structure of the underlying workbook, and a small sample dataset suitable for previews. Chart types are referenced from OPF chart content payloads; the engine resolves the reference against catalogs.chartTypes (inline) -> catalogs.chartTypes.source -> the default catalog at https://www.pptx.gallery/chart-types.";
         readonly type: "object";
         readonly additionalProperties: false;
@@ -7624,7 +7632,7 @@ declare const schemas: {
     readonly narrative: {
         readonly $schema: "https://json-schema.org/draft/2020-12/schema";
         readonly $id: "https://openpresentation.org/schema/opf-narrative/v1";
-        readonly title: "OPF Narrative Template";
+        readonly title: "Narrative Template";
         readonly description: "Schema for narrative template files in the openpresentation.org catalog. Each template describes a named story arc (e.g. 'problem-solution', 'scqa') as an ordered list of beats. Templates are referenced from OPF documents via narrative — either as a bare id string (e.g. 'classic-story') or as an inline object whose shape matches this schema (sans '$schema').";
         readonly type: "object";
         readonly required: ["$schema", "id", "name", "beats"];
@@ -7770,8 +7778,8 @@ declare const schemas: {
     readonly socialPlatform: {
         readonly $schema: "https://json-schema.org/draft/2020-12/schema";
         readonly $id: "https://openpresentation.org/schema/opf-social-platform/v1";
-        readonly title: "OPF Social Platform";
-        readonly description: "Schema for social-platform records in the pptx.gallery library. Each record describes a single social-media platform — its base URL, profile-URL pattern, handle prefix, brand color, and themed icons. Records are referenced from OPF documents indirectly: the property keys of any Socials object (Organization.socials, Speaker.socials) match record ids, and renderers use the catalog record to format URLs and pick icons. The engine resolves references against catalogs.socialPlatforms (inline) → catalogs.socialPlatforms.source → the default catalog at https://www.pptx.gallery/social-platforms.";
+        readonly title: "Social Platform";
+        readonly description: "Schema for social-platform records in the pptx.gallery library. Each record describes a single social-media platform — its base URL, profile-URL pattern, handle prefix, brand color, and themed icons. Records are referenced from OPF documents indirectly: the property keys of any Socials object (Organization.socials, Speaker.socials) match record ids, and renderers use the catalog record to format URLs and pick icons. The engine resolves references against catalogs.socialPlatforms (inline) → catalogs.socialPlatforms.source → the default catalog at https://www.pptx.gallery/social-platforms.";
         readonly type: "object";
         readonly required: ["$schema", "id", "name"];
         readonly properties: {
@@ -7783,7 +7791,7 @@ declare const schemas: {
             readonly id: {
                 readonly type: "string";
                 readonly pattern: "^[a-z][a-z0-9-]*$";
-                readonly description: "Stable slug used by OPF documents to reference this platform — appears as a property key on Socials objects. Lowercase kebab-case.";
+                readonly description: "Stable slug used by OPF documents to reference this platform — appears as a property key on Socials objects. Lowercase kebab-case.";
                 readonly examples: ["linkedin", "x", "github", "youtube", "instagram", "facebook", "tiktok", "threads", "mastodon", "bluesky"];
             };
             readonly name: {
@@ -7793,7 +7801,7 @@ declare const schemas: {
             };
             readonly summary: {
                 readonly type: "string";
-                readonly description: "One-sentence positioning of the platform — what it's used for and who's on it.";
+                readonly description: "One-sentence positioning of the platform — what it's used for and who's on it.";
                 readonly examples: ["Professional social network for individuals and companies.", "Real-time microblog for news, opinions, and discussion."];
             };
             readonly description: {
@@ -7804,7 +7812,7 @@ declare const schemas: {
             readonly baseUrl: {
                 readonly type: "string";
                 readonly format: "uri";
-                readonly description: "Canonical base URL of the platform — used as the prefix when normalizing handles to full URLs.";
+                readonly description: "Canonical base URL of the platform — used as the prefix when normalizing handles to full URLs.";
                 readonly examples: ["https://linkedin.com", "https://x.com", "https://github.com", "https://youtube.com"];
             };
             readonly profileUrlPattern: {
@@ -7881,7 +7889,7 @@ declare const schemas: {
     readonly language: {
         readonly $schema: "https://json-schema.org/draft/2020-12/schema";
         readonly $id: "https://openpresentation.org/schema/opf-language/v1";
-        readonly title: "OPF Language";
+        readonly title: "Language";
         readonly description: "Schema for language records in the pptx.gallery library. Each record names a presentation language, carries a BCP-47 language tag, and pairs it with sensible default font schemes for PowerPoint and Google Slides output. Languages are referenced from OPF documents via language; the engine resolves the reference against catalogs.languages (inline) → catalogs.languages.source → the default catalog at https://www.pptx.gallery/languages. The presentation language field also accepts BCP-47 tags directly or inline Language objects for engine-aware language records that carry default-font hints.";
         readonly type: "object";
         readonly required: ["$schema", "id", "name", "bcp47"];
@@ -7980,7 +7988,7 @@ declare const schemas: {
     readonly colorScheme: {
         readonly $schema: "https://json-schema.org/draft/2020-12/schema";
         readonly $id: "https://openpresentation.org/schema/opf-color-scheme/v1";
-        readonly title: "OPF Color Scheme";
+        readonly title: "Color Scheme";
         readonly description: "Schema for color-scheme records in the pptx.gallery library. Each scheme is a named palette with the twelve PowerPoint color slots (six accents, two darks, two lights, plus hyperlink and followed-hyperlink), suitable for being mapped directly into OOXML theme XML. Color schemes are referenced from OPF documents via design.colorScheme or design.colorScheme.id; the engine resolves the reference against catalogs.colorSchemes (inline) -> catalogs.colorSchemes.source -> the default catalog at https://www.pptx.gallery/color-schemes. Slot overrides on design.colorScheme take precedence over the resolved scheme.\n\nThe slot fields here mirror the inline-override fields on the in-document ColorScheme type (in opf.schema.json), so library entries and inline OPF overrides are interchangeable.";
         readonly type: "object";
         readonly required: ["$schema", "id", "name"];
@@ -8108,7 +8116,7 @@ declare const schemas: {
     readonly fontScheme: {
         readonly $schema: "https://json-schema.org/draft/2020-12/schema";
         readonly $id: "https://openpresentation.org/schema/opf-font-scheme/v1";
-        readonly title: "OPF Font Scheme";
+        readonly title: "Font Scheme";
         readonly description: "Schema for font-scheme records in the pptx.gallery library. Each scheme pairs a major (heading) and minor (body) font family in the OOXML majorFont/minorFont sense, scoped to a target app (PowerPoint or Google Slides) and a language family (Latin, East Asian, or Complex Script). Font schemes are referenced from OPF documents via design.fontScheme or design.fontScheme.id; the engine resolves the reference against catalogs.fontSchemes (inline) → catalogs.fontSchemes.source → the default catalog at https://www.pptx.gallery/font-schemes. Role overrides on design.fontScheme (heading, body, accent, code) take precedence over the resolved scheme.";
         readonly type: "object";
         readonly required: ["$schema", "id", "name", "major", "minor"];
@@ -8219,8 +8227,8 @@ declare const schemaEntries: readonly [{
     readonly schema: {
         readonly $schema: "https://json-schema.org/draft/2020-12/schema";
         readonly $id: "https://openpresentation.org/schema/opf/v1";
-        readonly title: "OPF — Open Presentation Format";
-        readonly description: "Open-source JSON format for describing PowerPoint presentations. Agents describe narratives, content, audience, reusable assets, and design — the engine handles OOXML complexity.\n\nFields that reference catalog records (narrative, language, tone, audience, purpose, design.theme / design.theme.id, design.colorScheme / design.colorScheme.id, design.fontScheme / design.fontScheme.id, Slide.layout, Chart.type, Organization.socials / Speaker.socials) resolve through the catalog system: inline 'catalogs.<kind>.records[]' on the document → 'catalogs.<kind>.source' on the document → engine defaults → the default catalog at https://www.pptx.gallery/<kind>. Every reference resolves to the catalog record's 'id' field. When an OPF document omits a reference entirely, the engine falls back to engine defaults (see /spec/reference/engine-defaults.json for a reference example). The defaults file is engine configuration; it is not part of the OPF document contract and has no JSON Schema.\n\nMost catalog references accept the bare 'id' as a string for the common case (e.g. narrative = 'classic-story', design.colorScheme = 'cool-horizon'). Audience, purpose, tone, design, and language object forms use 'id' as a base catalog reference plus inline overrides. Asset references use 'asset:<id>' strings that point into the top-level assets registry.";
+        readonly title: "Presentation";
+        readonly description: "Open-source JSON format for describing PowerPoint presentations. Agents describe narratives, content, audience, reusable assets, and design — the engine handles OOXML complexity.\n\nFields that reference catalog records (narrative, language, tone, audience, purpose, design.theme / design.theme.id, design.colorScheme / design.colorScheme.id, design.fontScheme / design.fontScheme.id, Slide.layout, Chart.type, Organization.socials / Speaker.socials) resolve through the catalog system: inline 'catalogs.<kind>.records[]' on the document → 'catalogs.<kind>.source' on the document → engine defaults → the default catalog at https://www.pptx.gallery/<kind>. Every reference resolves to the catalog record's 'id' field. When an OPF document omits a reference entirely, the engine falls back to engine defaults (see /spec/reference/engine-defaults.json for a reference example). The defaults file is engine configuration; it is not part of the OPF document contract and has no JSON Schema.\n\nMost catalog references accept the bare 'id' as a string for the common case (e.g. narrative = 'classic-story', design.colorScheme = 'cool-horizon'). Audience, purpose, tone, design, and language object forms use 'id' as a base catalog reference plus inline overrides. Asset references use 'asset:<id>' strings that point into the top-level assets registry.";
         readonly type: "object";
         readonly required: ["slides"];
         readonly additionalProperties: false;
@@ -8233,11 +8241,11 @@ declare const schemaEntries: readonly [{
             readonly name: {
                 readonly type: "string";
                 readonly description: "Display name of the presentation for GUI/TUI lists, library/search indexing, OS-level metadata, and default export filenames. This is deck identity, not slide content. Use slides[].title and slides[].subtitle for text that should appear on presented slides.";
-                readonly examples: ["Q4 2026 Business Review", "Series B Pitch — Acme", "The Future of Agentic Workflows"];
+                readonly examples: ["Q4 2026 Business Review", "Series B Pitch — Acme", "The Future of Agentic Workflows"];
             };
             readonly description: {
                 readonly type: "string";
-                readonly description: "Free-form prose describing what this presentation is about. Used by agents and humans as a deck-level summary; complements purpose (the goal) and narrative (the structured storyline). Round-trips to OOXML 'docProps/core.xml' as '<dc:description>' (PowerPoint surfaces this as the 'Comments' field in File → Properties).";
+                readonly description: "Free-form prose describing what this presentation is about. Used by agents and humans as a deck-level summary; complements purpose (the goal) and narrative (the structured storyline). Round-trips to OOXML 'docProps/core.xml' as '<dc:description>' (PowerPoint surfaces this as the 'Comments' field in File → Properties).";
                 readonly examples: ["Quarterly business review covering revenue, product, and hiring milestones for the executive team."];
             };
             readonly filename: {
@@ -8283,17 +8291,21 @@ declare const schemaEntries: readonly [{
                 readonly examples: ["Bob Lee", ["Bob Lee", "Carla Diaz"]];
             };
             readonly audience: {
-                readonly type: "array";
-                readonly items: {
-                    readonly oneOf: [{
-                        readonly type: "string";
-                    }, {
-                        readonly $ref: "#/$defs/Audience";
-                    }];
-                };
-                readonly minItems: 1;
-                readonly description: "Intended audiences for the presentation. Each item accepts either:\n- A string shorthand: free-form description ('Series B investors'), an audiences catalog id ('executives'), an HTTPS URL, or a 'pkg:' reference.\n- An inline Audience object for custom audience metadata or catalog-backed overrides. Object form mirrors https://openpresentation.org/schema/opf-audience/v1 without '$schema'.\n\nResolution order for catalog ids and references: inline catalogs.audiences.records[] → catalogs.audiences.source → default catalog at https://www.pptx.gallery/audiences.";
-                readonly examples: [["executives"], ["board", "c-suite"], ["Series B investors", "https://acme.com/decks/audiences/acme-board.json"], [{
+                readonly oneOf: [{
+                    readonly type: "string";
+                }, {
+                    readonly type: "array";
+                    readonly items: {
+                        readonly oneOf: [{
+                            readonly type: "string";
+                        }, {
+                            readonly $ref: "#/$defs/Audience";
+                        }];
+                    };
+                    readonly minItems: 1;
+                }];
+                readonly description: "Intended audiences for the presentation. Accepts either:\n- A single string shorthand: free-form description ('Series B investors'), an audiences catalog id ('executives'), an HTTPS URL, or a 'pkg:' reference.\n- An array of string shorthands and/or inline Audience objects for custom audience metadata or catalog-backed overrides. Object form mirrors https://openpresentation.org/schema/opf-audience/v1 without '$schema'.\n\nResolution order for catalog ids and references: inline catalogs.audiences.records[] → catalogs.audiences.source → default catalog at https://www.pptx.gallery/audiences.";
+                readonly examples: ["executives", "Biology Students and Wildlife Enthusiasts", ["executives"], ["board", "c-suite"], ["Series B investors", "https://acme.com/decks/audiences/acme-board.json"], [{
                     readonly id: "executives";
                     readonly attentionBudgetMinutes: 20;
                 }, {
@@ -8309,7 +8321,7 @@ declare const schemaEntries: readonly [{
                 }, {
                     readonly $ref: "#/$defs/Purpose";
                 }];
-                readonly description: "Primary goal of the presentation. Accepts either:\n- A string shorthand: free-form goal ('Raise a Series B round of $30M'), a purposes catalog id ('decide', 'align'), an HTTPS URL, or a 'pkg:' reference.\n- An inline Purpose object for custom purpose metadata or catalog-backed overrides. Object form mirrors https://openpresentation.org/schema/opf-purpose/v1 without '$schema'.\n\nResolution order for catalog ids and references: inline catalogs.purposes.records[] → catalogs.purposes.source → default catalog at https://www.pptx.gallery/purposes.";
+                readonly description: "Primary goal of the presentation. Accepts either:\n- A string shorthand: free-form goal ('Raise a Series B round of $30M'), a purposes catalog id ('decide', 'align'), an HTTPS URL, or a 'pkg:' reference.\n- An inline Purpose object for custom purpose metadata or catalog-backed overrides. Object form mirrors https://openpresentation.org/schema/opf-purpose/v1 without '$schema'.\n\nResolution order for catalog ids and references: inline catalogs.purposes.records[] → catalogs.purposes.source → default catalog at https://www.pptx.gallery/purposes.";
                 readonly examples: ["Raise a Series B round of $30M", "align", "educate", "https://acme.com/decks/purposes/fundraise.json", "pkg:@acme/decks/purposes/fundraise", {
                     readonly id: "decide";
                     readonly outcome: "Approve the Q4 hiring plan";
@@ -8324,7 +8336,7 @@ declare const schemaEntries: readonly [{
                 }, {
                     readonly $ref: "#/$defs/Language";
                 }];
-                readonly description: "Language for the presentation content. Accepts either:\n- A string shorthand: a BCP-47 language tag ('en-US', 'en-GB', 'ja-JP', 'fr'), a languages catalog id ('english', 'japanese'), an HTTPS URL, or a 'pkg:' reference.\n- An inline Language object for custom language metadata or catalog-backed overrides. Object form mirrors https://openpresentation.org/schema/opf-language/v1 without '$schema'.\n\nResolution order for catalog ids and references: inline catalogs.languages.records[] → catalogs.languages.source → default catalog at https://www.pptx.gallery/languages.";
+                readonly description: "Language for the presentation content. Accepts either:\n- A string shorthand: a BCP-47 language tag ('en-US', 'en-GB', 'ja-JP', 'fr'), a languages catalog id ('english', 'japanese'), an HTTPS URL, or a 'pkg:' reference.\n- An inline Language object for custom language metadata or catalog-backed overrides. Object form mirrors https://openpresentation.org/schema/opf-language/v1 without '$schema'.\n\nResolution order for catalog ids and references: inline catalogs.languages.records[] → catalogs.languages.source → default catalog at https://www.pptx.gallery/languages.";
                 readonly examples: ["en-US", "en-GB", "es-MX", "ja-JP", "fr", "english", "japanese", "https://acme.com/decks/languages/en-acme.json", "pkg:@acme/decks/languages/en-acme", {
                     readonly id: "english";
                     readonly bcp47: "en-US";
@@ -8343,7 +8355,7 @@ declare const schemaEntries: readonly [{
                 }, {
                     readonly $ref: "#/$defs/Tone";
                 }];
-                readonly description: "Desired tone for the presentation. Accepts either:\n- A string shorthand: a tones catalog id ('formal'), an HTTPS URL, or a 'pkg:' reference.\n- An inline Tone object for custom tone metadata or catalog-backed overrides. Object form mirrors https://openpresentation.org/schema/opf-tone/v1 without '$schema'.\n\nResolution order for catalog ids and references: inline catalogs.tones.records[] → catalogs.tones.source → default catalog at https://www.pptx.gallery/tones.";
+                readonly description: "Desired tone for the presentation. Accepts either:\n- A string shorthand: a tones catalog id ('formal'), an HTTPS URL, or a 'pkg:' reference.\n- An inline Tone object for custom tone metadata or catalog-backed overrides. Object form mirrors https://openpresentation.org/schema/opf-tone/v1 without '$schema'.\n\nResolution order for catalog ids and references: inline catalogs.tones.records[] → catalogs.tones.source → default catalog at https://www.pptx.gallery/tones.";
                 readonly examples: ["formal", "casual", "inspirational", "technical", "persuasive", "https://acme.com/decks/tones/acme-voice.json", "pkg:@acme/decks/tones/acme-voice", {
                     readonly id: "formal";
                     readonly voiceCues: ["Use precise, concise language."];
@@ -8388,7 +8400,7 @@ declare const schemaEntries: readonly [{
                 }, {
                     readonly $ref: "#/$defs/Narrative";
                 }];
-                readonly description: "Structured storyline describing the deck's arc and beats. Resolves to the 'id' of a 'narratives' catalog record.\n\nAccepts two forms:\n- String shorthand for the common case: 'narrative = \"classic-story\"'. Accepts a bare id (lowercase kebab-case), an HTTPS URL pointing at a record file, or a 'pkg:' reference to a locally-installed package.\n- Object form for inline overrides or fully custom narratives: 'narrative = { id: \"classic-story\", beats: [...] }'. The object shape mirrors https://openpresentation.org/schema/opf-narrative/v1 (sans '$schema'), so a library record and an inline narrative are interchangeable.\n\nResolution order: inline catalogs.narratives.records[] → catalogs.narratives.source → default catalog at https://www.pptx.gallery/narratives. Unknown ids produce a validation warning, not an error.\n\nDeck-level concerns that aren't part of the storyline (audience, tone, takeaway, duration) live as siblings on the presentation root rather than inside the narrative object.";
+                readonly description: "Structured storyline describing the deck's arc and beats. Resolves to the 'id' of a 'narratives' catalog record.\n\nAccepts two forms:\n- String shorthand for the common case: 'narrative = \"classic-story\"'. Accepts a bare id (lowercase kebab-case), an HTTPS URL pointing at a record file, or a 'pkg:' reference to a locally-installed package.\n- Object form for inline overrides or fully custom narratives: 'narrative = { id: \"classic-story\", beats: [...] }'. The object shape mirrors https://openpresentation.org/schema/opf-narrative/v1 (sans '$schema'), so a library record and an inline narrative are interchangeable.\n\nResolution order: inline catalogs.narratives.records[] → catalogs.narratives.source → default catalog at https://www.pptx.gallery/narratives. Unknown ids produce a validation warning, not an error.\n\nDeck-level concerns that aren't part of the storyline (audience, tone, takeaway, duration) live as siblings on the presentation root rather than inside the narrative object.";
                 readonly examples: ["classic-story", "problem-solution", "scqa", "pitch-deck", {
                     readonly id: "custom-pitch";
                     readonly name: "Custom Pitch";
@@ -8746,7 +8758,7 @@ declare const schemaEntries: readonly [{
             };
             readonly Organization: {
                 readonly type: "object";
-                readonly description: "An organization associated with the presentation — typically the presenting company, but also hosts, partners, clients, or sponsors. Surfaced on cover slides, footers, and brand bars; the primary organization's logo is the default deck logo unless overridden by design.logo.";
+                readonly description: "An organization associated with the presentation — typically the presenting company, but also hosts, partners, clients, or sponsors. Surfaced on cover slides, footers, and brand bars; the primary organization's logo is the default deck logo unless overridden by design.logo.";
                 readonly required: ["id", "name"];
                 readonly properties: {
                     readonly id: {
@@ -8857,7 +8869,7 @@ declare const schemaEntries: readonly [{
             };
             readonly Socials: {
                 readonly type: "object";
-                readonly description: "Social media handles or URLs, keyed by platform id from the 'socialPlatforms' catalog. Each value is a string — either a full URL or a platform handle (e.g., '@acme'). The catalog record for each platform carries the URL pattern, handle prefix, brand color, and themed icons used by renderers.\n\nKeys resolve to the 'id' of a 'socialPlatforms' catalog record. Resolution order: inline catalogs.socialPlatforms.records[] → catalogs.socialPlatforms.source → default catalog at https://www.pptx.gallery/social-platforms. Unknown platform keys render with engine fallbacks (the raw value as text). Used both for organization and speaker records.";
+                readonly description: "Social media handles or URLs, keyed by platform id from the 'socialPlatforms' catalog. Each value is a string — either a full URL or a platform handle (e.g., '@acme'). The catalog record for each platform carries the URL pattern, handle prefix, brand color, and themed icons used by renderers.\n\nKeys resolve to the 'id' of a 'socialPlatforms' catalog record. Resolution order: inline catalogs.socialPlatforms.records[] → catalogs.socialPlatforms.source → default catalog at https://www.pptx.gallery/social-platforms. Unknown platform keys render with engine fallbacks (the raw value as text). Used both for organization and speaker records.";
                 readonly additionalProperties: {
                     readonly type: "string";
                     readonly description: "Handle or URL for the platform identified by the property key.";
@@ -8878,7 +8890,7 @@ declare const schemaEntries: readonly [{
             };
             readonly Narrative: {
                 readonly type: "object";
-                readonly description: "Structured storyline used by AI to shape generated content. Mirrors the OPF Narrative Template record at https://openpresentation.org/schema/opf-narrative/v1 (sans '$schema'), so a library record and an inline narrative are interchangeable.\n\nNarrative declares the deck's intended story arc; slides may opt into beats via Slide.beat. The narrative does not constrain slide structure — validators warn on drift (orphan slides, unused beats) but never error. Slides are the source of truth; narrative is intent that travels with the deck.\n\nWhen 'id' matches a record in the resolved 'narratives' catalog, the inline fields override matching fields on the catalog record (beats merge by beat 'id'). When 'id' doesn't match, this object defines a fully custom inline narrative.\n\nDeck-level concerns that aren't part of the storyline (audience, tone, takeaway, duration) live as siblings on the presentation root rather than inside this object.";
+                readonly description: "Structured storyline used by AI to shape generated content. Mirrors the OPF Narrative Template record at https://openpresentation.org/schema/opf-narrative/v1 (sans '$schema'), so a library record and an inline narrative are interchangeable.\n\nNarrative declares the deck's intended story arc; slides may opt into beats via Slide.beat. The narrative does not constrain slide structure — validators warn on drift (orphan slides, unused beats) but never error. Slides are the source of truth; narrative is intent that travels with the deck.\n\nWhen 'id' matches a record in the resolved 'narratives' catalog, the inline fields override matching fields on the catalog record (beats merge by beat 'id'). When 'id' doesn't match, this object defines a fully custom inline narrative.\n\nDeck-level concerns that aren't part of the storyline (audience, tone, takeaway, duration) live as siblings on the presentation root rather than inside this object.";
                 readonly properties: {
                     readonly id: {
                         readonly type: "string";
@@ -8889,7 +8901,7 @@ declare const schemaEntries: readonly [{
                     readonly name: {
                         readonly type: "string";
                         readonly description: "Human-readable narrative name.";
-                        readonly examples: ["Classic Story", "Problem → Solution", "SCQA", "Founder Pitch"];
+                        readonly examples: ["Classic Story", "Problem → Solution", "SCQA", "Founder Pitch"];
                     };
                     readonly summary: {
                         readonly type: "string";
@@ -8962,7 +8974,7 @@ declare const schemaEntries: readonly [{
             };
             readonly NarrativeBeat: {
                 readonly type: "object";
-                readonly description: "A single narrative beat — a labeled segment of the story arc with a specific dramatic purpose (e.g. 'hook', 'problem', 'evidence', 'ask'). Slides reference beats via Slide.beat. Beats may also carry slide-blueprint hints (slideType, layoutHint, thoughtCues, instructions) that guide the assigned slide.\n\nMirrors the Beat definition in narrative.schema.json (https://openpresentation.org/schema/opf-narrative/v1) so library entries and inline OPF beats are interchangeable.";
+                readonly description: "A single narrative beat — a labeled segment of the story arc with a specific dramatic purpose (e.g. 'hook', 'problem', 'evidence', 'ask'). Slides reference beats via Slide.beat. Beats may also carry slide-blueprint hints (slideType, layoutHint, thoughtCues, instructions) that guide the assigned slide.\n\nMirrors the Beat definition in narrative.schema.json (https://openpresentation.org/schema/opf-narrative/v1) so library entries and inline OPF beats are interchangeable.";
                 readonly required: ["id", "name"];
                 readonly properties: {
                     readonly id: {
@@ -8983,7 +8995,7 @@ declare const schemaEntries: readonly [{
                     };
                     readonly instructions: {
                         readonly type: "string";
-                        readonly description: "Short author-facing instruction for the beat — typically one phrase. Complements 'description' with a concise directive.";
+                        readonly description: "Short author-facing instruction for the beat — typically one phrase. Complements 'description' with a concise directive.";
                         readonly examples: ["Capture audience attention", "Introduce problem", "Detail implementation", "Inspire & conclude"];
                     };
                     readonly slideCount: {
@@ -8998,7 +9010,7 @@ declare const schemaEntries: readonly [{
                     };
                     readonly layoutHint: {
                         readonly type: "string";
-                        readonly description: "Suggested layout id for the beat's opening slide. Resolves the same way as Slide.layout — against catalogs.layouts and the default catalog at https://www.pptx.gallery/layouts.";
+                        readonly description: "Suggested layout id for the beat's opening slide. Resolves the same way as Slide.layout — against catalogs.layouts and the default catalog at https://www.pptx.gallery/layouts.";
                         readonly examples: ["section-divider", "title-slide", "title-left", "two-column", "text-left"];
                     };
                     readonly thoughtCues: {
@@ -9410,12 +9422,12 @@ declare const schemaEntries: readonly [{
                     };
                     readonly major: {
                         readonly type: "string";
-                        readonly description: "Heading (major) font family — mirrors the OOXML majorFont entry. Pairs with 'minor'.";
+                        readonly description: "Heading (major) font family — mirrors the OOXML majorFont entry. Pairs with 'minor'.";
                         readonly examples: ["Aptos Display", "Calibri", "Microsoft YaHei", "Arial Black"];
                     };
                     readonly minor: {
                         readonly type: "string";
-                        readonly description: "Body (minor) font family — mirrors the OOXML minorFont entry. Pairs with 'major'.";
+                        readonly description: "Body (minor) font family — mirrors the OOXML minorFont entry. Pairs with 'major'.";
                         readonly examples: ["Aptos", "Calibri", "Microsoft YaHei", "Arial"];
                     };
                     readonly type: {
@@ -9852,7 +9864,7 @@ declare const schemaEntries: readonly [{
                     };
                     readonly layout: {
                         readonly type: "string";
-                        readonly description: "Optional slide layout reference. Resolves to the 'id' of a 'layouts' catalog record. When omitted, engines infer a layout from the slide's root payload or promoted region keys. Accepts a bare id (lowercase kebab-case, e.g. 'title-subtitle'), an HTTPS URL pointing at a record file, or a 'pkg:' reference. Free-form custom layout names that don't resolve through any catalog fall through to engine-defined layouts.\n\nResolution order: inline catalogs.layouts.records[] → catalogs.layouts.source → default catalog at https://www.pptx.gallery/layouts.";
+                        readonly description: "Optional slide layout reference. Resolves to the 'id' of a 'layouts' catalog record. When omitted, engines infer a layout from the slide's root payload or promoted region keys. Accepts a bare id (lowercase kebab-case, e.g. 'title-subtitle'), an HTTPS URL pointing at a record file, or a 'pkg:' reference. Free-form custom layout names that don't resolve through any catalog fall through to engine-defined layouts.\n\nResolution order: inline catalogs.layouts.records[] → catalogs.layouts.source → default catalog at https://www.pptx.gallery/layouts.";
                         readonly examples: ["title", "title-subtitle", "text-2x", "chart-3x", "image-bleed", "blank", "https://acme.com/decks/layouts/cover.json", "pkg:@acme/decks/layouts/cover"];
                     };
                     readonly title: {
@@ -9886,7 +9898,7 @@ declare const schemaEntries: readonly [{
                         readonly items: {
                             readonly $ref: "#/$defs/ListItem";
                         };
-                        readonly description: "Full-slide generic list payload. Presence of this field infers type 'list'.";
+                        readonly 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.";
                     };
                     readonly bullets: {
                         readonly type: "array";
@@ -9946,7 +9958,7 @@ declare const schemaEntries: readonly [{
                         readonly items: {
                             readonly $ref: "#/$defs/ContentPayload";
                         };
-                        readonly description: "Layout-agnostic content blocks rendered together as a composed payload when exact placement is unspecified.";
+                        readonly description: "Layout-agnostic content blocks rendered together as a composed payload when exact placement is unspecified. At slide root, multiple content payload kinds with no explicit type, blocks, or regions are accepted as shorthand for equivalent blocks.";
                     };
                     readonly design: {
                         readonly $ref: "#/$defs/Design";
@@ -10786,7 +10798,7 @@ declare const schemaEntries: readonly [{
             };
             readonly Catalogs: {
                 readonly type: "object";
-                readonly description: "Catalog overrides for the in-document references. Every property is optional. The default catalog for a kind lives at https://www.pptx.gallery/<kind> (e.g. https://www.pptx.gallery/narratives, https://www.pptx.gallery/themes). For each kind, declaring a 'source' replaces the default registry and/or 'records' adds inline records that take precedence over anything fetched from a source.\n\nResolution order for any reference (e.g. narrative, design.theme): inline catalogs.<kind>.records[] → catalogs.<kind>.source → default catalog at https://www.pptx.gallery/<kind>. Every reference resolves to the catalog record's 'id' field. References that are themselves URLs or 'pkg:' references skip the catalog lookup and resolve directly.";
+                readonly description: "Catalog overrides for the in-document references. Every property is optional. The default catalog for a kind lives at https://www.pptx.gallery/<kind> (e.g. https://www.pptx.gallery/narratives, https://www.pptx.gallery/themes). For each kind, declaring a 'source' replaces the default registry and/or 'records' adds inline records that take precedence over anything fetched from a source.\n\nResolution order for any reference (e.g. narrative, design.theme): inline catalogs.<kind>.records[] → catalogs.<kind>.source → default catalog at https://www.pptx.gallery/<kind>. Every reference resolves to the catalog record's 'id' field. References that are themselves URLs or 'pkg:' references skip the catalog lookup and resolve directly.";
                 readonly properties: {
                     readonly narratives: {
                         readonly $ref: "#/$defs/CatalogEntry";
@@ -10873,7 +10885,7 @@ declare const schemaEntries: readonly [{
     readonly schema: {
         readonly $schema: "https://json-schema.org/draft/2020-12/schema";
         readonly $id: "https://openpresentation.org/schema/opf-audience/v1";
-        readonly title: "OPF Audience";
+        readonly title: "Audience";
         readonly description: "Schema for audience records in the pptx.gallery library. Each record names an audience archetype (e.g. 'executives', 'engineering-team', 'investors') and carries seniority, technical-fluency, decision-power, and attention-budget hints used by AI-driven generation. Audiences are referenced from OPF documents via audience; the engine resolves the reference against catalogs.audiences (inline) → catalogs.audiences.source → the default catalog at https://www.pptx.gallery/audiences. The audience field also accepts free-form strings; this catalog is for engine-aware audience archetypes that carry generation hints.";
         readonly type: "object";
         readonly required: ["$schema", "id", "name"];
@@ -10977,7 +10989,7 @@ declare const schemaEntries: readonly [{
     readonly schema: {
         readonly $schema: "https://json-schema.org/draft/2020-12/schema";
         readonly $id: "https://openpresentation.org/schema/opf-purpose/v1";
-        readonly title: "OPF Purpose";
+        readonly title: "Purpose";
         readonly description: "Schema for purpose records in the pptx.gallery library. Each record names a presentation objective such as informing, aligning, persuading, driving a decision, or selling. Purposes are referenced from OPF documents via purpose; the engine resolves the reference against catalogs.purposes (inline) → catalogs.purposes.source → the default catalog at https://www.pptx.gallery/purposes. The purpose field also accepts free-form strings and inline Purpose objects.";
         readonly type: "object";
         readonly required: ["$schema", "id", "name"];
@@ -11068,7 +11080,7 @@ declare const schemaEntries: readonly [{
     readonly schema: {
         readonly $schema: "https://json-schema.org/draft/2020-12/schema";
         readonly $id: "https://openpresentation.org/schema/opf-tone/v1";
-        readonly title: "OPF Tone";
+        readonly title: "Tone";
         readonly description: "Schema for tone records in the pptx.gallery library. Each record names a presentation tone (e.g. 'formal', 'casual', 'inspirational') and carries voice cues, anti-patterns, and sample phrases that AI-driven generation uses to shape output. Tones are referenced from OPF documents via tone; the engine resolves the reference against catalogs.tones (inline) → catalogs.tones.source → the default catalog at https://www.pptx.gallery/tones.";
         readonly type: "object";
         readonly required: ["$schema", "id", "name"];
@@ -11168,7 +11180,7 @@ declare const schemaEntries: readonly [{
     readonly schema: {
         readonly $schema: "https://json-schema.org/draft/2020-12/schema";
         readonly $id: "https://openpresentation.org/schema/opf-theme/v1";
-        readonly title: "OPF Theme";
+        readonly title: "Theme";
         readonly description: "Schema for theme records in the pptx.gallery library. Each theme is a small, named bundle that pairs a color scheme, a font scheme, a default theme-controlled background, and a slide size. Themes are referenced from OPF documents via design.theme or design.theme.id; the engine resolves the reference against catalogs.themes (inline) → catalogs.themes.source → the default catalog at https://www.pptx.gallery/themes. Inline overrides on design.colorScheme / design.fontScheme / design.background / design.dimensions take precedence over a resolved theme.";
         readonly type: "object";
         readonly required: ["$schema", "id", "name"];
@@ -11280,7 +11292,7 @@ declare const schemaEntries: readonly [{
     readonly schema: {
         readonly $schema: "https://json-schema.org/draft/2020-12/schema";
         readonly $id: "https://openpresentation.org/schema/opf-layout/v1";
-        readonly title: "OPF Slide Layout";
+        readonly title: "Slide Layout";
         readonly description: "Schema for slide-layout records in the pptx.gallery library. Each record describes a semantic slide layout — what regions it exposes and what content kinds those regions are intended to hold. Layouts are referenced from OPF documents via Slide.layout; the engine resolves the reference against catalogs.layouts (inline) → catalogs.layouts.source → the default catalog at https://www.pptx.gallery/layouts. Free-form custom layout names that don't resolve through any catalog fall through to engine-defined layouts.";
         readonly type: "object";
         readonly required: ["$schema", "id", "name"];
@@ -11447,7 +11459,7 @@ declare const schemaEntries: readonly [{
     readonly schema: {
         readonly $schema: "https://json-schema.org/draft/2020-12/schema";
         readonly $id: "https://openpresentation.org/schema/opf-chart-type/v1";
-        readonly title: "OPF Chart Type";
+        readonly title: "Chart Type";
         readonly description: "Schema for chart-type records in the pptx.gallery catalog. Each record describes a named chart variant, its Open XML mapping, its series/category cardinality, the column structure of the underlying workbook, and a small sample dataset suitable for previews. Chart types are referenced from OPF chart content payloads; the engine resolves the reference against catalogs.chartTypes (inline) -> catalogs.chartTypes.source -> the default catalog at https://www.pptx.gallery/chart-types.";
         readonly type: "object";
         readonly additionalProperties: false;
@@ -11756,7 +11768,7 @@ declare const schemaEntries: readonly [{
     readonly schema: {
         readonly $schema: "https://json-schema.org/draft/2020-12/schema";
         readonly $id: "https://openpresentation.org/schema/opf-narrative/v1";
-        readonly title: "OPF Narrative Template";
+        readonly title: "Narrative Template";
         readonly description: "Schema for narrative template files in the openpresentation.org catalog. Each template describes a named story arc (e.g. 'problem-solution', 'scqa') as an ordered list of beats. Templates are referenced from OPF documents via narrative — either as a bare id string (e.g. 'classic-story') or as an inline object whose shape matches this schema (sans '$schema').";
         readonly type: "object";
         readonly required: ["$schema", "id", "name", "beats"];
@@ -11905,8 +11917,8 @@ declare const schemaEntries: readonly [{
     readonly schema: {
         readonly $schema: "https://json-schema.org/draft/2020-12/schema";
         readonly $id: "https://openpresentation.org/schema/opf-social-platform/v1";
-        readonly title: "OPF Social Platform";
-        readonly description: "Schema for social-platform records in the pptx.gallery library. Each record describes a single social-media platform — its base URL, profile-URL pattern, handle prefix, brand color, and themed icons. Records are referenced from OPF documents indirectly: the property keys of any Socials object (Organization.socials, Speaker.socials) match record ids, and renderers use the catalog record to format URLs and pick icons. The engine resolves references against catalogs.socialPlatforms (inline) → catalogs.socialPlatforms.source → the default catalog at https://www.pptx.gallery/social-platforms.";
+        readonly title: "Social Platform";
+        readonly description: "Schema for social-platform records in the pptx.gallery library. Each record describes a single social-media platform — its base URL, profile-URL pattern, handle prefix, brand color, and themed icons. Records are referenced from OPF documents indirectly: the property keys of any Socials object (Organization.socials, Speaker.socials) match record ids, and renderers use the catalog record to format URLs and pick icons. The engine resolves references against catalogs.socialPlatforms (inline) → catalogs.socialPlatforms.source → the default catalog at https://www.pptx.gallery/social-platforms.";
         readonly type: "object";
         readonly required: ["$schema", "id", "name"];
         readonly properties: {
@@ -11918,7 +11930,7 @@ declare const schemaEntries: readonly [{
             readonly id: {
                 readonly type: "string";
                 readonly pattern: "^[a-z][a-z0-9-]*$";
-                readonly description: "Stable slug used by OPF documents to reference this platform — appears as a property key on Socials objects. Lowercase kebab-case.";
+                readonly description: "Stable slug used by OPF documents to reference this platform — appears as a property key on Socials objects. Lowercase kebab-case.";
                 readonly examples: ["linkedin", "x", "github", "youtube", "instagram", "facebook", "tiktok", "threads", "mastodon", "bluesky"];
             };
             readonly name: {
@@ -11928,7 +11940,7 @@ declare const schemaEntries: readonly [{
             };
             readonly summary: {
                 readonly type: "string";
-                readonly description: "One-sentence positioning of the platform — what it's used for and who's on it.";
+                readonly description: "One-sentence positioning of the platform — what it's used for and who's on it.";
                 readonly examples: ["Professional social network for individuals and companies.", "Real-time microblog for news, opinions, and discussion."];
             };
             readonly description: {
@@ -11939,7 +11951,7 @@ declare const schemaEntries: readonly [{
             readonly baseUrl: {
                 readonly type: "string";
                 readonly format: "uri";
-                readonly description: "Canonical base URL of the platform — used as the prefix when normalizing handles to full URLs.";
+                readonly description: "Canonical base URL of the platform — used as the prefix when normalizing handles to full URLs.";
                 readonly examples: ["https://linkedin.com", "https://x.com", "https://github.com", "https://youtube.com"];
             };
             readonly profileUrlPattern: {
@@ -12019,7 +12031,7 @@ declare const schemaEntries: readonly [{
     readonly schema: {
         readonly $schema: "https://json-schema.org/draft/2020-12/schema";
         readonly $id: "https://openpresentation.org/schema/opf-language/v1";
-        readonly title: "OPF Language";
+        readonly title: "Language";
         readonly description: "Schema for language records in the pptx.gallery library. Each record names a presentation language, carries a BCP-47 language tag, and pairs it with sensible default font schemes for PowerPoint and Google Slides output. Languages are referenced from OPF documents via language; the engine resolves the reference against catalogs.languages (inline) → catalogs.languages.source → the default catalog at https://www.pptx.gallery/languages. The presentation language field also accepts BCP-47 tags directly or inline Language objects for engine-aware language records that carry default-font hints.";
         readonly type: "object";
         readonly required: ["$schema", "id", "name", "bcp47"];
@@ -12121,7 +12133,7 @@ declare const schemaEntries: readonly [{
     readonly schema: {
         readonly $schema: "https://json-schema.org/draft/2020-12/schema";
         readonly $id: "https://openpresentation.org/schema/opf-color-scheme/v1";
-        readonly title: "OPF Color Scheme";
+        readonly title: "Color Scheme";
         readonly description: "Schema for color-scheme records in the pptx.gallery library. Each scheme is a named palette with the twelve PowerPoint color slots (six accents, two darks, two lights, plus hyperlink and followed-hyperlink), suitable for being mapped directly into OOXML theme XML. Color schemes are referenced from OPF documents via design.colorScheme or design.colorScheme.id; the engine resolves the reference against catalogs.colorSchemes (inline) -> catalogs.colorSchemes.source -> the default catalog at https://www.pptx.gallery/color-schemes. Slot overrides on design.colorScheme take precedence over the resolved scheme.\n\nThe slot fields here mirror the inline-override fields on the in-document ColorScheme type (in opf.schema.json), so library entries and inline OPF overrides are interchangeable.";
         readonly type: "object";
         readonly required: ["$schema", "id", "name"];
@@ -12252,7 +12264,7 @@ declare const schemaEntries: readonly [{
     readonly schema: {
         readonly $schema: "https://json-schema.org/draft/2020-12/schema";
         readonly $id: "https://openpresentation.org/schema/opf-font-scheme/v1";
-        readonly title: "OPF Font Scheme";
+        readonly title: "Font Scheme";
         readonly description: "Schema for font-scheme records in the pptx.gallery library. Each scheme pairs a major (heading) and minor (body) font family in the OOXML majorFont/minorFont sense, scoped to a target app (PowerPoint or Google Slides) and a language family (Latin, East Asian, or Complex Script). Font schemes are referenced from OPF documents via design.fontScheme or design.fontScheme.id; the engine resolves the reference against catalogs.fontSchemes (inline) → catalogs.fontSchemes.source → the default catalog at https://www.pptx.gallery/font-schemes. Role overrides on design.fontScheme (heading, body, accent, code) take precedence over the resolved scheme.";
         readonly type: "object";
         readonly required: ["$schema", "id", "name", "major", "minor"];