You are Claude Code implementing a BMAD story. CONTEXT: - Process: cto_review_story_runner_dashboard - Story ID: CTO.001 - Working directory: C:\Users\info\mission-control-v2\worktrees_claude\cto_review_story_runner_dashboard\CTO.001 - BASE_REF_SHA: 10ee8db2b5f9112eee63514876fd822cefd87a64 STORY FILE CONTENT: # Story CTO.001: Add psutil dependency to requirements.txt ## Context De `terminal_monitor.py` module importeert `psutil` voor process scanning, maar deze dependency ontbreekt in `requirements.txt`. Dit veroorzaakt import errors bij fresh installs. Evidence: `tools/story-runner/dashboard/terminal_monitor.py:13` importeert psutil, maar `requirements.txt` bevat alleen `piexif` en `Pillow`. ## Story Als **developer** wil ik dat **psutil in requirements.txt staat** zodat **pip install -r requirements.txt alle benodigde dependencies installeert**. ## Acceptance Criteria - **AC1:** psutil is toegevoegd aan requirements.txt met versie constraint. - **Verification (repo-root):** `grep -E "^psutil" requirements.txt` - **Expected:** `psutil>=5.9.0` - **AC2:** psutil is importeerbaar in Python. - **Verification (repo-root):** `python -c "import psutil; print(\"OK\")"` - **Expected:** `OK` ## Tasks / Subtasks - [ ] Voeg `psutil>=5.9.0` toe aan requirements.txt (AC: 1) - [ ] Verifieer dat pip install werkt (AC: 2) ## Dev Notes ### Scope - **In scope:** requirements.txt wijzigen - **Out-of-scope:** Andere dependency changes, Python versie upgrades ### No broad refactors (hard rule) Geen andere wijzigingen aan requirements.txt dan psutil toevoegen. ### Touched paths allowlist (repo-relatief, exact) - `requirements.txt` **Verificatie (subset-check):** - `git diff --name-only HEAD~1...HEAD` moet subset zijn van allowlist ### Test- en gate-commands - `pip install -r requirements.txt --dry-run` - `python -c "import psutil; print(psutil.__version__)"` ### Rollback plan ```bash git checkout HEAD~1 -- requirements.txt ``` ## Dev Agent Record ### Completion Notes List (in te vullen door dev agent) ### File List (in te vullen door dev agent) ## Status ready-for-dev INSTRUCTIONS: 1. Implement the story exactly as specified in the acceptance criteria. 2. Follow the touched paths allowlist strictly - do not modify files outside the allowlist. 3. After implementing, verify each acceptance criteria passes. 4. Commit your changes with message: "impl: CTO.001" 5. Do NOT merge - the runner handles merging. HARD RULES: - No broad refactors beyond what the story requires. - Stay within the touched paths allowlist. - All verification commands must pass. - If blocked, FAIL with a clear error message. NOW IMPLEMENT THE STORY.