provider-trace-session-contract

You can verify end-to-end provider trace contracts by running tests that validate providerMetadata, sessions, and envelope propagation from the provider entrypoint through the runner and repository to the dashboard.

A trace envelope encapsulates session and provider metadata for observability. You validate it to ensure trace views render consistent human-readable fields across runtime, persistence, and dashboard layers.

You test session reuse by executing end-to-end validations where plain and tool-enabled providers share the same ChatRequest shape, ensuring the runner differentiates tool behavior while maintaining session continuity.

Yes, this approach validates provider mode semantics by ensuring trace envelopes propagate correctly to storage and the dashboard, providing guardrails so traces render accurately in human terms rather than raw JSON.

Your dashboard renders raw JSON because trace envelopes and providerMetadata are not propagating correctly through the repository layer. Enforcing a cross-layer provider trace contract ensures the UI renders human-readable fields accurately.