[A13xB0]

Fixes Kpa-clawbot#2193 (in the fork for review; not submitted upstream).

Problem

On an instance that keeps months of packets, the Overview tab's Packets / Hour chart becomes unreadable: 2,932 hourly bars in 720 units of plot, a date label every day, and the hours with no packets (which the server leaves out) squeezed off the axis.

Before and after

Both use the real /api/analytics/rf answer from the instance in the issue (2,933 hourly buckets over 124 days), served to the page in place of the fixture's own.

Before (master, page on "All data"):

After, same data:

Phone:

A short store (pre-prod, 7 days in memory, plus a few old packets a day for weeks before that because they were heard again). The chart starts where the real data does:

Change

All in public/analytics.js; no API change.

• packetsPerHourCard() replaces the inline block:
  • rolls the hours up to hourly, 6-hourly, daily or weekly bars, at most 180, and titles the card to match (Packets / Day);
  • counts missing hours as zero;
  • puts about 10 labels on round UTC times;
  • starts on the first UTC day with at least 2% of a typical recent day (the median of the last seven whole days), at its first hour with a tenth of a typical hour. Scanning forward, an outage after the start is never taken for it.
• Theme refresh before the data: every load fires theme-refresh about 300 ms after the theme resolves, and the page re-rendered the current tab on it. When the analytics answers came later (a busy or just-restarted server), the Overview was drawn from an empty object and threw Cannot read properties of undefined (reading 'totalTransmissions'). It now skips that refresh until the data has landed; loadAnalytics() renders the tab with the current theme when it does.

The span is still picked by the page's time window.

Tests

• tests/unit/test-issue-2193-packets-per-hour.js (in test-all.sh, red then green): 122 days gives 123 daily bars with 4 to 12 labels; 7 days gives 168 hourly bars; missing hours are drawn as zero; the chart starts at the data, not at the stragglers, and not after an outage; no data says so.
• The theme-refresh guard has no test of its own: it's a three-line early return, and the commit message explains the race.
• sh test-all.sh passes; the Neighbor-graph filter E2E fails under CI load: skip-message transition is undone by a later re-render (#1758 lifecycle) Kpa-clawbot/CoreScope#1925 neighbour-graph theme-refresh test and the analytics chart test still pass; the screenshots show no page errors and no sideways scroll at 1280 px or 390 px.

🤖 Generated with Claude Code

https://claude.ai/code/session_01KaR4xu8gVykQBkH8yG8m6H

[A13xB0]

Submitted upstream as Kpa-clawbot#2194.

[A13xB0]

Merged upstream as Kpa-clawbot#2194; closing.