kanban-setuplisted

User-invoked only (`/kanban-setup`) because it creates real GitHub issues. **This creates real, visible GitHub issues.** Always show the user the full preview list of issues about to be created and wait for confirmation before creating anything — don't create blind, and don't skip items silently. ## 1. Prerequisite `gh project` commands need the `project` scope. Check `gh auth status`; if `project` isn't listed, tell the user to run `gh auth refresh -s project -s read:project` (interactive, opens a browser) and stop until it's done. ## 2. Board setup (idempotent — skip if it already exists) ``` gh project list --owner <owner> --format json ``` Locate the board the way `next` §1 does (title match `<repo> Board`, then label fallback). An unrelated existing board on the owner's account is not evidence this repo has one — don't treat any non-empty list as "done." If no title match exists: `gh project create --owner <owner> --title "<repo> Board"`. **Status field must have an "In Review" option** — `session-handoff` moves cards there. Projects v2's default Status field ships with only Todo/In Progress/Done. Check with `gh project field-list <number> --owner <owner> --format json` (look at the `Status` field's `options`); don't assume. - Missing "In Review": `gh` has no command to add an option to an *existing* single-select field — `field-create` only makes new fields (verified via `gh project field-create --help`). The only CLI-level fix is the GraphQL mutation `updatePr