Versioned public API (v2) with a deprecation window

We've seen two breaking changes to the API surface within about five weeks (response envelope/field-casing changes, new pagination behavior). That's risky for anyone building a durable integration against it. A versioned API (/v2/) with a published deprecation window for /v1/ would let partners build real automation with confidence instead of re-testing after every release.