Add a local telemetry view using Aspire-compatible OpenTelemetry output

[KSemenenko]

Problem

Operators and developers need a local-first telemetry surface that helps them inspect activity without requiring cloud infrastructure.

Scope

• Track a local telemetry view that consumes Aspire-compatible OpenTelemetry output
• Cover traces, metrics, and logs relevant to sessions, tools, and workflows
• Keep the view useful during local development and operator troubleshooting

Out of scope

• Mandatory cloud export or vendor lock-in
• Replacing the underlying runtime instrumentation model

Implementation notes

• Keep local telemetry a first-class product loop
• Align the issue with the emitted OTel signals from the runtime
• Preserve optional cloud export as a separate concern

Definition of Done

• The issue defines what the local telemetry view must show
• The local-first observability story is explicit enough to implement later

Verification

• Review the issue against the feature spec and runtime observability issue

Dependencies

• Parent epic: [Epic] Add observability, evaluation, and trust controls #20