When an external MCP client attempts to connect to StudioMCP.exe, sending pre-flight discovery requests (such as server/discover or unhandled method probes prior to completing the traditional initialize handshake) causes StudioMCP.exe to panic and drop the IPC connection with an EOF error instead of returning a proper JSON-RPC error response.
Expected behavior
It should handshake with server/discover
