Problem
The post-#1396 signal for 28-enterprise-b2b shows that the source desktop mega navigation exceeds the structure represented by core Navigation.
The source contains:
- mega-panel wrappers;
- a four-column grid;
- column headings;
- rich per-link descriptions;
- a featured region;
- desktop hover/focus behavior plus a separate mobile details navigation.
Blocks Engine currently emits a valid canonical core/navigation tree with all destinations and rich link labels, but core/navigation-submenu flattens the mega panel into one list. The panel, grid, columns, and headings are absent from the block tree.
Current evidence
After dynamic navigation is represented by the static proxy:
score 0.7398
coverage 0.8104
matched 420 / 670
desktop presence 120
The signal also reports repeated caret and rich-description color/typography deltas. The generated rich-label markers and CSS are present, so those deltas must be checked against a real WordPress/browser render before changing projection code.
Plan
- Import
28-enterprise-b2b into a disposable WordPress runtime using the current Static Site Importer and Blocks Engine candidates.
- Capture the rendered desktop navigation and compare the caret/description computed styles with source.
- Separate browser-confirmed projection defects from static-signal limitations.
- Implement a structured companion mega-navigation block for source structure core Navigation cannot represent.
- Preserve editability, URLs, labels, responsive behavior, and exact source geometry without falling back to opaque
core/html.
Acceptance
- Evidence identifies which rich-label deltas reproduce in the browser.
- The mega panel retains its authored grid, headings, descriptions, and featured region.
- Desktop and mobile behavior remain editable and deterministic.
- No
core/html fallback is introduced.
- WordPress block validity, static parity, browser parity, packaging, and solved-site promotion gates pass.
AI assistance disclosure: OpenAI GPT-5.6 Sol via OpenCode used the corrected static-parity signal to separate canonical navigation preservation from missing mega-menu structure, inspected the generated rich-label markers and WordPress core rendering contracts, searched for existing tracking, and drafted this evidence-first companion-block plan. Chris Huber directed the work and remains responsible for the issue.
Problem
The post-#1396 signal for
28-enterprise-b2bshows that the source desktop mega navigation exceeds the structure represented by core Navigation.The source contains:
Blocks Engine currently emits a valid canonical
core/navigationtree with all destinations and rich link labels, butcore/navigation-submenuflattens the mega panel into one list. The panel, grid, columns, and headings are absent from the block tree.Current evidence
After dynamic navigation is represented by the static proxy:
The signal also reports repeated caret and rich-description color/typography deltas. The generated rich-label markers and CSS are present, so those deltas must be checked against a real WordPress/browser render before changing projection code.
Plan
28-enterprise-b2binto a disposable WordPress runtime using the current Static Site Importer and Blocks Engine candidates.core/html.Acceptance
core/htmlfallback is introduced.AI assistance disclosure: OpenAI GPT-5.6 Sol via OpenCode used the corrected static-parity signal to separate canonical navigation preservation from missing mega-menu structure, inspected the generated rich-label markers and WordPress core rendering contracts, searched for existing tracking, and drafted this evidence-first companion-block plan. Chris Huber directed the work and remains responsible for the issue.