Commit message prompt: written from the diff

Write a git commit message for the diff below, for the people who will read this project's history later, so that someone running git log or git blame a year from now can tell what changed and, above all, why.

The diff:
"""
{{diff}}
"""

Why this change was made (the problem, the ticket, the decision behind it): {{reason}}
Issue or ticket numbers to reference: {{issue_refs}}
Our commit convention: {{convention}}

Recent commit messages from this repository, to match their style:
"""
{{recent_commits}}
"""

Write the message in this form:
1. A summary line under 72 characters (50 or fewer if it fits), in the imperative mood ("Add", "Fix", "Remove"), with no full stop at the end. If the convention is Conventional Commits, start with the type and optional scope, for example "fix(billing): round tax per line before summing". That example shows the form only.
2. A blank line.
3. A body of 2 to 6 lines, wrapped at 72 characters, that explains why the change was needed and what it does at a high level: the problem, the approach, and any side effect a reader should know about, such as a changed default. Do not list every file or restate the diff line by line.
4. Footer lines for the issue numbers I gave, in the form our convention uses (for example "Refs #123"). Use a closing keyword such as "Fixes" only if I said the change fully resolves the issue, because many hosts close the issue automatically when they see one. If the change breaks a public interface, add a "BREAKING CHANGE:" footer that says what callers must do.

Return the message in a code block, ready for git commit -F. Below it, add at most two short notes, only if needed: changes in the diff that look unrelated to the reason (debug output, formatting, a stray file), with a suggestion to put them in their own commit.

Do not describe anything the diff does not contain, and do not add issue numbers, co-author lines or sign-offs I did not give. Avoid phrases such as "This commit" or "Various fixes".

If the reason is not given and the diff does not make it clear, write the summary line and put [WHY: one line on the reason] in the body instead of inventing one. If the diff mixes several unrelated changes, say so first and suggest how to split it.