RR-55: CLI and registry scripts on the 0.14 sibling APIs (merge after render/pptx 0.14 publish)

[michaeljgrimm]

The CLI (packages/cli) and the registry-consumer scripts on the published 0.14 set. Based on main (core 0.14.0 release, #444). Ready to merge: every package it needs is on npm.

The set

release-plan.json now names core 0.14.0 (f9e9433), opf-render 0.14.0 (66866e5c), opf-pptx 0.14.0 (ac946771) and opf-editor 0.14.2 (d4216427; 0.14.0 and 0.14.1 were never published). verificationRefs and exampleRefs are the npm gitHeads. The CLI entry (0.11.0) and bundledCore are untouched: release-train prep cli moves them.

CLI

• Uses only the 0.14 APIs of its optional peers (no compatibility path). Peer ranges ^0.14.0, devDependencies 0.14.0, pnpm-lock.yaml refreshed (17 lines: the CLI importer's two peers and the core they depend on).
• Old to new: prepareNodeFonts is loadFonts (the handle goes as { fonts } to paginate, renderSlideSvg, svgToPng, svgToPdf, toPptx); renderSvg(deck, { slideIndex }) is renderSlideSvg(deck, index, ...); fromPptx(..., { signals: true }) returns { presentation, signals }; a thrown OPFRenderError, OPFPptxError or OPFValidationError with findings is reported as those findings.
• pdf.vectorSupported is gone (vector is the default). signals.version is the version the signals carry.
• A 0.13 peer exits 2 with peer-too-old and the install command (the CLI checks features: loadFonts, renderSlideSvg, inventoryTypefaces).
• The golden SVG digests (render-hashes.json) are generated with UPDATE_GOLDEN=1 against the published opf-render 0.14.0: the three digests are unchanged, only the labels moved (0.12.0 to 0.14.0), so files.mjs compares them again instead of skipping.
• Changelog fragment changes/rr-55-cli-peers.md.

Registry scripts

Moved to the 0.14 names, and their published 0.13 variants deleted: the published-matrix consumer and engines-installed.mjs (plain re-exports), browser-check, test-packed-ecosystem, the developer quickstart, layout-contract, native-quote, native-feature-matrix, native-powerpoint, probe-code-native, the code, quote and metric geometry and browser scripts (fonts: to fontFamilies where 0.14 ignored it), the registry gallery editor (lazyFontsBaseUrl now decides whether lazy-fonts.json ships), the site showcase, the deployed-font check, the installed-parity font host, and the two evidence fixtures that still used { family } font roles. probe-code-layout-gap, probe-metric-layout-gap, probe-payload-fit-gaps and review-metric-corpus pin old versions on purpose and are unchanged. The matrix consumer package.json and lock are refreshed by prepare-consumer.mjs --update-lock.

The plan-CLI gate

The plan still names CLI 0.11.0, whose optional peers are opf-render ^0.13.1 and opf-pptx ^0.13.2. Installing it beside the planned 0.14 libraries fails with ERESOLVE (reproduced with npm), and its commands call the 0.13 APIs. scripts/release-plan-cli.mjs decides on that exact condition: it reads the plan CLI's peerDependencies from the registry (injectable reader) and skips it only when the plan's render or pptx do not satisfy them. A read failure is an error, never a silent skip. The registry consumer (test-packed-ecosystem --registry), the developer quickstart, test-registry-fidelity and the registry toolchain leave the CLI out and print: "release plan's CLI 0.11.0 requires opf-render ^0.13.1, opf-pptx ^0.13.2; the plan has opf-render 0.14.0, opf-pptx 0.14.0: skipped until a compatible CLI is in the plan". They run the CLI again as soon as prep cli puts CLI 0.14.0 (peers ^0.14.0) in the plan; no shim. Unit tests: pnpm check:release-plan-cli (8 tests: semver, mismatch, match, missing peers, read failure, this checkout's ranges). packages/cli/test/packed.mjs --registry installs the plan CLI alone and is not gated.

Docs sweep

docs/, skills/, README.md and the package READMEs describe the current API: loadFonts and { fonts }, deck-level renderSvg and renderSlideSvg, .presentation on editor sessions and results, the browser loadFonts and canvas fonts option, validate/Findings. Files: docs/quickstart.md, docs/font-fidelity.md, docs/live-editor.md, docs/dynamic-composition.md, docs/compatibility-matrix.md, docs/design-resolution.md, docs/templates-and-variables.md, docs/yaml.md, docs/cli.md, packages/cli/README.md, skills/opf-export/references/rendering.md, skills/opf-edit/references/editor.md, skills/opf-layout/references/geometry.md, plus the current-set lines of README and six more pages. docs/programs, docs/evidence, docs/plans, changelogs and the compatibility matrix's history rows are untouched.

Results (Node 24.21.0, Windows, against the published 0.14 packages)

• pnpm --filter @openpresentation/cli test: 91 node:test tests, cli.mjs 92 checks (1 symlink check skipped on this account), files.mjs 84 checks with the golden compared. pnpm test:cli:packed and pnpm test:cli:packed:peers (render and pptx 0.14.0 from npm) pass.
• node scripts/check-changed.mjs on the 44 changed files: biome, check:changes, check:engines-range, check:font-tracker, check:gallery-tracker, check:release-plan-cli, check:release-report, check:runners, check:text, check:works-percent, typecheck and CLI tests pass. check:schema-docs and test:skills pass.
• Registry (real npm, the four 0.14 libraries): test-packed-ecosystem --registry (includes test-installed-code --registry), test-packed-browser registry (canvas, rich-text, layout, block, list, create, styled-table), test-layout-contract-registry (100 layouts), test-registry-fidelity, test-installed-code-guards --registry, quote geometry (6), code geometry (8) and browser (8), metric guards, metric geometry (60) and browser (50), pnpm test:developer-quickstart.
• Published-matrix: prepare-consumer.mjs (tsc NodeNext, Bundler, emit), the TypeScript consumer, browser-check.mjs in Chromium, and the full font-switch matrix through engines-installed.mjs with the opf-v0.14.0 harness (61 of 61 decks, 18 switches, 274 states) pass.
• Not run: the CLI part of the registry scripts (gated), the PowerPoint steps of the native scripts, the full installed-parity run over the gallery snippets, build-registry-gallery-editor and build-site-showcase --registry against the final plan (both passed earlier with the editor tarball in the slot).

🤖 Generated with Claude Code

---

Note

Medium Risk
Breaking change for CLI optional peers and many integration scripts; incorrect peer gating or API mismatches could break CI/registry checks until the CLI train catches the plan.

Overview
RR-55 moves the CLI and registry consumer tooling onto the coordinated 0.14 sibling APIs and bumps release-plan.json (core/renderer/pptx/editor pins and verification refs). The CLI now requires peers ^0.14.0, loads fonts once via loadFonts, passes { fonts } through render/export/import, uses renderSlideSvg per slide, reads fromPptx(..., { signals: true }) as { presentation, signals }, defaults PDF to vector (drops pdf.vectorSupported), and surfaces thrown library findings in reports; 0.13 peers fail with peer-too-old.

Registry scripts, parity harnesses, gallery editor build, published-matrix consumer, and smoke tests are updated to the same names (validate, renderSvg, editor.presentation, etc.); old 0.13 shims and duplicated published variants are removed. Docs and README pins/examples are swept to 0.14.0 and the new font/render API. A check:release-plan-cli gate skips installing/running plan CLI 0.11.0 beside 0.14 libraries when peer ranges conflict, until prep cli lands a compatible CLI.

^{Reviewed by Cursor Bugbot for commit 368cb75. Configure here.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: e06f37eb-499f-4749-9252-0b7884e5e175)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 8fad50df-6861-4f54-b982-e70aa05fb3a1)