RR-20: release opf-render 0.14.0

[michaeljgrimm]

RR-20: release-prep PR for @openpresentation/opf-render 0.14.0 (from 0.13.1), opened by scripts/release-train.mjs prep (RR-51).

• package.json: version 0.13.1 -> 0.14.0.
• CHANGELOG.md: node scripts/changelog-fragments.mjs assemble --version 0.14.0 moved 16 fragment(s) into the release section.
• Lockfile refreshed with npm install --package-lock-only against the registry.
• package.json: opf.requiresUnreleasedCore (0.14.0) deleted; it gated CI's packed install on a core that was not yet published, and must not reach a release.

Dependency floors raised to the train's versions (each already on npm):

field	package	from	to
dependencies	@openpresentation/opf	^0.13.0	^0.14.0

Train: --core 0.14.0 --render 0.14.0 --pptx 0.14.0 --editor 0.14.0 --cli 0.14.0. Merge only after CI is green; the train then tags the merge commit:
node scripts/release-train.mjs tag render --core 0.14.0 --render 0.14.0 --pptx 0.14.0 --editor 0.14.0 --cli 0.14.0 --execute (or run ... --execute).

Resume

• Done: the release-prep commit on this branch.
• Left: CI green, review, merge (by a person), then the tag step above. If CI needs a fixture change caused by the new
  dependency versions (for example the CLI's render hashes), add it to this PR.
• Re-running prep finds this PR and changes nothing.

---

Note

Low Risk
This PR only bumps versions, refreshes the lockfile, consolidates changelog fragments, and drops the unreleased-core CI gate—no renderer source changes in the diff.

Overview
Release train prep for @openpresentation/opf-render 0.14.0 (from 0.13.1): bumps package.json / lockfile version, raises @openpresentation/opf to ^0.14.0, and removes opf.requiresUnreleasedCore so CI’s packed install against published deps is no longer gated on an unreleased core.

Changelog housekeeping: sixteen changes/*.md fragments are assembled into ## 0.14.0 (2026-10-07) in CHANGELOG.md and the fragment files are deleted (node scripts/changelog-fragments.mjs assemble). That section records what ships with this tag (preview FA work, golden baseline RR-20 for core 0.14.0, and the breaking RR-55 fonts/render API)—those behaviors are not introduced in this diff; they landed in earlier commits on the branch.

^{Reviewed by Cursor Bugbot for commit 00ba341. 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: bd1dbfe9-66e8-41bf-a057-08dd21bd4ffd)