API versioning: Specification
Public HTTP versioning with additive-only changes inside a version, explicit breaking-change rules, Sunset headers before removal, and a documented default-version policy that never silently redefines field meaning.
Consumer expectations, including authentication and error shapes, are verified against the real provider in CI before merge; HTTP status codes cannot be mocked away on either side of the contract.