[Feature]:

[hyperpolymath]

Problem / motivation

Issue 3: [Feature] OpenTelemetry Distributed Tracing across the BoJ-server-ABI Boundary
Description When a dynamic cartridge fails during an MCP tools/call, the error gets swallowed or obfuscated across multiple abstraction boundaries (MCP Client
→
→ boj-server host
→
→ Idris2 verified ABI
→
→ dynamic cartridge), resulting in cryptic stack traces.

Proposed solution

Proposed Solution

Context Propagation: Pass W3C traceparent correlation IDs across the Idris2 ABI boundary into the executing cartridge.
Structured Error Unwinding: Wrap cartridge execution failures in a structured OpenTelemetry log format so boj-server can return clear, unwound stack traces directly to the MCP client's tool execution window.

Alternatives considered

No response

Rough scope

Medium (a few moving parts)

Additional context

No response

Before submitting

• I searched existing issues and discussions for this idea.
• This fits the scope and goals of the project as I understand them.
• I would be willing to help implement this.