test(#27): test research agent for a feature ticket

.env.example

@@ -1,2 +1,3 @@
 # Anthropic API Key for Claude models
 ANTHROPIC_API_KEY=your_api_key_here
+MCP_SERVER_URL=https://your-mcp-server/mcp    

docs/testing/research-workflow-test-report-10577.md

@@ -0,0 +1,187 @@
+> cht-agent@0.1.0 research
+> node dist/cli/research.js tickets/10577.md
+
+╔════════════════════════════════════════════════════════════════╗
+║              CHT Multi-Agent System - Research CLI             ║
+╚════════════════════════════════════════════════════════════════╝
+
+📄 Loading ticket from: /Users/andra/Documents/GitHub/cht-agent/tickets/10577.md
+
+✅ Ticket parsed successfully!
+
+🤖 Initializing Research Supervisor...
+
+📋 Issue Details:
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+Title: Add ability to filter tasks
+Type: feature
+Priority: high
+Domain: tasks-and-targets
+Components: webapp/src/ts/modules/tasks, webapp/src/ts/components/filters, Report filtering feature (existing pattern to follow), task.action.form, task.name
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+🔍 Running Research Phase...
+
+
+========================================
+RESEARCH SUPERVISOR - Starting Research Phase
+========================================
+Issue: Add ability to filter tasks
+Domain: tasks-and-targets
+Components: webapp/src/ts/modules/tasks, webapp/src/ts/components/filters, Report filtering feature (existing pattern to follow), task.action.form, task.name
+========================================
+
+
+=== DOCUMENTATION SEARCH NODE ===
+
+[Documentation Search Agent] Starting documentation search...
+[Documentation Search Agent] Domain: tasks-and-targets
+[Documentation Search Agent] Issue: Add ability to filter tasks
+[Documentation Search Agent] Search query: tasks-and-targets webapp/src/ts/modules/tasks webapp/src/ts/components/filters Report filtering feature (existing pattern to follow) task.action.form task.name Add ability to filter tasks # Description
+
+When CHWs provide services in the community, they face challenges navigating the CHT tasks. With numerous tasks listed, it often becomes difficult to scroll through and identify specifi
+[Documentation Search Agent] Found 10 documentation references
+[Documentation Search Agent] Confidence: 0.85
+
+=== CONTEXT ANALYSIS NODE ===
+
+[Context Analysis Agent] Starting context analysis...
+[Context Analysis Agent] Domain: tasks-and-targets
+[Context Analysis Agent] No resolved issues found for domain: tasks-and-targets
+[Context Analysis Agent] Found 0 similar past issues
+[Context Analysis Agent] Extracted 0 reusable patterns
+[Context Analysis Agent] Found 0 relevant design decisions
+[Context Analysis Agent] Generated 3 recommendations
+
+=== GENERATE PLAN NODE ===
+[Research Supervisor] Generating orchestration plan...
+[Research Supervisor] Plan generated successfully
+
+========================================
+RESEARCH SUPERVISOR - Research Phase Complete
+========================================
+Final Phase: complete
+Errors: 0
+========================================
+
+
+╔════════════════════════════════════════════════════════════════╗
+║                      RESEARCH RESULTS                          ║
+╚════════════════════════════════════════════════════════════════╝
+
+⏱️  Duration: 34.72 seconds
+📊 Phase: complete
+❌ Errors: 0
+
+📚 DOCUMENTATION SEARCH RESULTS
+──────────────────────────────────────────────────────────────────────
+Source: kapa-ai
+Confidence: 85%
+
+Documentation References (10):
+
+1. Tasks sidebar filter.component.ts#L1 L39
+   URL: https://github.com/medic/cht-core/blob/master/webapp/src/ts/modules/tasks/tasks-sidebar-filter.component.ts#L1-L39
+   Topics: tasks-and-targets
+
+2. Tasks sidebar filter.component.ts#L40 L168
+   URL: https://github.com/medic/cht-core/blob/master/webapp/src/ts/modules/tasks/tasks-sidebar-filter.component.ts#L40-L168
+   Topics: tasks-and-targets
+
+3. Task type filter.component.ts
+   URL: https://github.com/medic/cht-core/blob/master/webapp/src/ts/components/filters/task-type-filter/task-type-filter.component.ts
+   Topics: tasks-and-targets
+
+4. Tasks.component.ts#L159 L225
+   URL: https://github.com/medic/cht-core/blob/master/webapp/src/ts/modules/tasks/tasks.component.ts#L159-L225
+   Topics: tasks-and-targets
+
+5. Tasks group.component.ts#L149 L266
+   URL: https://github.com/medic/cht-core/blob/master/webapp/src/ts/modules/tasks/tasks-group.component.ts#L149-L266
+   Topics: tasks-and-targets
+
+6. Tasks content.component.ts#L254 L361
+   URL: https://github.com/medic/cht-core/blob/master/webapp/src/ts/modules/tasks/tasks-content.component.ts#L254-L361
+   Topics: tasks-and-targets
+
+7. Tasks content.component.ts#L362 L370
+   URL: https://github.com/medic/cht-core/blob/master/webapp/src/ts/modules/tasks/tasks-content.component.ts#L362-L370
+   Topics: tasks-and-targets
+
+8. Tasks content.component.ts#L143 L253
+   URL: https://github.com/medic/cht-core/blob/master/webapp/src/ts/modules/tasks/tasks-content.component.ts#L143-L253
+   Topics: tasks-and-targets
+
+9. Tasks.component.ts#L1 L44
+   URL: https://github.com/medic/cht-core/blob/master/webapp/src/ts/modules/tasks/tasks.component.ts#L1-L44
+   Topics: tasks-and-targets
+
+10. Tasks route.guard.provider.ts
+   URL: https://github.com/medic/cht-core/blob/master/webapp/src/ts/modules/tasks/tasks-route.guard.provider.ts
+   Topics: tasks-and-targets
+
+Suggested Approaches:
+   1. Implement following CHT best practices and existing patterns
+
+🔎 CONTEXT ANALYSIS RESULTS
+──────────────────────────────────────────────────────────────────────
+Similar Past Issues: 0
+Reusable Patterns: 0
+Design Decisions: 0
+Historical Success Rate: 50%
+
+Recommendations:
+   1. Ensure comprehensive test coverage for new feature
+   2. Update documentation and configuration examples
+   3. Validate changes with integration tests before deployment
+
+📋 ORCHESTRATION PLAN
+──────────────────────────────────────────────────────────────────────
+Estimated Complexity: HIGH
+Estimated Effort: 1 week
+
+Proposed Approach:
+   Implement following CHT best practices and existing patterns
+
+Key Findings:
+   1. 10 documentation references found
+   2. 0 similar past implementations identified
+   3. Historical success rate: 50%
+   4. Ensure comprehensive test coverage for new feature
+   5. Update documentation and configuration examples
+
+Implementation Phases (4):
+
+   1. Setup and Configuration [low]
+      Set up development environment and review documentation
+      Components: development environment, documentation
+
+   2. Core Implementation [high]
+      Implement Add ability to filter tasks
+      Components: webapp/src/ts/modules/tasks, webapp/src/ts/components/filters, Report filtering feature (existing pattern to follow), task.action.form, task.name
+      Dependencies: Setup and Configuration
+
+   3. Testing [medium]
+      Write and run unit, integration, and e2e tests
+      Components: test suite, test data
+      Dependencies: Core Implementation
+
+   4. Documentation [low]
+      Update documentation and configuration examples
+      Components: docs, examples
+      Dependencies: Testing
+
+⚠️  Risk Factors:
+   1. No similar past implementations found - breaking new ground
+   2. Multiple constraints to satisfy: Filter UX should be consistent with the existing reporting filter feature, Must work offline, Decision needed on whether task type filtering uses `task.action.form` or `task.name` (low-consequence decision), Tasks with multiple actions must be handled correctly when filtering by task type
+   3. High priority issue - requires careful attention and thorough testing
+   4. Changes span multiple components - requires coordination and integration testing
+
+╔════════════════════════════════════════════════════════════════╗
+║                  Research Phase Complete! ✅                   ║
+╚════════════════════════════════════════════════════════════════╝
+
+💡 Next Steps:
+   1. Review the orchestration plan
+   2. Validate research findings
+   3. Proceed to Development Phase (coming soon)