feat: add Launch Llama footer badge

[andrewzolotukhin]

Summary

Add the Launch Llama Newsletter badge to the public landing-page footer with separate light- and dark-theme images and the supplied referral tracking link.

Original request

Use the repository PR workflow, do not create a blog post, and add the supplied Launch Llama light/dark badge snippets to the footer.

What changed

• Added a dedicated Launch Llama footer badge using the exact https://tools.launchllama.co?utm_source=badge&utm_medium=referral destination.
• Rendered the standard featured-badge.png?v=2 asset in light mode and the white featured-badge-white.png?v=2 asset in dark mode at 200×50.
• Preserved the supplied alt text, new-tab behavior, and noopener noreferrer relationship; badge images are lazy loaded.
• Added component coverage for markup and theme classes plus Playwright coverage for real light/dark visibility switching.

Reasoning

The implementation follows the existing footer-badge convention: hosted <img> elements avoid expanding Next.js remote image configuration, explicit dimensions prevent layout shift, and Tailwind theme classes keep both variants server-renderable without client-side theme branching. The badge is placed before the terminal OpenHunts badge to preserve the existing footer ordering pattern.

Blog post

Skipped per the original request. This is a small badge-only footer attribution and does not justify a standalone public release post.

Screenshots / preview evidence

Preview: https://xpenser-pr-080.cleverbrush.com

Manual QA exercised the footer at 390×844 and 1440×900 in light and dark themes, with light/dark mobile and desktop screenshots captured during the session. Verified:

• The standard badge is visible in light mode and the white badge is visible in dark mode.
• Both assets load successfully at their declared 200×50 dimensions.
• The exact referral destination, target="_blank", rel="noopener noreferrer", alt text, dimensions, and lazy-loading attributes are present.
• Clicking the badge opens https://tools.launchllama.co/?utm_source=badge&utm_medium=referral in a new tab.
• The footer has no horizontal overflow at mobile or desktop widths.
• Fresh-session browser console and page-error checks are clean.

The passing Playwright e2e job and its Playwright report artifact provide stable browser-test evidence for the updated public homepage flow.

Validation

• npm run lint
• npm run typecheck
• npm test — 95 files, 520 tests passed
• Lint and test
• Deploy PR environment
• Playwright e2e
• Preview QA in light and dark modes at mobile and desktop sizes
• SigNoz traces, ERROR logs, and http.server.duration.count checked; recorded as an infrastructure telemetry skip because xpenser-web-pr-80 did not appear after an ingestion recheck
• PR-ready notification attempted; skipped because the configured default notifier at 127.0.0.1:8787 was unavailable

Telemetry

For xpenser-web-pr-80 in the post-QA one-hour window:

• Trace searches returned no rows before or after the ingestion wait.
• ERROR log searches returned no rows before or after the ingestion wait.
• http.server.duration.count returned no matching metric series before or after the ingestion wait.
• The preview remained healthy under both manual and CI traffic, and this footer-only diff does not touch telemetry configuration.
• The preceding footer-badge PR documented the same missing-preview-telemetry condition, so this is recorded as an infrastructure skip rather than a badge blocker.

Screenshots / Preview

See the preview evidence above and the linked passing Playwright job/report artifact.

Checklist

• I kept the change focused.
• I updated docs or tests where needed; tests were updated and the blog skip is documented above.
• I checked for secrets, local env files, and generated build output.
• API changes keep contracts, endpoint metadata, and handlers aligned (not applicable; no API changes).