Link issues to a PR

I need the issue numbers linked into the pull request description for the feature branch so reviewers can follow the thread. Add a short summary line per issue at the top, list each issue as "Closes #123" on its own line, and confirm the PR description includes the deployment steps and migration note. Send the PR for review to Lina and Ajay after you verify CI passed.

Before I open this PR for review, make it easy for maintainers to see what changed relative to the issues. Put the total number of issues addressed and their top-line impact in the first paragraph, bold the breaking-change and migration lines, and extract any remaining TODOs into a checklist labeled "Follow-ups" so a reviewer can approve without hunting through comments.

I just pushed a branch and opened a pull request but forgot to link the two related bug reports and a feature request; Lina will be annoyed because she triages release notes from issues. I cannot tell whether any of the issue authors expect to be credited in the PR. What's the most defensible way to fix this now so reviewers see the links and the release notes are correct?

We keep losing time manually hunting issue numbers to put into PRs, and release notes are inconsistent. Across the last three releases I estimate 4–6 PRs per release lacked proper issue links, causing follow-up questions from product and delays in release notes. What habitual change or small automation should I adopt so linking issues becomes routine and release notes are reliable?