{"version":"2.1.246","anchor":"mcp-connections-now-report-four-auth-lifecycle-moments-to-no","canonical_anchor":"mcp-connections-now-report-four-auth-lifecycle-moments-to-no","heading":"MCP connections now report four auth-lifecycle moments to nobody","tier":"soon","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/mcp-connections-now-report-four-auth-lifecycle-moments-to-no","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### MCP connections now report four auth-lifecycle moments to nobody\n\nMCP now fires auth-loss and reconnect events that nothing in this build listens to.\n\n**What**\n\nMCP 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.\n\n**Details**\n\n- The four are `authLost`, `reauthReconnect`, `cachedAdopt` and `cachedDialFailed`, none of which existed previously.\n- Every use of them in the build is a fire, never a listen, so they are instrumentation points waiting for a consumer.\n\n**Evidence**\n\n`cachedDialFailed`\n\n- Area: MCP\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}