chore(conductor): Add new track 'extend test simulation to have further in breadth test (not remove the original though as its a useful small test) to extensively test all facets of possible gui interaction.'

conductor/tracks.md

@@ -37,3 +37,8 @@ This file tracks all major tracks for the project. Each track has its own detail
 
 - [ ] **Track: 4-Tier Architecture Implementation & Conductor Self-Improvement**
 *Link: [./tracks/mma_implementation_20260224/](./tracks/mma_implementation_20260224/)*
+
+---
+
+- [ ] **Track: extend test simulation to have further in breadth test (not remove the original though as its a useful small test) to extensively test all facets of possible gui interaction.**
+*Link: [./tracks/gui_sim_extension_20260224/](./tracks/gui_sim_extension_20260224/)*

conductor/tracks/gui_sim_extension_20260224/index.md

@@ -0,0 +1,5 @@
+# Track gui_sim_extension_20260224 Context
+
+- [Specification](./spec.md)
+- [Implementation Plan](./plan.md)
+- [Metadata](./metadata.json)

conductor/tracks/gui_sim_extension_20260224/metadata.json

@@ -0,0 +1,8 @@
+{
+  "track_id": "gui_sim_extension_20260224",
+  "type": "chore",
+  "status": "new",
+  "created_at": "2026-02-24T19:17:00Z",
+  "updated_at": "2026-02-24T19:17:00Z",
+  "description": "extend test simulation to have further in breadth test (not remove the original though as its a useful small test) to extensively test all facets of possible gui interaction."
+}

conductor/tracks/gui_sim_extension_20260224/plan.md

@@ -0,0 +1,26 @@
+# Implementation Plan: Extended GUI Simulation Testing
+
+## Phase 1: Setup and Architecture
+- [ ] Task: Review the existing baseline simulation test to identify reusable components or fixtures without modifying the original.
+- [ ] Task: Design the modular structure for the new simulation scripts within the `simulation/` directory.
+- [ ] Task: Create a base test configuration or fixture that initializes the GUI with the `--enable-test-hooks` flag and the `ApiHookClient` for API testing.
+- [ ] Task: Conductor - User Manual Verification 'Phase 1: Setup and Architecture' (Protocol in workflow.md)
+
+## Phase 2: Context and Chat Simulation
+- [ ] Task: Create the test script `sim_context.py` focused on the Context and Discussion panels.
+- [ ] Task: Simulate file aggregation interactions and context limit verification.
+- [ ] Task: Implement history generation and test chat submission via API hooks.
+- [ ] Task: Conductor - User Manual Verification 'Phase 2: Context and Chat Simulation' (Protocol in workflow.md)
+
+## Phase 3: AI Settings and Tools Simulation
+- [ ] Task: Create the test script `sim_ai_settings.py` for AI model configuration changes (Gemini/Anthropic).
+- [ ] Task: Create the test script `sim_tools.py` focusing on file exploration, search, and MCP-like tool triggers.
+- [ ] Task: Validate proper panel rendering and data updates via API hooks for both AI settings and tool results.
+- [ ] Task: Conductor - User Manual Verification 'Phase 3: AI Settings and Tools Simulation' (Protocol in workflow.md)
+
+## Phase 4: Execution and Modals Simulation
+- [ ] Task: Create the test script `sim_execution.py`.
+- [ ] Task: Simulate the AI generating a PowerShell script that triggers the explicit confirmation modal.
+- [ ] Task: Assert the modal appears correctly and accepts input/approval from the simulated user.
+- [ ] Task: Validate the executed output via API hooks.
+- [ ] Task: Conductor - User Manual Verification 'Phase 4: Execution and Modals Simulation' (Protocol in workflow.md)

conductor/tracks/gui_sim_extension_20260224/spec.md

@@ -0,0 +1,27 @@
+# Specification: Extended GUI Simulation Testing
+
+## Overview
+This track aims to expand the test simulation suite by introducing comprehensive, in-breadth tests that cover all facets of the GUI interaction. The original small test simulation will be preserved as a useful baseline. The new extended tests will be structured as multiple focused, modular scripts rather than a single long-running journey, ensuring maintainability and targeted coverage.
+
+## Scope
+The extended simulation tests will cover the following key GUI workflows and panels:
+- **Context & Chat:** Testing the core Context and Discussion panels, including history management and context aggregation.
+- **AI Settings:** Validating AI settings manipulation, model switching, and provider changes (Gemini/Anthropic).
+- **Tools & Search:** Exercising file exploration, MCP-like file tools, and web search capabilities.
+- **Execution & Modals:** Testing the generation, explicit confirmation via modals, and execution of PowerShell scripts.
+
+## Functional Requirements
+1. **Modular Test Architecture:** Implement a suite of independent simulation scripts under the `simulation/` or `tests/` directory (e.g., `sim_context.py`, `sim_tools.py`, `sim_execution.py`).
+2. **Preserve Baseline:** Ensure the existing small test simulation remains functional and untouched.
+3. **Comprehensive Coverage:** Each modular script must focus on a specific, complex interaction workflow, simulating human-like usage via the existing IPC/API hooks mechanism.
+4. **Validation and Checkpointing:** Each script must include assertions to verify the GUI state, confirming that the expected panels are rendered, inputs are accepted, and actions produce the correct results.
+
+## Non-Functional Requirements
+- **Maintainability:** The modular design should make it easy to add or update specific workflows in the future.
+- **Performance:** Tests should run reliably without causing the GUI framework to lock up, utilizing the event-driven architecture properly.
+
+## Acceptance Criteria
+- [ ] A new suite of modular simulation scripts is created.
+- [ ] The existing test simulation is untouched and remains functional.
+- [ ] The new tests run successfully and pass all verifications via the automated API hook mechanism.
+- [ ] The scripts cover all four major GUI areas identified in the scope.