Headless MCP reconnect failures show a readable message instead of a raw client error.
What's wrong with this entry?
When reconnecting or toggling an MCP server fails in headless mode, the error is now mapped to a friendlier message before display instead of the raw client error being shown.
- The failure is logged as "mcp reconnect/toggle failed" with the underlying error, or "(no detail)" when the error carries none.
- A related path sanitises the server name before putting it in "Server not found:".
mcp reconnect/toggle failed
Strings lifted out of the shipped bundle, so the claim above can be checked against them.