flow-shiplisted

# Ship ## Overview `ship` takes the verified work on the current branch and turns it into one pull request: it commits whatever is dirty, pushes the branch, and opens (or updates) a single PR against the base, attaching the latest `verify` evidence so a reviewer sees the proof, not a promise. It is the last step of a story — run it after a green verify. ## Command ```bash ai-flow ship ``` > If bare `ai-flow` is not on `PATH`, use `npx @landry_pouth/coding-flow ship`. Uses > `gh` when available; without it, `ship` pushes and prints the compare URL to open > the PR by hand. Useful flags: - `--base <ref>` — target branch (default: the remote's default branch). - `--title <text>` — PR title (default: derived from the commits). - `--draft` — open the PR as a draft (never auto-merged). - `--web` — open the PR in the browser afterward. - `--no-evidence` — do not attach the latest verify evidence. - `--no-commit` — do not auto-commit a dirty tree; push existing commits only. - `--auto-merge` / `--no-auto-merge` — override the project's `autoMergeEpic` config for this run (see Auto-Merge below). - `--merge-method <merge|squash|rebase>` — merge strategy when auto-merging (default: `merge`). - `--dry-run` — show what would happen without pushing. ## Behavior - **One feature = one branch = one PR.** Idempotent: if the PR already exists, the push updates it — nothing is recreated. - It keys off the current **branch**, so it works the same inside a worktree or a normal che