OpenAPI

RESOURCES

Versioning

The current public contract is v6.6.6 with stable route paths, explicit API lifecycle headers, live status evidence, and a versioned /api/v1 profile, membership, organization-read, developer, and capability-evidence surface.

Policy

  • Every update, including small fixes and documentation changes, advances exactly one release version; releases cannot skip a valid successor.
  • The package, worker fingerprint, health metadata, release manifest, changelog, and OpenAPI info version move together.
  • The release train rolls x.0.9 to x.1.0 and x.9.0 to the next major .0.0 as documented in the repository policy.
  • Every new release uses the shared update banner and includes detailed release notes dated Month Day, Year without a clock time.
  • Deprecated behavior must be called out in the changelog and contract before removal.