MCP connections that finish after you switch accounts get dropped, but almost all of it is dark.
Connect attempts are stamped with their account and discarded across a switch; only the policy-blocked path runs without the disabled discovery cache.
What's wrong with this entry?
Every connect attempt is tagged with the account in effect when it began; results that settle after a switch are dropped and their sockets closed instead of being written into the app's server list. Also new: cached servers are re-dialled and adopted on lazy connect, and a disable or policy denial landing mid-flight replaces the row rather than losing to the connect. Only the policy-blocked path runs on a default build; the rest sits behind the discovery cache, which is off.
- An account change bumps a process-wide counter and fires a one-shot telemetry event.
- Mid-flight denials produce a
disabledrow or aPOLICY_BLOCKEDfailed row.
applyConnectionResult: disposing connect that settled after a disable
Strings lifted out of the shipped bundle, so the claim above can be checked against them.