Remember that PR titles become commit messages after merging, so keep them informative for other devs and users. As a rule of thumb, PR titles should be able to double as a changelog entry with no further clarification needed. Please use a PR title that conforms to conventional commits:
<commit_type>: <description>, for example: "fix: prevent race condition when using data adapter". Some other commit types arefix,feat,ci,doc,refactor... For a full list of commit types visit https://www.conventionalcommits.org/en/v1.0.0/ Then delete this text.
If the changes resolve an issue or follow some other PR, link to them here. Only link something if it is directly relevant. Then delete this text.
Explain why this change exists and what it does at a high level — write for a reviewer seeing it for the first time, and for someone reading it a year from now to understand the motivation. Give the context the diff can't: the problem, the approach, and any trade-offs or alternatives considered. Don't restate what the code already shows or pad with detail. Then delete this text.
Describe how you convinced yourself the change works, so a reviewer can judge whether the evidence is enough; e.g., "CI passes", "Tested manually in stagingrepo#123", screenshots of a terminal session, or any other evidence. Note anything you couldn't test and why. Then delete this text.