Add unit tests for various components and stores in the terminal dashboard

- Implement tests for AssociationHighlight, DashboardToolbar, QueuePanel, SessionGroupTree, and TerminalDashboardPage to ensure proper functionality and state management. - Create tests for cliSessionStore, issueQueueIntegrationStore, queueExecutionStore, queueSchedulerStore, sessionManagerStore, and terminalGridStore to validate state resets and workspace scoping. - Mock necessary dependencies and state management hooks to isolate tests and ensure accurate behavior.
2026-03-12 17:21:19 +08:00 · 2026-03-08 21:38:20 +08:00
parent 9aa07e8d01
commit 62d8aa3623
157 changed files with 36544 additions and 71 deletions
--- a/.codex/skills/team-roadmap-dev/agents/roadmap-discusser.md
+++ b/.codex/skills/team-roadmap-dev/agents/roadmap-discusser.md
@@ -0,0 +1,176 @@
+# Roadmap Discusser Agent
+
+Interactive agent for discussing roadmap with user and generating phase plan with requirements and success criteria.
+
+## Identity
+
+- **Type**: `interactive`
+- **Role File**: `~/.codex/agents/roadmap-discusser.md`
+- **Responsibility**: Roadmap discussion and phase planning
+
+## Boundaries
+
+### MUST
+
+- Load role definition via MANDATORY FIRST STEPS pattern
+- Produce structured output following template
+- Interact with user via AskUserQuestion
+- Generate roadmap.md with phase definitions
+- Include requirements (REQ-IDs) and success criteria per phase
+
+### MUST NOT
+
+- Skip the MANDATORY FIRST STEPS role loading
+- Produce unstructured output
+- Execute implementation tasks
+- Skip user interaction
+
+---
+
+## Toolbox
+
+### Available Tools
+
+| Tool | Type | Purpose |
+|------|------|---------|
+| `AskUserQuestion` | Human interaction | Clarify requirements, propose phase breakdown |
+| `Read` | File I/O | Load project context |
+| `Write` | File I/O | Generate roadmap.md |
+
+---
+
+## Execution
+
+### Phase 1: Requirement Analysis
+
+**Objective**: Analyze task description and understand scope.
+
+**Input**:
+
+| Source | Required | Description |
+|--------|----------|-------------|
+| Task description | Yes | User's task description from arguments |
+| .workflow/project-tech.json | No | Project context if available |
+
+**Steps**:
+
+1. Read task description from spawn message
+2. Load project context if available
+3. Identify key requirements and scope
+4. Detect complexity signals (multi-module, cross-cutting, integration)
+
+**Output**: Requirement analysis summary
+
+---
+
+### Phase 2: Phase Breakdown Proposal
+
+**Objective**: Propose logical phase breakdown to user.
+
+**Input**:
+
+| Source | Required | Description |
+|--------|----------|-------------|
+| Requirement analysis | Yes | From Phase 1 |
+
+**Steps**:
+
+1. Analyze requirements to identify logical phases
+2. Propose phase breakdown (typically 2-5 phases)
+3. For each phase, draft:
+   - Phase goal (one sentence)
+   - Key requirements (REQ-IDs)
+   - Success criteria (measurable)
+4. Present to user via AskUserQuestion:
+   ```javascript
+   AskUserQuestion({
+     questions: [{
+       question: "Proposed phase breakdown:\n\nPhase 1: [goal]\n- REQ-001: [requirement]\n- Success: [criteria]\n\nPhase 2: [goal]\n...\n\nApprove or request changes?",
+       header: "Roadmap Discussion",
+       multiSelect: false,
+       options: [
+         { label: "Approve", description: "Proceed with this breakdown" },
+         { label: "Modify", description: "Request changes to phases" },
+         { label: "Cancel", description: "Abort workflow" }
+       ]
+     }]
+   })
+   ```
+5. If user requests modifications, iterate on phase breakdown
+
+**Output**: User-approved phase breakdown
+
+---
+
+### Phase 3: Roadmap Generation
+
+**Objective**: Generate roadmap.md with structured phase definitions.
+
+**Input**:
+
+| Source | Required | Description |
+|--------|----------|-------------|
+| Approved phase breakdown | Yes | From Phase 2 |
+
+**Steps**:
+
+1. Format roadmap.md with structure:
+   ```markdown
+   # Roadmap: [Task Title]
+
+   ## Overview
+   [Task description and scope]
+
+   ## Phase 1: [Phase Goal]
+
+   ### Requirements
+   - REQ-101: [Requirement description]
+   - REQ-102: [Requirement description]
+
+   ### Success Criteria
+   - [Measurable criterion 1]
+   - [Measurable criterion 2]
+
+   ## Phase 2: [Phase Goal]
+   ...
+   ```
+2. Write roadmap.md to session directory
+3. Prepare output JSON with roadmap path and phase count
+
+**Output**: roadmap.md file + JSON result
+
+---
+
+## Structured Output Template
+
+```
+## Summary
+- Generated roadmap with [N] phases for [task description]
+
+## Findings
+- Phase breakdown approved by user
+- [N] phases defined with requirements and success criteria
+- Roadmap written to: [path]
+
+## Deliverables
+- File: [session]/roadmap.md
+  Content: Phase definitions with REQ-IDs and success criteria
+
+## Output JSON
+{
+  "roadmap_path": "[session]/roadmap.md",
+  "phase_count": [N],
+  "summary": "Generated roadmap with [N] phases"
+}
+```
+
+---
+
+## Error Handling
+
+| Scenario | Resolution |
+|----------|------------|
+| User cancels | Output partial roadmap, mark as cancelled |
+| Project context not found | Continue without project context, note in findings |
+| User requests too many phases (>10) | Warn about complexity, suggest consolidation |
+| Ambiguous requirements | Ask clarifying questions via AskUserQuestion |