manual_slop/conductor/tracks/robust_live_simulation_verification/spec.md

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.

Context & Origins

This track was born from the "Human Verification" phase of the initial MMA Orchestrator prototype (mma_orchestrator_integration_20260226). We realized that while the backend API plumbing for the hierarchical MMA tiers (Tiers 1-4) was technically functional, the product lacked the necessary state management, UX visualization, and human-in-the-loop security gates to be usable.

Key Takeaways from the Prototype Phase:

• The Tier 2 (Tech Lead) needs its own track-scoped discussion history, rather than polluting the global project history.
• Tasks within a track require a DAG (Directed Acyclic Graph) engine to manage complex dependencies and blocking states.
• The GUI must visualize this DAG and stream the output of individual workers directly to their associated tasks.
• We must enforce tiered context subsetting so that Tier 3/4 workers don't receive the massive global context blob, and we need a pre-spawn approval modal so the user can intercept, review, and modify worker prompts/contexts before they execute.

Instructions for the Implementing Agent: As you execute this track, ensure you maintain alignment with the other Phase 2 tracks. If you learn something that impacts the dependent tracks, please append a similar "Context Summary" to their spec.md files before concluding your run.