pull-requestcreatelisted

# Create Pull Request ## Context - Remote URL: !`git remote get-url origin` - Review bot: !`bun ${CLAUDE_PLUGIN_ROOT}/scripts/detect-bot.ts` - PR Template: !`bun ${CLAUDE_PLUGIN_ROOT}/scripts/pr-template.ts` !`bun ${CLAUDE_PLUGIN_ROOT}/scripts/git-context.ts` !`bun ${CLAUDE_PLUGIN_ROOT}/scripts/contributing.ts` ## Title - Check the log in the context above to determine the repo's commit style: - **subject** (default): `${subject}: ${summary}` (e.g., `api: add timeout to request`) - **conventional**: `${type}: ${summary}` (e.g., `fix: add timeout to request`) - Keep under 50 characters, max 100 - Use imperative mood, lowercase except proper nouns ## Body Lead with intent: why this change, the decisions a reviewer can't reconstruct from the diff, and how you know it works. Don't restate what the diff, git, or the status checks already carry. Mine the session for the substance that never reached the code (rejected alternatives, overturned theories, what you observed testing, scope added or dropped) and state each as a self-contained decision, not as a delta against a plan the reviewer never saw. - Open with a bare verb ("Adds", "Fixes", "Removes") when the change is self-evident, or with the problem when it needs justifying. Don't restate the title. - Default to prose. A small PR is a tight paragraph with no headers. Add `##` sections only when length earns them. Length tracks substance, not diff size. - Reference the motivating issue at the end of the opening (`Clo