chore(conductor): Archive old track and initialize 4 new Phase 2 MMA tracks

This commit is contained in:
2026-02-27 19:19:11 -05:00
parent 41ae3df75d
commit 6e0948467f
13 changed files with 131 additions and 2 deletions

View File

@@ -0,0 +1,15 @@
# Implementation Plan: Robust Live Simulation Verification
## Phase 1: Framework Foundation
- [ ] Task: Create `tests/visual_sim_mma_v2.py` based on existing simulation patterns.
- [ ] Task: Implement helper methods in `ApiHookClient` for querying specific DearPyGui item states (e.g., `get_text_value`, `get_node_status`).
## Phase 2: Epic & Track Verification
- [ ] Task: Write the simulation routine to trigger a new Epic and verify the Track Browser updates correctly.
- [ ] Task: Verify that selecting a newly generated track successfully loads its initial (empty) state into the DAG visualizer.
## Phase 3: DAG & Spawn Interception Verification
- [ ] Task: Simulate the "Start Track" action and verify the DAG visualizer populates with tasks.
- [ ] Task: Simulate the Auto-Queue advancing to a "Ready" task.
- [ ] Task: Verify the "Approve Worker Spawn" modal appears with the correct prompt and context.
- [ ] Task: Simulate clicking "Approve" and verify the worker's simulated output streams into the correct task detail view.

View File

@@ -0,0 +1,13 @@
# Track Specification: Robust Live Simulation Verification
## Overview
Establish a robust, visual simulation framework to prevent regressions in the complex GUI and asynchronous orchestration layers. This track replaces manual human verification with an automated script that clicks through the GUI and verifies the rendered state.
## Goals
1. **Simulation Framework Setup:** Build a dedicated test script (`tests/visual_sim_mma_v2.py`) utilizing `ApiHookClient` to control the live GUI.
2. **Simulate Epic Planning:** Automate the clicking of "New Epic", inputting a prompt, and verifying the expected Tier 1 tracks appear in the UI.
3. **Simulate Execution & Spawning:** Automate the selection of a track, the generation of the DAG, and the interaction with the HITL Approval modal.
## Constraints
- Must run against a live instance of the application using `--enable-test-hooks`.
- Must fail loudly if the visual state (e.g., rendered DAG nodes, text box contents) does not match expectations.