[kvlonge]

Why

Keep SQLBuild's repository and documentation branding aligned with the approved artwork used on sqlstack.io.

Changes

• Reuse the original approved light/dark SQLBuild lockups from the SQLStack website asset archive, without redrawing them.
• Use the approved symbol from sqlstack-io/sqlstack for the home/docs favicons.
• Refresh home/docs headers and existing social cards; make the README logo theme-aware using the same website assets.
• Keep this separate from implementation work: only README and website branding files change. No runtime, dependency or workflow changes.

Verification

• npm run build --prefix website passed.
• python3 website/scripts/check_links.py website/dist: 122 pages, 0 broken links.
• Browser inspection of home/docs in light/dark themes at desktop and narrow widths; no clipping or horizontal overflow. Inspected both social cards and transparent artwork over light/dark backgrounds.
• Independent read-only review found no blockers; artwork identity, dimensions and changed social-card pixel regions checked.
• Public-repository hygiene, diff whitespace and duplicate-code checks passed.
• No DuckShop case applies: this is an image/branding-only change with no compiler or project-shape behavior.