## What changed - The RMCP streamable HTTP tests now wait for metadata and tool readiness before issuing tool calls. - OAuth state is isolated per test home. - The helper server startup path now uses bounded bind retries so transient `AddrInUse` collisions do not fail the test immediately. ## Why this fixes the flake - The old tests could begin issuing tool requests before the helper server had finished advertising its metadata and tools, so the first request sometimes raced the server startup sequence. - On top of that, shared OAuth state and occasional bind collisions on CI runners introduced cross-test environmental noise unrelated to the functionality under test. - Readiness polling makes the client wait for an observable “server is ready” signal, while isolated state and bounded bind retries remove external contention that was causing intermittent failures. ## Scope - Test-only change. |
||
|---|---|---|
| .. | ||
| bin | ||
| auth_status.rs | ||
| lib.rs | ||
| logging_client_handler.rs | ||
| oauth.rs | ||
| perform_oauth_login.rs | ||
| program_resolver.rs | ||
| rmcp_client.rs | ||
| utils.rs | ||