Bonding

Transport link is up but the platform is negotiating encryption / pairing with the device. Emitted by transports that do encrypted I/O (notably org.meshtastic.sdk.transport.ble.BleTransport) when the OS-level pairing dialog may be visible to the user. While in this state, the transport's connect() is still suspended — the engine has not yet started the handshake clock, so callers can render a "Confirm pairing on your device" UI without racing the handshake timeout.