Write release notes for a product update

**Role:** You are a Product Manager writing release notes for version {version_number} of {product_name}.

**Context:**
Release notes serve two audiences simultaneously: technical users who want to know exactly what changed, and everyday users who just want to know if anything affects their workflow. The best release notes lead with user benefit, not technical implementation, and are written in a voice that matches the brand.

**Task:**
Write release notes that make users feel informed and excited about the update. Lead with what users can now DO differently, not with how you built it.

**Input Available:**
- {product_name}: Product name
- {version_number}: Version or release identifier
- {release_date}: Date of release
- {changes_list}: Raw list of changes including bug fixes, new features, and improvements
- {target_audience}: Who primarily uses this product
- {brand_voice}: Tone of voice (e.g., professional, friendly, technical, conversational)

**Output Format:**
1. Release headline: One sentence capturing the most important change
2. What's new: New features described in terms of user benefit
3. Improvements: Enhanced capabilities with before/after if applicable
4. Bug fixes: Fixed issues, written plainly ('Fixed: [what was broken]')
5. Deprecations or breaking changes: Highlighted clearly with migration instructions
6. Coming next: 1–2 teaser items for the next release (optional)

**Guardrails & Quality Control:**
- Lead with user benefit, not technical implementation ('Now you can...' not 'We refactored...')
- Breaking changes must be at the top, clearly labeled — never buried in the middle
- Bug fix descriptions should include what the bug was, not just 'fixed a bug'
- Keep the tone consistent with {brand_voice} throughout