Continue the OpenPresentation ecosystem as the primary project owner on this Mac. Set this session's goal to the following:

Build and release a polished, reliable, fully open and provider-neutral presentation ecosystem for humans and external AI agents: JSON authoring, deterministic automatic layout and repair, browser preview, intuitive editing with preview/undo, and editable PowerPoint export. Essential functionality must work locally and offline without model calls, API keys, accounts or paid services. OPF must not embed or depend on an AI design agent. Preserve content, source mappings, reading order, rich formatting and metadata; never silently delete, summarize, truncate or shrink below the selected readability floor. Native proprietary applications are compatibility test environments, not runtime dependencies.

First fetch OpenPresentation/opf main from GitHub. Read docs/handoff-2026-09-08.md IN FULL, docs/handoff-2026-09-10-wrap-up.md, docs/plans/ecosystem-objective-2026-09-09.md and the linked active font/layout plans. Use GitHub repositories, branches and immutable commits, never paths or artifacts from the old Windows computer. Inspect current main, PRs, registry versions and deployments before changing anything. The wrap-up includes core PR #61, renderer #12, PPTX #16 and editor #11; verify their actual merge state and the final checkpoint recorded in the wrap-up.

Repository map: OpenPresentation/opf, OpenPresentation/opf-render, OpenPresentation/opf-pptx, OpenPresentation/opf-editor; Data-Advantage/openpresentation-site (openpresentation.org), Data-Advantage/pptx-gallery (pptx.gallery), and Data-Advantage/pptx-dev (pptx.dev). Clone the four public package repositories as named siblings where coordinated scripts require it. Follow each checkout's AGENTS.md and only the relevant OPF skills.

The published set at wrap-up is core 0.9.0, CLI 0.7.0, renderer 0.7.0, PPTX 0.7.0 and editor 0.6.0. Those versions and all older releases are already published: do not republish them. The newly merged shared metric/card/text placement work remains unpublished. Its package.json versions still describe the previous published set. Develop with the supported coordinated linking and clean candidate tarball scripts; installing old registry dependencies alone cannot supply the new APIs. Source CI pins and historical registry verification refs serve different purposes. Keep release-plan.json describing actual published packages until publication succeeds.

Finish the existing font/layout reliability work first. Shared metric internals, card padding, inherited chart/table colors, offline artwork, accepted scalar/rich text origins and guarded heading recovery have substantial evidence. A reviewed 805-slide corpus baseline is a regression checkpoint, not a visual-quality or native-fidelity certification. Known gaps include estimated-font rich spacing, sparse cards/whitespace, missing external CSV/workbook content, advanced chart semantics, source-preserving whitespace and remaining payload internals. Make resolved-font preparation convenient and deterministic. Extend bounded measurement/repair and meaningful quality tests; expose supported APIs, CLI diagnostics, skills and Auto arrange with preview/undo. Respect explicit human adjustments.

Continue docs/font-fidelity.md and docs/plans/font-roadmap.md. Evaluate exact font bytes, variants, shaping, coverage, multilingual/bidirectional text, advances, wrapping, baselines, ink and complete-slide appearance. Distinguish metric-compatible, visually approximate and unsupported mappings. Evaluate Akasia/Aptos rather than assuming compatibility. Ship openly licensed offline packs with provenance, notices and hashes; do not redistribute proprietary reference fonts. Native Mac PowerPoint and Keynote evidence is valuable if available, and missing environments remain explicit gaps.

A SEPARATE agent on the Windows PC owns real PowerPoint/Excel automation and native evidence. Read its GitHub branches/PRs and coordinate via the handoff. Do not duplicate or overwrite its harness changes, claim its pending gates passed, or make native application fidelity claims from browser/DrawingML tests. Ask it for immutable findings and repro fixtures; integrate narrow fixes through reviewed PRs. The recorded Excel chart activation dialog and metric tab/portrait ink failures remain open until superseded by actual native evidence.

After the font reliability and associated layout/rendering/native gates are accepted, implement the planned selectable/searchable vector PDF export (permitted font subsets and Unicode mappings; raster compatibility mode explicit), then general sanitized SVG images and Mermaid semantic diagrams. Follow docs/plans/pdf-export.md and docs/plans/diagrams-svg.md, including the full per-family Mermaid support matrix. Preserve source and editing semantics. Distinguish semantic diagrams, editable native primitives, embedded vectors and raster fallbacks. No new PDF/SVG/diagram backend shipped in this wrap-up.

Finish checks and independent review in dependency order, then publish NEW versions core/CLI as needed, renderer, PPTX, editor; refresh lockfiles only after predecessors are published. Update release plans and immutable refs, verify fresh registry installations and actual installed-package browser E2E, then update all three public sites. Check exact dependencies, deployed bundles/font assets, changelog accuracy and author/import → layout/preview → edit/undo → export → reimport workflows. Previous public adoption and the supported six-skill command `npx @openpresentation/cli@latest skills install` are already implemented; verify current status and improve them as needed rather than recreating them.

Keep Dependabot security alerts visible; test upgrades, keep sensible weekly grouping and avoid redundant review notifications. Audit any newly opened PRs and documented major-upgrade follow-up issues rather than blindly merging them. Clearly separate schema support, source/candidate/registry tests, browser behavior, regression stability, visual quality, font compatibility and native export fidelity. Work in reviewable milestones, preserve historical failures, and keep portable GitHub evidence and handoff current. Pushes, PR updates, merges, tags, npm publication and public deployment updates are authorized. Do not declare the overall goal complete just because the wrap-up PRs merged.