Under the hood
Artifact publish telemetry gains two new MCP failure reasons: opaque_mcp_server_id and unknown_mcp_tool
What
When artifact publishing checks an MCP (Model Context Protocol) server manifest and fails, it now records two additional, more specific failure reasons alongside the existing ones like host_server_unavailable and unresolved_mcp_server:
opaque_mcp_server_idunknown_mcp_tool
Why
More specific failure reasons make it easier to tell exactly why an artifact's MCP manifest was rejected, building on earlier additions to this same validation chain such as the first-party server name collision check.