fix(wireguard): replace dead Proton configs with a working set

The seven Proton configs imported April 10 completed the WireGuard handshake but Proton routed no data: DNS and traffic through the tunnel timed out on every server. Fresh configs from the Proton dashboard route data normally. That confirms the old keys were deauthorized account-side, not a local routing, firewall, or NetworkManager fault.

Swap in three fresh configs (NL, US-CA, US-TX) and point the panel tunnels manual-test at the new connection names.

1 files changed, 2 insertions, 2 deletions

diff --git a/todo.org b/todo.org
index d04812f..874d85c 100644
--- a/todo.org
+++ b/todo.org
@@ -697,8 +697,8 @@ Expected: Account shows your Proton username instead of 'None'. After that, prot
 *** Tunnels round-trip: panel rows + bar badge (first real tunnel-owned route)
 What we're verifying: the panel's Tunnels tab drives a real wireguard tunnel up and down, and the bar indicator grows the vpn badge while the tunnel owns the default route (the badge has never rendered live — every prior check ran with the wlan owning the route).
 - Open the net panel (left-click the bar's net module), switch Connections to the Tunnels page.
-- Confirm the rows: tailscale (up), and the seven Proton configs (USNY, USDC, USCALA, USCASF, USGAAT, switzerlan-zurich1/2), all down.
-- Select USNY, press Bring Up, wait for the row to land.
+- Confirm the rows: tailscale (up), and the three Proton configs (wg-US-TX-714, wg-US-CA-144, wg-NL-781), all down.
+- Select wg-US-TX-714, press Bring Up, wait for the row to land.
 Expected: the bar's net glyph gains the small vpn badge; its tooltip names the owner ("Tunnel: default route via wgpvpn (wireguard)").
 - Press Bring Down on the same row.
 Expected: badge gone, tooltip back to normal, internet still works (the wlan owns the route again).