{
  "meta": {
    "agent": "planner",
    "task_id": "53",
    "title": "Filter terminal tasks from Pipeline Kanban board",
    "created_at": "2026-04-02T12:00:00Z"
  },
  "inputs": [
    {
      "name": "issue-53",
      "type": "context",
      "ref": "https://github.com/AgentSDE/agent-core-control-center/issues/53",
      "notes": "Tasks with terminal status stuck in Kanban phase columns"
    },
    {
      "name": "pipeline-page",
      "type": "file",
      "ref": "app/pipeline/page.tsx",
      "notes": "Kanban board implementation — grouping logic at lines 166–182"
    }
  ],
  "outputs": [
    {
      "name": "plan",
      "type": "plan",
      "format": "md",
      "content": "See plan.md"
    }
  ],
  "files": [
    {
      "path": "app/pipeline/page.tsx",
      "action": "modify",
      "reason": "Add terminal-status filter before Kanban column grouping"
    }
  ],
  "steps": [
    {
      "id": "S1",
      "summary": "Add terminal-status filter to Kanban grouping in app/pipeline/page.tsx",
      "acceptance": [
        "Tasks with status 'complete' are excluded from all Kanban phase columns",
        "Tasks with status 'error' are excluded from all Kanban phase columns",
        "Tasks with status 'cancelled' are excluded from all Kanban phase columns",
        "Tasks in non-terminal states continue to appear in their correct phase column",
        "List view (details fallback) still shows all tasks unfiltered",
        "npm run lint passes",
        "npm run build passes"
      ],
      "depends_on": []
    }
  ],
  "risks": [
    {
      "risk": "Terminal status string values may not match API response exactly",
      "mitigation": "Verify against existing StatusBadge usage and status dropdown values in the same file"
    }
  ],
  "assumptions": [
    "The API returns status as lowercase strings matching 'complete', 'error', 'cancelled'",
    "No dedicated 'Complete' column is needed — terminal tasks are simply hidden from Kanban"
  ],
  "open_questions": []
}