Commita819f96unknown_key

fix(landing): stop rendering two stacked landing pages

fix(landing): stop rendering two stacked landing pages

LandingPage rendered <Land2030/> immediately followed by <LandingHero/> —
two full documents in one response, so scrolling revealed a second site with
its own H1. Render a single landing surface. Full 2030 reboot to follow.

https://claude.ai/code/session_01QKaJBYpD6DGErWHrRVChkf

Claude committed on May 31, 2026Parent: f635e2f

1 file changed+4−6a819f9669f58e6a29d9df24b773c400ae99914c0

1 changed file+4−6

Modifiedsrc/views/landing.tsx+4−6View fileUnified Split

@@ -1612,13 +1612,11 @@ const Land2030: FC = () => (

16121612);

16131613

16141614// Backwards-compatible default — web.tsx imports `LandingPage`.

1615// The 2030 prelude is rendered above the existing LandingHero so every

1616// existing L10/U1/Q1/M1 regression assertion keeps passing untouched.

1615// Single landing surface. The bolted-on <Land2030 /> prelude was rendering a

1616// SECOND full page above LandingHero — two stacked <h1> documents as you

1617// scrolled. Render exactly one page; the 2030 reboot replaces this wholesale.

16171618export const LandingPage: FC<LandingPageProps> = (props) => (

1618 <>

1619 <Land2030 />

1620 <LandingHero {...props} />

1621 </>

1619 <LandingHero {...props} />

16221620);

16231621

16241622export default LandingPage;

16251623