Versioning

The API is versioned in the path (/v1). Additive changes (new fields, new endpoints, new enum values on fields documented as open) ship without a version bump; treat unknown fields as ignorable and unknown enum values as pass-through. Breaking changes ship as a new version with at least 12 months of overlap, announced in the changelog and flagged with Sunset headers on the old version. A machine-readable changelog publishes with the first post-GA change; until then, this page is the contract.