provider-capability-envelope

What problem does it solve?

Prevent dashboard and trace-contract drift when a provider has both a high-level mode switch and lower-level runtime gates.

Core Features & Use Cases

• Inspect the server/provider wiring to find the explicit mode input and any legacy compatibility flags.
• Resolve the provider’s runtime flags first and build prompt/tool-policy text from those resolved flags rather than raw config booleans.
• Preview the resolved route before building the tool contract so the runtime can decide capability from the executing provider rather than the caller’s guess.
• Keep provider adapters honest about structured-output differences when the tool loop depends on machine-readable turns.
• Add regression tests where explicit mode contradicts legacy booleans so the modern contract wins, and tests for fail-closed runtime conditions.

Quick Start

Review the server/provider wiring to identify how tool access mode is configured and ensure the runtime flags are resolved before prompts are generated.