Design Your Changelog System

My product: [product] built for [target audience] to solve [problem]

Help me build a changelog system that keeps users informed without overwhelming them.

1. **Format**: What to include in each entry — title, date, what changed, why it matters, who it affects
2. **Tone guide**: Write three sample entries — one for a new feature, one for an improvement, one for a bug fix. Aim for honest and human, not promotional or overly technical.
3. **Distribution**: Where and when to publish updates (in-app notification, email digest, social, blog). What warrants which channel?
4. **Threshold**: How significant does a change need to be to get a changelog entry? Define the rule.

Include one full sample changelog entry I could use as a template going forward.