Releases and versioning

Public specifications are versioned independently by API family. Additive optional fields may ship within a version. Removing/renaming a field, changing requiredness, narrowing an enum incompatibly, changing authentication, or changing status semantics requires a new major version.

The owner repository is changed first. Automation may open a portal sync PR after owner checks, but it cannot merge. Portal CI validates lifecycle, provenance, schemas, examples, forbidden paths, secrets, links, and the static build.

Preview operations can evolve additively before stable promotion. Pin generated clients and review release notes. Stable operations follow the documented compatibility window and deprecation policy.