Publish and validate provider catalog support records

[Haz3-jolt]

Outcome

Publish one reviewable support record for every built-in provider identity and configured backend, and validate that catalog records and user documentation agree with it.

Current repository evidence

SETUP.md documents only Azure OpenAI configuration. packages/ai/src/azure-openai-models.ts has no source revision or retrieval metadata, and packages/ai/README.md has no provider support matrix. The umbrella names many regional and subscription identities whose exact API, auth, and catalog details must not be guessed during implementation.

Acceptance criteria

• Define a versioned support-record schema for provider identity, region or subscription boundary, official source URLs and revisions, API dialects, auth methods, exact environment and setting names, catalog source, limitations, terms constraints, and last review date.
• Add a reviewed record before each provider or backend integration claims support; ambiguous OAuth, endpoint, or compatibility claims must be resolved explicitly or marked unsupported with evidence.
• Generate or validate public provider setup and limitation tables from those records so documentation cannot silently diverge from implementation.
• Cross-check every catalog provider/model identity, API dialect, regional boundary, and provenance reference against the support records in local tests.
• Fail validation for undocumented environment variables, duplicate identities, missing provenance, stale unresolved placeholders, or a claimed capability with no conformance fixture.

Verification

Run the support-record validator, documentation generation check, catalog tests, and pnpm check:generated. This audit did not run tests or consult remote provider documentation.

Coordination

#271 owns deterministic catalog generation. Each provider child owns its implementation and provider-specific fixture. This issue supplies the reviewed facts needed to avoid guessed endpoints, authentication, and compatibility behavior.

Source

ROADMAP.md Product vision §2.7 and §7.6; Technical implementation roadmap, Phase 2: Provider contract and Initial adapters. #10 Authentication, Model catalog, and completion documentation criteria.

Repository audit

Audited against Axl 88944a2. Provider breadth after foundation safeguards. Source inspection, not an executed behavior test. Roadmap references: L90, L97, L102, L1669, L1695.

Tracking key: axl-backlog:providers.catalog-support-records.

Issue tracking

Axl issue mirror: #370 | GitHub #370

Parent: #10

Related issues:

• #271 (Generate and validate the authoritative static model catalog #271)
• #279 (Build a reusable provider and codec conformance suite #279)
• #374 (Publish the TypeScript SDK with a verified external consumer #374)