stats + revenue: name every rail, and say when the canary is filtered out

[MikeyPetrillo]

Two findings, both surfaced by checking things that were reported as looking wrong but turned out to be reported correctly.

1. One chain shown as two rows; two rails shown as hex ids

Found while verifying the Monad rail was healthy. It is — but the per-chain split on the public /api/stats was reporting the same chain twice:

Shown as	Reality
monad 19 + eip155:143 42	monad, 61
celo 35 + eip155:42220 16	celo, 51
stellar 71 + stellar:pubnet 20	stellar, 91
eip155:10 14, eip155:1329 9	optimism and sei — unnamed entirely

networkFromPaymentResponse maps CAIP2_NAMES[id] || id, so a chain missing from that map is booked under its raw id. Sei and Optimism, the two most recently added rails, were never added — every settlement on them has displayed publicly as a hex chain id since they shipped.

No money affected. What is affected: per-chain revenue reads low for every split rail, on a surface that looks authoritative.

Fixed both ways — the two missing names, plus mergeNetworkCounters folding raw-id counters into their named bucket at read time. Deliberately not a history rewrite: stored counters stay as recorded, and a chain we genuinely cannot name still reports under its raw id rather than vanishing, because silently dropping revenue is worse than showing a hex string. Totals asserted conserved.

scripts/test-chain-names.js fails if any offerable chain lacks a name, so a thirteenth rail cannot ship unnamed.

Note on the guard itself: its first version called railStatus(), which reads boot state and is empty offline — so the assertion that matters passed while checking zero rails. It now sources the static NETWORKS map and checks 12.

2. "I don't see any canary runs on the revenue page"

The canary was running fine — it settled on 11 of 12 rails that day, all present in /api/revenue/daily. Only Celo was missing, and Celo's facilitator is down.

The chart defaults to External scope, which is correct and stays: the canary buys from us with our own wallet, and counting it as revenue would inflate every number on the page. But that made "the canary stopped running" and "the canary is excluded by the current filter" look identical on screen.

The page now says, when internal settlements exist and are hidden: how many chains, how many days, which control reveals them, and why they are excluded. The number on the chart does not move. The note hides itself when the scope already includes internal, because a note that renders in every state is decoration.

Verification

• 10 assertions in test-chain-names.js, 4 added to test-revenue-chart.js (jsdom), both in CI
• Six mutations, all killed: removing optimism from the map, dropping unnameable chains, overwriting instead of summing, never showing the note, showing it when nothing is hidden, and dropping the why
• Sweeps clean: 209 strict / 295 lenient tools, 526/526 through MCP, full offline battery