Versioning

Use the deployed /v1/openapi.public.json for schemas and /v1/capabilities for scope, feature, availability and stability metadata. They come from one registry and mounted route models. The documentation reference is a hash-checked source snapshot and can differ from a deployed release.

Q preserves operation IDs and rejects incompatible schema/security changes in release checks. The deprecation policy describes notice and removal requirements. Stable status belongs to an operation, not an entire API prefix.

SDK release versions and package names are defined in sdks/release.json. Use the SDK support matrix and matching API release. Locally tested archives remain unpublished until their separate release workflow succeeds. Generated Python/TypeScript clients are contract checks; supported installed packages are qualified separately.

Machine consumers can use /llms.txt, /llms-full.txt on the documentation application, and /llms.txt or /.well-known/llms.txt on the API. The compact API and documentation text share the same generated source.