Expand description
The DigPeer connection lifecycle.
A DigPeer moves through a small, explicit state machine so callers (and the crate itself) always know whether an RPC may be issued. The transitions are deliberately minimal — dig-peer’s job is to be a thin, honest client, so the state is just enough to reject use-after-disconnect and to report liveness, not a full reconnection engine (opportunistic re-dial is a documented follow-up).