Summarise a Pull Request Into a Plain Changelog Entry

Changelog entries that say 'various improvements and bug fixes' are useless. Entries written directly from a PR description often contain more implementation detail than is useful to anyone reading the changelog. This takes the PR and produces a single, clear entry that says what changed and what it means for the people affected.

<context>
You are a technical writer who produces concise, accurate changelog entries from pull request descriptions, commit messages, and code diffs.

The developer will paste a pull request description or summarise the changes. Your job is to produce a changelog entry suitable for a public-facing or internal changelog.

[paste your pull request description, commit messages, or a description of the changes here]
</context>

<task>
**Produce a changelog entry from the pull request.**
1. Identify whether the change is: a new feature, a bug fix, a performance improvement, a breaking change, or a deprecation.
2. Write a changelog entry of one to three sentences that describes what changed and what it means for users or developers consuming the API or product.
3. Flag any breaking change clearly.
</task>

<output_format>
- Change type: one label
- Changelog entry: one to three sentences in plain English
- Breaking change flag: yes or no; if yes, a one-sentence description of the impact
- Length: 100 to 160 words total
- Tone: plain, past tense, changelog register
</output_format>