provider-trace-session-contract

Validate provider mode, session reuse, and trace envelope propagation across runtime layers.

Updated Mar 13, 2026

Search Tags:#workflow #testing #dashboard #observability #trace #contract #provider

Ready to run

npx skills add https://github.com/JDL440/nfl-eval --skill provider-trace-session-contract

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: provider-trace-session-contract
Source: https://github.com/JDL440/nfl-eval/tree/main/.squad/skills/provider-trace-session-contract
Command: npx skills add https://github.com/JDL440/nfl-eval --skill provider-trace-session-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures consistent provider-mode semantics, session reuse behavior, and trace envelope integrity across runtime wiring, persistence, and dashboard observability.

Core Features & Use Cases

Verifies propagation of providerMetadata, sessions, and envelopes from the provider entrypoint through the runner and repository to the dashboard.
Supports end-to-end validation when plain providers and tool-enabled providers share the same ChatRequest shape but require different tool behavior.
Provides guardrails to ensure trace views render the same fields in human terms, not just raw JSON.

Quick Start

Run an end-to-end test to verify providerContext propagation and trace rendering across provider, runner, repository, and dashboard.

Frequently Asked Questions about provider-trace-session-contract

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify provider trace contracts across the runner, repository, and dashboard?▼

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.

What is a trace envelope and when do I need to validate it?▼

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.

How do I test session reuse behavior for both plain and tool-enabled providers?▼

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.

Can I use this approach to validate provider mode semantics in my observability dashboard?▼

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.

Why does my dashboard render raw JSON instead of accurate trace views for my provider?▼

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.