2e1d724e3e
`streamable_http_client` yields `(read, write, get_session_id)` on mcp 1.x and `(read, write)` on 2.x. `_run_http` unpacked a fixed 3-tuple, so on 2.x every HTTP and SSE MCP server failed its handshake with `ValueError: not enough values to unpack (expected 3, got 2)` and parked after exhausting its retry ladder. Only stdio servers kept working. This is the same defect as the import gating fixed earlier in this branch, one layer further in. That fix's own comment claimed reaching `streamable_http_client` was "the path that does work" — reaching it was necessary and not sufficient, and the comment asserted the half that was never exercised. Corrected along with the code. Unpacked positionally rather than by arity, since this file deliberately supports both SDK generations and `get_session_id` was never used here. The reason this survived review is worth the test it now has: the existing coverage in test_mcp_client_cert.py fakes the transport with a 3-tuple, so it encoded 1.x's shape into the assertion and passed on 2.x regardless. The new test drives `_run_http` once per arity the supported SDK range actually yields, and asserts the streams handed to ClientSession are the first two — positional, because 1.x's third element is not a stream. Verified it fails on the 2.x case without this change. Found while pointing a real HTTP MCP server at a live deployment running this branch: the server parked at startup and no tool from it ever registered.