Improve Figma-to-WordPress parity and runtime bindings

[chubes4]

Summary

Improve generic Figma HTML to editable WordPress conversion across the Fisiostetic and FSE Pilot fixtures.

• preserve native image border save shape, presentation geometry, and equal physical borders
• preserve CSS background-image box dimensions and cover/contain scaling in editable core/image blocks
• canonicalize runtime binding assets and routes through the same site-plan pipeline as page markup
• normalize duplicate binding occurrences and retain binding-bearing shells
• compose provider-backed forms around one exact controls slot so headings, copy, layout, and decorative media remain native blocks
• cover replaced form runtime-island selectors so provider materialization fully supersedes preserved controls
• aggregate multi-page Figma text-coverage evidence and classify semantic form-control clone composition intentionally

Runtime evidence

Fisiostetic

• 159/159 valid native editor blocks
• zero fallbacks
• approximately 1.77% visual mismatch

FSE Pilot

• provider-enabled five-page import completes
• 165/165 valid native editor blocks
• zero invalid blocks
• zero preserved runtime islands after provider materialization
• background image geometry now renders at the source 691 x 345.5 box with object-fit: cover
• overlap mismatch improved from 31.69% to 29.32%

Latest FSE evidence root:

/var/folders/lr/c_cmmt7s0592m4njz99v5yb40000gn/T/opencode/fse-background-image-geometry-runtime-proof

Validation

• composer test in figma-transformer
• composer test in php-transformer
• 248 PHP parity fixtures
• PHP package install proof
• real provider-enabled FSE WP Codebox import and editor validation
• real Fisiostetic editor and visual-parity acceptance

Residual gaps

• FSE visual parity is not complete; the remaining overlap mismatch is 29.32%, concentrated in newsletter/footer, card-grid, navigation, and typography presentation.
• Authoritative Figma desktop/mobile screenshots were unavailable, so Figma-to-HTML pixel parity remains unproven.
• FSE still reports one intentionally blank form-control text layer as an empty decoded text node; emitted text coverage is zero-loss.
• The provider-enabled acceptance path currently relies on the open WP Codebox staged-file streaming repair in Stream large staged files into Playground wp-codebox#1993.

Related

• Gate generated-site acceptance and built status on parity evidence static-site-importer#673
• [Epic] Production readiness: static HTML → working WordPress site (visual + feature parity) static-site-importer#489
• Stream large staged files into Playground without whole-file base64 allocation wp-codebox#1990
• Stream large staged files into Playground wp-codebox#1993

AI assistance

• Model: OpenAI GPT-5.6 Sol
• Tool: OpenCode
• Use: Investigated Figma/HTML/WordPress evidence, implemented the transformer and site-plan changes, added regression coverage, and ran the acceptance workflows. Chris Huber reviewed and remains responsible for the changes.