complete-workflowlisted

# Complete Workflow (no gaps, no mistakes) Follow `docs/COMPLETE-WORKFLOW.md` exactly. The loop is: ``` GOAL → CONTRACT → PLAN → RESERVE → RUN → EVIDENCE → REVIEW → MERGE → RELEASE → LAUNCH ``` ## Mandatory, every session 1. **Rehydrate first.** Read the current owner request, task contract (`goal_show`), ledger (`plan_show`), checklist, branch/worktree state, and `origin/main` before any mutation. Summaries alone are never authority. 2. **Contract.** If no goal exists, call `goal_set` with one outcome, named terminal gates, fixed denominator, scope, baseline SHA, deadline or `none`. Freeze before the first mutation. 3. **Plan.** Call `plan_create` with non-overlapping tasks; each task has a named acceptance condition and concrete scope. 4. **Reserve.** Call `wp_reserve` (preview with `--dry-run`, then reserve). 5. **Execute with the right tool:** - Browser/web → `chrome_*` tools, using ONLY the user's NORMAL Chrome profile (launched on port 9222 via `scripts/launch-chrome-cdp.mjs` — the profile logged into all accounts). Never a dedicated automation profile, a fresh/guest window, or a logged-out Chrome. If normal Chrome is not on 9222, run the launcher first; never fall back to another profile. - Visible desktop → `computer_*` tools. - Lanes/commands → `wp_run` (argv only, no shell). - Context/knowledge → the matching skill from the skill map (Superpowers for planning/TDD/debugging, Anthropic official for docx/pdf/