Runs kicked off through MCP now start their own root trace instead of nesting under FastMCP's identity-less protocol span. Your traces attribute the work to the actual run, so observability for MCP-driven activity lines up with everything else instead of disappearing into a generic parent.