/**
 * In-memory round-trip tests for the protocol bridge.
 *
 * The whole client/server loop is exercised without spawning a single process.
 * A {@link createProviderHost} stands up the *server* half over an
 * {@link InMemoryTransport}, publishing one trivial tool — `ping`, which returns
 * the text `"pong"`. A {@link createServerEndpoint} stands up the *client* half
 * over the transport's paired socket. Because the two halves share a linked pair,
 * a `listTools` / `callTool` issued on the client travels to the host, runs the
 * real kernel runner, and returns — all in one process.
 *
 * The cases pin the four behaviours a downstream consumer depends on:
 *   1. the endpoint enumerates the host's tools (under their qualified names);
 *   2. invoking a tool returns the host's content faithfully;
 *   3. the `mountProtocolBridge` wrapping shape — a {@link defineTool} whose `run`
 *      forwards to the endpoint — yields the same `"pong"`;
 *   4. an operation before `connect` faults with kind `not_connected`.
 */
export {};
