Draw calls to MCP servers, and what each Evidence position carries

[wu-sheng]

The page's renderer is Horizon's, and two Horizon changes since the pin (88e0110) draw what asz.view already carries. This moves the embedded renderer to them.

• internal/view/conversation-view is rebuilt with tools/conversation-view.sh update c903e77876c99358873b89f4803becdc5470ca30. That is the newest commit on Horizon's main.
• Between the old pin and the new one, two Horizon commits touch what asz embeds:
  • feat(conversation-view): draw calls to MCP servers on their own lane, with what they did skywalking-horizon-ui#175 draws calls to MCP servers.
  • feat: adopt the latest OAP, with OTLP trace stores beside Zipkin, MCP e2e and Evidence per position skywalking-horizon-ui#176 makes the Evidence tab show what the document carries for each position.
• docs/en/changes/changes.md records the change under MCP calls.

What the page shows now

• A call to an MCP server sits on its own MCP lane, named by its server and tool. Its card shows how it ended and the time the plugin measured around it, and the inspector gains an Execution tab: the server and where its configuration came from, the outcome, the measured time, and the size and digest of the arguments and the answer.
• The Evidence tab lists the step's own positions, then each of its change and execution records. The picked position shows what the document carries for it: the step's text, the call's result on a result position, or the record itself. It used to show the step's text under every position, so a call's request and result showed the same thing.

Checked

• make conversation-view-check passes: the embedded copy is what c903e77 builds.
• make check passes.
• I built asz from this branch and served a root of real Claude Code sessions that called an MCP server. The call sits on the MCP lane as web · echo, the Execution tab is there, and Evidence lists request, result and the execution record; the result chip shows the call's result, echo: {"text": "over http"}.