chore(todo): close the speedtest streaming task, file its panel manual test

1 files changed, 10 insertions, 2 deletions

diff --git a/todo.org b/todo.org
index 41a0512..f41b6f7 100644
--- a/todo.org
+++ b/todo.org
@@ -65,8 +65,11 @@ Fixed (dotfiles =8dd36c4=). Root cause: =_fuzzel= ignored fuzzel's exit code, so
 
 Craig's report (roam inbox, 2026-07-02): hitting cancel via escape at the step after choosing "timer" does nothing but proceed to the next step — likely the same for the other dialog steps.
 
-** TODO [#B] Network panel: stream speedtest results live :feature:waybar:network:solo:
-Craig's ask (roam inbox, 2026-07-02): the speedtest only shows results at the end; typical speedtest UIs report the numbers as they come in. Stream the CLI's progress into the results box as it arrives, then the final numbers at the end. Related finding: the "Tip" row under the results (screenshot ~/pictures/screenshots/2026-07-02_225441.png) is a static hardcoded string shown after every run, not derived from the results — replace it with result-aware guidance or drop it (Craig asked what criteria produced it; the answer is none).
+** DONE [#B] Network panel: stream speedtest results live :feature:waybar:network:solo:
+CLOSED: [2026-07-02 Thu]
+Shipped (dotfiles =38171e8=). =run_speedtest_stream= runs speedtest-go's plain mode, whose lines land one per completed phase (parser written against a real captured hotel-wifi run). Panel: a checklist fills in as ping → download → upload arrive, final rows at the end. =net speedtest= streams the same lines at the terminal (=--json= keeps the one-shot envelope). Bonus from the text mode: jitter (rides the Ping row) and packet loss (own row, warns >1%) — the JSON mode never reported either. The static Tip is gone; =speedtest_tips= derives guidance from the numbers (high ping >100ms, download < half of upload, <10 Mbps both ways, loss >1%), each tip naming its trigger values — that's the answer to Craig's "what criteria" question: the old tip had none, the new ones are stated rules. 509 net tests / 45 suites green; live CLI run streamed correctly and fired the asymmetric-download tip on real numbers (33 down / 76 up). Manual test filed for the in-panel run.
+
+Craig's ask (roam inbox, 2026-07-02): the speedtest only shows results at the end; typical speedtest UIs report the numbers as they come in. Stream the CLI's progress into the results box as it arrives, then the final numbers at the end. Screenshot: ~/pictures/screenshots/2026-07-02_225441.png.
 
 ** TODO [#B] Bluetooth panel: switch placement + panel title :feature:waybar:bluetooth:solo:
 Craig's ask (roam inbox, 2026-07-02): move the bluetooth on/off switch above all the buttons. "Bluetooth" becomes the panel's title, with the on/off switch right-justified on that title row. Panel code in ~/.dotfiles =bluetooth/= (GTK4 + Blueprint, phase-2 PanelModel/presenter — see the shipped panel task in Resolved). Presenter tests + the AT-SPI smoke likely need their layout assertions updated.
@@ -862,6 +865,11 @@ Expected: an alarm appears on the bar showing 14:30 as its fire time.
 Expected: a fail notification names the bad input; nothing is created.
 - Cancel the test alarm (right-click the module, pick it).
 
+*** Speed test streams in the panel
+What we're verifying: the panel's speed test fills in as phases complete instead of dumping everything at the end (the CLI path is live-verified; this is the GTK rendering).
+- Open the net panel, Diagnostics → Network Performance → Run Speedtest.
+Expected: a Ping/Download/Upload checklist appears under the running row; ping lands within seconds, download mid-run, upload near the end; then the final rows (with jitter on Ping, a Packet loss row) replace it. A Tip row appears only if a rule fired, and it names the numbers that triggered it.
+
 *** Proton VPN CLI sign-in (velox now, ratio on its trip)
 What we're verifying: the proton CLI has its own account store (separate from the retired GTK app's), so the panel's proton rows can't toggle until you sign in once per machine.
 - Run in a terminal: protonvpn login <your-proton-username> (it prompts for the password).