Preserve route-specific header visibility and menu labels on inner pages

[chubes4]

Reproduction

Import https://ward-behavior-path.base44.app/ through Studio trunk from URL using published DLA v0.8.4 and SSI v1.20.7. In a real 1600px Chromium browser, compare source and imported /about/ and /why-choose-us/. The source visible header reads Ward / BEHAVIORAL CONSULTING / Menu / Get Started; the imported one replaces Menu with About or Why Choose Us, and additionally shows a Back / About Us or Back / Why Choose Us row before the hero. Source has a Back header node in its DOM, but it is not visible in body text at this width. WordPress made it visible. On Home the visible menu label remains Home.

This explains part of the released DLA compare body text count mismatch (besides the desirable accessibility skip link), and is a real first-screen visual difference, independent of typography/container measurements tracked at #2353.

Acceptance

Preserve source-authored per-route header labels and breakpoint visibility when lowering shared header and route-specific inner-page chrome to editable blocks. At 1600px About and Why Choose Us should present the same visible menu title and hidden Back row as source, while phone/tablet and Home retain their own observed states. Add a neutral multi-route browser geometry/text regression with a route-specific hidden header row.

AI assistance: OpenAI GPT-6 Sol via OpenCode compared the published-release Studio import with the public source in Chromium, localized the hidden/visible header mismatch, and drafted this issue under Chris Huber direction.

[chubes4]

Review finding: an isolated theme-assembly candidate proposed per-route templates plus retaining end-anchored chrome when its text is not in lifted shared parts. It has not been published. Its neutral test hard-coded the Ward site name and expected the Back / About Us row to survive, while the live source hides that row at desktop and the WordPress import currently shows it incorrectly. No fresh paired import proved source-visible Menu/no-Back on desktop or mobile behavior. Focused 2 JS tests and typecheck passed, but the submitted Homeboy gate used mismatched pnpm and did not run. The candidate and test remain isolated review evidence; next fix must trace source breakpoint visibility and verify fresh WordPress rendering at 390/768/1600px before publication.

AI assistance: OpenAI GPT-6 Sol via OpenCode compared live source and WordPress visible header text, reviewed the Homeboy candidate and its tests, and rejected an unproven implementation under Chris Huber direction.

[chubes4]

Root-cause split after browser-checking live → retained capture → imported WordPress on /about/: the captured DLA HTML already replaces live desktop Menu with About and inserts an About Us span into the mobile Back row (live mobile row contains only Back). That source-capture loss is now tracked at Automattic/data-liberation-agent#479. The header.lg:hidden desktop row has display:none live but display:flex on WordPress because the generated page stylesheet loads after the authored shared stylesheet and overrides responsive utilities; that CSS cascade fault remains at #2353. A generic JS theme/chrome candidate for this issue was withheld: it preserved the added Back row and did not restore source text or desktop hiding. Reassess this issue after those two owning fixes rather than shipping the unverified candidate.

AI assistance: OpenAI GPT-6 Sol via OpenCode compared the live source, retained DLA capture and imported WordPress DOM at 390/768/1600px and reviewed the Homeboy theme candidate under Chris Huber direction.