Preserve data-attribute-targeted header min-height when projecting empty layout wrappers

[chubes4]

Reproduction

Import https://www.rugliocooks.com/ using Data Liberation 0.7.2 and Static Site Importer 1.20.0 (WordPress 7.1.2). At 1440px the source and portable capture have #SITE_HEADER height 102px and the hero begins at y=102. The imported header has height 0 and the hero begins at y=0, shifting the hero and every subsequent section up 102px on all sampled desktop routes.

In source and captured DOM, an otherwise empty descendant <div data-mesh-id="SITE_HEADERinlineContent"> matches [data-mesh-id="SITE_HEADERinlineContent"] { min-height: 102px }; computed min-height is 102px. Gutenberg output replaces it with an empty wp-block-group blocks-engine-empty-visual-group blocks-engine-attribute-state-* without the source data attribute; computed min-height is 0. The parent header and first masterPage grid row collapse to zero. At 1440px, root grid rows change from 102px 0px 900px 131px to 0px 0px 900px 131px.

Acceptance

Add a neutral fixture with an empty layout wrapper sized only by an authored data-attribute selector. Project its authored sizing onto an editable core Group (or preserve an appropriate selector target) without a source-specific identifier; verify the browser height and downstream grid placement at 390/768/1440. Fresh Ruglio import restores the 102px header and hero starts at y=102 without disturbing phone layout.

AI disclosure: OpenAI GPT-6 Sol via OpenCode compared source, portable capture, and WordPress computed styles in Playwright and drafted this issue; Chris Huber directs the parity loop.

[chubes4]

Fresh paired-package retest disproves the simple transform-only fixture as a fix. Imported the retained eight-page capture with SSI main 73a01a310a88 paired against BE 8e8383fe14c3 (contains the merged navigation-font fix). At 1440px Playwright now measures source/capture/WordPress navigation 16px / 16px / 16px; however #SITE_HEADER is still 102px / 102px / 0px, so hero stays y=0 instead of y=102. Report still has one unsupported newsletter fallback.

Specific cascade gap: theme assets/assets/css/stylesheet-bundle-2b3aff8ca0a11d3d.css:192 carries [data-mesh-id="SITE_HEADERinlineContent"] { height:auto; width:100%; position:static; min-height:102px } verbatim. WP emits the corresponding carrier as wp-block-group blocks-engine-empty-visual-group blocks-engine-attribute-state-* without data-mesh-id; rule matches nothing. A direct HtmlTransformer fixture with inline <style> already projects the selector correctly, so that fixture misses the actual full-site/route stylesheet bundle projection boundary. Please make the regression go through artifact/site-plan composition and materialized theme CSS, including desktop media-linked stylesheet ownership, and verify browser hero y=102 at 1440px on a fresh paired import.

AI disclosure: OpenAI GPT-6 Sol via OpenCode built the fresh paired package, ran Studio import and Playwright computed-style checks, and traced generated CSS; Chris Huber directs the parity loop.

[chubes4]

Confirmed on a fresh eight-route Studio import: SSI main 73a01a310a88 paired with the exact Blocks Engine candidate snapshot (0072824cfdd3, source commit 1dbda3192), using the retained DLA 0.7.2 capture. Playwright at 1440px measures source/capture/import header heights 102/102/102px, hero y 102/102/102, navigation 16/16/16px. Home, About, and Contact full-page heights also match the capture at tablet and desktop widths (1133, 2006, 1694px). At the phone viewport the captured/imported header remains 0px as intended for the device-split mobile document. The site still fails the separate desktop newsletter form fallback gate (#1776), so this is a scoped header resolution, not a solved-site claim. Draft PR: #2348. All 10 required PR checks are green.

AI disclosure: OpenAI GPT-6 Sol via OpenCode rebuilt the paired importer, ran Studio and Playwright across widths, reviewed the generated PR and drafted this verification note; Chris Huber directs the parity loop.