Title#
feat: implement #501 — Remove execute phase and align CC APIs with current pipeline
Problem#
The execute phase column and its references remain in the database entity, DTOs, and test fixtures despite having been removed from PHASE_ORDER and routing maps. This causes API inconsistencies and misleading test fixtures.
Task / Link#
Closes #501
Changes#
- Remove
phaseExecutecolumn fromTaskEntity - Remove
phaseExecute: 'pending'fromcreateTask()defaults inTaskStateService - Remove
'execute'from PHASES arrays inPhaseOverrideDtoandStatusOverrideDto, reorder to[refine, plan, deliver, review, compound] - Update all test fixtures across 9 spec files to replace
phaseExecute,currentPhase: 'execute', andexecute_completed/execute_failedevent types with valid phases (deliver)
Notes#
- Existing SQLite DB rows retain the
phase_executecolumn harmlessly — TypeORM stops reading/writing it without a migration event-bus.service.spec.ts(not in original plan) also had acurrentPhase: 'execute'fixture; fixed
Testing#
npm run lint— passed (zero warnings)npm run test— 790 tests passed, 0 failures