#api deprecation notice

API Deprecation Notice from a Changelog (No Invented Sunset Dates)

Turn a pasted changelog into a customer deprecation notice. No invented sunset dates, replacement APIs, or traffic stats.

Act as an API program manager writing a customer deprecation notice from a changelog. You only announce endpoints, dates, and replacements that appear in Inputs. You do not invent a sunset date, a migration window, a traffic percentage, or a successor API. This is not a git changelog and not a Keep a Changelog dump. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Product and API surface: [Product] - Pasted changelog excerpt (include version and date if present): [Changelog] - Endpoints or fields being removed (quote from Changelog): [Removed] - Replacement I can prove (or NONE): [Replacement] - Sunset or last-call date that is already committed in Changelog or policy: [Sunset or NONE] - Support channel and SLA I may cite: [Support] - Who must act (role, not named people unless pasted): [Audience] - Migration steps I can prove: [Steps] - Words I must not use: [Banned] - Word budget: [Budget or 350] Generate: 1. Honesty ledger: every version, date, endpoint, field, and replacement that appears in Changelog, Removed, Replacement, Sunset. Forbidden: any date or successor not on that list. 2. Subject line (70 chars max) using Product and Removed only. Print the count. No sunset date unless Sunset is not NONE. 3. Notice body: what is going away, what stays, who must act. Quote Removed. If Sunset is NONE, write sunset date not specified and do not pick one. 4. Replacement paragraph: only Replacement. If NONE, write no successor named in the brief. 5. Migration: numbered steps from Steps only. Missing auth, SDK, or URL writes NOT IN INPUTS. 6. Support footer: only Support. Do not invent a status page URL. 7. FAQ (4): only questions answerable from Inputs. If a question needs a date you do not have, write not specified. 8. Compliance pass: quote Banned words, invented sunset dates, invented traffic share. Cut them. Print word count vs Budget. Constraints: - Customer deprecation notice, not a git changelog and not Keep a Changelog. - Never invent a sunset date, last-call date, or replacement path. - Do not claim usage percentages, request volume, or breaking-change class unless Changelog states them. - Stay under Budget words. - No emojis.