Implementation Contract

Contract table

For environment variables, add one row per value when that is clearer than a comma-separated list. Record both the producer and every consumer; this catches values that provisioning emits under one name while runtime code expects another.

Reconciliation before merge

1. Compare every azure.yaml service and hook target with the frozen service names.
2. Search code, Bicep outputs, azd hooks, CI, and docs for each environment-variable producer and consumer.
3. Exercise the Responses endpoint with contract-valid metadata and validate response/citation/refusal schemas.
4. Initialize the toolbox endpoint, compare discovered MCP names and schemas with the frozen snapshot, and fail on drift.
5. Confirm model endpoint, deployment name, and token scope agree across provisioning and agent configuration.
6. Compare runtime and package manifests with the resolved version row and run compatibility checks in the generated application.
7. Update the contract and all consumers in one change when an intentional interface change is required.