5. Versioning & migrations

5.1 How is the API versioned, and what’s the policy for breaking changes?

Versions are managed with standard versioning. If a breaking change is required, clients are notified in advance via changelogs by email.

5.2 Is there a migration path between versions?

We avoid breaking changes by evolving the schema (adding fields vs removing). Deprecated fields remain available for a transition period and are documented. If a breaking change is unavoidable, it will be announced ahead of time and included in the changelog.