conductor(track): Initialize testing consolidation track and add execution order

TASKS.md

@@ -64,3 +64,26 @@
 
 **Scope:** Phase 1 (Meta-tooling token fix) → Phase 2 (Seal GUI HITL bypass) → Phase 3 (Fix DAG Engine cascading blocks).
 
+### `testing_consolidation_20260302` (initialized)
+**Priority:** Medium
+**Depends on:** `tech_debt_and_test_cleanup_20260302`
+**Track dir:** `conductor/tracks/testing_consolidation_20260302/`
+
+**Audit-confirmed gaps:**
+- `visual_mma_verification.py` manually runs `subprocess.Popen` instead of using the robust `live_gui` fixture.
+- Duplicate architectural logic between tests and `simulation/` directories causing fragmentation.
+
+**Scope:** Phase 1 (Migrate manual launchers to fixtures) → Phase 2 (Consolidate simulation scripts).
+
+---
+
+## Track Dependency Order (Execution Guide)
+To ensure smooth execution, execute the tracks in the following order:
+1. `feature_bleed_cleanup_20260302` (Base cleanup of GUI structure)
+2. `mma_agent_focus_ux_20260302` (Depends on feature bleed cleanup Phase 1)
+3. `architecture_boundary_hardening_20260302` (Fixes critical HITL & Token leaks; independent but foundational)
+4. `tech_debt_and_test_cleanup_20260302` (Re-establishes testing foundation; run after feature tracks)
+5. `testing_consolidation_20260302` (Refactors testing methodology; depends on tech debt cleanup)
+6. `conductor_workflow_improvements_20260302` (Meta-level updates to skills/workflow docs; can be run anytime)
+
+