/**
 * Reference-client interop for HTTP mode (#303).
 *
 * Drives the OAuth 2.1 authorization server and the /mcp endpoint with the
 * official MCP client SDK's own auth machinery — discovery, dynamic
 * registration, PKCE authorization, code exchange, refresh — over a real TCP
 * socket. If the reference implementation can complete the whole journey and
 * then list and call tools, a real remote client has no protocol-level reason
 * to fail. The only simulated part is the human: the browser form POST is
 * played by fetch.
 */
export {};