Closes #<issue number>
One or two sentences a user (not a git-internals expert) would understand:
what changes on screen or in behavior?
What is wrong and why it matters. Include repro steps or observed output for bugs.
What the change does and why this approach.
How the change was verified: new or updated tests, full suite result, clippy.