Versioning

The public boundary is /v1/developer. Within v1 changes are additive only: new routes, optional request fields, new response fields, new error codes and new enum values on responses. Parse unknown values defensively.

• We do not remove or rename a route, field or code, narrow what a field accepts, or change a documented status within v1.
• A breaking change ships as v2 beside v1, with a migration guide and a deprecation window announced to every owner of an active key.
• Scope changes never widen an existing key.
• Until general release the contract is a pilot: limits may be tuned, and any breaking change is announced to pilot owners first.