OpenPresentation handoff — September 21, 2026

The shipped ColorRef train is core 0.11.0, CLI/renderer 0.9.0, PPTX 0.9.1 and editor 0.8.0, on Node 24. Shared furniture is already published. The developer-ready milestone and broad ecosystem goal remain open. The quickstart, compatibility matrix and release-plan.json describe this train; older dated handoffs are historical.

Accepted source and production#

All seven primary local checkouts were clean and fast-forwarded from GitHub before this work. The sync receipt records both old and new commits. No local branches or archived prototypes were deleted.

The owner checked those three production sites after the 17 September merges. Fresh verification in this checkpoint is recorded separately in the evidence ledger. A source SHA, registry publication, browser workflow and native application result are different evidence; none substitutes for another.

ColorRef slot/role/variable resolution, variables, payload ids/extensions and catalog bundling are published. Bundling inlines catalog records, not remote media/data. Furniture (furniture-flow-v2) exports as editable tagged slide shapes with OPF_FURNITURE_V1 provenance. Controlled imports use current native content; arbitrary Office round-trip and real native Header/Footer (p:hf) are not certified. Content, source whitespace, metadata, reading order, formatting, human adjustments and undo remain required preservation boundaries.

Current work and decision boundaries#

PR93 is squash-merged as 937047ff9f65d936126c577d3c6b7c5f9a61e364. Its tested tree matches the merged tree; post-merge OPF CI, macOS/Windows CLI compatibility and coordinated installed-package/browser acceptance all passed. No npm package version or visual baseline changed.

Issue88 remains the public acceptance tracker. The original production audit identified first-slide-only Inspector editing and whole-JSON reserialization. pptx-dev PR45 implements all-slide editing, exact JSON source/history, stale-draft cancellation, render recovery and accessible font notes. Its local Node 24 evidence includes 622 unit tests and all 17 browser workflows; Author built-in, document-local and loaded-catalog choices also passed separately on canonical production. App PR CI and canonical deployment acceptance must be recorded before treating these Inspector fixes as shipped. Linux CI passed; Windows failed four exact clipboard string assertions before any source-preservation claim can pass that gate. The failed run is retained for diagnosis; do not merge on the local results alone.

Site43 and gallery35 are merged, green in post-merge CI and verified on canonical production. Agent CLI guidance now pins 0.9.0, and gallery ColorRef/bundle copy describes the published train. The broader audit found a separate old website docs snapshot, stale current upstream composition/data/rich-text availability prose, gallery docs denying its own editor, and binary evidence in the AI-facing full-text guide. This checkpoint corrects the three upstream guides. Gallery36 is merged as f17e9ae and its canonical docs-to-editor flow passes. The website snapshot/exporter follow-up still requires review, CI, deployment and fresh public checks before closing the remaining docs checklist. The follow-up evidence records exact acceptance boundaries; dated observations are not later deployment claims. Keep issue88 open until its remaining checklist passes.

The superseded changelog drafts editor24/render26/PPTX40 describe the predecessor versions. Their useful historical facts are retained: renderer0.8.1 includes shared accepted furniture geometry; PPTX0.8.1 includes furniture export/import provenance. Current README/changelog release headings name the newer train. All three drafts are now closed; cleanup receipts retain final states and branch identities. Closing these drafts did not delete branches.

Leave all five geometry drafts as one coordinated set: core94, renderer27, editor25, PPTX42 and site40. None is accepted by this checkpoint. Do not merge site40 independently. Native HF documentation drafts core92/PPTX41 remain roadmap; do not implement p:hf here.

Compatibility and remaining goal#

• Renderer issue24 remains deferred at the unchanged 0.1px tolerance. Preserve rejected experiments and archived shaping branches. No platform offsets, weakened assertions or golden changes to hide residuals.
• Native Office issue87 remains separate: host recovery, picture open/edit/save/ reopen, current-content provenance, tabs, notes-master ordering, physical font identity and embedding. No Windows COM retries or process killing before owner-confirmed recovery. Restricted Aptos4.40 is excluded without permission.
• Fresh source/installed-package/browser/CI checks are required for changed code. A green portable gate is not native or font acceptance. This documentation correction publishes no npm package. Public application deployments have their own PR, CI and canonical-browser receipts.
• Later, not now: move docs/fixtures/color-references.opf.json into examples with a reviewed renderer golden/corpus increase from 126 to 127+, optional PPTX schemeClr/theme writing, and editor canvas named-color fidelity.
• Broader deterministic repair, full visual editor, fonts/IME/bidi and source preservation coverage remain on the developer roadmap. PDF is raster-backed; selectable PDF and SVG/Mermaid follow font reliability.

Keep the workflow offline and provider-neutral without a required account or model call. Preserve exact evidence, authored content and explicit adjustments. Do not mark the overall goal complete while required work remains unresolved.