Deep Adapter Recipes Proof

This report records the generated-surface adapter recipes that are already covered by tests, browser examples, and package-consumer smoke. It complements docs/adapter-recipes-roadmap.md, which remains the forward-looking checklist for broader public-release hardening.

Vega-Lite Compile-To-Vega

Status: proven in adapter tests and browser example coverage.

• test/adapters/vega.test.ts compiles a Vega-Lite spec through public vega-lite and vega APIs, runs a Vega View, and anchors to the generated scenegraph mark by markName, markType, and datum predicate.
• examples/vega-basic and scripts/verify-examples-browser.mjs verify rendered Vega marks, target alignment, generated obstacles, visible notes, visible connectors, and screenshot evidence.

Mermaid Flowchart And Sequence SVG

Status: flowchart and sequence browser-proven, with translated-label data-hook recipes also browser-proven; sequence SVG fixture coverage is also kept in adapter tests.

• examples/mermaid-basic renders real Mermaid flowchart and sequence diagrams, annotates rendered flowchart node labels, a rendered flowchart edge route, a sequence actor, a sequence message label, and mermaid-sequence-route. Browser verification checks target alignment against actual Mermaid SVG nodes, paths, actor elements, message labels, and line.messageLine0/path message routes.
• The same browser example renders a localized Ingresso dati node and anchors mermaid-translated-data through [data-node-id="flow-intake"] plus the translated-node class, proving consumers can avoid label text when Mermaid translated labels or user-authored labels are unstable.
• test/adapters/mermaid.test.ts covers a Mermaid sequence-style SVG fixture with participant, message label, and message route anchors using labels, data-message-id, and data-edge-id.
• src/adapters/mermaid.ts treats common sequence classes such as actor, messageText, path.messageLine0, line.messageLine0, and messageLine1 as default obstacles and route candidates.

D2 Nested Diagrams And Routes

Status: nested compiled geometry is test-proven; rendered D2 SVG and route anchors are browser-proven in the basic example.

• test/adapters/d2.test.ts walks nested diagram shapes, layer shapes, and generated connection routes from compiled D2 geometry.
• examples/d2-basic and browser verification check rendered D2 shapes and connection routes through target-alignment assertions.
• SVG-only consumers are covered by rendered SVG selectors, classes, labels, data attributes, shape ids, and connection ids in the D2 adapter tests.

React Flow Viewport, Handles, And Editing

Status: public state, transformed viewport coordinates, measured handles, edge anchors, and host-owned edit patches are browser-proven and test-proven.

• test/adapters/react-flow.test.ts normalizes node boxes through viewport x, y, and zoom, uses measured handle geometry before fallback side anchors, and extracts node, handle, and edge obstacles.
• examples/react-flow-basic runs with a non-identity React Flow viewport, verifies rendered nodes, edges, and handles against public adapter output in the browser, and persists a dragged note edit as a host-owned annotation patch.
• npm run test:dogfood:external can run with PONCHIA_ANNOTATIONS_EXTERNAL_CONSUMER_MODE=react-flow; the local external pass measured a real rendered React Flow diagram, fed 7 rendered nodes, 6 generated edge routes, 12 handles, and 42 sampled SVG route points through prepareReactFlowAnnotations, then verified visible notes/connectors and target alignment in Chromium.
• test/adapters/authoring-contract.test.ts, test/core/edit.test.ts, and examples/react-basic cover edit-patch preservation and note/anchor movement contracts.

Remaining Limits

• The clean generated-surface dogfood consumer still uses invented report content, but npm run test:dogfood:self-report now covers a real release-evidence report built from the repository's own readiness and completion data. npm run test:dogfood:external adds env-gated external Astro/React host passes over rendered DOM stack-page geometry and rendered React Flow diagram geometry; broader production-specific Vega, Mermaid, D2, and editing surfaces should still keep feeding friction reports before widening 0.1.x stability promises.