API Lifecycle And Deprecation¶
Current Public Contract Anchors¶
Versioning Rule Of Thumb¶
- if a surface is versioned explicitly, use that versioned page first
- if a surface is not yet versioned explicitly, treat the current Reference page plus the Changelog as the public truth
Deprecation Expectations¶
Until a stricter written policy is published:
- breaking public changes must be called out in the changelog
- versioned surfaces such as
agent-api/v1should not change silently - migration-relevant behavior should be summarized in Version History
What To Check Before Upgrading¶
- Version History
- Changelog
- the exact CLI/config/reference pages your automation depends on