Attribute Figma acceptance across conversion layers

[chubes4]

Summary

Progresses #619.

Make the Figma-to-WordPress acceptance harness usable for both the canonical production corpus and arbitrary operator-owned .fig files, while attributing parity to the conversion layer that introduced the difference.

The v2 matrix requires independent evidence for:

• Figma to HTML at desktop and mobile viewports.
• HTML to WordPress blocks at desktop and mobile viewports.
• End-to-end Figma to WordPress parity at desktop and mobile viewports.
• Decode, normalize, emit, isolated import, editor validity, zero fallback blocks, and responsive frame selection.

The default production profile continues to require FSE Pilot, Twenty Twenty-Five Community, and Fisiostetic. --profile=manifest evaluates every supplied fixture, allowing ad-hoc .fig files through the same fail-closed engine.

Parity evidence declares comparison: figma_html, html_wordpress, or figma_wordpress; mislabeled evidence fails rather than being credited to the wrong layer.

How to test

1. Run cd php-transformer && composer test.
2. Confirm the canonical/unit suites, 244 parity fixtures, production matrix contract, and package install proof pass.
3. Run php scripts/production-acceptance-matrix.php --help from the repository root.
4. Confirm the default profile documents the canonical three fixtures and --profile=manifest documents arbitrary fixture support.
5. Supply a manifest containing any uniquely slugged fixture and all v2 stage evidence, then run php scripts/production-acceptance-matrix.php --profile=manifest --manifest=/path/to/manifest.json --output=/tmp/acceptance.
6. Confirm the arbitrary fixture is evaluated and summary.json reports blocks-engine/figma-wordpress-acceptance/v2 with profile: manifest.

Compatibility

This supersedes the newly introduced blocks-engine/figma-wordpress-acceptance/v1 output contract with v2. Provider integrations must emit the six explicit layered parity stages and their comparison identity instead of the ambiguous desktop_parity and mobile_parity stages. No PHP Transformer runtime API, WordPress site-plan schema, or extension path changes.

AI assistance

• AI assistance: Yes
• Tool(s): OpenCode with openai/gpt-5.6-sol
• Used for: Designed and implemented generic manifest fixtures, layered parity attribution, fail-closed validation, contract tests, and documentation. Chris reviews and owns the change.