Release 0.3.1

[fstubner]

v0.3.0 is tagged at 21d58d4, 21 commits behind main. Everything since is a bug fix found by using the desktop app on a real network. Releasing the tag as it stands would ship a build where pinging your own machine reports total loss, a fresh install runs one probe at a time, and arp --clear claims to have cleared a table it never touched.

Why 0.3.1 rather than moving the tag

v0.3.0 has been public for four days. Moving a published tag is the kind of thing that bites whoever already fetched it, and the draft release can simply be retargeted.

What's in it

Three of the seven fixes are for faults that reported success while doing nothing — the category that survives longest because nothing looks wrong:

ping 127.0.0.1 / own LAN address	100% loss → works
ping ::1	100% loss → works
Max concurrent probes, fresh install	1 → 256 (every scan was serialised)
netscli arp --clear unelevated	"ARP table cleared", exit 0 → fails with the reason, exit 1
Discover	now includes hosts only the neighbour table knows
Settings dialog	centred, number field themed
Run-options menu items	were dismissed before their own click could fire

Plus: the app opens on Discover, completion toasts only fire for tabs you are not looking at, a "Clear ARP table, then discover" action, and six dependency updates.

Version surfaces

Bumped per docs/PUBLISHING.md — the four crate manifests including their inter-workspace dep specs, package.json, tauri.conf.json, and Cargo.lock via cargo update -w. That document's verification command prints 0.3.1 and nothing else.

Verified

Full workspace tests, 144 GUI unit tests, tsc -b clean. The GUI e2e suite passes end to end.

Not done here

Tagging and publishing are deliberately left out — crates.io is irreversible. After this merges: git tag v0.3.1 && git push origin v0.3.1, retarget the draft release, then publish.