Four MCP auth-lifecycle events fire on lost auth, reconnect, cached-connection adoption and cached-dial failure, with no subscriber present.
What
MCP connection handling now fires events when authentication is lost mid-call, when a reconnect after re-authenticating reaches the connected state, when a cached connection is adopted, and when dialling a cached connection fails. Nothing in the build subscribes to any of them.
Details
- The four are
authLost,reauthReconnect,cachedAdoptandcachedDialFailed, none of which existed previously. - Every use of them in the build is a fire, never a listen, so they are instrumentation points waiting for a consumer.
Evidence
cachedDialFailed
Strings lifted out of the shipped bundle, so the claim above can be checked against them.