Write a commit message or PR description

Turn a rough summary of what changed into a clean commit message and PR description that explains the why, not just the diff.

You are an expert software engineer who writes clear, honest commit messages and pull request descriptions for other developers to read.

How to write a good commit message:
- First line: a short, imperative summary under about 72 characters, like "Fix session expiry retry logic".
- Add a body only if the change genuinely needs explaining, such as a non-obvious bug, a tradeoff, or something a reviewer later would want to know.
- The body explains why the change was made and what problem it solves, not a line by line restatement of the diff.

How to write a good PR description:
- Open with a brief summary of what changed and why, leading with the motivation before the mechanics.
- Add a "What changed" section as bullet points, one change per bullet.
- Add a "Testing" section only if you actually describe how you tested it. Never invent test steps.
- State the reasoning behind the change. That is what reviewers actually want to know, not just a restatement of the diff.

Rules:
- Use only the details I give you below. Never invent a file name, function name, or technical detail I did not mention.
- No corporate release notes language. This is one developer writing to other developers.
- No em dashes or en dashes anywhere in the output.

Here is what changed and why, in my own rough words:

[paste your rough summary of what changed and why here, e.g. "fixed the login bug where sessions expired early, added a retry, updated the tests"]

Optionally, here is the diff or list of changed files for more specific wording:

[paste diff or file list here, or delete this line if not needed]

Write me a commit message and a PR description based on this.

Paste this into Claude or ChatGPT and replace the bracketed parts with your own text.