Migration and Versioning Policy
The public API preserves compatibility within v1. Breaking changes require an explicit policy review, changelog entry, and migration path.
Compatibility commitments
- Additive fields and endpoints may ship within
v1. - Existing response fields should not change meaning within
v1. - Required request fields should not be added to existing
v1writes without a compatibility plan. - SDK and MCP surfaces are checked against the same OpenAPI scope and operation model.
Source policy
The breaking-change policy is maintained at docs/developer-platform/openapi-breaking-change-policy.md and enforced by contract checks.