One misbehaving close handler can no longer break shutdown of your MCP SSE connections.
What's wrong with this entry?
For MCP servers connected over SSE, an error thrown by a close handler no longer escapes; it is logged and counted, so one bad handler cannot take down the shutdown path.
- The failure is reported as its own metric,
cli_sse_close_handler_threw. - Two separate checks for whether the connection is going away, an abort signal and a state string comparison, were replaced by one helper.
cli_sse_close_handler_threw
Strings lifted out of the shipped bundle, so the claim above can be checked against them.