aaune

Contract governance

API changelog and support policy

Aune does not ship breaking public behavior under an existing major contract. Additive schema changes can ship within v1; breaking changes require a new version, migration guide, and at least six months of notice.

REST
public_bookings_api_v1
MCP
aune_mcp_v3
Skill
2.0.0
Breaking notice
At least six months
Legacy paths
Deprecated, still compatible

2026-07-10

  • Added canonical `/v1` REST aliases and RFC problem responses.
  • Added OAuth 2.1 discovery, dynamic registration, PKCE S256, narrow scopes, rotating refresh tokens, introspection, revocation, and connected-app control.
  • Added atomic booking truth, cancellation, rescheduling, transactional outbox, signed webhooks, deterministic sandbox, docs search, TypeScript SDK, Python SDK, and CLI previews.
  • Expanded MCP with docs search and booking lifecycle tools; moving follows the same confirmed-booking path as other supported verticals.

Deprecation policy

  • Legacy `/api/public/*` routes return `Deprecation: true` and a successor link to `/v1`.
  • A sunset date is announced only after equivalent production migration paths and telemetry exist.
  • Security fixes may narrow unsafe behavior immediately, with a public incident or security note.
  • Every public contract change updates OpenAPI, MCP schemas, Agent Card, SDK tests, examples, docs index, evals, and changelog in the same release.

Compatibility promise

Existing confirmed booking IDs, issued option verification windows, idempotency records, webhook event IDs, and consent evidence remain interpretable during rollback and version migration.