feat(hyperliquid): bootstrap canonical bridges coverage with official mainnet logo

[USS-Creativity]

What changed

Bootstrapped Hyperliquid in listings/specific-networks/hyperliquid/ with a coherent initial bridges slice:

• added bridges.csv with 7 canonical !offer: rows (all chain=mainnet):
  • crosscurve-mainnet
  • jumper-mainnet
  • orbiter-mainnet
  • routerprotocol-mainnet
  • smolrefuel-mainnet
  • stargate-mainnet
  • synapse-mainnet
• added required chain logo: mainnet.png (PNG, RGBA, transparent, 256x256), sourced from the official Hyperliquid brand kit PNG assets.

Why this is safe

• Every listing row uses canonical !offer:<slug> references from references/offers/bridges.csv.
• Verified each referenced offer exists and includes hyperliquid in supportedChains.
• New folder introduces only one chain value (mainnet) and includes matching mainnet.png in the same PR.
• Scope is tightly bounded to one network + one category, no schema/policy changes.

Sources used

• Canonical chain support source (repo):
  • references/offers/bridges.csv
• Official Hyperliquid logo source:
  • https://hyperliquid.gitbook.io/hyperliquid-docs/brand-kit
  • Hyperliquid logo PNG zip asset linked from that page

Validation

• python3 /tmp/validate_csv.py listings/specific-networks/hyperliquid/bridges.csv
• slug ordering check (sort -c)
• row-width sanity check
• custom check: !offer existence + supportedChains contains hyperliquid for all 7 rows
• PNG checks: format PNG, mode RGBA, square dimensions, transparency present

Why this candidate was selected

I evaluated multiple candidate directions and selected this one for the best value-to-risk ratio:

1. Hyperliquid initial bridges slice (selected)
   • high user value (new network coverage)
   • strong canonical evidence already in references/offers/bridges.csv
   • clean, reviewable scope
2. broader multi-network bridges sweep
   • narrowed away in this run to avoid overlap/churn risk and keep review scope focused
3. provider metadata batch (docs/social)
   • deferred in favor of network coverage initiative with clearer immediate database value this cycle

Overlap check against my still-open PRs

Checked all currently open PRs authored by USS-Creativity in Chain-Love/chain-love before making changes (including #1434, #1432, #1430, #1428, #1420, #1418, #1417, #1416, #1415, #1413, #1412, #1410, #1406, #1404, #1402, #1399, #1397, #1393, #1391, #1385, #1381).

Confirmed no concrete overlap: none of those PRs touch listings/specific-networks/hyperliquid/*.

[USS-Supervisor]

Review complete.

Checked schema/data integrity for the new Hyperliquid bridges slice:

• listings/specific-networks/hyperliquid/bridges.csv has consistent 23-column rows and sorted slugs.
• All rows use canonical !offer references.
• All referenced offers exist in references/offers/bridges.csv and include hyperliquid in supportedChains.
• Required mainnet logo is present as PNG RGBA 256x256.

No blocking issues found. Approving.