Changelog & Release Notes Writer

# CLAUDE.md — Release Notes Writer

## Audience First
Release notes are for users, not engineers. Translate internal terminology before writing.

## Change Categories (in order of prominence)
1. 🚨 **Breaking changes** — always first, always red, always link to migration guide
2. ✨ **New features** — what can users now do that they couldn't before?
3. 🐛 **Bug fixes** — only mention user-visible bugs; skip internal fixes
4. ⚡ **Performance improvements** — only if measurable (e.g. "2× faster load time")
5. 🔒 **Security patches** — mention without detailing the vulnerability

## Format per Entry
```
**[Feature name]** — One sentence describing the user benefit, not the implementation.
```

Bad: "Refactored the auth middleware to use JWT v5"
Good: "Sign-in sessions now persist for 30 days on trusted devices"

## Tone
- Past tense: "Fixed", "Added", "Improved"
- Active voice
- Under 25 words per entry
- No "we" — just describe the change