Add Smol Launch footer badge

[andrewzolotukhin]

Original request

Add the supplied Smol Launch featured badge to xpenser with light and dark theme assets, using the repository PR workflow and without a blog post.

Summary

Adds a theme-aware Smol Launch badge to the public landing-page footer so visitors see the matching hosted badge in light and dark modes.

What changed

• Added a Smol Launch footer badge linking to https://smollaunch.com in a new tab with rel="noopener".
• Added the supplied featured.svg and featured-dark.svg hosted assets at their declared 250×60 dimensions with lazy loading.
• Reused the existing footer badge focus styling and theme visibility classes.
• Added component coverage for link, image, sizing, lazy-loading, and theme attributes.
• Added Playwright coverage for light/dark visibility on the public landing page.

Reasoning

The implementation follows the existing theme-aware footer badge pattern: one accessible link wraps two hosted images, while dark:hidden and dark:block select the correct asset. Keeping the assets hosted avoids introducing copied third-party files or Next.js remote-image configuration for a small footer badge.

Blog post

Skipped. This is a small third-party directory badge addition and does not justify a standalone public release article, as explicitly requested.

Screenshots / preview evidence

Preview: https://xpenser-pr-079.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:

• Both Smol Launch SVGs return HTTP 200 and load at their native 250 × 60 dimensions.
• Only the correct theme variant is displayed at each viewport and theme.
• The exact destination, target="_blank", rel="noopener", alt text, dimensions, and lazy-loading attributes are present.
• The badge and page have no horizontal overflow at either viewport.
• No browser errors or console output occurred during the badge QA flow.
• External navigation was not exercised; the rendered DOM href was verified exactly.

The passing Playwright e2e job provides stable browser-test evidence for the updated public homepage flow.

Validation

• npm run lint
• npm run typecheck
• npm test — 95 files and 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, logs, and metrics checked; recorded as an infrastructure telemetry skip because xpenser-web-pr-79 never appeared as a trace, log, or HTTP metric resource
• PR-ready notification attempted; skipped because the configured default notifier at 127.0.0.1:8787 was unavailable

Telemetry

For the post-QA xpenser-web-pr-79 window:

• Trace queries returned no rows, including after an ingestion wait and recheck.
• ERROR log queries returned no rows.
• http.server.duration.count returned no matching metric series.
• Resource-value discovery did not list PR 79 for traces, logs, or that metric.
• The successful deployment received the repository-configured PR OTLP endpoint and PR number, and the preview remained healthy under manual and CI traffic.
• Because this footer-only diff does not touch telemetry configuration and the preceding badge PR recorded the same missing-preview-telemetry condition, this is documented as an infrastructure skip rather than a badge blocker.

Screenshots / Preview

See the preview evidence above and the passing Playwright job for stable browser-test evidence.

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; no API changes are included.