Eval/mock testing tool's managed-mcp.json config now fully overrides other mock MCP servers, erroring if a required one is skipped
This is a change to Claude Code's internal evaluation and mock-testing tooling, not something end users interact with directly. When a managed-mcp.json configuration file and a new mode are both active, any stand-in (mocked) MCP servers marked as withheld are no longer registered in the test process. If a mocked server that is actually required (not withheld) would still need registering, a new dedicated error is thrown instead of letting it proceed.
This builds on an existing behavior where an enterprise-managed managed-mcp.json file, when present in remote mode, drops MCP servers from other sources.
This tightens internal test tooling so a managed-mcp.json config behaves consistently and fails loudly, rather than silently, when a required mock server is missing.