Fix generic provider form topology materialization

[chubes4]

Summary

• Validate and materialize generic/form-control-topology/v1 through canonical Jetpack field blocks and submit controls.
• Project bounded source grid layout facts through generic/provider-layout-target-map/v1 onto Jetpack's rendered form and provider wrappers.
• Persist validated overlays into frontend and editor stylesheets and fail closed on unsupported provider structure or unsafe layout facts.
• Prepare Jetpack Forms after dependency activation and add the static-entry front-page fallback for activated imports.

Tracking

Replacement for #760. Refs #765 and #757. #760 remains unchanged.

Verification

• npm test
• php tests/smoke-wordpress-site-plan-materializer.php
• php tests/form-materializer-smoke.php
• Fixture87 matrix against Blocks Engine trunk 772dcb9a: Homeboy runs 2c5ba708-ccd5-4ae4-b326-c4e0fcc3286c and 6fdbc629-3094-4e07-b6b9-41e7fcd8bc4c.

Fixture87 generation completed, but the WP Codebox runtime still reports no static front page, so editor/rendered-DOM evidence is unavailable. Visual evidence is non-acceptance only: aligned mismatch 93.77% (raw 96.16%); no parity claim.

AI Assistance

AI assistance: gpt-5.6-sol via OpenCode was used to diagnose, implement, test, and verify this provider-form repair. Chris Huber remains responsible for every line.