# Implementation Plan: Live GUI Testing Infrastructure

## Phase 1: Infrastructure & Core Utilities [checkpoint: db251a1]
Establish the mechanism for managing the live GUI process and providing it to tests.

- [x] Task: Create `tests/conftest.py` with a session-scoped fixture to manage the `gui.py --enable-test-hooks` process.
- [x] Task: Enhance `api_hook_client.py` with robust connection retries and health checks to handle GUI startup time.
- [x] Task: Update `conductor/workflow.md` to formally document the "Live GUI Testing" requirement and the use of the `--enable-test-hooks` flag.
- [x] Task: Conductor - User Manual Verification 'Phase 1: Infrastructure & Core Utilities' (Protocol in workflow.md)

## Phase 2: Test Suite Migration
Migrate existing tests to use the live GUI fixture and API hooks.

- [ ] Task: Refactor `tests/test_api_hook_client.py` and `tests/test_conductor_api_hook_integration.py` to use the live GUI fixture.
- [ ] Task: Refactor GUI performance tests (`tests/test_gui_performance_requirements.py`, `tests/test_gui_stress_performance.py`) to verify real metrics (FPS, memory) via hooks.
- [ ] Task: Audit and update all remaining tests in `tests/` to ensure they either use the live server or are explicitly marked as pure unit tests.
- [ ] Task: Conductor - User Manual Verification 'Phase 2: Test Suite Migration' (Protocol in workflow.md)

## Phase 3: Conductor Integration & Validation
Ensure the Conductor framework itself supports and enforces this new testing paradigm.

- [ ] Task: Verify that new track creation generates plans that include specific API hook verification tasks.
- [ ] Task: Perform a full test run using `run_tests.py` (or equivalent) to ensure 100% pass rate in the new environment.
- [ ] Task: Conductor - User Manual Verification 'Phase 3: Conductor Integration & Validation' (Protocol in workflow.md)