The caller's own agent connection state, seen from the active workspace.

Membership is enforced by the tenant context and the read is pinned to the caller's user id, so nobody sees another member's activity. It is NOT pinned to this tenant: an agent bound to another of the caller's workspaces comes back as elsewhere (named only while the caller is still a member there), so a multi-workspace user who did connect is not left waiting. A principal with no user row (a service token, dev auth) has no agent of its own and reads as not connected.

Pollable, but the consumer should back off and stop on success or a hidden tab: the single-workspace case is one LIMIT 1 index read, the elsewhere case up to three.