Release Notes Generator

# Task
Write release notes from the product changes below. Use ONLY the provided information.

# Inputs
- Changes: {changes}
- Audience: {audience}
- Product context: {product_context}
- Key benefits: {key_benefits}
- Constraints: {constraints}

# Anti-hallucination rules
1. Describe only the changes provided. Do not invent features or improvements.
2. If a change's user impact is not clear from the input, mark it [IMPACT TBD].
3. Do not promise future features or timelines.

# Audience handling
Adapt the language to the stated audience:
- **End users**: Focus on what changed and what to do. No technical jargon.
- **Technical/developers**: Include API changes, migration steps, breaking changes.
- **Internal stakeholders**: Include business context, metrics impact, and rollout plan.

# Change classification
Classify each change:
- **New**: Brand new capability
- **Improved**: Enhancement to existing feature
- **Fixed**: Bug fix
- **Changed**: Behavior change (flag if breaking)
- **Deprecated**: Feature being removed (include timeline)

# Output structure
1. **Release headline** (1 sentence, benefit-led)
2. **Highlights** (top 3 changes, 1 sentence each)
3. **Full release notes** (grouped by classification: New > Improved > Fixed > Changed > Deprecated)
4. **What to do next** (user actions if any: migration steps, settings to check, etc.)
5. **Known issues** (if any from the input, otherwise omit)

<context>
  <changes>{changes}</changes>
  <audience>{audience}</audience>
  <product_context>{product_context}</product_context>
  <key_benefits>{key_benefits}</key_benefits>
  <constraints>{constraints}</constraints>
</context>
<task>Write release notes using ONLY the provided changes.</task>
<instructions>
  Only describe provided changes. Mark unclear impact [IMPACT TBD]. No future promises.
  Adapt language to audience (end users: no jargon; technical: include APIs/migration; internal: business context).
  Classify: New, Improved, Fixed, Changed (flag breaking), Deprecated (include timeline).
</instructions>
<output>
  Return: release headline, highlights (top 3), full notes grouped by classification, what to do next, known issues (if any).
</output>

Changes: {changes}
Audience: {audience}
Product context: {product_context}
Key benefits: {key_benefits}
Constraints: {constraints}

Rules: only provided changes, mark unclear impact [IMPACT TBD], no future promises. Adapt to audience. Classify: New, Improved, Fixed, Changed (flag breaking), Deprecated.

Based on the entire content above, return:
1. Release headline (1 sentence)
2. Highlights (top 3)
3. Full notes by classification
4. What to do next
5. Known issues (if any)