feat: add neeed.directory footer badge

[andrewzolotukhin]

Summary

Adds a theme-aware neeed.directory badge to the existing homepage footer badge collection, with focused unit and browser coverage.

Original request

Add one more footer badge linking to the xpenser listing on neeed.directory, using the supplied light and dark SVG variants. Do not publish a blog post.

What changed

• Added the hosted neeed.directory light and dark SVG badge variants to the homepage footer.
• Uses the supplied destination URL and accessible label, explicit 139 × 44 dimensions, and existing external-link/focus conventions.
• Shows the light asset in light mode and the dark asset in dark mode.
• Added component assertions for the link, sources, dimensions, and theme classes.
• Extended the public homepage Playwright test to exercise both system color schemes.

Reasoning

The implementation follows the existing Findly.tools badge pattern so hosted directory badges retain consistent accessibility, theme behavior, layout, and focus treatment. The badge remains externally hosted because the provider supplies the assets and the footer already uses raw hosted images for this class of integration.

Blog post

Skipped: this is a small footer-only directory badge, and the original request explicitly asked for no blog post.

Validation

• npm run lint
• npm run typecheck
• npm test — 95 files, 520 tests passed
• Lint and test
• Deploy PR environment
• Playwright e2e
• Preview QA
• SigNoz traces and logs
• SigNoz metrics explicitly checked; this preview web service exposed no matching HTTP or Node.js metric series

Screenshots / Preview

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

Manual QA captured the footer at 390 × 844 and 1440 × 900 in both light and dark themes. Verified:

• The correct theme asset is visible and the alternate is hidden.
• Both hosted SVGs load completely with natural and rendered dimensions of 139 × 44.
• The destination, target="_blank", and rel="noopener noreferrer" are correct.
• The 13-badge container wraps without horizontal overflow.
• Keyboard focus shows the repository-standard two-pixel ring.
• No browser console or runtime errors were reported.

The passing Playwright job above provides the stable CI evidence for the updated public homepage flow.

Telemetry

For xpenser-web-pr-76 over the post-QA hour:

• Web traces were present, including successful HTTP 200 server spans.
• No error traces were found.
• No ERROR logs were found.
• http.server.duration.count and nodejs.eventloop.utilization returned no matching metric series for this preview service, recorded as an explicit metrics skip rather than a UI blocker.

Checklist

• I kept the change focused.
• I updated docs or tests where needed.
• 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).