Goal

Publish a ready-for-review GitHub PR, resolve its merge conflicts, and get all applicable PR checks passing on the final pushed head. If an open PR already exists with current branch/changes, do not create another PR.

Merge Conflicts

Resolve every conflicted hunk deliberately. For visible UI conflicts, preserve the head branch's local UI structure, interaction model, copy, and styling intent by default. Incorporate compatible or required base changes, but do not replace local UI work merely because the base is newer.

PR Title & Body

Focus the PR content on the ROI of the changes in simple, clear language:

• Start from the problem the branch solves.
• Explain what changed.
• Highlight the real-world benefit: time saved, manual work removed, risk reduced, workflows made faster, support burden reduced, reliability improved, recovery made easier, maintenance made cheaper, or revenue/profit protected.
• Make the value specific to this diff. Do not use generic business language that could describe any PR.

Include: