[itz4blitz]

What changed and why

The Call health card grew tall once it carried video numbers under the connection ones. It now stays the size it was and has two tabs: Connection (round trip, jitter, loss, traffic, transport) and Video (sending, receiving and rendered frame rates, resolution, last image, and its own send and receive graph). The Video graph keeps video's own rates and shows nothing for the seconds no video ran.

This commit was written on 4 November and never opened as a pull request. It is rebased onto main here, with the lab scenario added.

Type

• feature
• fix
• perf
• refactor
• chore
• docs

Platforms

• windows
• macos
• linux
• android
• ios

Proof

Scenario: e2e/scenarios/compact-call-health

Lab run:

The scenario starts the app with TINYCLIENT_PROVE=compact-call-health, which exits 0 only when the Video history holds video's own rates and none for seconds without video, and the Connection history is unchanged by them. It does not open the card. The card's two tabs are covered by the --shot --demo states (--tiny-menu stats and --tiny-menu stats-video with TINYCLIENT_SHOT_VIDEO=1), which are design previews, not measured call proof.

Compatibility

Client only. No protocol or stored data changes; ChartSample gains a field that lives in memory.

Risk and rollback

A wrong tab state shows the Connection tab, which is what the card showed before video numbers existed. Revert the PR.

Release note

Call health stays compact, with Connection and Video on their own tabs.

🤖 Generated with Claude Code

[github-actions]

Tiny Code Review

✅ No blocking findings — see the review · run

[github-actions]

Tiny Code Review

✅ No blocking findings.

The change is a contained GUI reorganization: it adds a video_kbps field to the in-memory ChartSample, a StatsTab state on the shell, and rewrites the stats card to render two tabs from the same history. The wire, stats collection and health grading are untouched; the chart math change (fixed 60-second x span, shared video scale) is conservative and clamped. I found no defect that gates the merge.

Residual risk

• The video chart draws a sample of (0, 0) for seconds with no video rather than leaving a gap, which reads as a flat zero line on the graph even though the stored history correctly holds None.
• prove_compact_call_health and the new unit test exercise the same in-memory history logic, so neither covers the tab rendering or the chart drawing itself; the --shot previews are the only coverage of the visual change.
• The details string built from all hints is only as useful as wherever the trimmed part of the card consumes it; if it ends up unused, clippy will flag it.

_{Agent run}