All current public operations are under the /v1 path prefix. Treat a change to that prefix as a new major API version.
Backward-compatibility guarantees, deprecation notice periods, sunset headers, and migration-support timelines have not yet been approved. They must be defined before this page becomes a public commitment.
- ignore unknown response fields;
- tolerate new enum values by routing them to an
unknown state rather than crashing;
- send only documented request fields because request validation is strict;
- pin generated clients to a reviewed OpenAPI revision;
- review the changelog before deploying an integration update.
Sakawave should publish additive schema changes and examples in the same pull request as implementation, and reserve breaking request, response, status, or semantic changes for a new major version with migration guidance. 
