Newly connected MCP servers can now replace a cached placeholder, and a failure there won't break the connection.
What's wrong with this entry?
Both MCP connect paths now pass the freshly built connected client to a global getConnectedClientWiring() callback, so a cached placeholder can be adopted by the real client.
- the server's memo keys are cleared before the callback runs
- if the callback throws, the connection still succeeds and only a per-server debug line is written, stating the placeholder is kept and adoption will retry
connected-client wiring failed (placeholder retained, adoption will retry):
Strings lifted out of the shipped bundle, so the claim above can be checked against them.