Plan: Filter terminal tasks from Pipeline Kanban#

Summary#

Filter tasks with terminal statuses (complete, error, cancelled) from the Kanban board before column grouping, so only genuinely in-progress work appears. The filter is based solely on overall status, not individual phase fields.

Files#

Steps#

1. Define a TERMINAL_STATUSES set containing 'complete', 'error', and 'cancelled' in app/pipeline/page.tsx.
2. In the if (data) block (line 175–182), filter data.data to exclude tasks whose status matches any terminal value before iterating into tasksByPhase.
3. Verify that the list view (the <details> fallback) still shows all tasks unfiltered, since it uses data.data directly.

Verification#

• npm run lint passes with zero warnings.
• npm run build compiles successfully.
• Manual check: a task with status: complete does not appear in any Kanban column; a task with phaseDeliver: complete but non-terminal status remains visible.

Risks#

• The status strings (complete, error, cancelled) must match exactly what the API returns. If the API uses different casing or values, the filter will silently miss tasks. Mitigation: verify against the StatusBadge component and the status filter dropdown values already in the file.