Prove Figma-to-WordPress reliability with an end-to-end acceptance matrix

[chubes4]

Problem

The three-file Figma transformer matrix now proves substantially improved .fig to HTML/CSS fidelity, but it does not prove the complete user outcome: a real Figma design becoming an editable WordPress site through Static Site Importer. We currently cannot call the workflow reliable under the generated-site acceptance gate.

Objective

Add a deterministic, reviewer-runnable matrix that carries the existing FSE Pilot Build Theme, Twenty Twenty-Five Community, and Fisiostetic fixtures through the complete generic pipeline:

.fig -> Kiwi decode -> normalized IR -> HTML/CSS artifact -> Static Site Importer -> WordPress blocks/theme -> rendered desktop/mobile comparison

This tracker owns proof and orchestration. Generic Figma transformation remains in figma-transformer; generic HTML-to-block conversion remains in the existing transformer/import boundaries; Static Site Importer remains product-agnostic.

Acceptance criteria

• One declared matrix command runs all three fixtures through a fresh, isolated WordPress import.
• Every source file parses with zero missing emitted text, assets, or vector placeholders.
• Every imported route is valid in the block editor and remains editable with native Gutenberg blocks.
• Imported output contains zero fallback blocks.
• Desktop and mobile rendered output achieve exact 1:1 visual parity with the corresponding source-frame evidence.
• Responsive sibling groups produce one route with bounded breakpoint behavior rather than independent fixed-width pages.
• Frame selection reports whether designer dev-status or heuristic fallback selected each route.
• Failures are attributed to a named stage and stable reason code: decode, normalize, emit, import, editor validity, fallback, desktop parity, mobile parity, or responsive selection.
• Matrix artifacts include compact machine-readable summaries and reviewer-resolvable screenshots/reports without local-only paths or URLs.
• The matrix runs deterministically in repository CI or a documented repository-owned command available to a fresh checkout.

Initial dependencies

• Responsive emission: Figma transformer: responsive emission — consume sibling-groups → emit @media #247
• Dev-status frame selection: Figma frame selection: consume dev-status (sectionStatus/handoffStatus) from Kiwi decode as primary signal, heuristics as fallback #280
• Kiwi field coverage: [Tracking] Kiwi → IR → HTML field coverage matrix (data parity foundation) #328
• Three-file Figma-to-HTML parity foundation: Improve Figma transformer parity from three-file matrix #608

Completion gate

This issue closes only when all three fixtures satisfy zero fallback blocks and exact desktop/mobile parity after import into WordPress. Partial results remain evidence for targeted follow-up issues and are not described as a reliable Figma-to-WordPress workflow.