[kvlonge]

Why

Give SQLBuild's website and docs the approved SQLStack parent-brand attribution while preserving SQLBuild's identity and approved logos.

Changes

• Add a linked, text-aligned “by SQLStack” beneath the wordmark with balanced 80px headers and vertically centered controls.
• Add theme-aware SQLStack symbols, “Part of SQLStack”, and product-family links to both footers; reuse unchanged SQLStack assets.
• Keep docs offsets on the shared height token and clear homepage anchor destinations below the sticky header.
• Add website-only browser regressions to the Website workflow. No root README promotion, backend, compiler, or engine changes; DuckShop does not apply to website layout/navigation.

Verification

• Website build passed; link checker: 122 pages, 0 broken links.
• 16 Chromium browser cases: homepage/docs, light/dark, 320/390/800/1440px; padding, alignment, theme assets, links, anchors, pagination, mobile menu offsets.
• Inspected desktop and touch-emulated mobile screenshots in both themes, plus pointer interaction recording. Mobile coarse-pointer behavior verified.
• Independent review finding fixed and negative-control checked. Public-repository scan and diff checks passed.
• Pages deployment succeeded. Live sqlbuild.com: all 16 browser cases passed; homepage/docs returned HTTP 200 and approved logo/SQLStack asset bytes matched. Inspected fresh live desktop/mobile light/dark captures and open mobile menus.