prlisted

# PR Dispatch on the first argument: - `create` → see Create below - `draft` → same as Create but create a draft PR instead of a regular PR - `update` → see Update below - `preview` → see Preview below - No argument or unknown → check if a PR exists for the current branch. If yes, run Update. If no, run Create. An optional `base=<branch>` argument (any position) sets the target branch. If omitted, default to the repo's default branch. Pass via `--base <branch>` to `gh pr create`. Ignored for `update` and `preview`. **Before drafting any PR body (create/draft/update/preview): Read [references/content-guidelines.md](references/content-guidelines.md) in full.** Do not draft from memory. ## Template Use this structure as a guideline; adapt sections to fit the actual changes. Do not add sections not defined here. Omit sections that don't apply. ```markdown # Overview [Brief summary of the PR's purpose and scope.] ["Resolves [PREFIX-1234](https://tracker.example.com/PREFIX-1234)". Use link for GitHub, Asana, Linear, etc. If no issue, omit this line.] ## Key Changes - **[Brief description of what changed]** - [Description of what changed and why. Can span multiple bullets if needed, but avoid excessive detail.] - **[Brief description of another change]** - [Description of what changed and why.] ## Design Decisions [Explanation of major design decisions made in the PR, focusing on architecture and rationale rather than implementation specifics.] ## Overall Flow [I