Previously, we would send an contact update when accepting a request using the same `busy` status for both the requester and the responder. This was obviously wrong and caused the requester to see their own busy status as the newly-added responder contact's status.
Zed Server
This crate is what we run at https://collab.zed.dev.
It contains our back-end logic for collaboration, to which we connect from the Zed client via a websocket after authenticating via https://zed.dev, which is a separate repo running on Vercel.