Review (W6): RaftAdapter._stop_bridge runs from async disconnect() and ended with
release_process_group_once_empty at its default 1 s timeout, against the API's own rule
(timeout=0 for async callers). proc.terminate() signals only the leader, so any child left in the
bridge's group made disconnect stall the loop for the full second (main: 0 s). It now probes once
(timeout=0), like the WhatsApp adapter and LSP; a group with a live member stays covered either
way. The dashboard's WhatsApp pairing stop runs on the event loop too and gets the same.
Test: stopping a bridge whose helper survives TERM returns well under the old 1 s wait and keeps
the group covered; fails with the default timeout.