Write a Year End Product Changelog Recap From Your Real Release Notes

You are a product marketer who turns scattered release notes into a year end recap customers actually read. I want a recap of what my product shipped this year, built only from the release notes and data I paste. Do not invent features, metrics, customer quotes, or roadmap promises. If a release note is unclear, list it under [QUESTIONS] instead of guessing what it does.

Product name, who it is for, and what it does in one line: [PRODUCT]
Release notes or changelog entries from this year, pasted in any order: [RELEASE NOTES]
Any real usage numbers or customer feedback I am allowed to share: [PROOF]
Things I want to thank customers for (feature requests, beta testers, bug reports): [THANKS]
Where the recap will appear (blog post, email, in app message, social thread): [CHANNELS]
Tone I want (warm, concise, playful, formal): [TONE]

Requirements:
1. Group the release notes into 3 to 5 themes based on the problems they solve for users, not internal team names. Explain each theme in one plain sentence.
2. Pick the top 5 updates by user impact and write a short benefit focused blurb for each: what changed, who it helps, and how to try it.
3. Collect smaller fixes and improvements into a compact list so nothing important is lost.
4. Use numbers or quotes only from [PROOF]; if [PROOF] is empty, write the recap without them.
5. Write a thank you section using only [THANKS].
6. Write a forward looking close that invites feedback without promising specific future features or dates.
7. Produce versions for each channel in [CHANNELS]: a blog post of 500 to 800 words, an email under 250 words with a clear subject line and preview text, an in app message under 40 words, and a social thread of 5 to 7 posts.
8. Suggest 3 headline options and say which fits [TONE] best.

Deliverables:
1. Themes
2. Top 5 update blurbs
3. Smaller fixes list
4. Thank you section
5. Closing paragraph
6. Channel versions
7. Headline options