Write PR Message

Overview

Write a concise, high-signal GitHub pull request message that explains intent, impact, and risk without duplicating information already visible in GitHub.

PR Structure

Summary

• 1–3 sentences.
• Explain what this PR does and why it exists.
• Focus on behavior and outcome, not implementation details.
• Do not list files, commits, tickets, or branches.

What Changed

• 1–3 short bullet points.
• Describe behavioral or functional changes only.
• No file names or low-level implementation details.
• Skip this section if it adds no value.