de906f9c75
Some checks failed
CI/CD / typecheck (pull_request) Successful in 1m3s
CI/CD / lint (pull_request) Successful in 2m5s
CI/CD / test (pull_request) Successful in 1m17s
CI/CD / build (pull_request) Successful in 2m12s
CI/CD / smoke (pull_request) Failing after 2m42s
CI/CD / publish (pull_request) Has been skipped
The probe waited for a 3s socket-inactivity timeout and treated the rejection as proof the endpoint was reachable. That only holds when nothing else is talking to mcplocal — /inspect streams every project's MCP traffic, so any other smoke file running concurrently keeps the socket busy and the timeout never fires. Adding one more traffic-generating smoke file was enough to tip it into a 10s test timeout; it passed in isolation the whole time. Resolve on response headers instead. That removes the dependence on the rest of the suite being quiet, and it is a stronger assertion than before: the test now reads the real status code and content-type, where a timeout-means-success probe would have passed just as happily against a slow 401. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01B5NAoE7VJA5TWvHsVfEmUr