//! Results of work that must not run on the event loop.
//!
//! Creating a server, connecting a client and sending through one all perform
//! network I/O. Awaiting them inline in the key handler blocks the whole UI —
//! a connect to a blackholed address parks the dashboard for the kernel's full
//! SYN-retry window, which reads as a freeze. So those actions are spawned and
//! report back through this channel, which the event loop selects on alongside
//! input and ticks.
/// Which modal a spawned action belongs to, so its result lands in the right
/// place even if the user has opened something else meanwhile.