Write a Design System Change Log Entry

Write a design system change log entry from the following inputs:

Component or token changed: [NAME]
Change type: [ADDED / UPDATED / DEPRECATED / REMOVED]
Version or date: [VERSION OR DATE]
Why the change happened: [REASON]
Breaking change: [YES / NO]
Migration steps for consumers: [STEPS OR N/A]
Visual before/after notes: [NOTES]
Owners: [DESIGN AND ENGINEERING OWNERS]
Related PR or ticket: [LINK OR ID]

Requirements:
1. Write a changelog entry that engineers and designers can scan in under two minutes.
2. State impact clearly: who must act, who can ignore, and by when if a deprecation exists.
3. Include code and Figma notes when relevant. Do not invent API names.
4. Provide a short migration checklist with verify steps.
5. Call out accessibility implications if tokens, contrast, or focus behavior changed.
6. Keep tone neutral and precise. No marketing fluff.
7. Add a FAQ of 2 likely consumer questions with direct answers.
8. End with a rollback note if the change is risky.