Reach visual parity and viable editing for the Evolve Healing reference import

## Problem

The public Evolve Healing site (`https://www.evolvehealing.net/`) compiles and materializes as a 66-page WordPress block theme, but the result does not satisfy the exact visual-parity, runtime-interaction, or editor-viability gates. This issue tracks fixture acceptance while generic child issues carry independently repairable root causes.

## Current evidence

### Working

- After #1459, the homepage and sampled feedback routes return HTTP 200 under a 512 MB PHP limit.
- The generated frontend no longer injects presentation CSS into theme JSON.
- `/cchfeedback/` preserves two source forms, 44 radio inputs, and expected legends.
- `/client-feedback-form/` preserves two source forms, 48 radio inputs, and expected legends.
- The two responsive form variants match captured source structure rather than accidental importer duplication.

### Failing

- The source automatically shows a “Grids Course Pop Up” after runtime settling. Its visible close control dismisses the live dialog.
- The captured artifact retains the open popup markup but has no scripts and no `interaction-states.json`; generated WordPress output therefore shows an inert popup that cannot be dismissed. Automattic/data-liberation-agent#151 owns the missing automatic-dialog evidence.
- Editor settings contain 123,037,995 CSS bytes and 200 presentation markers, with PHP already peaking at 345,833,472 bytes before final admin serialization.
- The post editor exhausts a 512 MB limit in `WP_Scripts::get_inline_script_data()` while attempting an approximately 127 MB allocation. #1465 owns bounded editor delivery under the #867 contract.
- The imported visual/editor result is not yet acceptable: the editor presentation appears zoomed/overscaled and the overall imported fixture requires exact source-versus-WordPress comparison after the editor can load. The visual symptom remains here as an acceptance failure until reproducible browser evidence identifies a generic child root cause.

## Ownership

This is a reference-site acceptance tracker, not a request for fixture-specific CSS, markup, memory-limit changes, or popup JavaScript.

- Data Liberation Agent owns faithful bounded capture of automatic dialog state and dismissal semantics.
- Blocks Engine owns native interaction projection, bounded presentation delivery, visual geometry, semantic blocks, and meaningful editor behavior.
- Static Site Importer owns deterministic materialization and final WordPress runtime/editor acceptance evidence.

## Acceptance criteria

- A fresh public-source capture and packaged import reproduces all retained routes without development checkout overrides.
- Desktop and mobile comparisons pass the configured exact visual-parity gate with no unexplained geometry, scale, typography, or responsive drift.
- The automatic popup matches source initial visibility and can be dismissed through a WordPress-native interaction.
- Frontend pages and post/site editors operate under a 512 MB PHP limit with bounded CSS and script payloads.
- Editor and frontend presentation match at equivalent canvas widths without zoom/scale distortion.
- Loaded blocks are valid, ordinary content is meaningfully editable, and the final site contains zero unsupported fallback blocks.
- Forms retain source field/group semantics while using the declared WordPress provider and pass owner submission evidence.
- SSI acceptance evidence binds passing route, visual, editor, interaction, fallback, provider, and materialization receipts before the fixture is marked accepted/built.

## Related

- #867
- #1459
- #1465
- #220
- Automattic/data-liberation-agent#151

## AI assistance

OpenAI GPT-5.6 Sol via OpenCode was used to inspect the generated WordPress site and source artifact, reproduce frontend/editor memory behavior, compare popup behavior against the live public source with Playwright, reconcile owning-layer trackers, and draft this issue. Chris Huber directed the acceptance standard and reviewed the evidence.

Read the acceptance evidence for the Evolve Healing routes, related issues #1459 and #1465, and the WP_Scripts::get_inline_script_data() failure; compare the public source with the packaged import under the 512 MB PHP limit. Done means the configured visual, editor, interaction, fallback, provider, and materialization gates pass without fixture-specific overrides, with no unsupported fallback blocks.

Written by the indexing model from the issue text.