@openpresentation/opf 0.2.1 → 0.3.0

package/dist/{validator-D7WwzKyx.d.ts → presentation-C8BOK0-5.d.ts}

@@ -1,13 +1,3 @@
-import { CatalogKind } from './catalogs.js';
-import { SchemaName } from './schemas.js';
-
-type JsonPrimitive = string | number | boolean | null;
-type JsonValue = JsonPrimitive | JsonObject | JsonValue[];
-interface JsonObject {
-    readonly [key: string]: JsonValue;
-}
-type JsonSchema = JsonObject;
-
 /**
  * Inline audience metadata for the presentation. Use 'id' to reference an audiences catalog record and override selected fields, or use 'name' for a custom inline audience.
  *
@@ -550,15 +540,13 @@ interface Presentation {
      */
     author?: (string | [string, ...(string)[]]);
     /**
-     * Intended audiences for the presentation. Each item accepts either:
-     * - A string shorthand: free-form description ('Series B investors'), an audiences catalog id ('executives'), an HTTPS URL, or a 'pkg:' reference.
-     * - An inline Audience object for custom audience metadata or catalog-backed overrides. Object form mirrors https://openpresentation.org/schema/opf-audience/v1 without '$schema'.
+     * Intended audiences for the presentation. Accepts either:
+     * - A single string shorthand: free-form description ('Series B investors'), an audiences catalog id ('executives'), an HTTPS URL, or a 'pkg:' reference.
+     * - 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'.
      *
      * Resolution order for catalog ids and references: inline catalogs.audiences.records[] → catalogs.audiences.source → default catalog at https://www.pptx.gallery/audiences.
-     *
-     * @minItems 1
      */
-    audience?: [(string | Audience), ...((string | Audience))[]];
+    audience?: (string | [(string | Audience), ...((string | Audience))[]]);
     /**
      * Primary goal of the presentation. Accepts either:
      * - 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.
@@ -2022,7 +2010,7 @@ interface Slide {
      */
     text?: (string | TextRun[]);
     /**
-     * Full-slide generic list payload. Presence of this field infers type 'list'.
+     * 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.
      */
     items?: ListItem[];
     /**
@@ -2121,7 +2109,7 @@ interface Slide {
         events: [TimelineEvent, ...(TimelineEvent)[]];
     });
     /**
-     * Layout-agnostic content blocks rendered together as a composed payload when exact placement is unspecified.
+     * 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.
      */
     blocks?: ContentPayload[];
     design?: Design1;
@@ -2671,30 +2659,4 @@ interface CatalogEntry10 {
     [k: string]: unknown;
 }
 
-interface ValidationIssue {
-    path: string;
-    message: string;
-    keyword: string;
-    schemaPath: string;
-    params: Record<string, unknown>;
-}
-interface ValidationResult {
-    valid: boolean;
-    errors: ValidationIssue[];
-    schemaName?: SchemaName;
-    catalogKind?: CatalogKind;
-}
-type SchemaOrKind = SchemaName | CatalogKind | JsonSchema;
-declare class OPFValidationError extends Error {
-    readonly issues: ValidationIssue[];
-    readonly result: ValidationResult;
-    constructor(result: ValidationResult);
-}
-declare function validate(value: unknown, schemaOrKind?: SchemaOrKind): ValidationResult;
-declare function assertValid<T = unknown>(value: T, schemaOrKind?: SchemaOrKind): T;
-declare function validatePresentation(value: unknown): ValidationResult;
-declare function assertValidPresentation(value: unknown): asserts value is Presentation;
-declare function validateCatalogRecord(kind: CatalogKind, value: unknown): ValidationResult;
-declare function assertValidCatalogRecord(kind: CatalogKind, value: unknown): void;
-
-export { OPFValidationError as O, type Presentation as P, type SchemaOrKind as S, type ValidationIssue as V, type ValidationResult as a, assertValid as b, assertValidCatalogRecord as c, assertValidPresentation as d, validateCatalogRecord as e, validatePresentation as f, validate as v };
+export type { Presentation as P };

package/dist/repo-readme.d.ts

@@ -0,0 +1,4 @@
+/** Raw markdown of the upstream OpenPresentation/opf README at this release. */
+declare const repoReadme: string;
+
+export { repoReadme };

package/dist/repo-readme.js

@@ -0,0 +1,9 @@
+// src/generated/repo-readme.ts
+var repoReadmeRaw = '# Open Presentation Format (OPF)\n\n[![npm version](https://img.shields.io/npm/v/@openpresentation/opf?label=npm)](https://www.npmjs.com/package/@openpresentation/opf)\n[![npm downloads](https://img.shields.io/npm/dw/@openpresentation/opf)](https://www.npmjs.com/package/@openpresentation/opf)\n[![license](https://img.shields.io/npm/l/@openpresentation/opf)](./LICENSE)\n\nPublic npm package: [`@openpresentation/opf`](https://www.npmjs.com/package/@openpresentation/opf) (`npm install @openpresentation/opf`).\n\nOpen Presentation Format is the portable, human-readable JSON document format for slide decks.\n\nThis repository is the canonical home for the OPF **spec**, **JSON Schemas**, **catalog presets**, examples, generated developer types, local validation tooling, and planning docs for the future render/edit/convert toolkit. OpenPresentation publishes open-source code and documentation only; it does not provide hosted APIs, hosted rendering functions, queues, storage, authentication, jobs, previews, SLAs, telemetry, or managed infrastructure.\n\n## File naming\n\nOpen Presentation Format documents are JSON files. Use `*.opf.json` for complete OPF presentation documents, for example `board-review.opf.json` or `deck.opf.json`.\n\nAvoid using bare `*.opf` for OPF JSON. The `.opf` extension is already used by other document and project formats, while `.opf.json` keeps the OPF identity and still makes the underlying JSON format clear to editors, validators, agents, and version-control tooling.\n\n## Naming and reuse\n\nThe format name is **Open Presentation Format**. The schemas, catalogs, packages, and local tooling in this repository are free and open source under the MIT license, so third-party tools may read, write, validate, render, convert, and describe support for Open Presentation Format without adopting any product-specific branding.\n\n## Why OPF\n\n`.pptx` is a zipped bundle of XML. Humans can\'t diff it, LLMs can\'t read or write it reliably, and git can\'t track it meaningfully. Every change looks like a binary blob.\n\nOPF is plain JSON. A human can open it in an editor. A model can read and write it without guessing at schema-by-example. Decks live in git like the rest of your work.\n\nThat\'s the shift that lets LLMs actually *author* decks. When the format stops fighting them, models can do the work that matters \u2014 narrative structure, persuasive framing, data analysis, chart recommendations, ruthless revision passes \u2014 instead of wrestling with `<p:sp>` tags.\n\nAnd they don\'t start from a blank canvas. [pptx.gallery](https://pptx.gallery) is the human-browsable reference for OPF catalog presets: layouts, themes, color schemes, font schemes, chart types, narratives, audiences, purposes, tones, languages, and social platforms.\n\n## Start in three steps\n\n1. **Install the format package.** `npm install @openpresentation/opf`.\n2. **Author and validate a deck.** Write a `*.opf.json` file \u2014 start from [`docs/how-opf-works.md`](./docs/how-opf-works.md) or copy [`examples/technical/full-feature-tour.opf.json`](./examples/technical/full-feature-tour.opf.json) \u2014 and run `validatePresentation` on it.\n3. **Build on it.** Browse presets at [pptx.gallery](https://pptx.gallery), pin the schemas in your pipeline, and track the [toolkit roadmap](#toolkit-roadmap) for the render and convert libraries.\n\nYour deck lives in git from the first commit. Nothing in these steps calls a hosted service, and nothing ever will \u2014 that boundary is the point.\n\n## JavaScript and TypeScript\n\nThe canonical JavaScript/TypeScript package is published at [`packages/javascript`](./packages/javascript) as [`@openpresentation/opf`](https://www.npmjs.com/package/@openpresentation/opf). The schema is pre-stable (0.x \u2014 expect breaking changes between minor versions until 1.0). Its responsibility is local and format-level only:\n\n- export the canonical schemas from [`spec/`](./spec)\n- export bundled catalog records from [`spec/`](./spec)\n- export a typed raw spec file manifest for package-addressable `spec/` content\n- generate TypeScript types, with `Presentation` as the top-level type\n- validate OPF JSON and catalog records locally\n\nIt does not render `.pptx`, parse `.pptx`, generate content with AI, fetch remote catalogs, call hosted APIs, or provide managed services. Future render/edit/convert packages are planned as separate MIT repos that depend on `@openpresentation/opf`.\n\n## Toolkit roadmap\n\nThe OPF format package is shipping first. The planned toolkit lives outside this format-only repo:\n\n| Planned repo | Role | Boundary |\n|---|---|---|\n| `opf-render` | OPF to SVG/PNG/PDF | Local and embeddable rendering library |\n| `opf-editor` | WYSIWYG bindings/components | Headless editor primitives plus optional UI components |\n| `opf-pptx` | OPF to PPTX and PPTX to OPF | Pure local import/export library for browser and server use where supported |\n\nThese repos provide OSS primitives only. Downstream applications own hosting, auth, storage, collaboration, queues, previews, analytics, support, and workflow UX.\n\n## Usage\n\nInstall from npm:\n\n```sh\npnpm add @openpresentation/opf\n# or: npm install @openpresentation/opf\n```\n\nTo work on the package itself, clone this repo and build the workspace:\n\n```sh\npnpm install\npnpm build\n```\n\nUse the format package from JavaScript or TypeScript:\n\n```ts\nimport {\n  presentation,\n  audiences,\n  purposes,\n  tones,\n  validatePresentation,\n} from "@openpresentation/opf";\n\nimport type { Presentation } from "@openpresentation/opf";\n\nconst deck: Presentation = {\n  name: "Quarterly Review",\n  slides: [{ title: "Quarterly Review", items: ["Revenue", "Product", "Hiring"] }],\n};\n\nconst result = validatePresentation(deck);\nconsole.log(result.valid); // schema correctness\nconsole.log(result.warnings); // advisory issues, e.g. unknown catalog ids\nconsole.log(audiences.length, purposes.length, tones.length);\n```\n\nUse focused imports when you only need one surface:\n\n```ts\nimport { presentation } from "@openpresentation/opf/schemas";\nimport { audiences, purposes } from "@openpresentation/opf/catalogs";\nimport { specFileEntries } from "@openpresentation/opf/spec-files";\nimport { validate } from "@openpresentation/opf/validator";\nimport type { Presentation } from "@openpresentation/opf/types";\n```\n\nUse raw JSON when an engine or resolver needs package-addressable files:\n\n```ts\nimport presentationSchema from "@openpresentation/opf/spec/schemas/opf.schema.json" with {\n  type: "json",\n};\n```\n\nUse the local-only CLI source during development:\n\n```sh\npnpm --filter @openpresentation/cli build\nnode packages/cli/dist/index.js schemas\nnode packages/cli/dist/index.js catalogs\nnode packages/cli/dist/index.js validate path/to/deck.opf.json\n```\n\n## Layout\n\n| Path | Contents |\n|---|---|\n| [`spec/schemas/opf.schema.json`](./spec/schemas/opf.schema.json) | Canonical JSON Schema for top-level OPF `Presentation` documents. |\n| [`docs/how-opf-works.md`](./docs/how-opf-works.md) | Conceptual introduction: the document model, content shapes, catalog resolution, and the validation philosophy. Start here. |\n| [`docs/design-resolution.md`](./docs/design-resolution.md) | The design precedence algorithm (slide design \u2192 deck design \u2192 resolved theme \u2192 engine defaults) with worked examples. |\n| [`docs/schema-reference.md`](./docs/schema-reference.md) | Author-facing reference for top-level OPF fields and every presentation schema `$defs` object/type. |\n| [`docs/catalog-schema-reference.md`](./docs/catalog-schema-reference.md) | Author-facing reference for every companion catalog schema. |\n| [`docs/content-payloads.md`](./docs/content-payloads.md) | Author-facing notes for slide and region content payloads, including chart and table object shapes. |\n| [`docs/examples.md`](./docs/examples.md) | Guide to the expanded scenario-oriented examples under `examples/gallery/`. |\n| [`spec/schemas/*.schema.json`](./spec/schemas) | Companion schemas for catalog records and sub-objects. |\n| [`spec/catalogs/<catalog-kind>/`](./spec/catalogs) | Canonical bundled catalog records. |\n| [`spec/openapi.yaml`](./spec/openapi.yaml) | Optional reference OpenAPI contract for downstream services that choose to expose OPF over HTTP. OpenPresentation does not host this API. |\n| [`examples/technical/`](./examples/technical) | Focused OPF fixtures for validator, renderer, catalog-resolution, design, content-payload, and region behavior. |\n| [`examples/gallery/`](./examples/gallery) | Broader OPF example decks organized by industry, function, education, government, presentation type, international, and design/media scenarios. |\n| [`packages/javascript/`](./packages/javascript) | Public pre-stable source for `@openpresentation/opf`. |\n| [`packages/cli/`](./packages/cli) | Local-only OPF CLI source; native distribution is deferred. |\n| [`legacy/`](./legacy) | Tombstone for service-specific clients, CLIs, tool integrations, and workflows removed from the OpenPresentation OSS repo. |\n\n## OpenPresentation Boundary\n\nOpenPresentation defines the format, bundled presets, local validation, examples, docs, and planned local render/edit/convert libraries. It does not provide hosted functions or managed product surfaces.\n\nFuture non-JavaScript OPF packages should follow the same local-first boundary: Python and Go packages should expose schemas, types/models, catalogs, validation, and package-addressable assets. Future toolkit packages should expose embeddable library APIs with no required network calls, hosted callbacks, hidden telemetry, or managed infrastructure assumptions.\n\nThe published JavaScript package copies package-addressable OPF schemas, catalogs, reference assets, and the optional reference `spec/openapi.yaml` from `spec/`. It intentionally remains `@openpresentation/opf` instead of introducing a separate `@openpresentation/opf-spec` package so downstream imports can advance by semver-pinning one canonical package.\n\n## License\n\nMIT. See [LICENSE](./LICENSE).\n';
+
+// src/repo-readme.ts
+var repoReadme = repoReadmeRaw;
+
+export { repoReadme };
+//# sourceMappingURL=repo-readme.js.map
+//# sourceMappingURL=repo-readme.js.map

package/dist/repo-readme.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../src/generated/repo-readme.ts","../src/repo-readme.ts"],"names":[],"mappings":";AAEO,IAAM,aAAA,GAAwB,g6TAAA;;;ACY9B,IAAM,UAAA,GAAqB","file":"repo-readme.js","sourcesContent":["// Generated by scripts/generate-content.mjs from README.md. Do not edit by hand.\n\nexport const repoReadmeRaw: string = \"# Open Presentation Format (OPF)\\n\\n[![npm version](https://img.shields.io/npm/v/@openpresentation/opf?label=npm)](https://www.npmjs.com/package/@openpresentation/opf)\\n[![npm downloads](https://img.shields.io/npm/dw/@openpresentation/opf)](https://www.npmjs.com/package/@openpresentation/opf)\\n[![license](https://img.shields.io/npm/l/@openpresentation/opf)](./LICENSE)\\n\\nPublic npm package: [`@openpresentation/opf`](https://www.npmjs.com/package/@openpresentation/opf) (`npm install @openpresentation/opf`).\\n\\nOpen Presentation Format is the portable, human-readable JSON document format for slide decks.\\n\\nThis repository is the canonical home for the OPF **spec**, **JSON Schemas**, **catalog presets**, examples, generated developer types, local validation tooling, and planning docs for the future render/edit/convert toolkit. OpenPresentation publishes open-source code and documentation only; it does not provide hosted APIs, hosted rendering functions, queues, storage, authentication, jobs, previews, SLAs, telemetry, or managed infrastructure.\\n\\n## File naming\\n\\nOpen Presentation Format documents are JSON files. Use `*.opf.json` for complete OPF presentation documents, for example `board-review.opf.json` or `deck.opf.json`.\\n\\nAvoid using bare `*.opf` for OPF JSON. The `.opf` extension is already used by other document and project formats, while `.opf.json` keeps the OPF identity and still makes the underlying JSON format clear to editors, validators, agents, and version-control tooling.\\n\\n## Naming and reuse\\n\\nThe format name is **Open Presentation Format**. The schemas, catalogs, packages, and local tooling in this repository are free and open source under the MIT license, so third-party tools may read, write, validate, render, convert, and describe support for Open Presentation Format without adopting any product-specific branding.\\n\\n## Why OPF\\n\\n`.pptx` is a zipped bundle of XML. Humans can't diff it, LLMs can't read or write it reliably, and git can't track it meaningfully. Every change looks like a binary blob.\\n\\nOPF is plain JSON. A human can open it in an editor. A model can read and write it without guessing at schema-by-example. Decks live in git like the rest of your work.\\n\\nThat's the shift that lets LLMs actually *author* decks. When the format stops fighting them, models can do the work that matters — narrative structure, persuasive framing, data analysis, chart recommendations, ruthless revision passes — instead of wrestling with `<p:sp>` tags.\\n\\nAnd they don't start from a blank canvas. [pptx.gallery](https://pptx.gallery) is the human-browsable reference for OPF catalog presets: layouts, themes, color schemes, font schemes, chart types, narratives, audiences, purposes, tones, languages, and social platforms.\\n\\n## Start in three steps\\n\\n1. **Install the format package.** `npm install @openpresentation/opf`.\\n2. **Author and validate a deck.** Write a `*.opf.json` file — start from [`docs/how-opf-works.md`](./docs/how-opf-works.md) or copy [`examples/technical/full-feature-tour.opf.json`](./examples/technical/full-feature-tour.opf.json) — and run `validatePresentation` on it.\\n3. **Build on it.** Browse presets at [pptx.gallery](https://pptx.gallery), pin the schemas in your pipeline, and track the [toolkit roadmap](#toolkit-roadmap) for the render and convert libraries.\\n\\nYour deck lives in git from the first commit. Nothing in these steps calls a hosted service, and nothing ever will — that boundary is the point.\\n\\n## JavaScript and TypeScript\\n\\nThe canonical JavaScript/TypeScript package is published at [`packages/javascript`](./packages/javascript) as [`@openpresentation/opf`](https://www.npmjs.com/package/@openpresentation/opf). The schema is pre-stable (0.x — expect breaking changes between minor versions until 1.0). Its responsibility is local and format-level only:\\n\\n- export the canonical schemas from [`spec/`](./spec)\\n- export bundled catalog records from [`spec/`](./spec)\\n- export a typed raw spec file manifest for package-addressable `spec/` content\\n- generate TypeScript types, with `Presentation` as the top-level type\\n- validate OPF JSON and catalog records locally\\n\\nIt does not render `.pptx`, parse `.pptx`, generate content with AI, fetch remote catalogs, call hosted APIs, or provide managed services. Future render/edit/convert packages are planned as separate MIT repos that depend on `@openpresentation/opf`.\\n\\n## Toolkit roadmap\\n\\nThe OPF format package is shipping first. The planned toolkit lives outside this format-only repo:\\n\\n| Planned repo | Role | Boundary |\\n|---|---|---|\\n| `opf-render` | OPF to SVG/PNG/PDF | Local and embeddable rendering library |\\n| `opf-editor` | WYSIWYG bindings/components | Headless editor primitives plus optional UI components |\\n| `opf-pptx` | OPF to PPTX and PPTX to OPF | Pure local import/export library for browser and server use where supported |\\n\\nThese repos provide OSS primitives only. Downstream applications own hosting, auth, storage, collaboration, queues, previews, analytics, support, and workflow UX.\\n\\n## Usage\\n\\nInstall from npm:\\n\\n```sh\\npnpm add @openpresentation/opf\\n# or: npm install @openpresentation/opf\\n```\\n\\nTo work on the package itself, clone this repo and build the workspace:\\n\\n```sh\\npnpm install\\npnpm build\\n```\\n\\nUse the format package from JavaScript or TypeScript:\\n\\n```ts\\nimport {\\n  presentation,\\n  audiences,\\n  purposes,\\n  tones,\\n  validatePresentation,\\n} from \\\"@openpresentation/opf\\\";\\n\\nimport type { Presentation } from \\\"@openpresentation/opf\\\";\\n\\nconst deck: Presentation = {\\n  name: \\\"Quarterly Review\\\",\\n  slides: [{ title: \\\"Quarterly Review\\\", items: [\\\"Revenue\\\", \\\"Product\\\", \\\"Hiring\\\"] }],\\n};\\n\\nconst result = validatePresentation(deck);\\nconsole.log(result.valid); // schema correctness\\nconsole.log(result.warnings); // advisory issues, e.g. unknown catalog ids\\nconsole.log(audiences.length, purposes.length, tones.length);\\n```\\n\\nUse focused imports when you only need one surface:\\n\\n```ts\\nimport { presentation } from \\\"@openpresentation/opf/schemas\\\";\\nimport { audiences, purposes } from \\\"@openpresentation/opf/catalogs\\\";\\nimport { specFileEntries } from \\\"@openpresentation/opf/spec-files\\\";\\nimport { validate } from \\\"@openpresentation/opf/validator\\\";\\nimport type { Presentation } from \\\"@openpresentation/opf/types\\\";\\n```\\n\\nUse raw JSON when an engine or resolver needs package-addressable files:\\n\\n```ts\\nimport presentationSchema from \\\"@openpresentation/opf/spec/schemas/opf.schema.json\\\" with {\\n  type: \\\"json\\\",\\n};\\n```\\n\\nUse the local-only CLI source during development:\\n\\n```sh\\npnpm --filter @openpresentation/cli build\\nnode packages/cli/dist/index.js schemas\\nnode packages/cli/dist/index.js catalogs\\nnode packages/cli/dist/index.js validate path/to/deck.opf.json\\n```\\n\\n## Layout\\n\\n| Path | Contents |\\n|---|---|\\n| [`spec/schemas/opf.schema.json`](./spec/schemas/opf.schema.json) | Canonical JSON Schema for top-level OPF `Presentation` documents. |\\n| [`docs/how-opf-works.md`](./docs/how-opf-works.md) | Conceptual introduction: the document model, content shapes, catalog resolution, and the validation philosophy. Start here. |\\n| [`docs/design-resolution.md`](./docs/design-resolution.md) | The design precedence algorithm (slide design → deck design → resolved theme → engine defaults) with worked examples. |\\n| [`docs/schema-reference.md`](./docs/schema-reference.md) | Author-facing reference for top-level OPF fields and every presentation schema `$defs` object/type. |\\n| [`docs/catalog-schema-reference.md`](./docs/catalog-schema-reference.md) | Author-facing reference for every companion catalog schema. |\\n| [`docs/content-payloads.md`](./docs/content-payloads.md) | Author-facing notes for slide and region content payloads, including chart and table object shapes. |\\n| [`docs/examples.md`](./docs/examples.md) | Guide to the expanded scenario-oriented examples under `examples/gallery/`. |\\n| [`spec/schemas/*.schema.json`](./spec/schemas) | Companion schemas for catalog records and sub-objects. |\\n| [`spec/catalogs/<catalog-kind>/`](./spec/catalogs) | Canonical bundled catalog records. |\\n| [`spec/openapi.yaml`](./spec/openapi.yaml) | Optional reference OpenAPI contract for downstream services that choose to expose OPF over HTTP. OpenPresentation does not host this API. |\\n| [`examples/technical/`](./examples/technical) | Focused OPF fixtures for validator, renderer, catalog-resolution, design, content-payload, and region behavior. |\\n| [`examples/gallery/`](./examples/gallery) | Broader OPF example decks organized by industry, function, education, government, presentation type, international, and design/media scenarios. |\\n| [`packages/javascript/`](./packages/javascript) | Public pre-stable source for `@openpresentation/opf`. |\\n| [`packages/cli/`](./packages/cli) | Local-only OPF CLI source; native distribution is deferred. |\\n| [`legacy/`](./legacy) | Tombstone for service-specific clients, CLIs, tool integrations, and workflows removed from the OpenPresentation OSS repo. |\\n\\n## OpenPresentation Boundary\\n\\nOpenPresentation defines the format, bundled presets, local validation, examples, docs, and planned local render/edit/convert libraries. It does not provide hosted functions or managed product surfaces.\\n\\nFuture non-JavaScript OPF packages should follow the same local-first boundary: Python and Go packages should expose schemas, types/models, catalogs, validation, and package-addressable assets. Future toolkit packages should expose embeddable library APIs with no required network calls, hosted callbacks, hidden telemetry, or managed infrastructure assumptions.\\n\\nThe published JavaScript package copies package-addressable OPF schemas, catalogs, reference assets, and the optional reference `spec/openapi.yaml` from `spec/`. It intentionally remains `@openpresentation/opf` instead of introducing a separate `@openpresentation/opf-spec` package so downstream imports can advance by semver-pinning one canonical package.\\n\\n## License\\n\\nMIT. See [LICENSE](./LICENSE).\\n\";\n","// The raw README.md from the OpenPresentation/opf repo at the version pinned\n// by this release.\n//\n// Source-of-truth: ../../../README.md. The build step inlines the markdown\n// into this module so consumers can render the upstream README without doing\n// any filesystem or network work at runtime.\n//\n// The package's own README.md (npm landing page) is a separate file — this\n// export is intended for sites that want to mirror the canonical upstream\n// README.\n\nimport { repoReadmeRaw } from \"./generated/repo-readme.js\";\n\n/** Raw markdown of the upstream OpenPresentation/opf README at this release. */\nexport const repoReadme: string = repoReadmeRaw;\n"]}

package/dist/schemas.d.ts

@@ -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;
             }, {
@@ -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";
@@ -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;
                 }, {
@@ -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";
@@ -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;
                 }, {
@@ -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";

package/dist/schemas.js

@@ -92,20 +92,29 @@ var presentation = {
       ]
     },
     "audience": {
-      "type": "array",
-      "items": {
-        "oneOf": [
-          {
-            "type": "string"
+      "oneOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "array",
+          "items": {
+            "oneOf": [
+              {
+                "type": "string"
+              },
+              {
+                "$ref": "#/$defs/Audience"
+              }
+            ]
           },
-          {
-            "$ref": "#/$defs/Audience"
-          }
-        ]
-      },
-      "minItems": 1,
-      "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[] \u2192 catalogs.audiences.source \u2192 default catalog at https://www.pptx.gallery/audiences.",
+          "minItems": 1
+        }
+      ],
+      "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[] \u2192 catalogs.audiences.source \u2192 default catalog at https://www.pptx.gallery/audiences.",
       "examples": [
+        "executives",
+        "Biology Students and Wildlife Enthusiasts",
         [
           "executives"
         ],
@@ -2460,7 +2469,7 @@ Resolution order: inline catalogs.fontSchemes.records[] -> catalogs.fontSchemes.
           "items": {
             "$ref": "#/$defs/ListItem"
           },
-          "description": "Full-slide generic list payload. Presence of this field infers type 'list'."
+          "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."
         },
         "bullets": {
           "type": "array",
@@ -2530,7 +2539,7 @@ Resolution order: inline catalogs.fontSchemes.records[] -> catalogs.fontSchemes.
           "items": {
             "$ref": "#/$defs/ContentPayload"
           },
-          "description": "Layout-agnostic content blocks rendered together as a composed payload when exact placement is unspecified."
+          "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."
         },
         "design": {
           "$ref": "#/$defs/Design",