feat: add Super Launch footer badge

[andrewzolotukhin]

Original request

Add the supplied Super Launch badge to xpenser using the PR workflow, without creating a blog post. The badge should link to https://www.superlaun.ch/products/2933 and use the hosted https://www.superlaun.ch/badge.png asset.

What changed

• Added an accessible Super Launch badge to the shared public-site footer.
• Preserved the hosted asset's verified 470×130 intrinsic ratio and rendered it at 235×65 so it fits the existing badge row without distortion.
• Opens the Super Launch product page in a new tab with rel="noopener".
• Added focused landing-page component coverage for the link, image metadata, lazy loading, and rendered sizing.
• Added Playwright coverage for visibility and link/image behavior in both light and dark color schemes.

Reasoning

The supplied snippet declared a 300×300 image, but the hosted PNG is actually 470×130. Using the verified intrinsic dimensions prevents distortion, while a 235px rendered width matches the scale of the existing footer badges. The implementation follows the repository's established plain <img> convention for small third-party hosted badges, avoiding a new Next.js remote-image allowlist entry for a single footer asset.

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-081.cleverbrush.com

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

• The hosted badge loads successfully with its real 470×130 intrinsic dimensions and renders at 235×65 without distortion.
• The badge remains clear and aligned with the existing footer badge stack in both themes and at both viewport sizes.
• The exact destination, target="_blank", rel="noopener", alt text, and lazy-loading attribute are present.
• Clicking the badge opens https://www.superlaun.ch/products/2933 in a separate tab.
• 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

Local

• npm run lint
• npm run typecheck
• npm test — 95 files, 520 tests passed
• Focused landing-page component test

GitHub / preview

• Lint and test
• Deploy PR environment
• Playwright e2e
• Preview QA in light and dark modes at mobile and desktop sizes
• Outbound Super Launch link verification
• SigNoz traces, ERROR/FATAL logs, and http.server.duration.count checked; recorded as an infrastructure telemetry skip because xpenser-web-pr-81 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-81 in the post-QA one-hour window:

• Trace searches returned no rows before or after the ingestion wait.
• ERROR/FATAL 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.
• PR feat: add Launch Llama footer badge #80 documented the same missing-preview-telemetry condition, so this is recorded as an infrastructure skip rather than a badge blocker.

Notification

The notification token is configured, but the default PR-ready notifier at http://127.0.0.1:8787/v1/pr-ready refused the connection. Notification was therefore skipped without exposing credentials.