jif c4f2746c43 Keep MCP tool calls bound to their thread (#36355) ...

## Why

Threads can configure the same MCP server name with different runtimes. Tool calls
must use the runtime associated with the thread that issued the call.

## What changed

- Route MCP readiness checks and call preparation through the invoking session.
- Add regression coverage that alternates calls between two threads and verifies
  that each thread continues using its own MCP server process and configuration.

GitOrigin-RevId: 5735f7b29a579f545351385ab01a575e35ead01e

2026-07-31 16:12:46 +00:00

..

common

Use model catalog collaboration mode messages (#36351)

2026-07-31 15:40:52 +00:00

remote_env_windows

Scope runtime workspace roots to execution environments (#32952)

2026-07-14 04:41:08 +00:00

suite

Keep MCP tool calls bound to their thread (#36355)

2026-07-31 16:12:46 +00:00

all.rs

[codex] Use expect in integration tests (#28441)

2026-06-15 21:53:47 -07:00

responses_headers.rs

Allow custom providers to opt into standalone web search (#34846)

2026-07-23 00:02:15 +00:00