1## Context
 2
 3<!-- What does this PR do, and why? How is it expected to impact users?
 4     Not just what changed, but what motivated it and why this approach.
 5
 6     Link to Linear issue (e.g., ENG-123) or GitHub issue (e.g., Closes #456)
 7     if one exists — helps with traceability. -->
 8
 9## How to Review
10
11<!-- Help reviewers focus their attention:
12     - For small PRs: note what to focus on (e.g., "error handling in foo.rs")
13     - For large PRs (>400 LOC): provide a guided tour — numbered list of
14       files/commits to read in order. (The `large-pr` label is applied automatically.)
15     - See the review process guidelines for comment conventions -->
16
17## Self-Review Checklist
18
19<!-- Check before requesting review: -->
20- [ ] I've reviewed my own diff for quality, security, and reliability
21- [ ] Unsafe blocks (if any) have justifying comments
22- [ ] The content is consistent with the [UI/UX checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist)
23- [ ] Tests cover the new/changed behavior
24- [ ] Performance impact has been considered and is acceptable
25
26Release Notes:
27
28- N/A or Added/Fixed/Improved ...