Policy
- Public package or endpoint removals require a documented replacement or explicit retirement path.
- Stable wire identifiers are not renamed only to match current display branding.
- Deprecated OpenAPI operations should carry machine-readable deprecation metadata.
- A removed product capability remains documented with its removal boundary rather than disappearing from historical release notes.
- Building, dark, and parked work is not presented as a deprecated public capability because it was never a normal public path.
What a migration notice must include
- Affected package, route, command, tool, or product surface
- First deprecated version
- Replacement
- Behavioral difference
- Credential or scope changes
- Data migration or cleanup requirement
- Last supported version or date, when one is committed