Update Pr

Overview

Rewrite pull request metadata as if drafting it from scratch for the current diff. Treat the title and body as a current reviewer-facing summary of the final net-new feature or bug fix in the PR, not as commentary about prior versions of the PR or the path taken to get there.

Workflow

1. Read the current PR title/body and the current branch diff before drafting.
2. Identify the PR's current net-new scope, APIs, behavior changes, and reviewer-relevant context.
3. Rewrite the body from scratch so it describes the shipped feature/fix as it exists now.
4. Review the title at the same time and update it whenever the body is updated.
5. Apply the update with gh pr edit.

Rules

• Never write the description as an update to itself. Do not say things like "this expands the original PR", "this PR now also", or similar process narration unless the user explicitly wants history called out.
• Describe the net-new feature or bug fix, not the implementation journey. Do not call out intermediate cleanup, refactors, rewrites, or iteration details unless they are necessary to understand the final delivered behavior.