Compatibility and migration

• REST breaking changes use a new path major such as /v2.
• SDK packages use SemVer.
• Event envelopes carry an explicit schema version.
• Additive fields may appear within a major version.
• Removal and behavior changes require a migration guide and announced support window.

Existing /api/graphql reads and /api/agent-credit/v1 integrations remain compatibility paths. New integrations should use /v1, wallet sessions, idempotency keys, typed workflows, and canonical completion tracking.

Deprecation lifecycle

Torq announces a breaking REST change through a new path major, an SDK migration note, and an event schema compatibility statement. Existing private-preview behavior is not silently expanded into public production availability. A deprecated workflow remains documented with its exact authority and completion behavior until its announced replacement and support window are available.

The current packages are private-preview prereleases. Public SDK SemVer compatibility begins only when registry publication, release ownership, and the public GA gate are independently proven.

Agent Credit action names map directly to the corresponding v1 borrower, lender, and liquidator workflow adapters. Torq continues to return calldata for customer-owned signers and never acquires relay authority.