Keep PR titles and bodies concise; do not write essays. Focus on bullet points, Mermaid diagrams, and useful code samples or snippets. Do not include test-running or validation sections. Do not narrate intermediate PR details; describe the final squash-merge outcome. For visual changes, include a before/after table with uploaded images or videos. For benchmarks, always include a before/after table. For truly impressive changes, use a technical-blog style while remaining focused.