Plan: Remove `execute` phase and reorder `deliver` before `review`#

Summary#

Remove all references to the deprecated execute pipeline phase and fix phase ordering so deliver comes before review across all UI components, type definitions, and constants in the control center.

Files#

File	Action	Description
`app/pipeline/page.tsx`	modify	Remove `execute` from `KANBAN_PHASES` array and `tasksByPhase` init; reorder `deliver` before `review`
`app/config/page.tsx`	modify	Remove `execute` from `SKILL_KEYS` array; reorder `deliver` before `review`
`lib/api/tasks.ts`	modify	Remove `phaseExecute` field from `Task` interface; reorder `phaseDeliver` before `phaseReview`
`app/pipeline/[taskId]/page.tsx`	modify	Remove `execute` entry from `PHASE_FIELDS`; reorder `deliver` before `review` in `PHASE_FIELDS` and the hardcoded dropdown (line ~185)

Steps#

S1: Update phase arrays and constants — Remove execute from KANBAN_PHASES in app/pipeline/page.tsx, SKILL_KEYS in app/config/page.tsx, and PHASE_FIELDS + dropdown in app/pipeline/[taskId]/page.tsx. Reorder all to: refine, plan, deliver, review, compound.
S2: Update Task interface and data structures — Remove phaseExecute from Task interface in lib/api/tasks.ts. Remove execute key from tasksByPhase object init in app/pipeline/page.tsx. Reorder field declarations so phaseDeliver precedes phaseReview.

Verification#

npm run lint passes with zero warnings
npm run build compiles successfully
Grep for execute in phase-related contexts returns zero hits

Risks#

phaseExecute in the Task interface mirrors the backend API response shape. If agent-core still sends this field, removing it is safe (TS will ignore extra props), but any code reading task.phaseExecute will break at compile time — the build step will catch this.

Plan: Remove execute phase and reorder deliver before review#