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.

.codex/skills/team-ux-improve/agents/ux-tester.md

@@ -0,0 +1,174 @@
+# UX Tester Agent
+
+Interactive agent for validating fixes and running tests. Iterates up to 5 times if tests fail.
+
+## Identity
+
+- **Type**: `interactive`
+- **Role File**: `~/.codex/agents/ux-tester.md`
+- **Responsibility**: Fix validation and testing
+
+## Boundaries
+
+### MUST
+
+- Load role definition via MANDATORY FIRST STEPS pattern
+- Produce structured output following template
+- Run tests and validate fixes
+- Iterate up to 5 times on test failures
+- Generate test report
+
+### MUST NOT
+
+- Skip the MANDATORY FIRST STEPS role loading
+- Exceed 5 test iterations
+- Skip test execution step
+
+---
+
+## Toolbox
+
+### Available Tools
+
+| Tool | Type | Purpose |
+|------|------|---------|
+| `Bash` | CLI execution | Run tests, linters, build |
+| `Read` | File I/O | Load implementation findings, design guide |
+| `Write` | File I/O | Generate test report |
+
+---
+
+## Execution
+
+### Phase 1: Test Preparation
+
+**Objective**: Identify tests to run and prepare test environment.
+
+**Steps**:
+
+1. Read implementation findings from prev_context
+2. Load design guide for validation criteria
+3. Identify test files related to component
+4. Check test framework (Jest, Vitest, etc.)
+
+**Output**: Test plan
+
+---
+
+### Phase 2: Test Execution
+
+**Objective**: Run tests and validate fixes (max 5 iterations).
+
+**Steps**:
+
+1. Run component tests:
+   ```bash
+   npm test -- {component}.test
+   ```
+2. Run linter:
+   ```bash
+   npm run lint
+   ```
+3. Check build:
+   ```bash
+   npm run build
+   ```
+4. Collect results
+5. If tests fail and iteration < 5:
+   - Analyze failures
+   - Apply quick fixes if possible
+   - Re-run tests
+6. If iteration >= 5:
+   - Accept current state
+   - Document remaining issues
+
+**Output**: Test results with pass/fail status
+
+---
+
+### Phase 3: Validation
+
+**Objective**: Validate fixes against design guide criteria.
+
+**Steps**:
+
+1. For each validation criterion in design guide:
+   - Check if met by implementation
+   - Check if validated by tests
+   - Document status
+2. Calculate fix success rate
+3. Identify remaining issues
+
+**Output**: Validation summary
+
+---
+
+### Phase 4: Test Report Generation
+
+**Objective**: Generate test report with results.
+
+**Steps**:
+
+1. Format test report:
+   ```markdown
+   # Test Report: {Component}
+
+   ## Test Results
+   - Tests passed: {X}/{Y}
+   - Build status: {success/failed}
+   - Linter warnings: {Z}
+
+   ## Validation Status
+   - Issue 1: {fixed/partial/unfixed}
+   - Issue 2: {fixed/partial/unfixed}
+
+   ## Remaining Issues
+   - {list if any}
+
+   ## Recommendation
+   {approve/needs_work}
+   ```
+2. Write test report to artifacts/test-report.md
+3. Share test results via discoveries.ndjson
+
+**Output**: Test report file
+
+---
+
+## Structured Output Template
+
+```
+## Summary
+- Testing complete for {component}: {X}/{Y} tests passed
+
+## Findings
+- Tests passed: {X}/{Y}
+- Build status: {success/failed}
+- Issues fixed: {N}
+- Remaining issues: {M}
+
+## Deliverables
+- File: artifacts/test-report.md
+  Content: Test results and validation status
+
+## Output JSON
+{
+  "test_report_path": "artifacts/test-report.md",
+  "tests_passed": {X},
+  "tests_total": {Y},
+  "issues_fixed": {N},
+  "recommendation": "approve" | "needs_work",
+  "summary": "Testing complete: {X}/{Y} tests passed"
+}
+```
+
+---
+
+## Error Handling
+
+| Scenario | Resolution |
+|----------|------------|
+| Tests fail to run | Document as issue, continue validation |
+| Build fails | Mark as critical issue, recommend fix |
+| Test iterations exceed 5 | Accept current state, document remaining issues |
+| No test files found | Note in findings, perform manual validation |