Where does a WiFi rescan live, and how does it show it's working? The count "· N in range" is
really a live status field — the natural home for "scanning…". My lean: an explicit ⟳ rescan
action in the engrave line (discoverable, same slot as "+ hidden"), with a flash-and-fade
busy state — the glyph spins, the count breathes, new rows fade in as found. The count is also
click-to-rescan as a shortcut. Use the selector on the right to feel each busy treatment.
net·01 — networks section
ONLINENET·01
channel
@Hyatt_WiFi-59 dBm · 44 ms
172.20.2.108/20 · gw 172.20.0.1 · route wlp170s0
networks· 5 in range⟳+ hidden
busy feedback style
The three busy signals
Spinner — the ⟳ glyph rotates while scanning. The clearest "working" cue; universal.
Count breathe — "· 5 in range" becomes "scanning…" and slow-pulses. Your idea: the status field animates in place, no extra chrome.
Section breathe — the whole list gives a faint gold breath while the scan runs; found rows fade in gold. Ambient, ties the animation to what's changing.
All (recommended) — spinner + count + fade-in together. The section breathe is optional; it can read as busy on a small panel, so it's off in "all" by default and its own option to try.
Why an explicit action, not only the count
Overloading the count as the sole trigger is elegant but a first look doesn't know it's clickable.
An explicit ⟳ rescan in the engrave line is discoverable, sits in the same slot as "+ hidden"
(consistent), and doesn't cost a heavy console key. Keeping the count clickable too gives power users
the shortcut without hiding the affordance. A dedicated RESCAN console key (next to DOCTOR /
SPEED TEST) is the third option — heavier, and rescan is a list action, not a diagnostic, so it fits
the engrave line better.