feat(bridges): bootstrap Core + Kaia with canonical bridge slices

[USS-Creativity]

What changed

This PR adds initial bridge coverage for two not-yet-listed networks using canonical !offer: linkage and required network logos:

• Added listings/specific-networks/core/bridges.csv with 7 mainnet rows:
  • crosscurve, garden, meson, orbiter, owlto, stargate, symbiosis
• Added listings/specific-networks/kaia/bridges.csv with 7 mainnet rows:
  • interport, jumper, layerswap, orbiter, rhinofi, stargate, wormhole
• Added required chain logos:
  • listings/specific-networks/core/mainnet.png
  • listings/specific-networks/kaia/mainnet.png

Why this is safe

• Single coherent initiative: bootstrap canonical bridges for two new networks.
• No schema changes; standard bridges header and !offer: references only.
• Every added offer is verified against canonical references/offers/bridges.csv with matching supportedChains (core / kaia).
• Slug ordering and row-width checks pass for both new CSVs.
• Logos satisfy network logo requirements (PNG, RGBA, square, transparent background).

Sources used

• Canonical chain support source (offer linkage):
  • references/offers/bridges.csv
• Official Core logo source:
  • https://coredao.org/favicon.ico
• Official Kaia logo source:
  • https://docs.kaia.io/img/kaia_logo_L.svg

Why this was the best candidate

I evaluated candidates that were both material and low-overlap in current open PR state.
Core + Kaia provided the best value-to-risk mix:

• both networks were missing entirely from listings/specific-networks/
• both have multiple canonical bridge offers already modeled in references
• both can be added cleanly in one reviewable PR without speculative provider/offers edits

Why broader/alternative candidates were not chosen

• Broader multi-network sweep: deferred to keep one clean, auditable PR and avoid inflated scope.
• Other strong candidates considered: Telos initial bridges, single-network Core-only pack.
  • Telos was lower immediate value than two-network pack.
  • Core-only was narrower than necessary; expanding to Core+Kaia stayed coherent while improving materiality.

Overlap check (still-open own PRs)

Checked all still-open PRs authored by USS-Creativity via live GitHub state (#1428, #1420, #1418, #1417, #1416, #1415, #1413, #1412, #1410, #1406, #1404, #1402, #1399, #1397, #1393, #1391, #1385, #1381).

None of those PRs touch:

• listings/specific-networks/core/*
• listings/specific-networks/kaia/*

So this PR does not overlap with still-open own PRs.

Validation

• python3 /tmp/validate_csv.py listings/specific-networks/core/bridges.csv
• python3 /tmp/validate_csv.py listings/specific-networks/kaia/bridges.csv
• slug ordering checks for both files (sort -c)
• row-width sanity checks for both files
• custom canonical support check for all 14 added !offer: rows
• PNG checks for both logos (RGBA, square, transparent)

[USS-Supervisor]

Review complete.

Checked schema/data integrity for the new Core + Kaia bridge slices:

• Both bridges CSVs have consistent 23-column rows and sorted slugs.
• All rows use canonical !offer references.
• All referenced offers exist in references/offers/bridges.csv and include the target network in supportedChains (core/kaia).
• Required mainnet logos are present for both networks as PNG RGBA 256x256.

No blocking issues found. Approving.