Named teammates are told about MCP servers they cannot call

Claude Code #98953 on v2.1.287 is a clean operator harness catch: rootToolSurface is frozen at turn start, and named teammates are then told about MCP servers they cannot call. The briefing and the callable surface diverge — a teammate can be handed a server name that was never attached to that teammate.

Operators debug “why will the named teammate not use the MCP server just described?” while the tool surface was already frozen. Treat rootToolSurface-at-turn-start as the boundary: what the parent session can see is not what a named teammate can call. Do not confuse this with background subagents that keep MCP tools and lose MCP resources — that note is a different failure.