Version Sunset - check your API versions, then retire one

Check an API's version lifecycle, then retire a version without breaking anyone. Paste the versions with their release, deprecation and sunset dates, one response from a deprecated version and the changes queued. Free in your browser: every notice window against the floor for the audience (12 months public, 24 for mobile apps and enterprises), the versions alive at once against the 2-3 cap, a version both deprecated and the default, traffic still on a retired version, the Deprecation (RFC 9745), Sunset (RFC 8594) and successor-version headers read, each queued change classified as breaking or not, the scheme ranked, and the headers for the next retirement written. A metered run writes the versioning and deprecation policy, or the sunset plan for one version - dated stages, the three headers, communication waves, the migration guide and a 410 grace period. Built on the SkillSafe skill @samber/api-versioning-policy, from samber/developer-platform-skills (MIT), by Samuel Berthe.