/**
 * MCP client transport tests (#23 / bug #13).
 *
 * These verify the server→client directions that the old hand-rolled,
 * POST-only transport never handled:
 *   1. A server-initiated REQUEST (`elicitation/create`) is ANSWERED with a
 *      JSON-RPC RESPONSE carrying the matching id (not silently dropped into a
 *      notification path).
 *   2. A server-initiated NOTIFICATION (`notifications/tools/list_changed`)
 *      fires the host-registered handler.
 *   3. The HTTP path builds a real Streamable-HTTP transport with a server-push
 *      channel, and an SSE-framed server message off that channel is parsed and
 *      dispatched to the right handler.
 *
 * A `MockTransport` (implementing the SDK `Transport` interface) drives the
 * client without a live MCP server.
 */
export {};
