Skip to main content

Task Breakdown: Generation Cancellation

Feature ID: generation-cancellation Plan: ./plan.md Status: Done (Retrospective) Last updated: 2026-05-01

Retrospective task list — all items shipped via PR #383.

Phase 1 — Contracts​

  • T1. Add CANCELLED to GenerateStatusType enum in packages/contracts/src/api/work/generate-status.enum.ts.
  • T2. Forward migration adjusting any DB check constraints that enumerated allowed status values.

Phase 2 — Service​

  • T3. cancelGeneration(workId, user) on WorkGenerationService with mode routing.
  • T4. Plumbing for in-process AbortController in the pipeline executor — signals cancellation between steps.
  • T5. markCancelled helper that closes the in-progress GenerationHistory row and updates work status.

Phase 3 — API​

  • T6. POST /api/works/:id/cancel-generation controller method with @HttpCode(202) and Swagger docs.
  • T7. e2e test in apps/api/test/ covering all four modes.

Phase 4 — Web​

  • T8. Cancel control on the work detail page.
  • T9. Cancel control on the activity views for in-progress runs.

Phase 5 — Docs​

  • T10. User-facing doc at docs/features/generation-cancellation.md.
  • T11. Updates to work-lifecycle.md describing the new terminal state.

Definition of Done​

  • All tasks shipped.
  • Tests pass.
  • User-facing doc present.
  • Constitution gates verified.