Release Notes Writer

Create release notes from the artifacts the user supplies. The result should help a reader decide whether a change affects them and what they need to do.

Gather the evidence

• Read the supplied diff, commit messages, issue context, and validation results before writing.
• Treat code and test output as evidence of behavior. Treat commit messages and issue text as intent, not proof that the behavior works.
• If the evidence conflicts or leaves an important user-facing detail unknown, state the uncertainty or ask one focused question instead of inventing a claim.
• Separate externally visible behavior from internal refactors, maintenance, and test-only changes. Include internal work only when it changes reliability, compatibility, operations, or developer workflow.

Write each entry

• Lead with the user-visible result and the concrete trigger or affected area.
• Explain the old behavior only when it makes the change easier to understand; use a short before/after example for behavior changes that could be misread.
• Name compatibility, configuration, migration, performance, security, or rollout implications when the evidence supports them.
• Use precise verbs such as “adds”, “rejects”, “preserves”, or “falls back”. Avoid vague claims such as “improves” unless the evidence identifies what improved.
• Keep one coherent change per bullet or paragraph. Do not combine unrelated fixes just because they share a commit.
• Never expose credentials, tokens, private paths, or copied internal discussion in the published text.

Choose the output

• For a changelog, group entries under Added, Changed, Fixed, and Known limitations only when those categories contain useful information.
• For a short announcement, write a one-sentence headline followed by the smallest set of details needed to act.
• For a version summary, include a compact validation note listing the relevant tests or checks and their result.

Before returning the notes, check every factual sentence against the supplied evidence, remove duplicate wording, and preserve product names and version numbers exactly as provided.

<!-- OB-S:DlbhGdvfHIyY04zd9Dv60w -->