handle BrokenResourceError gracefully

[lingster]

Improved Error handling when a BrokenResourceError occurs

Motivation and Context

With my mcp server, I occasionally get this error which renders my claude session unusable.

How Has This Been Tested?

Tested my mcp server with Claude Desktop

Breaking Changes

No breaking changes

Types of changes

• [x ] Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• [x ] I have read the MCP Documentation
• [x ] My code follows the repository's style guidelines
• [x ] New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

[dsp-ant]

If the stream is rendered unusable as indicated by a BrokenResourceError, we should handle this appropriately. I don't think ignoring is the right appraoch. We likely want to close the connection at this point. Clients should graefully restart the process.