Chrome subscribes to OS-level NetworkChangeNotifier callbacks (OnNetworkConnected, OnNetworkDisconnected, OnNetworkMadeDefault) and triggers migration in response. neqo-bin has no such hook.

This would require:

1. Platform-specific network change detection (e.g., network-interface or network-manager crate on Linux, SCNetworkReachability / NWPathMonitor on macOS)
2. A new event or callback from neqo-bin into the transport when the available network set changes
3. Enumerating available alternate sockets/interfaces to migrate to