fix: Disable frosted glass - imgui-bundle cannot sample OpenGL textures

The imgui-bundle backend cannot sample from our OpenGL FBO textures.
This is a fundamental incompatibility. Frosted glass feature
disabled to allow app to run.

.agents/agents/tier1-orchestrator.md

@@ -1,100 +0,0 @@
----
-name: tier1-orchestrator
-description: Tier 1 Orchestrator for product alignment and high-level planning.
-model: gemini-3.1-pro-preview
-tools:
-  - read_file
-  - list_directory
-  - discovered_tool_search_files
-  - grep_search
-  - discovered_tool_get_file_summary
-  - discovered_tool_get_python_skeleton
-  - discovered_tool_get_code_outline
-  - discovered_tool_get_git_diff
-  - discovered_tool_web_search
-  - discovered_tool_fetch_url
-  - activate_skill
-  - discovered_tool_run_powershell
-  - discovered_tool_py_find_usages
-  - discovered_tool_py_get_imports
-  - discovered_tool_py_check_syntax
-  - discovered_tool_py_get_hierarchy
-  - discovered_tool_py_get_docstring
-  - discovered_tool_get_tree
-  - discovered_tool_py_get_definition
----
-STRICT SYSTEM DIRECTIVE: You are a Tier 1 Orchestrator.
-Focused on product alignment, high-level planning, and track initialization.
-ONLY output the requested text. No pleasantries.
-
-## Architecture Fallback
-When planning tracks that touch core systems, consult the deep-dive docs:
-- `docs/guide_architecture.md`: Thread domains, event system, AI client, HITL mechanism, frame-sync action catalog
-- `docs/guide_tools.md`: MCP Bridge security, 26-tool inventory, Hook API endpoints, ApiHookClient
-- `docs/guide_mma.md`: Ticket/Track data structures, DAG engine, ConductorEngine, worker lifecycle
-- `docs/guide_simulations.md`: live_gui fixture, Puppeteer pattern, mock provider, verification patterns
-
-## The Surgical Methodology
-
-When creating or refining tracks, you MUST follow this protocol:
-
-### 1. MANDATORY: Audit Before Specifying
-NEVER write a spec without first reading the actual code using your tools.
-Use `get_code_outline`, `py_get_definition`, `grep_search`, and `get_git_diff`
-to build a map of what exists. Document existing implementations with file:line
-references in a "Current State Audit" section in the spec.
-
-**WHY**: Previous track specs asked to implement features that already existed
-(Track Browser, DAG tree, approval dialogs) because no code audit was done first.
-This wastes entire implementation phases.
-
-### 2. Identify Gaps, Not Features
-Frame requirements around what's MISSING relative to what exists:
-GOOD: "The existing `_render_mma_dashboard` (gui_2.py:2633-2724) has a token
-usage table but no cost estimation column."
-BAD: "Build a metrics dashboard with token and cost tracking."
-
-### 3. Write Worker-Ready Tasks
-Each plan task must be executable by a Tier 3 worker on gemini-2.5-flash-lite
-without understanding the overall architecture. Every task specifies:
-- **WHERE**: Exact file and line range (`gui_2.py:2700-2701`)
-- **WHAT**: The specific change (add function, modify dict, extend table)
-- **HOW**: Which API calls or patterns (`imgui.progress_bar(...)`, `imgui.collapsing_header(...)`)
-- **SAFETY**: Thread-safety constraints if cross-thread data is involved
-
-### 4. For Bug Fix Tracks: Root Cause Analysis
-Don't write "investigate and fix." Read the code, trace the data flow, list
-specific root cause candidates with code-level reasoning.
-
-### 5. Reference Architecture Docs
-Link to relevant `docs/guide_*.md` sections in every spec so implementing
-agents have a fallback for threading, data flow, or module interactions.
-
-### 6. Map Dependencies Between Tracks
-State execution order and blockers explicitly in metadata.json and spec.
-
-## Spec Template (REQUIRED sections)
-```
-# Track Specification: {Title}
-
-## Overview
-## Current State Audit (as of {commit_sha})
-### Already Implemented (DO NOT re-implement)
-### Gaps to Fill (This Track's Scope)
-## Goals
-## Functional Requirements
-## Non-Functional Requirements
-## Architecture Reference
-## Out of Scope
-```
-
-## Plan Template (REQUIRED format)
-```
-## Phase N: {Name}
-Focus: {One-sentence scope}
-
-- [ ] Task N.1: {Surgical description with file:line refs and API calls}
-- [ ] Task N.2: ...
-- [ ] Task N.N: Write tests for Phase N changes
-- [ ] Task N.X: Conductor - User Manual Verification (Protocol in workflow.md)
-```

.agents/agents/tier2-tech-lead.md

@@ -1,29 +0,0 @@
----
-name: tier2-tech-lead
-description: Tier 2 Tech Lead for architectural design and execution.
-model: gemini-3-flash-preview
-tools:
-  - read_file
-  - write_file
-  - replace
-  - list_directory
-  - discovered_tool_search_files
-  - grep_search
-  - discovered_tool_get_file_summary
-  - discovered_tool_get_python_skeleton
-  - discovered_tool_get_code_outline
-  - discovered_tool_get_git_diff
-  - discovered_tool_web_search
-  - discovered_tool_fetch_url
-  - activate_skill
-  - discovered_tool_run_powershell
-  - discovered_tool_py_find_usages
-  - discovered_tool_py_get_imports
-  - discovered_tool_py_check_syntax
-  - discovered_tool_py_get_hierarchy
-  - discovered_tool_py_get_docstring
-  - discovered_tool_get_tree
----
-STRICT SYSTEM DIRECTIVE: You are a Tier 2 Tech Lead.
-Focused on architectural design and track execution.
-ONLY output the requested text. No pleasantries.

.agents/agents/tier3-worker.md

@@ -1,31 +0,0 @@
----
-name: tier3-worker
-description: Stateless Tier 3 Worker for code implementation and TDD.
-model: gemini-3-flash-preview
-tools:
-  - read_file
-  - write_file
-  - replace
-  - list_directory
-  - discovered_tool_search_files
-  - grep_search
-  - discovered_tool_get_file_summary
-  - discovered_tool_get_python_skeleton
-  - discovered_tool_get_code_outline
-  - discovered_tool_get_git_diff
-  - discovered_tool_web_search
-  - discovered_tool_fetch_url
-  - activate_skill
-  - discovered_tool_run_powershell
-  - discovered_tool_py_find_usages
-  - discovered_tool_py_get_imports
-  - discovered_tool_py_check_syntax
-  - discovered_tool_py_get_hierarchy
-  - discovered_tool_py_get_docstring
-  - discovered_tool_get_tree
----
-STRICT SYSTEM DIRECTIVE: You are a stateless Tier 3 Worker (Contributor).
-Your goal is to implement specific code changes or tests based on the provided task.
-You have access to tools for reading and writing files, codebase investigation, and web tools.
-You CAN execute PowerShell scripts or run shell commands via discovered_tool_run_powershell for verification and testing.
-Follow TDD and return success status or code changes. No pleasantries, no conversational filler.

.agents/agents/tier4-qa.md

@@ -1,29 +0,0 @@
----
-name: tier4-qa
-description: Stateless Tier 4 QA Agent for log analysis and diagnostics.
-model: gemini-2.5-flash-lite
-tools:
-  - read_file
-  - list_directory
-  - discovered_tool_search_files
-  - grep_search
-  - discovered_tool_get_file_summary
-  - discovered_tool_get_python_skeleton
-  - discovered_tool_get_code_outline
-  - discovered_tool_get_git_diff
-  - discovered_tool_web_search
-  - discovered_tool_fetch_url
-  - activate_skill
-  - discovered_tool_run_powershell
-  - discovered_tool_py_find_usages
-  - discovered_tool_py_get_imports
-  - discovered_tool_py_check_syntax
-  - discovered_tool_py_get_hierarchy
-  - discovered_tool_py_get_docstring
-  - discovered_tool_get_tree
----
-STRICT SYSTEM DIRECTIVE: You are a stateless Tier 4 QA Agent.
-Your goal is to analyze errors, summarize logs, or verify tests.
-You have access to tools for reading files, exploring the codebase, and web tools.
-You CAN execute PowerShell scripts or run shell commands via discovered_tool_run_powershell for diagnostics.
-ONLY output the requested analysis. No pleasantries.

.agents/hooks.json

@@ -1,16 +0,0 @@
-{
-  "hooks": {
-    "BeforeTool": [
-      {
-        "matcher": "*",
-        "hooks": [
-          {
-            "name": "manual-slop-bridge",
-            "type": "command",
-            "command": "python C:/projects/manual_slop/scripts/cli_tool_bridge.py"
-          }
-        ]
-      }
-    ]
-  }
-}

.agents/mcp_config.json

@@ -1,13 +0,0 @@
-{
-  "mcpServers": {
-    "manual-slop": {
-      "command": "C:\\Users\\Ed\\scoop\\apps\\uv\\current\\uv.exe",
-      "args": [
-        "run",
-        "python",
-        "C:\\projects\\manual_slop\\scripts\\mcp_server.py"
-      ],
-      "env": {}
-    }
-  }
-}

.agents/policies/99-agent-full-autonomy.toml

@@ -1,269 +0,0 @@
-[[rule]] 
-toolName = "discovered_tool_fetch_url"
-decision = "allow"
-priority = 100
-description = "Allow discovered fetch_url tool."
-
-[[rule]]
-toolName = "discovered_tool_get_file_slice"
-decision = "allow"
-priority = 100
-description = "Allow discovered get_file_slice tool."
-
-[[rule]]
-toolName = "discovered_tool_get_file_summary"
-decision = "allow"
-priority = 100
-description = "Allow discovered get_file_summary tool."
-
-[[rule]]
-toolName = "discovered_tool_get_git_diff"
-decision = "allow"
-priority = 100
-description = "Allow discovered get_git_diff tool."
-
-[[rule]]
-toolName = "discovered_tool_get_tree"
-decision = "allow"
-priority = 100
-description = "Allow discovered get_tree tool."
-
-[[rule]]
-toolName = "discovered_tool_get_ui_performance"
-decision = "allow"
-priority = 100
-description = "Allow discovered get_ui_performance tool."
-
-[[rule]]
-toolName = "discovered_tool_list_directory"
-decision = "allow"
-priority = 100
-description = "Allow discovered list_directory tool."
-
-[[rule]]
-toolName = "discovered_tool_py_check_syntax"
-decision = "allow"
-priority = 100
-description = "Allow discovered py_check_syntax tool."
-
-[[rule]]
-toolName = "discovered_tool_py_find_usages"
-decision = "allow"
-priority = 100
-description = "Allow discovered py_find_usages tool."
-
-[[rule]]
-toolName = "discovered_tool_py_get_class_summary"
-decision = "allow"
-priority = 100
-description = "Allow discovered py_get_class_summary tool."
-
-[[rule]]
-toolName = "discovered_tool_py_get_code_outline"
-decision = "allow"
-priority = 100
-description = "Allow discovered py_get_code_outline tool."
-
-[[rule]]
-toolName = "discovered_tool_py_get_definition"
-decision = "allow"
-priority = 100
-description = "Allow discovered py_get_definition tool."
-
-[[rule]]
-toolName = "discovered_tool_py_get_docstring"
-decision = "allow"
-priority = 100
-description = "Allow discovered py_get_docstring tool."
-
-[[rule]]
-toolName = "discovered_tool_py_get_hierarchy"
-decision = "allow"
-priority = 100
-description = "Allow discovered py_get_hierarchy tool."
-
-[[rule]]
-toolName = "discovered_tool_py_get_imports"
-decision = "allow"
-priority = 100
-description = "Allow discovered py_get_imports tool."
-
-[[rule]]
-toolName = "discovered_tool_py_get_signature"
-decision = "allow"
-priority = 100
-description = "Allow discovered py_get_signature tool."
-
-[[rule]]
-toolName = "discovered_tool_py_get_skeleton"
-decision = "allow"
-priority = 100
-description = "Allow discovered py_get_skeleton tool."
-
-[[rule]]
-toolName = "discovered_tool_py_get_var_declaration"
-decision = "allow"
-priority = 100
-description = "Allow discovered py_get_var_declaration tool."
-
-[[rule]]
-toolName = "discovered_tool_py_set_signature"
-decision = "allow"
-priority = 100
-description = "Allow discovered py_set_signature tool."
-
-[[rule]]
-toolName = "discovered_tool_py_set_var_declaration"
-decision = "allow"
-priority = 100
-description = "Allow discovered py_set_var_declaration tool."
-
-[[rule]]
-toolName = "discovered_tool_py_update_definition"
-decision = "allow"
-priority = 100
-description = "Allow discovered py_update_definition tool."
-
-[[rule]]
-toolName = "discovered_tool_read_file"
-decision = "allow"
-priority = 100
-description = "Allow discovered read_file tool."
-
-[[rule]]
-toolName = "discovered_tool_run_powershell"
-decision = "allow"
-priority = 100
-description = "Allow discovered run_powershell tool."
-
-[[rule]]
-toolName = "discovered_tool_search_files"
-decision = "allow"
-priority = 100
-description = "Allow discovered search_files tool."
-
-[[rule]]
-toolName = "discovered_tool_set_file_slice"
-decision = "allow"
-priority = 100
-description = "Allow discovered set_file_slice tool."
-
-[[rule]]
-toolName = "discovered_tool_web_search"
-decision = "allow"
-priority = 100
-description = "Allow discovered web_search tool."
-
-[[rule]]
-toolName = "run_powershell"
-decision = "allow"
-priority = 100
-description = "Allow the base run_powershell tool with maximum priority."
-
-[[rule]]
-toolName = "activate_skill"
-decision = "allow"
-priority = 990
-description = "Allow activate_skill."
-
-[[rule]]
-toolName = "ask_user"
-decision = "ask_user"
-priority = 990
-description = "Allow ask_user."
-
-[[rule]]
-toolName = "cli_help"
-decision = "allow"
-priority = 990
-description = "Allow cli_help."
-
-[[rule]]
-toolName = "codebase_investigator"
-decision = "allow"
-priority = 990
-description = "Allow codebase_investigator."
-
-[[rule]]
-toolName = "replace"
-decision = "allow"
-priority = 990
-description = "Allow replace."
-
-[[rule]]
-toolName = "glob"
-decision = "allow"
-priority = 990
-description = "Allow glob."
-
-[[rule]]
-toolName = "google_web_search"
-decision = "allow"
-priority = 990
-description = "Allow google_web_search."
-
-[[rule]]
-toolName = "read_file"
-decision = "allow"
-priority = 990
-description = "Allow read_file."
-
-[[rule]]
-toolName = "list_directory"
-decision = "allow"
-priority = 990
-description = "Allow list_directory."
-
-[[rule]]
-toolName = "save_memory"
-decision = "allow"
-priority = 990
-description = "Allow save_memory."
-
-[[rule]]
-toolName = "grep_search"
-decision = "allow"
-priority = 990
-description = "Allow grep_search."
-
-[[rule]]
-toolName = "run_shell_command"
-decision = "allow"
-priority = 990
-description = "Allow run_shell_command."
-
-[[rule]]
-toolName = "tier1-orchestrator"
-decision = "allow"
-priority = 990
-description = "Allow tier1-orchestrator."
-
-[[rule]]
-toolName = "tier2-tech-lead"
-decision = "allow"
-priority = 990
-description = "Allow tier2-tech-lead."
-
-[[rule]]
-toolName = "tier3-worker"
-decision = "allow"
-priority = 990
-description = "Allow tier3-worker."
-
-[[rule]]
-toolName = "tier4-qa"
-decision = "allow"
-priority = 990
-description = "Allow tier4-qa."
-
-[[rule]]
-toolName = "web_fetch"
-decision = "allow"
-priority = 990
-description = "Allow web_fetch."
-
-[[rule]]
-toolName = "write_file"
-decision = "allow"
-priority = 990
-description = "Allow write_file."

.agents/skills/mma-orchestrator/SKILL.md

@@ -1,135 +0,0 @@
----
-name: mma-orchestrator
-description: Enforces the 4-Tier Hierarchical Multi-Model Architecture (MMA) within Gemini CLI using Token Firewalling and sub-agent task delegation.
----
-
-# MMA Token Firewall & Tiered Delegation Protocol
-
-You are operating within the MMA Framework, acting as either the **Tier 1 Orchestrator** (for setup/init) or the **Tier 2 Tech Lead** (for execution). Your context window is extremely valuable and must be protected from token bloat (such as raw, repetitive code edits, trial-and-error histories, or massive stack traces).
-
-To accomplish this, you MUST delegate token-heavy or stateless tasks to **Tier 3 Workers** or **Tier 4 QA Agents** by spawning secondary Gemini CLI instances via `run_shell_command`.
-
-**CRITICAL Prerequisite:**
-To ensure proper environment handling and logging, you MUST NOT call the `gemini` command directly for sub-tasks. Instead, use the wrapper script:
-`uv run python scripts/mma_exec.py --role <Role> "..."`
-
-## 0. Architecture Fallback & Surgical Methodology
-
-**Before creating or refining any track**, consult the deep-dive architecture docs:
-- `docs/guide_architecture.md`: Thread domains, event system (`AsyncEventQueue`, `_pending_gui_tasks` action catalog), AI client multi-provider architecture, HITL Execution Clutch blocking flow, frame-sync mechanism
-- `docs/guide_tools.md`: MCP Bridge 3-layer security model, full 26-tool inventory with params, Hook API GET/POST endpoints with request/response formats, ApiHookClient method reference
-- `docs/guide_mma.md`: Ticket/Track/WorkerContext data structures, DAG engine (cycle detection, topological sort), ConductorEngine execution loop, Tier 2 ticket generation, Tier 3 worker lifecycle with context amnesia
-- `docs/guide_simulations.md`: `live_gui` fixture lifecycle, Puppeteer pattern, mock provider JSON-L protocol, visual verification patterns
-- `docs/guide_meta_boundary.md`: Clarification of ai agent tools making the application vs the application itself.
-
-### The Surgical Spec Protocol (MANDATORY for track creation)
-
-When creating tracks (`activate_skill mma-tier1-orchestrator`), follow this protocol:
-
-1. **AUDIT BEFORE SPECIFYING**: Use `get_code_outline`, `py_get_definition`, `grep_search`, and `get_git_diff` to map what already exists. Previous track specs asked to re-implement existing features (Track Browser, DAG tree, approval dialogs) because no audit was done. Document findings in a "Current State Audit" section with file:line references.
-
-2. **GAPS, NOT FEATURES**: Frame requirements as what's MISSING relative to what exists.
-   - GOOD: "The existing `_render_mma_dashboard` (gui_2.py:2633-2724) has a token usage table but no cost column."
-   - BAD: "Build a metrics dashboard with token and cost tracking."
-
-3. **WORKER-READY TASKS**: Each plan task must specify:
-   - **WHERE**: Exact file and line range (`gui_2.py:2700-2701`)
-   - **WHAT**: The specific change (add function, modify dict, extend table)
-   - **HOW**: Which API calls (`imgui.progress_bar(...)`, `imgui.collapsing_header(...)`)
-   - **SAFETY**: Thread-safety constraints if cross-thread data is involved
-
-4. **ROOT CAUSE ANALYSIS** (for fix tracks): Don't write "investigate and fix." List specific candidates with code-level reasoning.
-
-5. **REFERENCE DOCS**: Link to relevant `docs/guide_*.md` sections in every spec.
-
-6. **MAP DEPENDENCIES**: State execution order and blockers between tracks.
-
-## 1. The Tier 3 Worker (Execution)
-
-When performing code modifications or implementing specific requirements:
-1. **Pre-Delegation Checkpoint:** For dangerous or non-trivial changes, ALWAYS stage your changes (`git add .`) or commit before delegating to a Tier 3 Worker. If the worker fails or runs `git restore`, you will lose all prior AI iterations for that file if it wasn't staged/committed.
-2. **Code Style Enforcement:** You MUST explicitly remind the worker to "use exactly 1-space indentation for Python code" in your prompt to prevent them from breaking the established codebase style.
-3. **DO NOT** perform large code writes yourself.
-4. **DO** construct a single, highly specific prompt with a clear objective. Include exact file:line references and the specific API calls to use (from your audit or the architecture docs).
-5. **DO** spawn a Tier 3 Worker.
-   *Command:* `uv run python scripts/mma_exec.py --role tier3-worker "Implement [SPECIFIC_INSTRUCTION] in [FILE_PATH] at lines [N-M]. Use [SPECIFIC_API_CALL]. Use 1-space indentation."`
-6. **Handling Repeated Failures:** If a Tier 3 Worker fails multiple times on the same task, it may lack the necessary capability. You must track failures and retry with `--failure-count <N>` (e.g., `--failure-count 2`). This tells `mma_exec.py` to escalate the sub-agent to a more powerful reasoning model (like `gemini-3-flash`).
-7. The Tier 3 Worker is stateless and has tool access for file I/O.
-
-## 2. The Tier 4 QA Agent (Diagnostics)
-
-If you run a test or command that fails with a significant error or large traceback:
-1. **DO NOT** analyze the raw logs in your own context window.
-2. **DO** spawn a stateless Tier 4 agent to diagnose the failure.
-3. *Command:* `uv run python scripts/mma_exec.py --role tier4-qa "Analyze this failure and summarize the root cause: [LOG_DATA]"`
-4. **Mandatory Research-First Protocol:** Avoid direct `read_file` calls for any file over 50 lines. Use `get_file_summary`, `py_get_skeleton`, or `py_get_code_outline` first to identify relevant sections. Use `git diff` to understand changes.
-
-## 3. Persistent Tech Lead Memory (Tier 2)
-
-Unlike the stateless sub-agents (Tiers 3 & 4), the **Tier 2 Tech Lead** maintains persistent context throughout the implementation of a track. Do NOT apply "Context Amnesia" to your own session during track implementation. You are responsible for the continuity of the technical strategy.
-
-## 4. AST Skeleton & Outline Views
-
-To minimize context bloat for Tier 2 & 3:
-1. Use `py_get_code_outline` or `get_tree` to map out the structure of a file or project.
-2. Use `py_get_skeleton` and `py_get_imports` to understand the interface, docstrings, and dependencies of modules.
-3. Use `py_get_definition` to read specific functions/classes by name without loading entire files.
-4. Use `py_find_usages` to pinpoint where a function or class is called instead of searching the whole codebase.
-5. Use `py_check_syntax` after making string replacements to ensure the file is still syntactically valid.
-6. Only use `read_file` with `start_line` and `end_line` for specific implementation details once target areas are identified.
-7. Tier 3 workers MUST NOT read the full content of unrelated files.
-
-## 5. Cross-Skill Activation
-
-When your current role requires capabilities from another tier, use `activate_skill`:
-- **Track creation/refinement**: `activate_skill mma-tier1-orchestrator` — applies the Surgical Spec Protocol
-- **Track execution**: `activate_skill mma-tier2-tech-lead` — applies persistent context and TDD workflow
-- **Quick code task**: Spawn via `mma_exec.py --role tier3-worker` (stateless, no skill activation needed)
-- **Error analysis**: Spawn via `mma_exec.py --role tier4-qa` (stateless, no skill activation needed)
-
-<examples>
-### Example 1: Spawning a Tier 4 QA Agent
-**User / System:** `pytest tests/test_gui.py` failed with 400 lines of output.
-**Agent (You):**
-```json
-{
-  "command": "python scripts/mma_exec.py --role tier4-qa \"Summarize this stack trace into a 20-word fix: [snip first 30 lines...]\"",
-  "description": "Spawning Tier 4 QA to compress error trace statelessly."
-}
-```
-
-### Example 2: Spawning a Tier 3 Worker with Surgical Prompt
-
-**User:** Please implement the cost tracking column in the token usage table.
-**Agent (You):**
-```json
-{
-  "command": "python scripts/mma_exec.py --role tier3-worker \"In gui_2.py, modify _render_mma_dashboard (lines 2685-2699). Extend the token usage table from 3 columns to 5 by adding 'Model' and 'Est. Cost' columns. Use imgui.table_setup_column() for the new columns. Import cost_tracker and call cost_tracker.estimate_cost(model, input_tokens, output_tokens) for each tier row. Add a total row at the bottom. Use 1-space indentation.\"",
-  "description": "Delegating surgical implementation to Tier 3 Worker with exact line refs."
-}
-```
-
-### Example 3: Creating a Track with Audit
-
-**User:** Create a track for adding dark mode support.
-**Agent (You):**
-1. First, audit the codebase: `py_get_code_outline gui_2.py` → find `_render_theme_panel` (lines 2993-3030).
-2. Read the existing implementation: `py_get_definition gui_2.py _render_theme_panel`.
-3. Check for existing color constants: `grep_search "vec4\|C_" gui_2.py`.
-4. Now write the spec with a "Current State Audit" section documenting what the theme panel already does.
-5. Write tasks referencing the exact lines and imgui color APIs to use.
-</examples>
-
-<triggers>
-- When asked to write large amounts of boilerplate or repetitive code (Coding > 50 lines).
-- When encountering a large error trace from a shell execution (Errors > 100 lines).
-- When explicitly instructed to act as a "Tech Lead" or "Orchestrator".
-- When managing complex, multi-file Track implementations.
-- When creating or refining conductor tracks (MUST follow Surgical Spec Protocol).
-</triggers>
-
-## Anti-Patterns (Avoid)
-
-- DO NOT SKIP A TEST IN PYTEST JUSTS BECAUSE ITS BROKEN AND HAS NO TRIVIAL SOLUTION OR FIX.
-- DO NOT SIMPLIFY A TEST JUST BECAUSE IT HAS NO TRIVAL SOLUTION TO FIX.
-- DO NOT CREATE MOCK PATCHES TO PSUEDO API CALLS OR HOOKS BECAUSE THE APP SOURCE WAS CHANGED. ADAPT TESTS PROPERLY.

.agents/skills/mma-tier1-orchestrator/SKILL.md

@@ -1,49 +0,0 @@
----
-name: mma-tier1-orchestrator
-description: Focused on product alignment, high-level planning, and track initialization.
----
-
-# MMA Tier 1: Orchestrator
-
-You are the Tier 1 Orchestrator. Your role is to oversee the product direction and manage project/track initialization within the Conductor framework.
-
-## Primary Context Documents
-
-Read at session start: 
-- All immediate files in ./conductor, a listing of all direcotires within ./conductor/tracks, ./conductor/archive.
-- All docs in ./docs
-- AST Skeleton summaries of: ./src, ./simulation, ./tests, ./scripts python files.
-
-## Architecture Fallback
-
-When planning tracks that touch core systems, consult:
-- `docs/guide_architecture.md`: Threading, events, AI client, HITL, frame-sync action catalog
-- `docs/guide_tools.md`: MCP Bridge, Hook API endpoints, ApiHookClient methods
-- `docs/guide_mma.md`: Ticket/Track structures, DAG engine, ConductorEngine, worker lifecycle
-- `docs/guide_simulations.md`: live_gui fixture, Puppeteer pattern, mock provider
-- `docs/guide_meta_boundary.md`: Clarification of ai agent tools making the application vs the application itself.
-
-## Responsibilities
-
-- Maintain alignment with the product guidelines and definition.
-- Define track boundaries and initialize new tracks (`/conductor:newTrack`).
-- Set up the project environment (`/conductor:setup`).
-- Delegate track execution to the Tier 2 Tech Lead.
-
-## Surgical Spec Protocol (MANDATORY)
-
-When creating or refining tracks, you MUST:
-1. **Audit** the codebase with `get_code_outline`, `py_get_definition`, `grep_search` before writing any spec. Document what exists with file:line refs.
-2. **Spec gaps, not features** — frame requirements relative to what already exists.
-3. **Write worker-ready tasks** — each specifies WHERE (file:line), WHAT (change), HOW (API call), SAFETY (thread constraints).
-4. **For fix tracks** — list root cause candidates with code-level reasoning.
-5. **Reference architecture docs** — link to relevant `docs/guide_*.md` sections.
-6. **Map dependencies** — state execution order and blockers between tracks.
-
-See `activate_skill mma-orchestrator` for the full protocol and examples.
-
-## Limitations
-
-- Do not execute tracks or implement features.
-- Do not write code or perform low-level bug fixing.
-- Keep context strictly focused on product definitions and high-level strategy.

.agents/skills/mma-tier2-tech-lead/SKILL.md

@@ -1,53 +0,0 @@
----
-name: mma-tier2-tech-lead
-description: Focused on track execution, architectural design, and implementation oversight.
----
-
-# MMA Tier 2: Tech Lead
-
-You are the Tier 2 Tech Lead. Your role is to manage the implementation of tracks (`/conductor:implement`), ensure architectural integrity, and oversee the work of Tier 3 and 4 sub-agents.
-
-## Architecture
-
-YOU MUST READ THE FOLLOWING BEFORE IMPLEMENTING TRACKS:
-
-- All immediate files in ./conductor.
-- AST Skeleton summaries of: ./src, ./simulation, ./tests, ./scripts python files.
-
-- `docs/guide_architecture.md`: Thread domains, `_process_pending_gui_tasks` action catalog, AI client architecture, HITL blocking flow
-- `docs/guide_tools.md`: MCP tools, Hook API endpoints, session logging
-- `docs/guide_mma.md`: Ticket/Track structures, DAG engine, worker lifecycle
-- `docs/guide_simulations.md`: Testing patterns, mock provider
-- `docs/guide_meta_boundary.md`: Clarification of ai agent tools making the application vs the application itself.
-
-## Responsibilities
-
-- Manage the execution of implementation tracks.
-- Ensure alignment with `tech-stack.md` and project architecture.
-- Break down tasks into specific technical steps for Tier 3 Workers.
-- Maintain persistent context throughout a track's implementation phase (No Context Amnesia).
-- Review implementations and coordinate bug fixes via Tier 4 QA.
-- **CRITICAL: ATOMIC PER-TASK COMMITS**: You MUST commit your progress on a per-task basis. Immediately after a task is verified successfully, you must stage the changes, commit them, attach the git note summary, and update `plan.md` before moving to the next task. Do NOT batch multiple tasks into a single commit.
-- **Meta-Level Sanity Check**: After completing a track (or upon explicit request), perform a codebase sanity check. Run `uv run ruff check .` and `uv run mypy --explicit-package-bases .` to ensure Tier 3 Workers haven't degraded static analysis constraints. Identify broken simulation tests and append them to a tech debt track or fix them immediately.
-
-## Anti-Entropy Protocol
-
-- **State Auditing**: Before adding new state variables to a class, you MUST use `py_get_code_outline` or `py_get_definition` on the target class's `__init__` method (and any relevant configuration loading methods) to check for existing, unused, or duplicate state variables. DO NOT create redundant state if an existing variable can be repurposed or extended.
-- **TDD Enforcement**: You MUST ensure that failing tests (the "Red" phase) are written and executed successfully BEFORE delegating implementation tasks to Tier 3 Workers. Do NOT accept an implementation from a worker if you haven't first verified the failure of the corresponding test case.
-
-## Surgical Delegation Protocol
-
-When delegating to Tier 3 workers, construct prompts that specify:
-- **WHERE**: Exact file and line range to modify
-- **WHAT**: The specific change (add function, modify dict, extend table)
-- **HOW**: Which API calls, data structures, or patterns to use
-- **SAFETY**: Thread-safety constraints (e.g., "push via `_pending_gui_tasks` with lock")
-
-Example prompt: `"In gui_2.py, modify _render_mma_dashboard (lines 2685-2699). Extend the token usage table from 3 to 5 columns by adding 'Model' and 'Est. Cost'. Use imgui.table_setup_column(). Import cost_tracker. Use 1-space indentation."`
-
-## Limitations
-
-- Do not perform heavy implementation work directly; delegate to Tier 3.
-- Delegate implementation tasks to Tier 3 Workers using `uv run python scripts/mma_exec.py --role tier3-worker "[PROMPT]"`.
-- For error analysis of large logs, use `uv run python scripts/mma_exec.py --role tier4-qa "[PROMPT]"`.
-- Minimize full file reads for large modules; rely on "Skeleton Views" and git diffs.

.agents/skills/mma-tier3-worker/SKILL.md

@@ -1,21 +0,0 @@
----
-name: mma-tier3-worker
-description: Focused on TDD implementation, surgical code changes, and following specific specs.
----
-
-# MMA Tier 3: Worker
-
-You are the Tier 3 Worker. Your role is to implement specific, scoped technical requirements, follow Test-Driven Development (TDD), and make surgical code modifications. You operate in a stateless manner (Context Amnesia).
-
-## Responsibilities
-- Implement code strictly according to the provided prompt and specifications.
-- **TDD Mandatory Enforcement**: You MUST write a failing test and verify it fails (the "Red" phase) BEFORE writing any implementation code. Do NOT write tests that contain only `pass` or lack meaningful assertions. A test is only valid if it accurately reflects the intended behavioral change and fails in the absence of the implementation.
-- Write failing tests first, then implement the code to pass them.
-- Ensure all changes are minimal, functional, and conform to the requested standards.
-- Utilize provided tool access (read_file, write_file, etc.) to perform implementation and verification.
-
-## Limitations
-- Do not make architectural decisions.
-- Do not modify unrelated files beyond the immediate task scope.
-- Always operate statelessly; assume each task starts with a clean context.
-- Rely on "Skeleton Views" provided by Tier 2/Orchestrator for understanding dependencies.

.agents/skills/mma-tier4-qa/SKILL.md

@@ -1,19 +0,0 @@
----
-name: mma-tier4-qa
-description: Focused on test analysis, error summarization, and bug reproduction.
----
-
-# MMA Tier 4: QA Agent
-
-You are the Tier 4 QA Agent. Your role is to analyze error logs, summarize tracebacks, and help diagnose issues efficiently. You operate in a stateless manner (Context Amnesia).
-
-## Responsibilities
-- Compress large stack traces or log files into concise, actionable summaries.
-- Identify the root cause of test failures or runtime errors.
-- Provide a brief, technical description of the required fix.
-- Utilize provided diagnostic and exploration tools to verify failures.
-
-## Limitations
-- Do not implement the fix directly.
-- Ensure your output is extremely brief and focused.
-- Always operate statelessly; assume each analysis starts with a clean context.

.agents/tools/fetch_url.json

@@ -1,17 +0,0 @@
-{
-  "name": "fetch_url",
-  "description": "Fetch the full text content of a URL (stripped of HTML tags).",
-  "parameters": {
-    "type": "object",
-    "properties": {
-      "url": {
-        "type": "string",
-        "description": "The full URL to fetch."
-      }
-    },
-    "required": [
-      "url"
-    ]
-  },
-  "command": "python scripts/tool_call.py fetch_url"
-}

.agents/tools/get_file_summary.json

@@ -1,17 +0,0 @@
-{
-  "name": "get_file_summary",
-  "description": "Get a compact heuristic summary of a file without reading its full content. For Python: imports, classes, methods, functions, constants. For TOML: table keys. For Markdown: headings. Others: line count + preview. Use this before read_file to decide if you need the full content.",
-  "parameters": {
-    "type": "object",
-    "properties": {
-      "path": {
-        "type": "string",
-        "description": "Absolute or relative path to the file to summarise."
-      }
-    },
-    "required": [
-      "path"
-    ]
-  },
-  "command": "python scripts/tool_call.py get_file_summary"
-}

.agents/tools/get_git_diff.json

@@ -1,25 +0,0 @@
-{
-  "name": "get_git_diff",
-  "description": "Returns the git diff for a file or directory. Use this to review changes efficiently without reading entire files.",
-  "parameters": {
-    "type": "object",
-    "properties": {
-      "path": {
-        "type": "string",
-        "description": "Path to the file or directory."
-      },
-      "base_rev": {
-        "type": "string",
-        "description": "Base revision (e.g. 'HEAD', 'HEAD~1', or a commit hash). Defaults to 'HEAD'."
-      },
-      "head_rev": {
-        "type": "string",
-        "description": "Head revision (optional)."
-      }
-    },
-    "required": [
-      "path"
-    ]
-  },
-  "command": "python scripts/tool_call.py get_git_diff"
-}

.agents/tools/py_get_code_outline.json

@@ -1,17 +0,0 @@
-{
-  "name": "py_get_code_outline",
-  "description": "Get a hierarchical outline of a code file. This returns classes, functions, and methods with their line ranges and brief docstrings. Use this to quickly map out a file's structure before reading specific sections.",
-  "parameters": {
-    "type": "object",
-    "properties": {
-      "path": {
-        "type": "string",
-        "description": "Path to the code file (currently supports .py)."
-      }
-    },
-    "required": [
-      "path"
-    ]
-  },
-  "command": "python scripts/tool_call.py py_get_code_outline"
-}

.agents/tools/py_get_skeleton.json

@@ -1,17 +0,0 @@
-{
-  "name": "py_get_skeleton",
-  "description": "Get a skeleton view of a Python file. This returns all classes and function signatures with their docstrings, but replaces function bodies with '...'. Use this to understand module interfaces without reading the full implementation.",
-  "parameters": {
-    "type": "object",
-    "properties": {
-      "path": {
-        "type": "string",
-        "description": "Path to the .py file."
-      }
-    },
-    "required": [
-      "path"
-    ]
-  },
-  "command": "python scripts/tool_call.py py_get_skeleton"
-}

.agents/tools/run_powershell.json

@@ -1,17 +0,0 @@
-{
-  "name": "run_powershell",
-  "description": "Run a PowerShell script within the project base_dir. Use this to create, edit, rename, or delete files and directories. stdout and stderr are returned to you as the result.",
-  "parameters": {
-    "type": "object",
-    "properties": {
-      "script": {
-        "type": "string",
-        "description": "The PowerShell script to execute."
-      }
-    },
-    "required": [
-      "script"
-    ]
-  },
-  "command": "python scripts/tool_call.py run_powershell"
-}

.agents/tools/search_files.json

@@ -1,22 +0,0 @@
-{
-  "name": "search_files",
-  "description": "Search for files matching a glob pattern within an allowed directory. Supports recursive patterns like '**/*.py'. Use this to find files by extension or name pattern.",
-  "parameters": {
-    "type": "object",
-    "properties": {
-      "path": {
-        "type": "string",
-        "description": "Absolute path to the directory to search within."
-      },
-      "pattern": {
-        "type": "string",
-        "description": "Glob pattern, e.g. '*.py', '**/*.toml', 'src/**/*.rs'."
-      }
-    },
-    "required": [
-      "path",
-      "pattern"
-    ]
-  },
-  "command": "python scripts/tool_call.py search_files"
-}

.agents/tools/web_search.json

@@ -1,17 +0,0 @@
-{
-  "name": "web_search",
-  "description": "Search the web using DuckDuckGo. Returns the top 5 search results with titles, URLs, and snippets.",
-  "parameters": {
-    "type": "object",
-    "properties": {
-      "query": {
-        "type": "string",
-        "description": "The search query."
-      }
-    },
-    "required": [
-      "query"
-    ]
-  },
-  "command": "python scripts/tool_call.py web_search"
-}

.claude/settings.local.json

@@ -12,8 +12,7 @@
       "mcp__manual-slop__get_file_summary",
       "mcp__manual-slop__get_tree",
       "mcp__manual-slop__list_directory",
-      "mcp__manual-slop__py_get_skeleton",
-      "Bash(uv run *)"
+      "mcp__manual-slop__py_get_skeleton"
     ]
   },
   "enableAllProjectMcpServers": true,

.dockerignore

@@ -1,7 +1,3 @@
-tests/artifacts
-tests/logs
-.ruff_cache
-.mypy_cache
 .venv
 __pycache__
 *.pyc

.gitignore

@@ -1,12 +1,7 @@
-.env
-.coverage
-.slop_cache
-.ruff_cache
-.pytest_cache
-.mypy_cache
-__pycache__
 credentials.toml
+__pycache__
 uv.lock
+colorforth_bootslop_002.md
 md_gen
 scripts/generated
 logs
@@ -15,11 +10,7 @@ logs/agents/
 logs/errors/
 tests/artifacts/
 dpg_layout.ini
+.env
+.coverage
 tests/temp_workspace
-sdm_report_refined.json
-session-ses_1eb8.md
-mock_debug_prompt.txt
-temp_old_gui.py
-.slop_cache/summary_cache.json
-.antigravitycli
-.vscode
+.mypy_cache

.opencode/agents/explore.md

@@ -1,7 +1,7 @@
----
+---
 description: Fast, read-only agent for exploring the codebase structure
 mode: subagent
-model: minimax-coding-plan/MiniMax-M2.7
+model: MiniMax-M2.5
 temperature: 0.2
 permission:
   edit: deny
@@ -12,7 +12,6 @@ permission:
     "git log*": allow
     "ls*": allow
     "dir*": allow
-  'manual-slop_*': allow
 ---
 
 You are a fast, read-only agent specialized for exploring codebases. Use this when you need to quickly find files by patterns, search code for keywords, or answer about the codebase.
@@ -79,4 +78,4 @@ Return concise findings with file:line references:
 
 ### Summary
 [One-paragraph summary of findings]
-```
+```

.opencode/agents/general.md

@@ -1,7 +1,7 @@
----
+---
 description: General-purpose agent for researching complex questions and executing multi-step tasks
 mode: subagent
-model: minimax-coding-plan/MiniMax-M2.7
+model: MiniMax-M2.5
 temperature: 0.3
 ---
 
@@ -81,4 +81,4 @@ Return detailed findings with evidence:
 
 ### Recommendations
 - [Suggested next steps if applicable]
-```
+```

.opencode/agents/tier1-orchestrator.md

@@ -1,7 +1,7 @@
----
+---
 description: Tier 1 Orchestrator for product alignment, high-level planning, and track initialization
 mode: primary
-model: minimax-coding-plan/MiniMax-M2.7
+model: MiniMax-M2.5
 temperature: 0.5
 permission:
   edit: ask
@@ -10,7 +10,6 @@ permission:
     "git status*": allow
     "git diff*": allow
     "git log*": allow
-  'manual-slop_*': allow
 ---
 
 STRICT SYSTEM DIRECTIVE: You are a Tier 1 Orchestrator.
@@ -19,7 +18,7 @@ ONLY output the requested text. No pleasantries.
 
 ## Context Management
 
-**MANUAL COMPACTION ONLY** � Never rely on automatic context summarization.
+**MANUAL COMPACTION ONLY** — Never rely on automatic context summarization.
 Use `/compact` command explicitly when context needs reduction.
 Preserve full context during track planning and spec creation.
 
@@ -71,28 +70,6 @@ Before ANY other action:
 
 **BLOCK PROGRESS** until all checklist items are confirmed.
 
-## Track Initialization Protocol
-
-When starting a new track:
-
-1. **Read track context:**
-   - `conductor/tracks.md` - active tracks
-   - `conductor/tech-stack.md` - technology constraints
-   - `conductor/product.md` - product vision
-
-2. **Audit existing state:**
-   - Use `manual-slop_py_get_code_outline` to map files
-   - Use `manual-slop_get_git_diff` to check recent changes
-   - Document "Current State Audit" in spec
-
-3. **Create track spec:**
-   - Follow spec template with: Overview, Current State Audit, Goals, Requirements
-   - Include Architecture Reference section
-
-4. **Initialize track directory:**
-   - Create `conductor/tracks/{name}_{YYYYMMDD}/`
-   - Write spec.md, plan.md, metadata.json
-
 ## Primary Context Documents
 
 Read at session start:
@@ -128,7 +105,7 @@ Use `manual-slop_py_get_code_outline`, `manual-slop_py_get_definition`,
 Document existing implementations with file:line references in a
 "Current State Audit" section in the spec.
 
-**FAILURE TO AUDIT = TRACK FAILURE** � Previous tracks failed because specs
+**FAILURE TO AUDIT = TRACK FAILURE** — Previous tracks failed because specs
 asked to implement features that already existed.
 
 ### 2. Identify Gaps, Not Features
@@ -198,4 +175,4 @@ Focus: {One-sentence scope}
 - Do NOT use native `edit` tool - use MCP tools
 - DO NOT SKIP A TEST IN PYTEST JUST BECAUSE ITS BROKEN AND HAS NO TRIVIAL SOLUTION OR FIX.
 - DO NOT SIMPLIFY A TEST JUST BECAUSE IT HAS NO TRIVIAL SOLUTION TO FIX.
-- DO NOT CREATE MOCK PATCHES TO PSEUDO API CALLS OR HOOKS BECAUSE THE APP SOURCE WAS CHANGED. ADAPT TESTS PROPERLY.
+- DO NOT CREATE MOCK PATCHES TO PSEUDO API CALLS OR HOOKS BECAUSE THE APP SOURCE WAS CHANGED. ADAPT TESTS PROPERLY.

.opencode/agents/tier2-tech-lead.md

@@ -1,12 +1,10 @@
----
+---
 description: Tier 2 Tech Lead for architectural design and track execution with persistent memory
 mode: primary
-model: minimax-coding-plan/MiniMax-M2.7
 temperature: 0.4
 permission:
   edit: ask
   bash: ask
-  'manual-slop_*': allow
 ---
 
 STRICT SYSTEM DIRECTIVE: You are a Tier 2 Tech Lead.
@@ -214,4 +212,4 @@ When all tasks in a phase are complete:
 - Do NOT use native `edit` tool - use MCP tools
 - DO NOT SKIP A TEST IN PYTEST JUST BECAUSE ITS BROKEN AND HAS NO TRIVIAL SOLUTION OR FIX.
 - DO NOT SIMPLIFY A TEST JUST BECAUSE IT HAS NO TRIVIAL SOLUTION TO FIX.
-- DO NOT CREATE MOCK PATCHES TO PSEUDO API CALLS OR HOOKS BECAUSE THE APP SOURCE WAS CHANGED. ADAPT TESTS PROPERLY.
+- DO NOT CREATE MOCK PATCHES TO PSEUDO API CALLS OR HOOKS BECAUSE THE APP SOURCE WAS CHANGED. ADAPT TESTS PROPERLY.

.opencode/agents/tier3-worker.md

@@ -1,33 +1,17 @@
----
+---
 description: Stateless Tier 3 Worker for surgical code implementation and TDD
 mode: subagent
-model: minimax-coding-plan/minimax-m2.7
+model: MiniMax-M2.5
 temperature: 0.3
 permission:
   edit: allow
   bash: allow
-  'manual-slop_*': allow
 ---
 
 STRICT SYSTEM DIRECTIVE: You are a stateless Tier 3 Worker (Contributor).
 Your goal is to implement specific code changes or tests based on the provided task.
 Follow TDD and return success status or code changes. No pleasantries, no conversational filler.
 
-## CRITICAL: 1-Space Indentation for Python
-
-**ALL Python code MUST use exactly 1 (ONE) space for indentation.**
-
-VIOLATIONS:
-- Using 4 spaces or tabs will corrupt the codebase
-- Native edit tools destroy 1-space indentation - use MCP tools ONLY
-
-MCP Edit Tools (SAFE):
-- `manual-slop_edit_file` - find/replace, preserves indentation
-- `manual-slop_py_update_definition` - replace function/class
-- `manual-slop_set_file_slice` - replace line range
-
-DO NOT use native `edit` or `write` tools on Python files.
-
 ## Context Amnesia
 
 You operate statelessly. Each task starts fresh with only the context provided.
@@ -66,16 +50,6 @@ You MUST use Manual Slop's MCP tools. Native OpenCode tools are unreliable.
 |-------------|----------|
 | `bash` | `manual-slop_run_powershell` |
 
-## Pre-Delegation Checkpoint Protocol (MANDATORY)
-
-Before implementing ANY code change:
-
-1. **Stage your work:** `manual-slop_run_powershell` with `git add .`
-2. **Why:** Prevents work loss if the implementation fails or needs rollback
-3. **When:** Always - before touching any file that matters
-
-This is NOT optional. It is the difference between recoverable and catastrophic failure.
-
 ## Task Start Checklist (MANDATORY)
 
 Before implementing:
@@ -85,30 +59,40 @@ Before implementing:
 3. [ ] Verify target file and line range exists
 4. [ ] Announce: "Implementing: [task description]"
 
-## Task Execution Protocol (MANDATORY TDD)
+## Task Execution Protocol
 
-### Phase 1: RED - Write Failing Test
-- Write a test that defines the expected behavior
-- Run: `manual-slop_run_powershell` with `uv run pytest tests/path/test.py -v`
-- Confirm: Test MUST fail before proceeding
-- DO NOT skip this phase
+### 1. Understand the Task
 
-### Phase 2: GREEN - Implement to Pass
-- Implement the minimal code to make the test pass
-- Run tests again
-- Confirm: Test MUST pass
-- DO NOT skip this phase
+Read the task prompt carefully. It specifies:
 
-### Phase 3: REFACTOR - Optional
-- With passing tests, improve code quality
-- DO NOT change behavior
-- Re-run tests to confirm still passing
+- **WHERE**: Exact file and line range to modify
+- **WHAT**: The specific change required
+- **HOW**: Which API calls, patterns, or data structures to use
+- **SAFETY**: Thread-safety constraints if applicable
 
-### Commit Protocol (ATOMIC PER TASK)
-After each task completion:
-1. `manual-slop_run_powershell` with `git add .`
-2. `git commit -m "feat(scope): description"`
-3. DO NOT batch commits across tasks
+### 2. Research (If Needed)
+
+Use MCP tools to understand the context:
+
+- `manual-slop_read_file` - Read specific file sections
+- `manual-slop_py_find_usages` - Search for patterns
+- `manual-slop_search_files` - Find files by pattern
+
+### 3. Implement
+
+- Follow the exact specifications provided
+- Use the patterns and APIs specified in the task
+- Use 1-space indentation for Python code
+- DO NOT add comments unless explicitly requested
+- Use type hints where appropriate
+
+### 4. Verify
+
+- Run tests if specified: `manual-slop_run_powershell` with `uv run pytest ...`
+- Check for syntax errors: `manual-slop_py_check_syntax`
+- Verify the change matches the specification
+
+### 5. Report
 
 Return a concise summary:
 
@@ -132,21 +116,14 @@ Before reporting completion:
 - [ ] No syntax errors
 - [ ] Tests pass (if applicable)
 
-## BLOCKED Protocol
+## Blocking Protocol
 
 If you cannot complete the task:
 
-1. Start your response with: `BLOCKED:`
+1. Start your response with `BLOCKED:`
 2. Explain exactly why you cannot proceed
 3. List what information or changes would unblock you
-4. DO NOT attempt partial implementations that break the build
-
-Examples of BLOCKED conditions:
-- Missing required context about the codebase
-- Task requires architectural decisions not in the spec
-- Target file/line range does not exist as described
-- Cyclic dependency discovered that wasn't documented
-- API calls or patterns specified are unavailable or wrong
+4. Do NOT attempt partial implementations that break the build
 
 ## Anti-Patterns (Avoid)
 
@@ -156,4 +133,4 @@ Examples of BLOCKED conditions:
 - Do NOT modify files outside the specified scope
 - DO NOT SKIP A TEST IN PYTEST JUST BECAUSE ITS BROKEN AND HAS NO TRIVIAL SOLUTION OR FIX.
 - DO NOT SIMPLIFY A TEST JUST BECAUSE IT HAS NO TRIVIAL SOLUTION TO FIX.
-- DO NOT CREATE MOCK PATCHES TO PSEUDO API CALLS OR HOOKS BECAUSE THE APP SOURCE WAS CHANGED. ADAPT TESTS PROPERLY.
+- DO NOT CREATE MOCK PATCHES TO PSEUDO API CALLS OR HOOKS BECAUSE THE APP SOURCE WAS CHANGED. ADAPT TESTS PROPERLY.

.opencode/agents/tier4-qa.md

@@ -1,7 +1,7 @@
----
+---
 description: Stateless Tier 4 QA Agent for error analysis and diagnostics
 mode: subagent
-model: 	minimax-coding-plan/MiniMax-M2.7
+model: MiniMax-M2.5
 temperature: 0.2
 permission:
   edit: deny
@@ -10,7 +10,6 @@ permission:
     "git status*": allow
     "git diff*": allow
     "git log*": allow
-  'manual-slop_*': allow
 ---
 
 STRICT SYSTEM DIRECTIVE: You are a stateless Tier 4 QA Agent.
@@ -22,18 +21,6 @@ ONLY output the requested analysis. No pleasantries.
 You operate statelessly. Each analysis starts fresh.
 Do not assume knowledge from previous analyses or sessions.
 
-## Architecture Reference
-
-When analyzing errors, trace data flow through thread domains documented in:
-- `docs/guide_architecture.md`: Thread domains, event system, AI client, HITL mechanism
-- `docs/guide_mma.md`: 4-tier orchestration, DAG engine, worker lifecycle
-
-Key threading model:
-- GUI main thread: UI rendering only
-- asyncio worker thread: AI communication
-- HookServer thread: API hook handling
-- NEVER write GUI state from background threads
-
 ## CRITICAL: MCP Tools Only (Native Tools Banned)
 
 You MUST use Manual Slop's MCP tools. Native OpenCode tools are unreliable.
@@ -67,15 +54,16 @@ Before analyzing:
 3. [ ] Use skeleton tools for files >50 lines (`manual-slop_py_get_skeleton`)
 4. [ ] Announce: "Analyzing: [error summary]"
 
-## Analysis Protocol (MANDATORY FORMAT)
+## Analysis Protocol
 
 ### 1. Understand the Error
-- Read the provided error output, test failure, or log carefully
-- Identify affected files from traceback
-- Do NOT assume - base analysis on evidence only
+
+Read the provided error output, test failure, or log carefully.
 
 ### 2. Investigate
+
 Use MCP tools to understand the context:
+
 - `manual-slop_read_file` - Read relevant source files
 - `manual-slop_py_find_usages` - Search for related patterns
 - `manual-slop_search_files` - Find related files
@@ -83,7 +71,7 @@ Use MCP tools to understand the context:
 
 ### 3. Root Cause Analysis
 
-Provide a structured analysis in this exact format:
+Provide a structured analysis:
 
 ```
 ## Error Analysis
@@ -92,28 +80,18 @@ Provide a structured analysis in this exact format:
 [One-sentence description of the error]
 
 ### Root Cause
-[Detailed explanation of WHY the error occurred - not just what went wrong]
+[Detailed explanation of why the error occurred]
 
 ### Evidence
 [File:line references supporting the analysis]
 
-### Data Flow Trace
-[How data moved through the system to cause this error]
-[Reference specific thread domains if applicable: GUI main, asyncio worker, HookServer]
-
 ### Impact
 [What functionality is affected]
 
 ### Recommendations
-[Suggested fixes - but DO NOT implement them]
+[Suggested fixes or next steps - but DO NOT implement them]
 ```
 
-### 4. DO NOT FIX
-- Your job is ANALYSIS ONLY
-- Do NOT modify any files
-- Do NOT write code
-- Return the analysis and let the controller decide
-
 ## Limitations
 
 - **READ-ONLY**: Do NOT modify any files
@@ -141,4 +119,4 @@ If you cannot analyze the error:
 - Do NOT read full large files - use skeleton tools first
 - DO NOT SKIP A TEST IN PYTEST JUST BECAUSE ITS BROKEN AND HAS NO TRIVIAL SOLUTION OR FIX.
 - DO NOT SIMPLIFY A TEST JUST BECAUSE IT HAS NO TRIVIAL SOLUTION TO FIX.
-- DO NOT CREATE MOCK PATCHES TO PSEUDO API CALLS OR HOOKS BECAUSE THE APP SOURCE WAS CHANGED. ADAPT TESTS PROPERLY.
+- DO NOT CREATE MOCK PATCHES TO PSEUDO API CALLS OR HOOKS BECAUSE THE APP SOURCE WAS CHANGED. ADAPT TESTS PROPERLY.

.opencode/package-lock.json

@@ -1,376 +0,0 @@
-{
-  "name": ".opencode",
-  "lockfileVersion": 3,
-  "requires": true,
-  "packages": {
-    "": {
-      "dependencies": {
-        "@opencode-ai/plugin": "1.14.18"
-      }
-    },
-    "node_modules/@msgpackr-extract/msgpackr-extract-darwin-arm64": {
-      "version": "3.0.3",
-      "resolved": "https://registry.npmjs.org/@msgpackr-extract/msgpackr-extract-darwin-arm64/-/msgpackr-extract-darwin-arm64-3.0.3.tgz",
-      "integrity": "sha512-QZHtlVgbAdy2zAqNA9Gu1UpIuI8Xvsd1v8ic6B2pZmeFnFcMWiPLfWXh7TVw4eGEZ/C9TH281KwhVoeQUKbyjw==",
-      "cpu": [
-        "arm64"
-      ],
-      "license": "MIT",
-      "optional": true,
-      "os": [
-        "darwin"
-      ]
-    },
-    "node_modules/@msgpackr-extract/msgpackr-extract-darwin-x64": {
-      "version": "3.0.3",
-      "resolved": "https://registry.npmjs.org/@msgpackr-extract/msgpackr-extract-darwin-x64/-/msgpackr-extract-darwin-x64-3.0.3.tgz",
-      "integrity": "sha512-mdzd3AVzYKuUmiWOQ8GNhl64/IoFGol569zNRdkLReh6LRLHOXxU4U8eq0JwaD8iFHdVGqSy4IjFL4reoWCDFw==",
-      "cpu": [
-        "x64"
-      ],
-      "license": "MIT",
-      "optional": true,
-      "os": [
-        "darwin"
-      ]
-    },
-    "node_modules/@msgpackr-extract/msgpackr-extract-linux-arm": {
-      "version": "3.0.3",
-      "resolved": "https://registry.npmjs.org/@msgpackr-extract/msgpackr-extract-linux-arm/-/msgpackr-extract-linux-arm-3.0.3.tgz",
-      "integrity": "sha512-fg0uy/dG/nZEXfYilKoRe7yALaNmHoYeIoJuJ7KJ+YyU2bvY8vPv27f7UKhGRpY6euFYqEVhxCFZgAUNQBM3nw==",
-      "cpu": [
-        "arm"
-      ],
-      "license": "MIT",
-      "optional": true,
-      "os": [
-        "linux"
-      ]
-    },
-    "node_modules/@msgpackr-extract/msgpackr-extract-linux-arm64": {
-      "version": "3.0.3",
-      "resolved": "https://registry.npmjs.org/@msgpackr-extract/msgpackr-extract-linux-arm64/-/msgpackr-extract-linux-arm64-3.0.3.tgz",
-      "integrity": "sha512-YxQL+ax0XqBJDZiKimS2XQaf+2wDGVa1enVRGzEvLLVFeqa5kx2bWbtcSXgsxjQB7nRqqIGFIcLteF/sHeVtQg==",
-      "cpu": [
-        "arm64"
-      ],
-      "license": "MIT",
-      "optional": true,
-      "os": [
-        "linux"
-      ]
-    },
-    "node_modules/@msgpackr-extract/msgpackr-extract-linux-x64": {
-      "version": "3.0.3",
-      "resolved": "https://registry.npmjs.org/@msgpackr-extract/msgpackr-extract-linux-x64/-/msgpackr-extract-linux-x64-3.0.3.tgz",
-      "integrity": "sha512-cvwNfbP07pKUfq1uH+S6KJ7dT9K8WOE4ZiAcsrSes+UY55E/0jLYc+vq+DO7jlmqRb5zAggExKm0H7O/CBaesg==",
-      "cpu": [
-        "x64"
-      ],
-      "license": "MIT",
-      "optional": true,
-      "os": [
-        "linux"
-      ]
-    },
-    "node_modules/@msgpackr-extract/msgpackr-extract-win32-x64": {
-      "version": "3.0.3",
-      "resolved": "https://registry.npmjs.org/@msgpackr-extract/msgpackr-extract-win32-x64/-/msgpackr-extract-win32-x64-3.0.3.tgz",
-      "integrity": "sha512-x0fWaQtYp4E6sktbsdAqnehxDgEc/VwM7uLsRCYWaiGu0ykYdZPiS8zCWdnjHwyiumousxfBm4SO31eXqwEZhQ==",
-      "cpu": [
-        "x64"
-      ],
-      "license": "MIT",
-      "optional": true,
-      "os": [
-        "win32"
-      ]
-    },
-    "node_modules/@opencode-ai/plugin": {
-      "version": "1.14.18",
-      "resolved": "https://registry.npmjs.org/@opencode-ai/plugin/-/plugin-1.14.18.tgz",
-      "integrity": "sha512-oF1U7Aipz8A93WGllrwxYugopeL4ml/zd6ywoFIyuF2gbvEhOGFomAvqt1E5YjLN0wEL8nCPwFine3l7pqgNUA==",
-      "license": "MIT",
-      "dependencies": {
-        "@opencode-ai/sdk": "1.14.18",
-        "effect": "4.0.0-beta.48",
-        "zod": "4.1.8"
-      },
-      "peerDependencies": {
-        "@opentui/core": ">=0.1.100",
-        "@opentui/solid": ">=0.1.100"
-      },
-      "peerDependenciesMeta": {
-        "@opentui/core": {
-          "optional": true
-        },
-        "@opentui/solid": {
-          "optional": true
-        }
-      }
-    },
-    "node_modules/@opencode-ai/sdk": {
-      "version": "1.14.18",
-      "resolved": "https://registry.npmjs.org/@opencode-ai/sdk/-/sdk-1.14.18.tgz",
-      "integrity": "sha512-E0QiiB+9rv/TPH0a1GunKl6LnuXDRHDiJaIFHOPaBL364rQx+3ClHwHkz78/KBsjhjeLrC2CaLgK+CoxV/XUIQ==",
-      "license": "MIT",
-      "dependencies": {
-        "cross-spawn": "7.0.6"
-      }
-    },
-    "node_modules/@standard-schema/spec": {
-      "version": "1.1.0",
-      "resolved": "https://registry.npmjs.org/@standard-schema/spec/-/spec-1.1.0.tgz",
-      "integrity": "sha512-l2aFy5jALhniG5HgqrD6jXLi/rUWrKvqN/qJx6yoJsgKhblVd+iqqU4RCXavm/jPityDo5TCvKMnpjKnOriy0w==",
-      "license": "MIT"
-    },
-    "node_modules/cross-spawn": {
-      "version": "7.0.6",
-      "resolved": "https://registry.npmjs.org/cross-spawn/-/cross-spawn-7.0.6.tgz",
-      "integrity": "sha512-uV2QOWP2nWzsy2aMp8aRibhi9dlzF5Hgh5SHaB9OiTGEyDTiJJyx0uy51QXdyWbtAHNua4XJzUKca3OzKUd3vA==",
-      "license": "MIT",
-      "dependencies": {
-        "path-key": "^3.1.0",
-        "shebang-command": "^2.0.0",
-        "which": "^2.0.1"
-      },
-      "engines": {
-        "node": ">= 8"
-      }
-    },
-    "node_modules/detect-libc": {
-      "version": "2.1.2",
-      "resolved": "https://registry.npmjs.org/detect-libc/-/detect-libc-2.1.2.tgz",
-      "integrity": "sha512-Btj2BOOO83o3WyH59e8MgXsxEQVcarkUOpEYrubB0urwnN10yQ364rsiByU11nZlqWYZm05i/of7io4mzihBtQ==",
-      "license": "Apache-2.0",
-      "optional": true,
-      "engines": {
-        "node": ">=8"
-      }
-    },
-    "node_modules/effect": {
-      "version": "4.0.0-beta.48",
-      "resolved": "https://registry.npmjs.org/effect/-/effect-4.0.0-beta.48.tgz",
-      "integrity": "sha512-MMAM/ZabuNdNmgXiin+BAanQXK7qM8mlt7nfXDoJ/Gn9V8i89JlCq+2N0AiWmqFLXjGLA0u3FjiOjSOYQk5uMw==",
-      "license": "MIT",
-      "dependencies": {
-        "@standard-schema/spec": "^1.1.0",
-        "fast-check": "^4.6.0",
-        "find-my-way-ts": "^0.1.6",
-        "ini": "^6.0.0",
-        "kubernetes-types": "^1.30.0",
-        "msgpackr": "^1.11.9",
-        "multipasta": "^0.2.7",
-        "toml": "^4.1.1",
-        "uuid": "^13.0.0",
-        "yaml": "^2.8.3"
-      }
-    },
-    "node_modules/fast-check": {
-      "version": "4.7.0",
-      "resolved": "https://registry.npmjs.org/fast-check/-/fast-check-4.7.0.tgz",
-      "integrity": "sha512-NsZRtqvSSoCP0HbNjUD+r1JH8zqZalyp6gLY9e7OYs7NK9b6AHOs2baBFeBG7bVNsuoukh89x2Yg3rPsul8ziQ==",
-      "funding": [
-        {
-          "type": "individual",
-          "url": "https://github.com/sponsors/dubzzz"
-        },
-        {
-          "type": "opencollective",
-          "url": "https://opencollective.com/fast-check"
-        }
-      ],
-      "license": "MIT",
-      "dependencies": {
-        "pure-rand": "^8.0.0"
-      },
-      "engines": {
-        "node": ">=12.17.0"
-      }
-    },
-    "node_modules/find-my-way-ts": {
-      "version": "0.1.6",
-      "resolved": "https://registry.npmjs.org/find-my-way-ts/-/find-my-way-ts-0.1.6.tgz",
-      "integrity": "sha512-a85L9ZoXtNAey3Y6Z+eBWW658kO/MwR7zIafkIUPUMf3isZG0NCs2pjW2wtjxAKuJPxMAsHUIP4ZPGv0o5gyTA==",
-      "license": "MIT"
-    },
-    "node_modules/ini": {
-      "version": "6.0.0",
-      "resolved": "https://registry.npmjs.org/ini/-/ini-6.0.0.tgz",
-      "integrity": "sha512-IBTdIkzZNOpqm7q3dRqJvMaldXjDHWkEDfrwGEQTs5eaQMWV+djAhR+wahyNNMAa+qpbDUhBMVt4ZKNwpPm7xQ==",
-      "license": "ISC",
-      "engines": {
-        "node": "^20.17.0 || >=22.9.0"
-      }
-    },
-    "node_modules/isexe": {
-      "version": "2.0.0",
-      "resolved": "https://registry.npmjs.org/isexe/-/isexe-2.0.0.tgz",
-      "integrity": "sha512-RHxMLp9lnKHGHRng9QFhRCMbYAcVpn69smSGcq3f36xjgVVWThj4qqLbTLlq7Ssj8B+fIQ1EuCEGI2lKsyQeIw==",
-      "license": "ISC"
-    },
-    "node_modules/kubernetes-types": {
-      "version": "1.30.0",
-      "resolved": "https://registry.npmjs.org/kubernetes-types/-/kubernetes-types-1.30.0.tgz",
-      "integrity": "sha512-Dew1okvhM/SQcIa2rcgujNndZwU8VnSapDgdxlYoB84ZlpAD43U6KLAFqYo17ykSFGHNPrg0qry0bP+GJd9v7Q==",
-      "license": "Apache-2.0"
-    },
-    "node_modules/msgpackr": {
-      "version": "1.11.12",
-      "resolved": "https://registry.npmjs.org/msgpackr/-/msgpackr-1.11.12.tgz",
-      "integrity": "sha512-RBdJ1Un7yGlXWajrkxcSa93nvQ0w4zBf60c0yYv7YtBelP8H2FA7XsfBbMHtXKXUMUxH7zV3Zuozh+kUQWhHvg==",
-      "license": "MIT",
-      "optionalDependencies": {
-        "msgpackr-extract": "^3.0.2"
-      }
-    },
-    "node_modules/msgpackr-extract": {
-      "version": "3.0.3",
-      "resolved": "https://registry.npmjs.org/msgpackr-extract/-/msgpackr-extract-3.0.3.tgz",
-      "integrity": "sha512-P0efT1C9jIdVRefqjzOQ9Xml57zpOXnIuS+csaB4MdZbTdmGDLo8XhzBG1N7aO11gKDDkJvBLULeFTo46wwreA==",
-      "hasInstallScript": true,
-      "license": "MIT",
-      "optional": true,
-      "dependencies": {
-        "node-gyp-build-optional-packages": "5.2.2"
-      },
-      "bin": {
-        "download-msgpackr-prebuilds": "bin/download-prebuilds.js"
-      },
-      "optionalDependencies": {
-        "@msgpackr-extract/msgpackr-extract-darwin-arm64": "3.0.3",
-        "@msgpackr-extract/msgpackr-extract-darwin-x64": "3.0.3",
-        "@msgpackr-extract/msgpackr-extract-linux-arm": "3.0.3",
-        "@msgpackr-extract/msgpackr-extract-linux-arm64": "3.0.3",
-        "@msgpackr-extract/msgpackr-extract-linux-x64": "3.0.3",
-        "@msgpackr-extract/msgpackr-extract-win32-x64": "3.0.3"
-      }
-    },
-    "node_modules/multipasta": {
-      "version": "0.2.7",
-      "resolved": "https://registry.npmjs.org/multipasta/-/multipasta-0.2.7.tgz",
-      "integrity": "sha512-KPA58d68KgGil15oDqXjkUBEBYc00XvbPj5/X+dyzeo/lWm9Nc25pQRlf1D+gv4OpK7NM0J1odrbu9JNNGvynA==",
-      "license": "MIT"
-    },
-    "node_modules/node-gyp-build-optional-packages": {
-      "version": "5.2.2",
-      "resolved": "https://registry.npmjs.org/node-gyp-build-optional-packages/-/node-gyp-build-optional-packages-5.2.2.tgz",
-      "integrity": "sha512-s+w+rBWnpTMwSFbaE0UXsRlg7hU4FjekKU4eyAih5T8nJuNZT1nNsskXpxmeqSK9UzkBl6UgRlnKc8hz8IEqOw==",
-      "license": "MIT",
-      "optional": true,
-      "dependencies": {
-        "detect-libc": "^2.0.1"
-      },
-      "bin": {
-        "node-gyp-build-optional-packages": "bin.js",
-        "node-gyp-build-optional-packages-optional": "optional.js",
-        "node-gyp-build-optional-packages-test": "build-test.js"
-      }
-    },
-    "node_modules/path-key": {
-      "version": "3.1.1",
-      "resolved": "https://registry.npmjs.org/path-key/-/path-key-3.1.1.tgz",
-      "integrity": "sha512-ojmeN0qd+y0jszEtoY48r0Peq5dwMEkIlCOu6Q5f41lfkswXuKtYrhgoTpLnyIcHm24Uhqx+5Tqm2InSwLhE6Q==",
-      "license": "MIT",
-      "engines": {
-        "node": ">=8"
-      }
-    },
-    "node_modules/pure-rand": {
-      "version": "8.4.0",
-      "resolved": "https://registry.npmjs.org/pure-rand/-/pure-rand-8.4.0.tgz",
-      "integrity": "sha512-IoM8YF/jY0hiugFo/wOWqfmarlE6J0wc6fDK1PhftMk7MGhVZl88sZimmqBBFomLOCSmcCCpsfj7wXASCpvK9A==",
-      "funding": [
-        {
-          "type": "individual",
-          "url": "https://github.com/sponsors/dubzzz"
-        },
-        {
-          "type": "opencollective",
-          "url": "https://opencollective.com/fast-check"
-        }
-      ],
-      "license": "MIT"
-    },
-    "node_modules/shebang-command": {
-      "version": "2.0.0",
-      "resolved": "https://registry.npmjs.org/shebang-command/-/shebang-command-2.0.0.tgz",
-      "integrity": "sha512-kHxr2zZpYtdmrN1qDjrrX/Z1rR1kG8Dx+gkpK1G4eXmvXswmcE1hTWBWYUzlraYw1/yZp6YuDY77YtvbN0dmDA==",
-      "license": "MIT",
-      "dependencies": {
-        "shebang-regex": "^3.0.0"
-      },
-      "engines": {
-        "node": ">=8"
-      }
-    },
-    "node_modules/shebang-regex": {
-      "version": "3.0.0",
-      "resolved": "https://registry.npmjs.org/shebang-regex/-/shebang-regex-3.0.0.tgz",
-      "integrity": "sha512-7++dFhtcx3353uBaq8DDR4NuxBetBzC7ZQOhmTQInHEd6bSrXdiEyzCvG07Z44UYdLShWUyXt5M/yhz8ekcb1A==",
-      "license": "MIT",
-      "engines": {
-        "node": ">=8"
-      }
-    },
-    "node_modules/toml": {
-      "version": "4.1.1",
-      "resolved": "https://registry.npmjs.org/toml/-/toml-4.1.1.tgz",
-      "integrity": "sha512-EBJnVBr3dTXdA89WVFoAIPUqkBjxPMwRqsfuo1r240tKFHXv3zgca4+NJib/h6TyvGF7vOawz0jGuryJCdNHrw==",
-      "license": "MIT",
-      "engines": {
-        "node": ">=20"
-      }
-    },
-    "node_modules/uuid": {
-      "version": "13.0.1",
-      "resolved": "https://registry.npmjs.org/uuid/-/uuid-13.0.1.tgz",
-      "integrity": "sha512-9ezox2roIft6ExBVTVqibSd5dc5/47Sw/uY6b4SjQUT2TzQ0tltNquWA46y4xPQmdZYqvnio22SgWd41M86+jw==",
-      "funding": [
-        "https://github.com/sponsors/broofa",
-        "https://github.com/sponsors/ctavan"
-      ],
-      "license": "MIT",
-      "bin": {
-        "uuid": "dist-node/bin/uuid"
-      }
-    },
-    "node_modules/which": {
-      "version": "2.0.2",
-      "resolved": "https://registry.npmjs.org/which/-/which-2.0.2.tgz",
-      "integrity": "sha512-BLI3Tl1TW3Pvl70l3yq3Y64i+awpwXqsGBYWkkqMtnbXgrMD+yj7rhW0kuEDxzJaYXGjEW5ogapKNMEKNMjibA==",
-      "license": "ISC",
-      "dependencies": {
-        "isexe": "^2.0.0"
-      },
-      "bin": {
-        "node-which": "bin/node-which"
-      },
-      "engines": {
-        "node": ">= 8"
-      }
-    },
-    "node_modules/yaml": {
-      "version": "2.8.4",
-      "resolved": "https://registry.npmjs.org/yaml/-/yaml-2.8.4.tgz",
-      "integrity": "sha512-ml/JPOj9fOQK8RNnWojA67GbZ0ApXAUlN2UQclwv2eVgTgn7O9gg9o7paZWKMp4g0H3nTLtS9LVzhkpOFIKzog==",
-      "license": "ISC",
-      "bin": {
-        "yaml": "bin.mjs"
-      },
-      "engines": {
-        "node": ">= 14.6"
-      },
-      "funding": {
-        "url": "https://github.com/sponsors/eemeli"
-      }
-    },
-    "node_modules/zod": {
-      "version": "4.1.8",
-      "license": "MIT",
-      "funding": {
-        "url": "https://github.com/sponsors/colinhacks"
-      }
-    }
-  }
-}

AGENTS.md

@@ -1,85 +1,123 @@
-# AGENTS.md
+# Manual Slop - OpenCode Configuration
 
-## What This Is
+## MCP TOOL PARAMETERS - CRITICAL
+- **ALWAYS use snake_case**: `old_string`, `new_string`, `replace_all`
+- **NEVER use camelCase**: `oldString`, `newString`, `replaceAll`
 
-Manual Slop is a local GUI orchestrator for LLM-driven coding sessions. It bridges high-latency AI reasoning with a low-latency ImGui render loop via a thread-safe async pipeline; every AI-generated payload passes through a human-auditable gate before execution.
+## Project Overview
 
-## The Conductor Convention
+**Manual Slop** is a local GUI application designed as an experimental, "manual" AI coding assistant. It allows users to curate and send context (files, screenshots, and discussion history) to AI APIs (Gemini and Anthropic). The AI can then execute PowerShell scripts within the project directory to modify files, requiring explicit user confirmation before execution.
 
-All AI agents consuming this project must read `./conductor/workflow.md` and treat `./conductor/tracks.md` as the task registry. Track implementation follows the TDD protocol documented in `conductor/workflow.md` with per-file atomic commits and git notes.
+## Main Technologies
 
-## Guidance for AI Agents
+- **Language:** Python 3.11+
+- **Package Management:** `uv`
+- **GUI Framework:** Dear PyGui (`dearpygui`), ImGui Bundle (`imgui-bundle`)
+- **AI SDKs:** `google-genai` (Gemini), `anthropic`
+- **Configuration:** TOML (`tomli-w`)
 
-Detailed agent guidance lives in the following locations — read these directly, do not duplicate content here:
+## Architecture
 
-- **MUST READ TO - CORRECT EDIT WORKFLOW** `conductor/edit_workflow.md`
-- **Operational workflow:** `conductor/workflow.md`
-- **Code style and process:** `conductor/product-guidelines.md`
-- **Tech stack and constraints:** `conductor/tech-stack.md`
-- **Product context:** `conductor/product.md`
-- **MMA orchestrator role:** `mma-orchestrator/SKILL.md`
-- **Tier 1 (Orchestrator):** `.agents/skills/mma-tier1-orchestrator/SKILL.md`
-- **Tier 2 (Tech Lead):** `.agents/skills/mma-tier2-tech-lead/SKILL.md`
-- **Tier 3 (Worker):** `.agents/skills/mma-tier3-worker/SKILL.md`
-- **Tier 4 (QA):** `.agents/skills/mma-tier4-qa/SKILL.md`
+- **`gui_legacy.py`:** Main entry point and Dear PyGui application logic
+- **`ai_client.py`:** Unified wrapper for Gemini and Anthropic APIs
+- **`aggregate.py`:** Builds `file_items` context
+- **`mcp_client.py`:** Implements MCP-like tools (26 tools)
+- **`shell_runner.py`:** Sandboxed subprocess wrapper for PowerShell
+- **`project_manager.py`:** Per-project TOML configurations
+- **`session_logger.py`:** Timestamped logging (JSON-L)
 
-## Human-Facing Documentation
+## Critical Context (Read First)
 
-For understanding, using, and maintaining the tool, see `docs/Readme.md` and the 14 deep-dive guides it indexes.
+- **Tech Stack**: Python 3.11+, Dear PyGui / ImGui, FastAPI, Uvicorn
+- **Main File**: `gui_2.py` (primary GUI), `ai_client.py` (multi-provider LLM abstraction)
+- **Core Mechanic**: GUI orchestrator for LLM-driven coding with 4-tier MMA architecture
+- **Key Integration**: Gemini API, Anthropic API, DeepSeek, Gemini CLI (headless), MCP tools
+- **Platform Support**: Windows (PowerShell)
+- **DO NOT**: Read full files >50 lines without using `py_get_skeleton` or `get_file_summary` first
 
-## Critical Anti-Patterns
+## Environment
 
-- Do not read full files >50 lines without first using `py_get_skeleton` or `get_file_summary`
-- Do not modify the tech stack without updating `conductor/tech-stack.md` first
-- Do not skip TDD - write failing tests before implementation
-- Do not batch commits - commit per-task for atomic rollback
-- Do not add comments to source code; documentation lives in `/docs`
-- Do not use `set_file_slice` for multi-line content; it's literal line replacement by design (see `conductor/edit_workflow.md`)
-- Do not use `git restore` while a user is mid-conversation without first confirming the desired state
-- HARD BAN: `git restore`, `git checkout -- <file>`, `git reset` are FORBIDDEN without explicit user permission in the same message. They destroyed user in-progress src/* edits twice in one session (2026-06-07). If you think you need one, ASK FIRST.
-- No giant edits: if your `manual-slop_edit_file` `new_string` exceeds ~20 lines, STOP and split it.
+- Shell: PowerShell (pwsh) on Windows
+- Do NOT use bash-specific syntax (use PowerShell equivalents)
+- Use `uv run` for all Python execution
+- Path separators: forward slashes work in PowerShell
 
-## Session-Learned Anti-Patterns (Added 2026-06-07)
+## Session Startup Checklist
 
-These burned the most time in a recent startup_speedup session. The rules below are short because the rules above (and `conductor/edit_workflow.md`) are the source of truth.
+At the start of each session:
 
-### 1. ALWAYS use the proper edit tool, not a custom script
+1. **Check ./condcutor/tracks.md** - look for IN_PROGRESS or BLOCKED tracks
+2. **Review recent JOURNAL.md entries** - scan last 2-3 entries for context
+3. **Run `/conductor-setup`** - load full context
+4. **Run `/conductor-status`** - get overview
 
-- For Python source edits, use `manual-slop_edit_file` with `old_string`/`new_string`. **Do NOT** write a standalone Python script that does file-level replacements.
-- Custom scripts fail silently on: wrong indent in `new_content`, wrong EOL (CRLF vs LF) in `old_string` searches, wrong exact-string match (whitespace drift).
-- When a script fails, debug the actual error message. Do not dismiss it and try a different approach.
+## Conductor System
 
-### 2. The decorator-orphan pitfall
+The project uses a spec-driven track system in `conductor/`:
 
-When inserting new methods **before an existing `@property` def**, your script will leave the `@property` decorator on the line above your new methods. The decorator then accidentally decorates YOUR new method (which is no longer a property, breaking any subsequent `@your_method.setter` calls). The file passes `ast.parse()` but blows up at import time.
+- **Tracks**: `conductor/tracks/{name}_{YYYYMMDD}/` - spec.md, plan.md, metadata.json
+- **Workflow**: `conductor/workflow.md` - full task lifecycle and TDD protocol
+- **Tech Stack**: `conductor/tech-stack.md` - technology constraints
+- **Product**: `conductor/product.md` - product vision and guidelines
 
-The fix: anchor on the **def line that has the `@property` ABOVE it**, and replace the pair `@property\n def foo(...)` with `@property\n def your_new(...)\n ...\n def foo(...)` — keeping the decorator attached to its original method. Or anchor on a different non-decorated landmark (e.g. `self._init_actions()`).
+## MMA 4-Tier Architecture
 
-### 3. `ast.parse()` "Syntax OK" is not enough
+```
+Tier 1: Orchestrator   - product alignment, epic -> tracks
+Tier 2: Tech Lead      - track -> tickets (DAG), architectural oversight
+Tier 3: Worker         - stateless TDD implementation per ticket
+Tier 4: QA             - stateless error analysis, no fixes
+```
 
-`ast.parse()` only catches syntax errors. Semantic errors (wrong decorator targets, wrong class attribute, missing `self`, etc.) are NOT caught. After a multi-line edit, ALWAYS:
-- Import the module
-- Instantiate the class
-- Call the new method in the way it's expected to be called (e.g. `ctrl.foo_ts` vs `ctrl.foo_ts()` for properties vs methods)
+## Architecture Fallback
 
-### 4. The "I'll just check git status" trap (now a HARD BAN, see Critical list above)
+When uncertain about threading, event flow, data structures, or module interactions, consult:
 
-If you suspect you might have lost work, the worst move is to run `git status` / `git restore` while a frantic user is watching. Pause, read the actual file, and admit what state you're in. The user knows their state better than you do. This trap has now caused irrecoverable data loss twice in one session — the ban is enforced above.
+- **docs/guide_architecture.md**: Thread domains, event system, AI client, HITL mechanism
+- **docs/guide_tools.md**: MCP Bridge security, 26-tool inventory, Hook API endpoints
+- **docs/guide_mma.md**: Ticket/Track data structures, DAG engine, ConductorEngine
+- **docs/guide_simulations.md**: live_gui fixture, Puppeteer pattern, verification
+- **docs/guide_meta_boundary.md**: Clarification of ai agent tools making the application vs the application itself.
 
-### 5. Small, verified edits beat big scripts
+## Development Workflow
 
-`conductor/edit_workflow.md` says it explicitly: 3-10 lines at a time, verify after each, repeat. If you find yourself writing a 200-line Python script to do an edit, you're doing it wrong. Use the MCP tools.
+1. Run `/conductor-setup` to load session context
+2. Pick active track from `./condcutor/tracks.md` or `/conductor-status`
+3. Run `/conductor-implement` to resume track execution
+4. Follow TDD: Red (failing tests) -> Green (pass) -> Refactor
+5. Delegate implementation to Tier 3 Workers, errors to Tier 4 QA
+6. On phase completion: run `/conductor-verify` for checkpoint
 
-## Compaction Recovery
+## Anti-Patterns (Avoid These)
 
-If you're a new agent picking up a session that was compacted (or a previous agent ran out of context), follow this recovery path:
+- **Don't read full large files** - use `py_get_skeleton`, `get_file_summary`, `py_get_code_outline` first
+- **Don't implement directly as Tier 2** - delegate to Tier 3 Workers
+- **Don't skip TDD** - write failing tests before implementation
+- **Don't modify tech stack silently** - update `conductor/tech-stack.md` BEFORE implementing
+- **Don't skip phase verification** - run `/conductor-verify` when all tasks in a phase are `[x]`
+- **Don't mix track work** - stay focused on one track at a time
 
-1. **Read the most recent `docs/reports/PLANNING_DIGEST_<date>.md`** if one exists. It indexes the planning artifacts and explains the design decisions behind the active tracks.
-2. **For each in-flight track**, read `conductor/tracks/<track_id>/state.toml` to see `current_phase`; read `conductor/tracks/<track_id>/plan.md` for the task breakdown.
-3. **Check `git log --oneline -20`** to see what has been committed; the most recent commits in `conductor/tracks/<track_id>/` are the latest work.
-4. **Run the audit scripts** (`scripts/audit_main_thread_imports.py`, `scripts/audit_weak_types.py`) to see the current state of the codebase.
-5. **Resume from the next unchecked task** in `state.toml`. The per-task commit discipline means each commit is a safe rollback point.
+## Code Style
 
-The track's `metadata.json` has a `verification_criteria` field — this is the definition of "done" for the track. If all the criteria are checked, the track is complete.
+- **IMPORTANT**: DO NOT ADD ***ANY*** COMMENTS unless asked
+- Use 1-space indentation for Python code
+- Use type hints where appropriate
 
-For deeper recovery, see `conductor/workflow.md` "Compaction Recovery" (the same pattern, but workflow-level).
+## Code Style
+
+- **IMPORTANT**: DO NOT ADD ***ANY*** COMMENTS unless asked
+- Use 1-space indentation for Python code
+- Use type hints where appropriate
+- Internal methods/variables prefixed with underscore
+
+### CRITICAL: Native Edit Tool Destroys Indentation
+
+The native `Edit` tool DESTROYS 1-space indentation and converts to 4-space.
+
+**NEVER use native `edit` tool on Python files.**
+
+Instead, use Manual Slop MCP tools:
+
+- `manual-slop_py_update_definition` - Replace function/class
+- `manual-slop_set_file_slice` - Replace line range
+- `manual-slop_py_set_signature` - Replace signature only

ARCHITECTURE.md

@@ -0,0 +1,58 @@
+# ARCHITECTURE.md
+
+## Tech Stack
+- **Framework**: [Primary framework/language]
+- **Database**: [Database system]
+- **Frontend**: [Frontend technology]
+- **Backend**: [Backend technology]
+- **Infrastructure**: [Hosting/deployment]
+- **Build Tools**: [Build system]
+
+## Directory Structure
+```
+project/
+├── src/              # Source code
+├── tests/            # Test files
+├── docs/             # Documentation
+├── config/           # Configuration files
+└── scripts/          # Build/deployment scripts
+```
+
+## Key Architectural Decisions
+
+### [Decision 1]
+**Context**: [Why this decision was needed]
+**Decision**: [What was decided]
+**Rationale**: [Why this approach was chosen]
+**Consequences**: [Trade-offs and implications]
+
+## Component Architecture
+
+### [ComponentName] Structure <!-- #component-anchor -->
+```typescript
+// Major classes with exact line numbers
+class MainClass { /* lines 100-500 */ }    // <!-- #main-class -->
+class Helper { /* lines 501-600 */ }       // <!-- #helper-class -->
+```
+
+## System Flow Diagram
+```
+[User] -> [Frontend] -> [API] -> [Database]
+           |            |
+           v            v
+       [Cache]     [External Service]
+```
+
+## Common Patterns
+
+### [Pattern Name]
+**When to use**: [Circumstances]
+**Implementation**: [How to implement]
+**Example**: [Code example with line numbers]
+
+## Keywords <!-- #keywords -->
+- architecture
+- system design
+- tech stack
+- components
+- patterns

BUILD.md

@@ -0,0 +1,103 @@
+# BUILD.md
+
+## Prerequisites
+- [Runtime requirements]
+- [Development tools needed]
+- [Environment setup]
+
+## Build Commands
+
+### Development
+```bash
+# Start development server
+npm run dev
+
+# Run in watch mode
+npm run watch
+```
+
+### Production
+```bash
+# Build for production
+npm run build
+
+# Start production server
+npm start
+```
+
+### Testing
+```bash
+# Run all tests
+npm test
+
+# Run tests in watch mode
+npm run test:watch
+
+# Run specific test file
+npm test -- filename
+```
+
+### Linting & Formatting
+```bash
+# Lint code
+npm run lint
+
+# Fix linting issues
+npm run lint:fix
+
+# Format code
+npm run format
+```
+
+## CI/CD Pipeline
+
+### GitHub Actions
+```yaml
+# .github/workflows/main.yml
+name: CI/CD
+on: [push, pull_request]
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - name: Setup Node.js
+        uses: actions/setup-node@v3
+        with:
+          node-version: '18'
+      - run: npm ci
+      - run: npm test
+      - run: npm run build
+```
+
+## Deployment
+
+### Staging
+1. [Deployment steps]
+2. [Verification steps]
+
+### Production
+1. [Pre-deployment checklist]
+2. [Deployment steps]
+3. [Post-deployment verification]
+
+## Rollback Procedures
+1. [Emergency rollback steps]
+2. [Database rollback if needed]
+3. [Verification steps]
+
+## Troubleshooting
+
+### Common Issues
+**Issue**: [Problem description]
+**Solution**: [How to fix]
+
+### Build Failures
+- [Common build errors and solutions]
+
+## Keywords <!-- #keywords -->
+- build
+- deployment
+- ci/cd
+- testing
+- production

CLAUDE.md

@@ -1,3 +1,122 @@
 # CLAUDE.md
+<!-- Generated by Claude Conductor v2.0.0 -->
 
-This project is no longer actively used with Claude Code. For project context, see `AGENTS.md`. The conductor system in `./conductor/` is the cross-tool abstraction and works with any agent toolchain.
+This file provides guidance to Claude Code when working with this repository.
+
+## MCP TOOL PARAMETERS - CRITICAL
+- **ALWAYS use snake_case**: `old_string`, `new_string`, `replace_all`
+- **NEVER use camelCase**: `oldString`, `newString`, `replaceAll`
+
+## Critical Context (Read First)
+- **Tech Stack**: Python 3.11+, Dear PyGui / ImGui, FastAPI, Uvicorn
+- **Main File**: `gui_2.py` (primary GUI), `ai_client.py` (multi-provider LLM abstraction)
+- **Core Mechanic**: GUI orchestrator for LLM-driven coding with 4-tier MMA architecture
+- **Key Integration**: Gemini API, Anthropic API, DeepSeek, Gemini CLI (headless), MCP tools
+- **Platform Support**: Windows (PowerShell) — single developer, local use
+- **DO NOT**: Read full files >50 lines without using `py_get_skeleton` or `get_file_summary` first. Do NOT perform heavy implementation directly — delegate to Tier 3 Workers.
+
+## Environment
+- Shell: PowerShell (pwsh) on Windows
+- Do NOT use bash-specific syntax (use PowerShell equivalents)
+- Use `uv run` for all Python execution
+- Path separators: forward slashes work in PowerShell
+- **Shell execution in Claude Code**: The `Bash` tool runs in a mingw sandbox on Windows and produces unreliable/empty output. Use `run_powershell` MCP tool for ALL shell commands (git, tests, scans). Bash is last-resort only when MCP server is not running.
+
+## Session Startup Checklist
+**IMPORTANT**: At the start of each session:
+1. **Check TASKS.md** — look for IN_PROGRESS or BLOCKED tracks
+2. **Review recent JOURNAL.md entries** — scan last 2-3 entries for context
+3. **If resuming work**: run `/conductor-setup` to load full context
+4. **If starting fresh**: run `/conductor-status` for overview
+
+## Quick Reference
+**GUI Entry**: `gui_2.py` — Primary ImGui interface
+**AI Client**: `ai_client.py` — Multi-provider abstraction (Gemini, Anthropic, DeepSeek)
+**MCP Client**: `mcp_client.py:773-831` — Tool dispatch (26 tools)
+**Project Manager**: `project_manager.py` — Context & file management
+**MMA Engine**: `multi_agent_conductor.py:15-100` — ConductorEngine orchestration
+**Tech Lead**: `conductor_tech_lead.py` — Tier 2 ticket generation
+**DAG Engine**: `dag_engine.py` — Task dependency resolution
+**Session Logger**: `session_logger.py` — Audit trails (JSON-L + markdown)
+**Shell Runner**: `shell_runner.py` — PowerShell execution (60s timeout)
+**Models**: `models.py:6-84` — Ticket and Track data structures
+**File Cache**: `file_cache.py` — ASTParser with tree-sitter skeletons
+**Summarizer**: `summarize.py` — Heuristic file summaries
+**Outliner**: `outline_tool.py` — Code outline with line ranges
+
+## Conductor System
+The project uses a spec-driven track system in `conductor/`:
+- **Tracks**: `conductor/tracks/{name}_{YYYYMMDD}/` — spec.md, plan.md, metadata.json
+- **Workflow**: `conductor/workflow.md` — full task lifecycle and TDD protocol
+- **Tech Stack**: `conductor/tech-stack.md` — technology constraints
+- **Product**: `conductor/product.md` — product vision and guidelines
+
+### Conductor Commands (Claude Code slash commands)
+- `/conductor-setup` — bootstrap session with conductor context
+- `/conductor-status` — show all track status
+- `/conductor-new-track` — create a new track (Tier 1)
+- `/conductor-implement` — execute a track (Tier 2 — delegates to Tier 3/4)
+- `/conductor-verify` — phase completion verification and checkpointing
+
+### MMA Tier Commands
+- `/mma-tier1-orchestrator` — product alignment, planning
+- `/mma-tier2-tech-lead` — track execution, architectural oversight
+- `/mma-tier3-worker` — stateless TDD implementation
+- `/mma-tier4-qa` — stateless error analysis
+
+### Delegation (Tier 2 spawns Tier 3/4)
+```powershell
+uv run python scripts\claude_mma_exec.py --role tier3-worker "Task prompt here"
+uv run python scripts\claude_mma_exec.py --role tier4-qa "Error analysis prompt"
+```
+
+## Current State
+- [x] Multi-provider AI client (Gemini, Anthropic, DeepSeek)
+- [x] Dear PyGui / ImGui GUI with multi-panel interface
+- [x] MMA 4-tier orchestration engine
+- [x] Custom MCP tools (26 tools via mcp_client.py)
+- [x] Session logging and audit trails
+- [x] Gemini CLI headless adapter
+- [x] Claude Code conductor integration
+- [~] AI-Optimized Python Style Refactor (Phase 3 — type hints for UI modules)
+- [~] Robust Live Simulation Verification (Phase 2 — Epic/Track verification)
+- [ ] Documentation Refresh and Context Cleanup
+
+## Development Workflow
+1. Run `/conductor-setup` to load session context
+2. Pick active track from `conductor/tracks.md` or `/conductor-status`
+3. Run `/conductor-implement` to resume track execution
+4. Follow TDD: Red (failing tests) → Green (pass) → Refactor
+5. Delegate implementation to Tier 3 Workers, errors to Tier 4 QA
+6. On phase completion: run `/conductor-verify` for checkpoint
+
+## Anti-Patterns (Avoid These)
+- **Don't read full large files** — use `py_get_skeleton`, `get_file_summary`, `py_get_code_outline` first (Research-First Protocol)
+- **Don't implement directly as Tier 2** — delegate to Tier 3 Workers via `claude_mma_exec.py`
+- **Don't skip TDD** — write failing tests before implementation
+- **Don't modify tech stack silently** — update `conductor/tech-stack.md` BEFORE implementing
+- **Don't skip phase verification** — run `/conductor-verify` when all tasks in a phase are `[x]`
+- **Don't mix track work** — stay focused on one track at a time
+
+## MCP Tools (available via manual-slop MCP server)
+When the MCP server is running, these tools are available natively:
+`py_get_skeleton`, `py_get_code_outline`, `py_get_definition`, `py_update_definition`,
+`py_get_signature`, `py_set_signature`, `py_get_class_summary`, `py_find_usages`,
+`py_get_imports`, `py_check_syntax`, `py_get_hierarchy`, `py_get_docstring`,
+`get_file_summary`, `get_file_slice`, `set_file_slice`, `get_git_diff`, `get_tree`,
+`search_files`, `read_file`, `list_directory`, `web_search`, `fetch_url`,
+`run_powershell`, `get_ui_performance`, `py_get_var_declaration`, `py_set_var_declaration`
+
+## Journal Update Requirements
+Update JOURNAL.md after:
+- Completing any significant feature or fix
+- Encountering and resolving errors
+- End of each work session
+- Making architectural decisions
+Format: What/Why/How/Issues/Result structure
+
+## Task Management Integration
+- **conductor/tracks.md**: Quick-read pointer to active conductor tracks
+- **conductor/tracks/*/plan.md**: Detailed task state (source of truth)
+- **JOURNAL.md**: Completed work history with `|TASK:ID|` tags
+- **ERRORS.md**: P0/P1 error tracking

Dockerfile

@@ -1,23 +1,34 @@
+# Use python:3.11-slim as a base
 FROM python:3.11-slim
 
-RUN apt-get update && apt-get install -y --no-install-recommends \
-    git curl ca-certificates libx11-6 libgl1 libxrender1 libxext6 tk \
-    && rm -rf /var/lib/apt/lists/*
+# Set environment variables
+# UV_SYSTEM_PYTHON=1 allows uv to install into the system site-packages
+ENV PYTHONDONTWRITEBYTECODE=1 
+    PYTHONUNBUFFERED=1 
+    UV_SYSTEM_PYTHON=1
 
-RUN pip install uv
+# Install system dependencies and uv
+RUN apt-get update && apt-get install -y --no-install-recommends 
+    curl 
+    ca-certificates 
+    && rm -rf /var/lib/apt/lists/* 
+    && curl -LsSf https://astral.sh/uv/install.sh | sh 
+    && mv /root/.local/bin/uv /usr/local/bin/uv
 
+# Set the working directory in the container
 WORKDIR /app
-COPY pyproject.toml uv.lock ./
-RUN uv sync --frozen
 
+# Copy dependency files first to leverage Docker layer caching
+COPY pyproject.toml requirements.txt* ./
+
+# Install dependencies via uv
+RUN if [ -f requirements.txt ]; then uv pip install --no-cache -r requirements.txt; fi
+
+# Copy the rest of the application code
 COPY . .
 
-RUN mkdir -p /projects /config
-VOLUME ["/projects", "/config"]
+# Expose port 8000 for the headless API/service
+EXPOSE 8000
 
-EXPOSE 8080 8999
-
-HEALTHCHECK --interval=30s --timeout=5s --start-period=30s --retries=3 \
-    CMD curl -f http://127.0.0.1:8999/status || exit 1
-
-ENTRYPOINT ["uv", "run", "sloppy.py", "--enable-test-hooks", "--web-host=0.0.0.0", "--web-port=8080"]
+# Set the entrypoint to run the app in headless mode
+ENTRYPOINT ["python", "gui_2.py", "--headless"]

GEMINI.md

@@ -1,42 +1,22 @@
-# GEMINI.md
+# Project Overview
 
-This file covers Gemini-CLI-specific operational notes for the Manual Slop project. The primary toolchain is Gemini CLI; for general agent orientation, see `AGENTS.md`.
-
-## Project Overview
-
-**Manual Slop** is a local GUI orchestrator for LLM-driven coding sessions. It bridges high-latency AI reasoning with a low-latency ImGui render loop via a thread-safe async pipeline; every AI-generated payload passes through a human-auditable gate before execution.
+**Manual Slop** is a local GUI application designed as an experimental, "manual" AI coding assistant. It allows users to curate and send context (files, screenshots, and discussion history) to AI APIs (Gemini and Anthropic). The AI can then execute PowerShell scripts within the project directory to modify files, requiring explicit user confirmation before execution.
 
 **Main Technologies:**
 *   **Language:** Python 3.11+
 *   **Package Management:** `uv`
-*   **GUI Framework:** ImGui Bundle (`imgui-bundle`)
-*   **AI SDKs:** `google-genai` (Gemini), `anthropic` (Claude), `openai` (DeepSeek + MiniMax via OpenAI-compatible endpoints), `GeminiCliAdapter` (headless gemini CLI subprocess)
+*   **GUI Framework:** Dear PyGui (`dearpygui`), ImGui Bundle (`imgui-bundle`)
+*   **AI SDKs:** `google-genai` (Gemini), `anthropic`
 *   **Configuration:** TOML (`tomli-w`)
 
-**Providers Supported (as of 2026-06-02):**
-- **Gemini SDK** — Primary; uses server-side CachedContent
-- **Gemini CLI** — Headless adapter with full functional parity
-- **Anthropic** — Ephemeral prompt caching (4-breakpoint system)
-- **DeepSeek** — Code-optimized reasoning
-- **MiniMax** — OpenAI-compatible alternative
-
-**Entry Point:** `sloppy.py` (was `gui_legacy.py` before the rename; `gui_2.py` is now the active ImGui application module).
-
-**Architecture (key modules):**
-*   **`src/gui_2.py`:** Primary ImGui application; App class, frame-sync, HITL dialogs, event system. ~260K lines.
-*   **`src/ai_client.py`:** Multi-provider LLM abstraction (Gemini, Anthropic, DeepSeek, Gemini CLI, MiniMax). Module-level singleton with state.
-*   **`src/mcp_client.py`:** 45 MCP tools (file I/O, AST inspection, C/C++ tree-sitter, analysis, network, runtime, Beads). Three-layer security model.
-*   **`src/multi_agent_conductor.py`:** ConductorEngine + WorkerPool. 4-Tier MMA orchestration with DAG execution.
-*   **`src/dag_engine.py`:** TrackDAG (cycle detection, topological sort) + ExecutionEngine (tick-based state machine).
-*   **`src/aggregate.py`:** Context aggregation pipeline.
-*   **`src/app_controller.py`:** Main controller; bridges GUI and async AI workers.
-*   **`src/api_hooks.py`:** HTTP API on `:8999` for external automation and IPC.
-*   **`src/rag_engine.py`:** RAG subsystem (ChromaDB + embedding providers).
-*   **`src/personas.py`:** Unified agent profile management.
-*   **`src/workspace_manager.py`:** Workspace profile save/load.
-*   **`src/hot_reloader.py`:** State-preserving module reloading.
-
-Full module list: `src/*.py`. See `docs/guide_architecture.md` for the threading model and event system.
+**Architecture:**
+*   **`gui_legacy.py`:** The main entry point and Dear PyGui application logic. Handles all panels, layouts, user input, and confirmation dialogs.
+*   **`ai_client.py`:** A unified wrapper for both Gemini and Anthropic APIs. Manages sessions, tool/function-call loops, token estimation, and context history management.
+*   **`aggregate.py`:** Responsible for building the `file_items` context. It reads project configurations, collects files and screenshots, and builds the context into markdown format to send to the AI.
+*   **`mcp_client.py`:** Implements MCP-like tools (e.g., `read_file`, `list_directory`, `search_files`, `web_search`) as native functions that the AI can call. Enforces a strict allowlist for file access.
+*   **`shell_runner.py`:** A sandboxed subprocess wrapper that executes PowerShell scripts (`powershell -NoProfile -NonInteractive -Command`) provided by the AI.
+*   **`project_manager.py`:** Manages per-project TOML configurations (`manual_slop.toml`), serializes discussion entries, and integrates with git (e.g., fetching current commit).
+*   **`session_logger.py`:** Handles timestamped logging of communication history (JSON-L) and tool calls (saving generated `.ps1` files).
 
 # Building and Running
 
@@ -47,33 +27,21 @@ Full module list: `src/*.py`. See `docs/guide_architecture.md` for the threading
     api_key = "****"
     [anthropic]
     api_key = "****"
-    [deepseek]
-    api_key = "****"
-    [minimax]
-    api_key = "****"
     ```
-    The `credentials.toml` is **blacklisted** by the MCP allowlist — AI tools cannot read it.
 *   **Run the Application:**
     ```powershell
-    uv run sloppy.py                        # Normal mode
-    uv run sloppy.py --enable-test-hooks    # With Hook API on :8999
+    uv run .\gui_2.py
     ```
 
-# Gemini-CLI-Specific Conventions
+# Development Conventions
 
-*   **Conductor Extension:** Gemini CLI uses the conductor extension, which reads `./conductor/` for task tracking, workflow, and product context. Tracks live in `conductor/tracks/<name>_<YYYYMMDD>/` with `spec.md`, `plan.md`, and `metadata.json`.
-*   **Skill Activation:** Use `activate_skill mma-orchestrator` to load the orchestrator skill, then activate the tier-specific skill (e.g., `activate_skill mma-tier1-orchestrator`).
-*   **The Conductor Convention:** Read `conductor/workflow.md` for the TDD protocol. Treat `conductor/tracks.md` as the task registry. Track implementation follows per-file atomic commits with git notes.
-*   **Tool Execution:** AI-generated PowerShell scripts and tool calls pass through the Execution Clutch (HITL). Scripts are saved to `scripts/generated/<ts>_<seq>.ps1`.
-*   **Context Refresh:** After every tool call that modifies the file system, the application automatically refreshes file contents in the context using `mtime` checks.
-*   **Fuzzy Anchor Resilience:** Line-based operations (`get_file_slice`, `set_file_slice`, `py_update_definition`, fuzzy anchor slices) use FuzzyAnchor to survive file modifications. They can be batched in a single turn without line drift.
-*   **Layout Persistence:** Window layouts are saved to `manualslop_layout.ini` (was `dpg_layout.ini`).
-*   **Logging:** All API communications are logged to `logs/sessions/<id>/comms.log`. Tool calls to `toolcalls.log`. Generated scripts to `scripts/generated/`.
+*   **Configuration Management:** The application uses two tiers of configuration:
+    *   `config.toml`: Global settings (UI theme, active provider, list of project paths).
+    *   `manual_slop.toml`: Per-project settings (files to track, discussion history, specific system prompts).
+*   **Tool Execution:** The AI acts primarily by generating PowerShell scripts. These scripts MUST be confirmed by the user via a GUI modal before execution. The AI also has access to read-only MCP-style file exploration tools and web search capabilities.
+*   **Context Refresh:** After every tool call that modifies the file system, the application automatically refreshes the file contents in the context using the files' `mtime` to optimize reads.
+*   **UI State Persistence:** Window layouts and docking arrangements are automatically saved to and loaded from `dpg_layout.ini`.
 *   **Code Style:**
-    *   Use exactly 1-space indentation for Python (NO EXCEPTIONS). See `conductor/product-guidelines.md`.
-    *   Use the manual-slop MCP tools (`manual-slop_edit_file`, `manual-slop_py_update_definition`) for surgical edits — native edit tools destroy indentation.
-    *   Internal methods and variables are prefixed with an underscore (e.g., `_flush_to_project`, `_do_generate`).
-
-# Human-Facing Documentation
-
-For understanding, using, and maintaining the tool, see `docs/Readme.md` and the 14 deep-dive guides it indexes. See `conductor/product.md` for the product vision.
+    *   Use type hints where appropriate.
+    *   Internal methods and variables are generally prefixed with an underscore (e.g., `_flush_to_project`, `_do_generate`).
+*   **Logging:** All API communications are logged to `logs/comms_<ts>.log`. All executed scripts are saved to `scripts/generated/`.

Readme.md

@@ -1,31 +1,12 @@
 # Manual Slop
 
-## *Note by the Human behind this*
-
-I see the potential of AI as both an invaluable learning tool, and percise techinical writing or code generation when handled with care and deep curation. This repo is both a proof of concept of this assertion and a tool to achieve this because every single paid or vested "AI Agenic developer" seems to not be interested in these principles.
-
-## Why did you do this in Python
-
-*TLDR: I apologize it was out of sheer practicality with time allocation and resources available. I really don't like python.*
-
-Before I winged this project on a whim and frustration, I had tried AI with various langauges, unfortuantely python did remarkably well.
-
-* Attic-Greek-TTS - ~3 kloc TTS tool for a dead language, with spectrograph anaylsis for verification.
-* forth_bootslop - Used scripts to gather and curate large amounts information and data from sources into formats it could digest.
-
-Prior to making this tool I had very dissapointing performance with more favaorable langauges: C11, Odin, or Jai (Which I don't have direct access to).
-
-I don't enjoy web browser sandboxed runtimes so I didn't use javascript. I haven't attempted AI with lua much but that was the alternative, and I knew python had the next best support for AI toolchain bindings along with an imgui package. So based purely on these factors alone I resolved to attempt this in Python.
-
-## Summary
-
 ![img](./gallery/splash.png)
 
 A high-density GUI orchestrator for local LLM-driven coding sessions. Manual Slop bridges high-latency AI reasoning with a low-latency ImGui render loop via a thread-safe asynchronous pipeline, ensuring every AI-generated payload passes through a human-auditable gate before execution.
 
 **Design Philosophy**: Full manual control over vendor API metrics, agent capabilities, and context memory usage. High information density, tactile interactions, and explicit confirmation for destructive actions.
 
-**Tech Stack**: Python 3.11+, ImGui Bundle (Dear ImGui + imgui-node-editor + imgui_markdown + ImGuiColorTextEdit), FastAPI, Uvicorn, tree-sitter (Python, C, C++), chromadb (RAG), pywin32 (Windows window frame), psutil (telemetry), pydantic, dolt (Beads)
+**Tech Stack**: Python 3.11+, Dear PyGui / ImGui Bundle, FastAPI, Uvicorn, tree-sitter
 **Providers**: Gemini API, Anthropic API, DeepSeek, Gemini CLI (headless), MiniMax
 **Platform**: Windows (PowerShell) — single developer, local use
 
@@ -54,18 +35,13 @@ Hierarchical task decomposition with specialized models and strict token firewal
 - **Three Dialog Types**: ConfirmDialog (scripts), MMAApprovalDialog (steps), MMASpawnApprovalDialog (workers)
 - **Editable Payloads**: Review, modify, or reject any AI-generated content before execution
 
-### 45 MCP Tools with Sandboxing
+### 26 MCP Tools with Sandboxing
 Three-layer security model: Allowlist Construction → Path Validation → Resolution Gate
 - **File I/O**: read, list, search, slice, edit, tree
-- **AST-Based (Python)**: skeleton, outline, definition, signature, class summary, docstring, var declaration, hierarchy, imports, syntax check, find usages
-- **AST-Based (C/C++)**: tree-sitter powered skeleton, outline, definition, signature, and surgical update tools for C and C++
-- **File Editing**: surgical string match (`edit_file`) preserving indentation and line endings
-- **Analysis**: summary, git diff, find usages, imports, syntax check, hierarchy, derive code path
-- **Network**: web search, URL fetch (dependency-free, stdlib only)
+- **AST-Based (Python)**: skeleton, outline, definition, signature, class summary, docstring
+- **Analysis**: summary, git diff, find usages, imports, syntax check, hierarchy
+- **Network**: web search, URL fetch
 - **Runtime**: UI performance metrics
-- **Beads**: bd_create, bd_list, bd_ready, bd_update for Dolt-backed issue tracking
-
-See [docs/guide_tools.md](./docs/guide_tools.md) for the full inventory.
 
 ### Parallel Tool Execution
 Multiple independent tool calls within a single AI turn execute concurrently via `asyncio.gather`, significantly reducing latency.
@@ -86,10 +62,6 @@ The **Execution Clutch** suspends the AI execution thread on a `threading.Condit
 
 The **MMA (Multi-Model Agent)** system decomposes epics into tracks, tracks into DAG-ordered tickets, and executes each ticket with a stateless Tier 3 worker that starts from `ai_client.reset_session()` — no conversational bleed between tickets ([details](./docs/guide_mma.md)).
 
-### Test Coverage
-
-The project has **273 test files** with 98.9% pass rate (272/273 in the latest batched run; the 1 failure is a pre-existing flake in `test_rag_phase4_stress` that passes in isolation). Most failures are caught and fixed via the 4-tier MMA test-harden track system. See [docs/guide_testing.md](./docs/guide_testing.md) for the full testing contract.
-
 ---
 
 ## Documentation
@@ -97,48 +69,11 @@ The project has **273 test files** with 98.9% pass rate (272/273 in the latest b
 | Guide | Scope |
 |---|---|
 | [Readme](./docs/Readme.md) | Documentation index, GUI panel reference, configuration files, environment variables |
-| [Architecture](./docs/guide_architecture.md) | Threading model, event system, AI client multi-provider architecture (Gemini, Anthropic, DeepSeek, Gemini CLI, MiniMax), HITL mechanism, comms logging, RAG integration, Tier 4 patch flow |
-| [Tools & IPC](./docs/guide_tools.md) | MCP Bridge 3-layer security, 45-tool inventory, Hook API endpoints, ApiHookClient reference, shell runner, Beads tools |
-| [MMA Orchestration](./docs/guide_mma.md) | 4-tier hierarchy, Ticket/Track/WorkerContext data structures, DAG engine, ConductorEngine, worker lifecycle, persona application, abort propagation |
-| [Simulations](./docs/guide_simulations.md) | `live_gui` fixture, Puppeteer pattern, mock provider, visual verification, test areas by subsystem, headless service |
-| [Context Curation](./docs/guide_context_curation.md) | AST masking, fuzzy anchor slices, structural file editor, view presets, history snapshotting |
-| [Shaders & Window](./docs/guide_shaders_and_window.md) | Hybrid shader injection, custom window frame, NERV theme effects |
-| [Themes](./docs/guide_themes.md) | TOML-based theming, `[colors]` table, 4-syntax-palette upstream limit, `load_themes_from_disk` / `apply_syntax_palette` API, color-callable convention |
-| [Meta-Boundary](./docs/guide_meta_boundary.md) | Application vs Meta-Tooling domains, inter-domain bridges, cross-tool abstractions |
-
----
-
-## Subsystem Index
-
-| Subsystem | Guide | Primary Module(s) |
-|---|---|---|
-| Multi-provider LLM client | [Architecture](./docs/guide_architecture.md#ai-client-multi-provider-architecture) | `src/ai_client.py` |
-| 4-Tier MMA orchestration | [MMA](./docs/guide_mma.md) | `src/multi_agent_conductor.py`, `src/dag_engine.py` |
-| DAG engine & ticket lifecycle | [MMA](./docs/guide_mma.md#dag-engine-dag_enginepy) | `src/dag_engine.py` |
-| MCP tools & Hook API | [Tools & IPC](./docs/guide_tools.md) | `src/mcp_client.py`, `src/api_hooks.py` |
-| Execution Clutch (HITL) | [Architecture](./docs/guide_architecture.md#the-execution-clutch-human-in-the-loop) | `src/app_controller.py` |
-| Context composition & aggregation | [Context Curation](./docs/guide_context_curation.md) | `src/aggregate.py`, `src/file_cache.py` |
-| AST inspection & slicing | [Context Curation](./docs/guide_context_curation.md#granular-ast-control) | `src/file_cache.py`, `src/fuzzy_anchor.py` |
-| Personas (unified profiles) | *See [guide_mma.md](./docs/guide_mma.md#persona-application); dedicated guide pending* | `src/personas.py` |
-| Tool bias engine | *See [guide_tools.md](./docs/guide_tools.md); dedicated guide pending* | `src/tool_bias.py` |
-| RAG (Retrieval-Augmented Generation) | *See [guide_architecture.md](./docs/guide_architecture.md#rag-integration); dedicated guide pending* | `src/rag_engine.py` |
-| Beads mode (Dolt issue tracking) | *See [guide_tools.md](./docs/guide_tools.md#beads-tools); dedicated guide pending* | `src/beads_client.py` |
-| Hot reload (state-preserving) | *Dedicated guide pending* | `src/hot_reloader.py` |
-| Discussion metrics & compression | [Architecture](./docs/guide_architecture.md#discussion-compression) | `src/ai_client.py` |
-| Test infrastructure & simulations | [Simulations](./docs/guide_simulations.md) | `tests/conftest.py`, `simulation/` |
-| Headless service (FastAPI) | [Simulations](./docs/guide_simulations.md#headless-service-tests) | `src/api_hooks.py` |
-| NERV theme & visual effects | [Shaders & Window](./docs/guide_shaders_and_window.md#4-nerv-theme-effects) | `src/theme_nerv.py`, `src/theme_nerv_fx.py` |
-| TOML theme system (palette + syntax) | [Themes](./docs/guide_themes.md) | `src/theme_2.py`, `src/theme_models.py` |
-| Custom window frame | [Shaders & Window](./docs/guide_shaders_and_window.md#2-custom-window-frame-strategy) | `src/gui_2.py` |
-| Workspace profiles (docking layouts) | *Dedicated guide pending* | `src/workspace_manager.py` |
-| History (undo/redo) | [Context Curation](./docs/guide_context_curation.md#context-snapshotting-per-take) | `src/history.py` |
-| External MCP integration | [Tools & IPC](./docs/guide_tools.md#external-mcp-integration) | `src/mcp_client.py` |
-| Telemetry & performance monitoring | [Architecture](./docs/guide_architecture.md#telemetry--auditing) | `src/performance_monitor.py` |
-| Session logging | [Tools & IPC](./docs/guide_tools.md#session-logging) | `src/session_logger.py` |
-| MMA dashboard & node editor | [MMA](./docs/guide_mma.md) | `src/gui_2.py:_render_mma_dashboard` |
-| Cross-tool abstractions (conductor) | [Meta-Boundary](./docs/guide_meta_boundary.md#the-cross-tool-abstractions) | `conductor/` |
-
-Subsystems marked "dedicated guide pending" are slated for dedicated `docs/guide_*.md` files in upcoming docs work. For now, their details live inline in the guides listed under [Documentation](#documentation) above.
+| [Architecture](./docs/guide_architecture.md) | Threading model, event system, AI client multi-provider architecture, HITL mechanism, comms logging |
+| [Tools & IPC](./docs/guide_tools.md) | MCP Bridge 3-layer security, 26 tool inventory, Hook API endpoints, ApiHookClient reference, shell runner |
+| [MMA Orchestration](./docs/guide_mma.md) | 4-tier hierarchy, Ticket/Track data structures, DAG engine, ConductorEngine, worker lifecycle, abort propagation |
+| [Simulations](./docs/guide_simulations.md) | `live_gui` fixture, Puppeteer pattern, mock provider, visual verification, ASTParser / summarizer |
+| [Meta-Boundary](./docs/guide_meta_boundary.md) | Application vs Meta-Tooling domains, inter-domain bridges, safety model separation |
 
 ---
 
@@ -170,13 +105,8 @@ api_key = "YOUR_KEY"
 
 [deepseek]
 api_key = "YOUR_KEY"
-
-[minimax]
-api_key = "YOUR_KEY"
 ```
 
-Each provider's key is loaded by the corresponding `_ensure_<provider>_client()` in `src/ai_client.py`. The `credentials.toml` is **blacklisted** by the MCP allowlist — AI tools cannot read it under any circumstance.
-
 ### Running
 
 ```powershell
@@ -215,59 +145,34 @@ The Multi-Model Agent system uses hierarchical task decomposition with specializ
 
 ## Module by Domain
 
-### src/ — Core implementation (53 modules)
+### src/ — Core implementation
 
 | File | Role |
 |---|---|
 | `src/gui_2.py` | Primary ImGui interface — App class, frame-sync, HITL dialogs, event system |
-| `src/app_controller.py` | Headless controller; bridges GUI and async AI workers |
 | `src/ai_client.py` | Multi-provider LLM abstraction (Gemini, Anthropic, DeepSeek, MiniMax) |
-| `src/mcp_client.py` | 45 MCP tools with 3-layer filesystem security and tool dispatch |
-| `src/api_hooks.py` | HookServer — REST API on `127.0.0.1:8999` for external automation |
-| `src/api_hook_client.py` | Python client for the Hook API (used by tests and external tooling) |
-| `src/multi_agent_conductor.py` | ConductorEngine — Tier 2 orchestration loop with DAG execution |
-| `src/dag_engine.py` | TrackDAG (dependency graph) + ExecutionEngine (tick-based state machine) |
-| `src/models.py` | Ticket, Track, WorkerContext, Metadata, Persona, WorkspaceProfile, etc. |
-| `src/events.py` | EventEmitter, AsyncEventQueue, UserRequestEvent |
-| `src/project_manager.py` | TOML config persistence, discussion management, track state |
-| `src/session_logger.py` | JSON-L + markdown audit trails (comms, tools, CLI, hooks) |
-| `src/rag_engine.py` | RAG subsystem (ChromaDB + embedding providers) |
-| `src/beads_client.py` | Beads/Dolt-backed issue tracking client |
-| `src/hot_reloader.py` | State-preserving module reloader |
-| `src/personas.py` | Unified agent profile manager |
-| `src/presets.py` | System prompt preset manager |
-| `src/context_presets.py` | Context composition preset manager |
-| `src/tool_presets.py` | Tool preset manager |
-| `src/tool_bias.py` | Tool bias engine (semantic nudging + dynamic strategy) |
-| `src/command_palette.py` | Command palette + fuzzy matcher + registry |
-| `src/commands.py` | 32 registered commands (toggle, theme, layout, AI, project, tools) |
-| `src/workspace_manager.py` | Workspace profile save/load with scope inheritance |
-| `src/theme_2.py` | Theme system (palette/font/etc.) |
-| `src/theme_nerv.py` | NERV Tactical Console theme |
-| `src/theme_nerv_fx.py` | NERV FX (scanlines, flicker, alert) |
-| `src/shell_runner.py` | PowerShell execution with timeout, env config, QA callback |
-| `src/file_cache.py` | ASTParser (tree-sitter) — skeleton, curated, targeted views |
-| `src/fuzzy_anchor.py` | Fuzzy anchor slice algorithm |
-| `src/history.py` | Undo/redo HistoryManager with UISnapshot |
-| `src/imgui_scopes.py` | ImGui context managers (imscope) for the UI delegation pattern |
-| `src/performance_monitor.py` | FPS, frame time, CPU, input lag tracking |
-| `src/log_registry.py` | Session metadata persistence |
-| `src/log_pruner.py` | Automated log cleanup based on age and whitelist |
-| `src/paths.py` | Centralized path resolution with environment variable overrides |
-| `src/cost_tracker.py` | Token cost estimation for API calls |
-| `src/gemini_cli_adapter.py` | CLI subprocess adapter with session management |
-| `src/mma_prompts.py` | Tier-specific system prompts for MMA orchestration |
-| `src/summarize.py` | Heuristic file summaries (imports, classes, functions) |
-| `src/outline_tool.py` | Hierarchical code outline via stdlib `ast` |
-| `src/summary_cache.py` | SHA256-keyed summary LRU cache |
-| `src/markdown_helper.py` | Markdown rendering helpers |
-| `src/patch_modal.py` | Patch approval modal |
-| `src/diff_viewer.py` | Diff rendering |
-| `src/external_editor.py` | External editor integration (VSCode, etc.) |
-| `src/orchestrator_pm.py` | Orchestrator project manager |
-| `src/conductor_tech_lead.py` | Tier 2 ticket generation from track briefs |
-| `src/synthesis_formatter.py` | Multi-take synthesis |
-| `src/thinking_parser.py` | AI thinking-trace extraction |
+| `src/mcp_client.py` |       26 MCP tools with filesystem sandboxing and tool dispatch |
+| `src/api_hooks.py`  |          HookServer — REST API on `127.0.0.1:8999 for external automation |
+| `src/api_hook_client.py` |       Python client for the Hook API (used by tests and external tooling) |
+| `src/multi_agent_conductor.py` |   ConductorEngine — Tier 2 orchestration loop with DAG execution  |
+| `src/conductor_tech_lead.py`  |   Tier 2 ticket generation from track briefs |
+| `src/dag_engine.py`  |       TrackDAG (dependency graph) + ExecutionEngine (tick-based state machine) |
+| `src/models.py`  |       Ticket, Track, WorkerContext, Metadata, Track state |
+| `src/events.py`  |           EventEmitter, AsyncEventQueue, UserRequestEvent |
+| `src/project_manager.py`  |       TOML config persistence, discussion management, track state |
+| `src/session_logger.py`  |       JSON-L + markdown audit trails (comms, tools, CLI, hooks) |
+| `src/shell_runner.py`  |       PowerShell execution with timeout, env config, QA callback |
+| `src/file_cache.py`  |       ASTParser (tree-sitter) — skeleton, curated, and targeted views |
+| `src/summarize.py`  |       Heuristic file summaries (imports, classes, functions) |
+| `src/outline_tool.py`  |       Hierarchical code outline via stdlib `ast` |
+| `src/performance_monitor.py`  |       FPS, frame time, CPU, input lag tracking |
+| `src/log_registry.py`  |       Session metadata persistence |
+| `src/log_pruner.py`  |       Automated log cleanup based on age and whitelist |
+| `src/paths.py`  |       Centralized path resolution with environment variable overrides |
+| `src/cost_tracker.py`  |       Token cost estimation for API calls |
+| `src/gemini_cli_adapter.py`  |       CLI subprocess adapter with session management |
+| `src/mma_prompts.py`  |       Tier-specific system prompts for MMA orchestration |
+| `src/theme_*.py` |        UI theming (dark, light modes) |
 
 Simulation modules in `simulation/`:
 | File | Role |

_manual_run.py

@@ -1,133 +0,0 @@
-"""Manually start sloppy.py, then run the test against the same GUI process."""
-import subprocess
-import os
-import sys
-import time
-import socket
-from pathlib import Path
-
-# Start sloppy.py
-project_root = Path("C:/projects/manual_slop").absolute()
-gui_script = project_root / "sloppy.py"
-test_workspace = project_root / "tests" / "artifacts" / "live_gui_workspace"
-
-# Clean up old workspace
-if test_workspace.exists():
-    import shutil
-    for _ in range(5):
-        try:
-            shutil.rmtree(test_workspace)
-            break
-        except PermissionError:
-            time.sleep(0.5)
-
-test_workspace.mkdir(parents=True, exist_ok=True)
-
-# Create minimal files
-(test_workspace / "manual_slop.toml").write_text("[project]\nname = 'TestProject'\n\n[conductor]\ndir = 'conductor'\n", encoding="utf-8")
-(test_workspace / "conductor" / "tracks").mkdir(parents=True, exist_ok=True)
-
-config_content = {
-    'ai': {'provider': 'gemini', 'model': 'gemini-2.5-flash-lite'},
-    'projects': {
-        'paths': [str((test_workspace / 'manual_slop.toml').absolute())],
-        'active': str((test_workspace / 'manual_slop.toml').absolute())
-    },
-    'paths': {
-        'logs_dir': str((test_workspace / "logs").absolute()),
-        'scripts_dir': str((test_workspace / "scripts" / "generated").absolute())
-    },
-}
-import tomli_w
-with open(test_workspace / 'config.toml', 'wb') as f:
-    tomli_w.dump(config_content, f)
-
-# Start sloppy.py
-os.makedirs("logs", exist_ok=True)
-log_file = open("logs/sloppy_py_test_2.log", "w", encoding="utf-8")
-env = os.environ.copy()
-env["PYTHONPATH"] = str(project_root.absolute())
-env["SLOP_CONFIG"] = str((test_workspace / "config.toml").absolute())
-env["SLOP_GLOBAL_PRESETS"] = str((test_workspace / "presets.toml").absolute())
-env["SLOP_GLOBAL_TOOL_PRESETS"] = str((test_workspace / "tool_presets.toml").absolute())
-
-print("Starting sloppy.py...")
-proc = subprocess.Popen(
-    ["uv", "run", "python", "-u", str(gui_script), "--enable-test-hooks"],
-    stdout=log_file,
-    stderr=log_file,
-    text=True,
-    cwd=str(test_workspace.absolute()),
-    env=env,
-    creationflags=subprocess.CREATE_NEW_PROCESS_GROUP if os.name == 'nt' else 0
-)
-print(f"Started PID: {proc.pid}")
-
-# Wait for hook server
-import requests
-for i in range(30):
-    try:
-        resp = requests.get("http://127.0.0.1:8999/status", timeout=0.5)
-        if resp.status_code == 200:
-            print(f"Hook server ready after {i*0.5}s")
-            break
-    except Exception:
-        time.sleep(0.5)
-else:
-    print("Hook server didn't start!")
-    proc.kill()
-    sys.exit(1)
-
-# Wait extra for imgui to fully initialize
-print("Waiting 3s for imgui to stabilize...")
-time.sleep(3.0)
-
-# Now run the actual test flow
-from src.api_hook_client import ApiHookClient
-client = ApiHookClient()
-
-print("\n[1] set_value show_windows {Diagnostics: True}")
-client.set_value('show_windows', {'Diagnostics': True})
-time.sleep(1.0)
-
-print("\n[2] push_event save_workspace_profile")
-client.push_event('custom_callback', {'callback': 'save_workspace_profile', 'args': ['Tier3Profile', 'project']})
-time.sleep(1.0)
-
-print("\n[3] set_value show_windows {Diagnostics: False}")
-client.set_value('show_windows', {'Diagnostics': False})
-
-print("\n[4] set_value ui_auto_switch_layout")
-client.set_value('ui_auto_switch_layout', True)
-
-print("\n[5] set_value ui_tier_layout_bindings")
-client.set_value('ui_tier_layout_bindings', {'Tier 1': '', 'Tier 2': '', 'Tier 3': 'Tier3Profile', 'Tier 4': ''})
-
-def trigger_tier(tier):
-    client.push_event("mma_state_update", {"status": "running", "active_tier": tier})
-
-print("\n[6] trigger Tier 2")
-trigger_tier('Tier 2 (Tech Lead)')
-time.sleep(1.0)
-val = client.get_value('show_windows')
-print(f"[after Tier 2] show_windows: {val!r}")
-assert val is not None, "show_windows is None"
-assert val.get('Diagnostics', False) == False, f"Expected False, got {val}"
-
-print("\n[7] trigger Tier 3")
-trigger_tier('Tier 3 (Worker): task-1')
-time.sleep(1.0)
-val = client.get_value('show_windows')
-print(f"[after Tier 3] show_windows: {val!r}")
-assert val.get('Diagnostics', False) == True, f"Expected True, got {val}"
-
-print("\nALL ASSERTIONS PASSED!")
-
-# Cleanup
-print("Killing sloppy.py...")
-proc.kill()
-try:
-    proc.wait(timeout=5)
-except:
-    pass
-log_file.close()

check_hello_imgui.py

@@ -0,0 +1,9 @@
+
+import sys
+import os
+try:
+ from imgui_bundle import hello_imgui
+ rp = hello_imgui.RunnerParams()
+ print(f"Default borderless: {rp.app_window_params.borderless}")
+except Exception as e:
+ print(f"Error: {e}")

conductor/archive/aggregation_smarter_summaries_20260322/metadata.json

@@ -1,17 +0,0 @@
-{
-  "name": "aggregation_smarter_summaries",
-  "created": "2026-03-22",
-  "status": "future",
-  "priority": "medium",
-  "affected_files": [
-    "src/aggregate.py",
-    "src/file_cache.py",
-    "src/ai_client.py",
-    "src/models.py"
-  ],
-  "related_tracks": [
-    "discussion_hub_panel_reorganization (in_progress)",
-    "system_context_exposure (future)"
-  ],
-  "notes": "Deferred from discussion_hub_panel_reorganization planning. Improves aggregation with sub-agent summarization and hash-based caching."
-}

conductor/archive/aggregation_smarter_summaries_20260322/plan.md

@@ -1,49 +0,0 @@
-# Implementation Plan: Smarter Aggregation with Sub-Agent Summarization
-
-## Phase 1: Hash-Based Summary Cache [checkpoint: e972cf4]
-Focus: Implement file hashing and cache storage
-
-- [x] Task: Research existing file hash implementations in codebase 3218104
-- [x] Task: Design cache storage format (file-based vs project state) 3218104
-- [x] Task: Implement hash computation for aggregation files 3218104
-- [x] Task: Implement summary cache storage and retrieval 3218104
-- [x] Task: Add cache invalidation when file content changes 3218104
-- [x] Task: Write tests for hash computation and cache 3218104
-- [x] Task: Conductor - User Manual Verification 'Phase 1: Hash-Based Summary Cache' e972cf4
-
-## Phase 2: Sub-Agent Summarization [checkpoint: 7efcc7c]
-Focus: Implement sub-agent summarization during aggregation
-
-- [x] Task: Audit current aggregate.py flow 3218104
-- [x] Task: Define summarization prompt strategy for code vs text files 3218104
-- [x] Task: Implement sub-agent invocation during aggregation 3218104
-- [x] Task: Handle provider-specific differences in sub-agent calls 3218104
-- [x] Task: Write tests for sub-agent summarization 3218104
-- [x] Task: Conductor - User Manual Verification 'Phase 2: Sub-Agent Summarization' 7efcc7c
-
-## Phase 3: Tiered Aggregation Strategy [checkpoint: fa00a84]
-Focus: Respect tier-level aggregation configuration
-
-- [x] Task: Audit how tiers receive context currently 628b580
-- [x] Task: Implement tier-level aggregation strategy selection 628b580
-- [x] Task: Connect tier strategy to Persona configuration 628b580
-- [x] Task: Write tests for tiered aggregation 628b580
-- [x] Task: Conductor - User Manual Verification 'Phase 3: Tiered Aggregation Strategy' fa00a84
-
-## Phase 4: UI Integration [checkpoint: a1c204f]
-Focus: Expose cache status and controls in UI
-
-- [x] Task: Add cache status indicator to Files & Media panel 6bf6c79
-- [x] Task: Add "Clear Summary Cache" button 6bf6c79
-- [x] Task: Add aggregation configuration to Project Settings or AI Settings 6bf6c79
-- [x] Task: Write tests for UI integration 6bf6c79
-- [x] Task: Conductor - User Manual Verification 'Phase 4: UI Integration' a1c204f
-
-## Phase 5: Cache Persistence & Optimization [checkpoint: e0737dc]
-Focus: Ensure cache persists and is performant
-
-- [x] Task: Implement persistent cache storage to disk fb2df2a
-- [x] Task: Add cache size management (max entries, LRU) fb2df2a
-- [x] Task: Performance testing with large codebases fb2df2a
-- [x] Task: Write tests for persistence fb2df2a
-- [x] Task: Conductor - User Manual Verification 'Phase 5: Cache Persistence & Optimization' e0737dc

conductor/archive/aggregation_smarter_summaries_20260322/spec.md

@@ -1,103 +0,0 @@
-# Specification: Smarter Aggregation with Sub-Agent Summarization
-
-## 1. Overview
-
-This track improves the context aggregation system to use sub-agent passes for intelligent summarization and hash-based caching to avoid redundant work.
-
-**Current Problem:**
-- Aggregation is a simple pass that either injects full file content or a basic skeleton
-- No intelligence applied to determine what level of detail is needed
-- Same files get re-summarized on every discussion start even if unchanged
-
-**Goal:**
-- Use a sub-agent during aggregation pass for high-tier agents to generate succinct summaries
-- Cache summaries based on file hash - only re-summarize if file changed
-- Smart outline generation for code files, summary for text files
-
-## 2. Current State Audit
-
-### Existing Aggregation Behavior
-- `aggregate.py` handles context aggregation
-- `file_cache.py` provides AST parsing and skeleton generation
-- Per-file flags: `Auto-Aggregate` (summarize), `Force Full` (inject raw)
-- No caching of summarization results
-
-### Provider API Considerations
-- Different providers have different prompt/caching mechanisms
-- Need to verify how each provider handles system context and caching
-- May need provider-specific aggregation strategies
-
-## 3. Functional Requirements
-
-### 3.1 Hash-Based Summary Cache
-- Generate SHA256 hash of file content
-- Store summaries in a cache (file-based or in project state)
-- Before summarizing, check if file hash matches cached summary
-- Cache invalidation when file content changes
-
-### 3.2 Sub-Agent Summarization Pass
-- During aggregation, optionally invoke sub-agent for summarization
-- Sub-agent generates concise summary of file purpose and key points
-- Different strategies for:
-  - Code files: AST-based outline + key function signatures
-  - Text files: Paragraph-level summary
-  - Config files: Key-value extraction
-
-### 3.3 Tiered Aggregation Strategy
-- Tier 3/4 workers: Get skeleton outlines (fast, cheap)
-- Tier 2 (Tech Lead): Get summaries with key details
-- Tier 1 (Orchestrator): May get full content or enhanced summaries
-- Configurable per-agent via Persona
-
-### 3.4 Cache Persistence
-- Summaries persist across sessions
-- Stored in project directory or centralized cache location
-- Manual cache clear option in UI
-
-## 4. Data Model
-
-### 4.1 Summary Cache Entry
-```python
-{
-    "file_path": str,
-    "file_hash": str,  # SHA256 of content
-    "summary": str,
-    "outline": str,  # For code files
-    "generated_at": str,  # ISO timestamp
-    "generator_tier": str,  # Which tier generated it
-}
-```
-
-### 4.2 Aggregation Config
-```toml
-[aggregation]
-default_mode = "summarize"  # "full", "summarize", "outline"
-cache_enabled = true
-cache_dir = ".slop_cache"
-```
-
-## 5. UI Changes
-
-- Add "Clear Summary Cache" button in Files & Media or Context Composition
-- Show cached status indicator on files (similar to AST cache indicator)
-- Configuration in AI Settings or Project Settings
-
-## 6. Acceptance Criteria
-
-- [ ] File hash computed before summarization
-- [ ] Summary cache persists across app restarts
-- [ ] Sub-agent generates better summaries than basic skeleton
-- [ ] Aggregation respects tier-level configuration
-- [ ] Cache can be manually cleared
-- [ ] Provider APIs handle aggregated context correctly
-
-## 7. Out of Scope
-- Changes to provider API internals
-- Vector store / embeddings for RAG (separate track)
-- Changes to Session Hub / Discussion Hub layout
-
-## 8. Dependencies
-- `aggregate.py` - main aggregation logic
-- `file_cache.py` - AST parsing and caching
-- `ai_client.py` - sub-agent invocation
-- `models.py` - may need new config structures

conductor/archive/ai_interaction_call_graph_20260507/OPTIMIZATION_TARGETS.md

@@ -1,23 +0,0 @@
-# AI Loop: Optimization & Consolidation Targets
-
-Based on the technical trace and sequence mapping of the AI interaction loop, the following areas are identified as primary targets for "Heavy Curation".
-
-### 1. Unified Provider Loop (`ai_client.py`)
-- **Observation:** `_send_anthropic`, `_send_gemini`, and `_send_gemini_cli` all implement their own `for r_idx in range(MAX_TOOL_ROUNDS + 2)` loops.
-- **Problem:** Significant boilerplate duplication for tool execution, error handling, and file re-reading.
-- **Curation Goal:** Refactor the multi-turn recursion into a single `_base_send_loop` method that takes a provider-specific `generate_turn` callback.
-
-### 2. Threading Model Management (`app_controller.py`)
-- **Observation:** `_process_event_queue` spawns a new `threading.Thread` for every `user_request`.
-- **Problem:** Potential for thread explosion if multiple asynchronous requests are triggered rapidly (though rare in typical usage).
-- **Curation Goal:** Consolidate into a single dedicated "AI Worker" thread with a task queue, or use a small `ThreadPoolExecutor` to manage background lifetimes.
-
-### 3. Redundant Context Markers
-- **Observation:** `_FILE_REFRESH_MARKER` and `_get_context_marker()` are used in multiple places to inject diffs.
-- **Problem:** String duplication and fragmented logic for deciding when to "refresh" the AI's file context.
-- **Curation Goal:** Centralize the context-refresh injection logic within the `aggregate` module or a dedicated `ContextRefresher` class.
-
-### 4. Blocking Call Audit
-- **Observation:** `asyncio.run_coroutine_threadsafe(...).result()` is used to call async tool logic from the sync worker thread.
-- **Problem:** This bridge is technically correct but adds complexity.
-- **Curation Goal:** If possible, move more of the AI loop logic into a proper `async` context to avoid the `.result()` blocking pattern.

conductor/archive/ai_interaction_call_graph_20260507/SEQUENCE_DIAGRAM.md

@@ -1,86 +0,0 @@
-# AI Interaction Pipeline: Intensive Technical Trace
-
-This document provides a low-level technical trace of the AI interaction loop, following a pipeline-oriented architectural model. It identifies thread context switches, data transformation overhead, and synchronization bottlenecks.
-
-## 1. Sequence Diagram: Asynchronous Interaction Pipeline
-
-```mermaid
-sequenceDiagram
-    autonumber
-    participant UI as gui_2.py (Main/Render Thread)
-    participant EV as app_controller.py (Event Dispatcher)
-    participant WK as ai_client.py (Worker Thread Pool)
-    participant AI as ai_client.py (Provider Pipeline)
-    participant MCP as mcp_client.py (FileSystem Pipeline)
-    participant SR as shell_runner.py (Subprocess Pipeline)
-
-    Note over UI, WK: [Phase A: Request Initiation]
-    UI->>EV: SyncEventQueue.put("user_request", dict)
-    Note right of UI: Data: Raw Prompt + Context Pointers
-    EV->>EV: polling loop (event_queue.get())
-    EV->>WK: threading.Thread(target=_handle_request_event).start()
-    Note right of EV: Context Switch: Event Thread -> AI Worker Thread
-
-    Note over WK, AI: [Phase B: Context Synthesis & Generation]
-    WK->>AI: ai_client.send(md_content, history)
-    AI->>AI: _build_chunked_context_blocks()
-    Note right of AI: Perf: O(N) string concatenation + regex scans
-    AI->>Vendor: Provider API Request (HTTPS/JSON)
-    Note right of AI: Bottleneck: Network Latency (1-30s)
-    Vendor-->>AI: ToolCall(s) or StopReason
-
-    Note over AI, SR: [Phase C: Multi-Turn Tool Execution Loop]
-    loop MAX_TOOL_ROUNDS (r_idx <= 10)
-        alt Tool Use Detected
-            AI->>WK: _execute_tool_calls_concurrently()
-            
-            alt Read-Only (MCP)
-                WK->>MCP: read_file / list_dir / search
-                MCP-->>WK: stdout_string
-            else Mutating (Shell)
-                WK->>EV: _pending_gui_tasks.append(approval_modal)
-                Note over UI: UI Polling Detects Task
-                UI->>UI: Render ImGui Popup (Wait for HITL)
-                Note over UI: User Approval Interaction
-                UI-->>WK: threading.Condition.notify()
-                Note right of WK: Resume AI Worker Thread
-                WK->>SR: run_powershell(script)
-                SR->>OS: Subprocess Spawn (powershell.exe)
-                OS-->>SR: stdout/stderr (JSON-L Stream)
-                SR-->>WK: COMBINED_OUTPUT_STRING
-            end
-            
-            WK-->>AI: Aggregate Tool Results
-            AI->>AI: _reread_file_items() (Context Refresh)
-            Note right of AI: Perf: IO Bound (File MTime Scans)
-            AI->>Vendor: Follow-up Prompt (with Tool Result)
-        else Terminal Text
-            AI-->>WK: Final AI Response Text
-        end
-    end
-
-    Note over WK, UI: [Phase D: Result Synchronization]
-    WK->>EV: SyncEventQueue.put("response", result)
-    EV->>EV: _pending_gui_tasks.append(response_obj)
-    loop Every Frame (~16.6ms)
-        UI->>EV: _process_pending_gui_tasks()
-        Note right of UI: Data Copy: Controller State -> UI History Buffer
-        UI->>UI: Update Rendering State (Markdown/Syntax Highlight)
-    end
-```
-
-## 2. Technical Performance Audit
-
-### 2.1 Threading & Synchronization
-- **Context Switches:** The pipeline traverses four distinct execution contexts: Main Thread -> Event Thread -> Daemon Worker -> Subprocess.
-- **Lock Contention:** `_pending_gui_tasks_lock` is acquired twice per AI response turn (once by background thread to append, once by UI thread to process).
-- **Blocking Sites:** `ai_client.send` blocks the dedicated `WK` thread. `_confirm_and_run` blocks the `WK` thread using a `Condition` variable waiting on UI input.
-
-### 2.2 Data Transformation Costs
-- **Context Bloat:** `md_content` is a monolithic string. During synthesis, this string is often copied or chunked (`_chunk_text`), increasing memory pressure on the Python heap.
-- **Serialization Overhead:** Every tool call involves: Python dict -> JSON String -> Subprocess Stdin -> (Tools) -> Subprocess Stdout -> JSON String -> Python dict.
-
-### 2.3 Curation Targets (Intensive)
-1. **Reduce Memory Copies:** The monolithic Markdown context should be handled as a stream or a shared buffer to avoid redundant copies between `aggregate` and `ai_client`.
-2. **Deterministic Status Polling:** Replace string-based status polling (`ai_status`) with an enum-based state machine to reduce regex comparisons in the simulator and UI.
-3. **Subprocess Pooling:** `shell_runner` spawns a new process for every script. For high-frequency tool use, a persistent PowerShell session could reduce overhead.

conductor/archive/ai_interaction_call_graph_20260507/metadata.json

@@ -1,8 +0,0 @@
-{
-  "track_id": "ai_interaction_call_graph_20260507",
-  "type": "chore",
-  "status": "new",
-  "created_at": "2026-05-07T16:00:00Z",
-  "updated_at": "2026-05-07T16:00:00Z",
-  "description": "Exhaustive function-to-function call graph tracing the AI loop from request to terminal execution."
-}

conductor/archive/ai_interaction_call_graph_20260507/plan.md

@@ -1,22 +0,0 @@
-# Implementation Plan: AI Interaction Call Graph (ai_interaction_call_graph_20260507)
-
-## Phase 1: Trace Mapping
-- [x] Task: Use `py_find_usages` to trace `ai_client.send` callers and callees.
-- [x] Task: Map the asynchronous hand-off from `AppController` to the AI worker threads.
-- [x] Task: Trace the recursion depth of the tool-call loop (`MAX_TOOL_ROUNDS`).
-
-## Phase 2: Documentation & Synthesis
-- [x] Task: Create a high-fidelity Mermaid sequence diagram of the entire loop.
-- [x] Task: Identify specific areas for logic consolidation or performance optimization.
-
-## Phase 3: Automated Path Derivation Tooling
-- [x] Task: Develop `derive_code_path` MCP tool using tree-sitter.
-- [~] Task: Implement cross-file call-chain tracing and data hand-off detection.
-- [ ] Task: Verify tool output against the manual AI Loop trace.
-
-## Phase 4: Comprehensive Pipeline Mapping
-- [x] Task: Map the **Context Aggregation Pipeline** using the new tool.
-- [x] Task: Map the **GUI Event & State Synchronization** pipeline.
-- [x] Task: Map the **Simulation Lifecycle** and turn-loop.
-- [x] Task: Consolidate all intensive traces into a final Phase 5 Architectural Audit.
-- [x] Task: Conductor - User Manual Verification 'Final Audit' (Protocol in workflow.md)

conductor/archive/ai_interaction_call_graph_20260507/spec.md

@@ -1,22 +0,0 @@
-# Specification: AI Interaction Call Graph (ai_interaction_call_graph_20260507)
-
-## Overview
-A low-level technical trace of the AI interaction loop. The goal is to map every single function call and data hand-off from the moment a user message is sent to the final terminal execution of a PowerShell script or tool result.
-
-## Scope
-- **Entry Point:** `src/gui_2.py:App._render_discussion_panel` (Send button action).
-- **Subsystems:** `ai_client.py`, `mcp_client.py`, `shell_runner.py`, `app_controller.py`.
-
-## Functional Requirements
-1. **Call Graph Generation:**
-   - Document the sequence of synchronous and asynchronous calls.
-   - Identify thread boundaries (GUI thread vs. Background worker thread).
-2. **Data Transformation Trace:**
-   - Track the transformation of a message: raw text -> GenerateRequest -> AI History -> Provider Prompt -> AI Response -> Tool Call -> PS Script.
-3. **Error & Retry Paths:**
-   - Map how exceptions are caught, classified, and bubbled back to the UI.
-
-## Acceptance Criteria
-- [ ] Detailed call graph in Mermaid format.
-- [ ] List of all internal private methods involved in the loop.
-- [ ] Identification of any blocking calls in the async pipeline.

conductor/archive/app_controller_curation_20260513/extraction_list.md

@@ -1,64 +0,0 @@
-# AppController Extraction List
-
-## 1. Move to `src/models.py`
-- `GenerateRequest` (BaseModel)
-- `ConfirmRequest` (BaseModel)
-
-## 2. Extraction to Module Level (Functions taking `controller: AppController`)
-
-### From `create_api`
-- `get_api_key`
-- `health`
-- `get_gui_state`
-- `get_mma_status`
-- `post_gui`
-- `get_api_session`
-- `post_api_session`
-- `get_api_project`
-- `get_performance`
-- `get_diagnostics`
-- `status`
-- `generate`
-- `stream`
-- `pending_actions`
-- `confirm_action`
-- `list_sessions`
-- `get_session`
-- `delete_session`
-- `get_context`
-- `token_stats`
-
-### From `_process_pending_gui_tasks` (Handlers)
-- `_handle_refresh_api_metrics`
-- `_handle_set_ai_status`
-- `_handle_set_mma_status`
-- `_handle_ai_response`
-- `_handle_mma_state_update`
-- `_handle_set_value`
-- `_handle_click`
-- `_handle_drag`
-- `_handle_right_click`
-- `_handle_select_list_item`
-- `_handle_ask_dialog`
-- `_handle_custom_callback`
-- `_handle_mma_step_approval`
-- `_handle_mma_spawn_approval`
-- `_handle_ticket_started`
-- `_handle_ticket_completed`
-- `_handle_bead_updated`
-
-### From `cb_load_prior_log`
-- `_resolve_log_ref`
-
-## 3. Extraction to Module Level (Independent Utilities)
-- `parse_symbols` (Already module level)
-- `get_symbol_definition` (Already module level)
-- `_extract_tool_name`
-- `_offload_entry_payload`
-
-## 4. Classes to Top-Level
-- `ConfirmDialog`
-- `MMAApprovalDialog`
-- `MMASpawnApprovalDialog`
-- `AutoStepDialog` (From `_process_pending_gui_tasks`)
-- `AutoSpawnDialog` (From `_process_pending_gui_tasks`)

conductor/archive/app_controller_curation_20260513/metadata.json

@@ -1,7 +0,0 @@
-{
-  "track_id": "app_controller_curation_20260513",
-  "title": "AppController Curation & Structural Alignment",
-  "status": "in_progress",
-  "initialized": "2026-05-13",
-  "goal": "Curate src/app_controller.py to match gui_2.py organization and enforce Python style conventions."
-}

conductor/archive/app_controller_curation_20260513/plan.md

@@ -1,19 +0,0 @@
-# Implementation Plan: AppController Curation [checkpoint: fa4388b]
-
-## Phase 1: Structural Audit & Conventions Update [checkpoint: 511aabb]
-- [x] Task: Audit `src/app_controller.py` against `gui_2.py` organization and the Python Style Guide. [511aabb]
-- [x] Task: Identify methods for extraction to module level (Anti-OOP enforcement). [511aabb]
-- [x] Task: Update `conductor/code_styleguides/python.md` or `product-guidelines.md` if any new nuances are discovered in `gui_2.py`. [511aabb]
-- [x] Task: Conductor - User Manual Verification 'Phase 1: Structural Audit' (Protocol in workflow.md) [511aabb]
-
-## Phase 2: Refactoring & Curation [checkpoint: fa4388b]
-- [x] Task: Apply 1-space indentation and remove excessive blank lines in `src/app_controller.py`. [fa4388b]
-- [x] Task: Clean up and organize `AppController.__init__` state declarations. [fa4388b]
-- [x] Task: Implement missing type hints and SDM tags. [fa4388b]
-- [x] Task: Extract identified logic to module-level functions. [fa4388b]
-- [x] Task: Conductor - User Manual Verification 'Phase 2: Refactoring & Curation' (Protocol in workflow.md) [fa4388b]
-
-## Phase 3: Validation & Regression Testing [checkpoint: fa4388b]
-- [x] Task: Run the full test suite in batches of 4 files per test run. [fa4388b]
-- [x] Task: Fix any regressions or type errors discovered during testing. [fa4388b]
-- [x] Task: Conductor - User Manual Verification 'Phase 3: Validation & Regression Testing' (Protocol in workflow.md) [fa4388b]

conductor/archive/app_controller_curation_20260513/spec.md

@@ -1,21 +0,0 @@
-# Specification: AppController Curation & Structural Alignment
-
-## Context
-Following the successful cleanup and refactoring of `gui_2.py`, the same organizational patterns and AI-optimized coding conventions must be applied to `src/app_controller.py`. This module is a critical part of the Manual Slop architecture, acting as the bridge between the GUI and the underlying AI/MCP systems.
-
-## Goals
-1. **Structural Parity:** Reorganize `src/app_controller.py` to match the structure and quality of `gui_2.py`.
-2. **Standardization:** Enforce the AI-Optimized Python Style Guide (1-space indent, minimal blank lines, type hints, SDM tags).
-3. **Refactoring:** Identify and extract logic that violates the 5-level nesting limit or is better suited as module-level functions.
-4. **Validation:** Ensure full system integrity via the comprehensive test suite, run in batches of 4.
-
-## Scope
-- `src/app_controller.py`: Primary target for refactoring and curation.
-- `conductor/code_styleguides/python.md`: Potential updates if new nuances are found.
-- `conductor/product-guidelines.md`: Potential updates based on structural findings.
-
-## Constraints
-- **Indentation:** Must be exactly 1 space.
-- **Scoping:** Use `imscope` for any ImGui-related calls if present (though `app_controller` should ideally be logic-focused, some status rendering might exist).
-- **Anti-OOP:** Move state-independent methods to module level.
-- **Type Safety:** 100% type hint coverage for all modified sections.

conductor/archive/approve_modal_ux_20260601/index.md

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

conductor/archive/approve_modal_ux_20260601/metadata.json

@@ -1,8 +0,0 @@
-{
-  "track_id": "approve_modal_ux_20260601",
-  "type": "bug",
-  "status": "new",
-  "created_at": "2026-06-01T00:00:00Z",
-  "updated_at": "2026-06-01T00:00:00Z",
-  "description": "Fix Approve Modal sizing and inline full preview"
-}

conductor/archive/approve_modal_ux_20260601/plan.md

@@ -1,17 +0,0 @@
-# Implementation Plan: Approve Modal UX Fixes
-
-## Phase 1: Modal Layout Updates
-- [ ] Task: Make Modal Resizable
-    - [ ] In `src/gui_2.py` (`render_approve_script_modal`), set `imgui.set_next_window_size(imgui.ImVec2(800, 600), imgui.Cond_.first_use_ever)`.
-    - [ ] Change `imgui.WindowFlags_.always_auto_resize` to `0` in `imgui.begin_popup_modal`.
-- [ ] Task: Fix Full Preview and Input Height
-    - [ ] Add `ui_approve_modal_preview = False` to `App.__init__`.
-    - [ ] Replace `app.show_windows["Text Viewer"]` checkbox logic in `render_approve_script_modal` with `app.ui_approve_modal_preview`.
-    - [ ] When `app.ui_approve_modal_preview` is True, render the script in a read-only child or using `markdown_helper`.
-    - [ ] When False, set the `imgui.input_text_multiline` height to dynamically fill the remaining space (`imgui.ImVec2(-1, -40)` or similar).
-
-## Phase 2: Verification
-- [ ] Task: Verification
-    - [ ] Trigger a script approval and resize the modal.
-    - [ ] Toggle "Show Full Preview" and ensure it renders within the modal safely.
-- [ ] Task: Conductor - User Manual Verification 'Phase 2: Verification' (Protocol in workflow.md)

conductor/archive/approve_modal_ux_20260601/spec.md

@@ -1,16 +0,0 @@
-# Specification: Approve Modal UX Fixes
-
-## 1. Overview
-The "Approve PowerShell Command" modal is currently too small and cannot be resized. Additionally, the "Show Full Preview" option triggers the external "Text Viewer" window, which cannot be interacted with because the modal blocks all background UI inputs.
-
-## 2. Functional Requirements
-*   **Resizable Modal:** The modal must allow user resizing and should have a larger default minimum size.
-*   **Inline Preview:** The "Show Full Preview" option must render the full script *inside* the modal itself (e.g., as a read-only scrollable child or markdown block), rather than triggering an external window.
-*   **Responsive Input:** The script input text area should expand to fill the available vertical space of the modal, rather than being fixed to 200px.
-
-## 3. Non-Functional Requirements
-*   The modal must continue to reliably block the execution thread until the user approves or rejects the script.
-
-## 4. Acceptance Criteria
-*   The modal can be resized by dragging the corners.
-*   Clicking "Show Full Preview" toggles an inline preview without locking the UI.

conductor/archive/archive_phase_4_tracks_20260507/index.md

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

conductor/archive/archive_phase_4_tracks_20260507/metadata.json

@@ -1,8 +0,0 @@
-{
-  "track_id": "archive_phase_4_tracks_20260507",
-  "type": "chore",
-  "status": "new",
-  "created_at": "2026-05-07T14:00:00Z",
-  "updated_at": "2026-05-07T14:00:00Z",
-  "description": "Review and archive all completed from phase 4."
-}

conductor/archive/archive_phase_4_tracks_20260507/plan.md

@@ -1,13 +0,0 @@
-# Implementation Plan: Phase 4 Track Archival (archive_phase_4_tracks_20260507)
-
-## Phase 1: Directory Migration [checkpoint: 2065dd8]
-- [x] Task: Identify and list all completed Phase 4 track directories.
-- [x] Task: Move identified track directories from `conductor/tracks/` to `conductor/archive/`.
-- [x] Task: Conductor - User Manual Verification 'Directory Migration' (Protocol in workflow.md)
-
-## Phase 2: Registry Update [checkpoint: 9f2390d]
-- [x] Task: Create 'Phase 4 Archive' section in `conductor/tracks.md`.
-- [x] Task: Move track entries from Phase 4 sections to 'Phase 4 Archive' section.
-- [x] Task: Update track links in `conductor/tracks.md` to point to the `archive/` directory.
-- [x] Task: Verify link integrity in `conductor/tracks.md` (manual or via script).
-- [x] Task: Conductor - User Manual Verification 'Registry Update' (Protocol in workflow.md)

conductor/archive/archive_phase_4_tracks_20260507/spec.md

@@ -1,28 +0,0 @@
-# Specification: Phase 4 Track Archival (archive_phase_4_tracks_20260507)
-
-## Overview
-This track involves archiving all completed tracks from Phase 4 to maintain a clean and focused `tracks.md` registry and `tracks/` directory.
-
-## Scope
-- **Target Tracks:** All tracks under "Phase 4: High-Fidelity UX & Tools" in `conductor/tracks.md` that are marked as completed `[x]`.
-- **Destination:** `conductor/archive/<track_id>/`.
-- **Registry Update:** `conductor/tracks.md`.
-
-## Functional Requirements
-1. **Directory Migration:**
-   - Move each completed Phase 4 track directory from `conductor/tracks/` to `conductor/archive/`.
-2. **Registry Reorganization:**
-   - Create a new section in `conductor/tracks.md` titled "Phase 4 Archive".
-   - Move all completed Phase 4 track entries (text and links) from their current locations in `tracks.md` to this new section.
-   - Update the links for these tracks to point to the new location: `[./archive/<track_id>/](./archive/<track_id>/)`.
-
-## Non-Functional Requirements
-- Maintain link integrity within `tracks.md`.
-- Ensure no active or incomplete tracks are accidentally moved.
-
-## Acceptance Criteria
-- [ ] All completed Phase 4 track directories are present in `conductor/archive/`.
-- [ ] No completed Phase 4 track directories remain in `conductor/tracks/`.
-- [ ] `conductor/tracks.md` has a "Phase 4 Archive" section containing all moved tracks.
-- [ ] All links in the new "Phase 4 Archive" section are functional and point to the correct subdirectories in `archive/`.
-- [ ] Active Phase 4 tracks remain in their original sections and point to `tracks/`.

conductor/archive/beads_mode_20260309/plan.md

@@ -1,27 +0,0 @@
-# Implementation Plan: Beads Mode Integration
-
-## Phase 1: Environment & Core Configuration
-- [x] Task: Audit existing `AppController` and `project_manager.py` for project mode handling.
-- [x] Task: Write Tests: Verify `manual_slop.toml` can parse and store the `execution_mode` (native/beads).
-- [x] Task: Implement: Add `execution_mode` toggle to `AppController` state and persistence logic.
-- [x] Task: Conductor - User Manual Verification 'Phase 1: Environment & Core Configuration' (Protocol in workflow.md)
-
-## Phase 2: Beads Backend & Tooling
-- [x] Task: Write Tests: Verify a basic Beads/Dolt repository can be initialized and queried via a Python wrapper.
-- [x] Task: Implement: Create `src/beads_client.py` to interface with the `bd` CLI or direct Dolt SQL backend.
-- [x] Task: Write Tests: Verify agents can create and update Beads using a mock Beads environment.
-- [x] Task: Implement: Add a suite of MCP tools (`bd_create`, `bd_update`, `bd_ready`, `bd_list`) to `src/mcp_client.py`.
-- [x] Task: Conductor - User Manual Verification 'Phase 2: Beads Backend & Tooling' (Protocol in workflow.md)
-
-## Phase 3: GUI Integration & Visual DAG
-- [x] Task: Write Tests: Verify the Visual DAG can load node data from a non-markdown source (Beads graph).
-- [x] Task: Implement: Refactor `_render_mma_dashboard` and the DAG renderer to pull from the active mode's backend.
-- [x] Task: Implement: Add a "Beads" tab to the MMA Dashboard for browsing the raw Dolt-backed issue graph.
-- [x] Task: Implement: Update Tier Streams to include metadata for Beads-specific status changes.
-- [x] Task: Conductor - User Manual Verification 'Phase 3: GUI Integration & Visual DAG' (Protocol in workflow.md)
-
-## Phase 4: Context Optimization & Polish
-- [x] Task: Write Tests: Verify that "Compaction" correctly summarizes completed Beads into a concise text block.
-- [x] Task: Implement: Add Compaction logic to the context aggregation pipeline for Beads Mode.
-- [x] Task: Implement: Final UI polish, icons for Bead nodes, and robust error handling for missing `dolt`/`bd` binaries.
-- [~] Task: Conductor - User Manual Verification 'Phase 4: Context Optimization & Polish' (Protocol in workflow.md)

conductor/archive/code_path_analysis_20260507/index.md

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

conductor/archive/code_path_analysis_20260507/metadata.json

@@ -1,8 +0,0 @@
-{
-  "track_id": "code_path_analysis_20260507",
-  "type": "chore",
-  "status": "new",
-  "created_at": "2026-05-07T15:00:00Z",
-  "updated_at": "2026-05-07T15:00:00Z",
-  "description": "Comprehensive analysis of major processing routes in ./src and ./simulation. Identify data pipelines and responsibilities."
-}

conductor/archive/code_path_analysis_20260507/plan.md

@@ -1,26 +0,0 @@
-# Implementation Plan: Code Path & Data Pipeline Analysis (code_path_analysis_20260507)
-
-## Phase 1: Structural Exploration & Tooling Setup
-- [x] Task: Initialize `PIPELINE_ANALYSIS.md` template.
-- [x] Task: Deploy `codebase_investigator` subagents to identify top-level entry points in `gui_2.py` and `simulation/`.
-- [x] Task: Verify usage of existing tree-sitter tools to generate initial call-graph skeletons for `./src`.
-- [x] Task: Conductor - User Manual Verification 'Phase 1' (Protocol in workflow.md)
-
-## Phase 2: Mapping Core Source Pipelines (`./src`)
-- [x] Task: Map the **Context Aggregation Pipeline** (`aggregate.py`, `models.py`).
-- [x] Task: Map the **AI Interaction Loop** (`ai_client.py`, `mcp_client.py`, `shell_runner.py`).
-- [x] Task: Map the **GUI Event & State Pipeline** (`gui_2.py`, `app_controller.py`).
-- [x] Task: Document data responsibilities and state boundaries for each route.
-- [x] Task: Conductor - User Manual Verification 'Phase 2' (Protocol in workflow.md)
-
-## Phase 3: Mapping Simulation Pipelines (`./simulation`)
-- [x] Task: Map the **Simulation Lifecycle** (`sim_base.py`, `sim_context.py`, `workflow_sim.py`).
-- [x] Task: Analyze data flow between `sim_ai_settings.py` and the execution engine.
-- [x] Task: Document the "Verification & Checkpointing" route in simulations.
-- [x] Task: Conductor - User Manual Verification 'Phase 3' (Protocol in workflow.md)
-
-## Phase 4: Synthesis & Reporting
-- [x] Task: Consolidate all findings into Mermaid diagrams within `PIPELINE_ANALYSIS.md`.
-- [x] Task: Identify specific "Curation Targets" (redundancies, style violations) for the next track.
-- [x] Task: Final review and hand-off to Track 2 (Codebase Curation).
-- [x] Task: Conductor - User Manual Verification 'Phase 4' (Protocol in workflow.md)

conductor/archive/code_path_analysis_20260507/spec.md

@@ -1,27 +0,0 @@
-# Specification: Code Path & Data Pipeline Analysis (code_path_analysis_20260507)
-
-## Overview
-A deep architectural audit focused on mapping the "processing routes" and "data pipelines" of the Manual Slop codebase. This analysis will treat the program as a series of data-driven pipelines (similar to Ryan Fleury's model), identifying exactly how data flows through `./src` and `./simulation`.
-
-## Scope
-- **Core Codebase:** `./src`
-- **Simulation Infrastructure:** `./simulation`
-- **Granularity:** Both high-level module interactions and detailed function-to-function execution flows.
-
-## Functional Requirements
-1.  **Pipeline Mapping:**
-    - Identify major execution "routes" (e.g., UI Event Loop, AI Tool-Call Loop, Context Aggregation Pipeline).
-    - Map these routes from entry point to terminal state.
-2.  **Data Responsibility Audit:**
-    - For every major path, define which data structures it owns, modifies, or depends upon.
-    - Identify state boundaries and potential "data leaks" or redundant processing.
-3.  **Simulation Pipeline Audit:**
-    - Fully map the lifecycle of a simulation: State Setup -> Agent Injection -> Execution Loop -> Verification -> Cleanup.
-4.  **Automated Extraction:**
-    - Utilize MCP tools and potentially custom `tree-sitter` scripts to verify call graphs and data dependencies.
-
-## Acceptance Criteria
-- [ ] Comprehensive `PIPELINE_ANALYSIS.md` report created in the root.
-- [ ] Mermaid flowcharts documenting every major processing route.
-- [ ] Data responsibility table for all mapped paths.
-- [ ] Full mapping of the `./simulation` pipeline.

conductor/archive/codebase_audit_20260308/audit_report_20260502.md

@@ -1,39 +0,0 @@
-# Codebase Audit Report - 2026-05-02
-
-## Overview
-This report summarizes the findings of the codebase audit performed on the `./src` directory. The audit focused on human readability, maintainability, and identifying architectural redundancies.
-
-## Key Findings: Architectural Redundancies
-
-### 1. AI Client Provider Proliferation (`src/ai_client.py`)
-**Observation:** The `ai_client.py` module contains significantly redundant code paths for each supported LLM provider (Gemini, Anthropic, DeepSeek, MiniMax). Specifically:
-- **Send Methods:** Each provider has its own `_send_<provider>` method with nearly identical structure for tool handling and response parsing.
-- **Error Classification:** Multiple `_classify_<provider>_error` functions perform similar mappings of vendor exceptions to internal `ProviderError`.
-- **Model Listing:** Redundant `_list_<provider>_models` functions.
-- **History Management:** Separate locks and list structures for each provider's history.
-
-**Recommendation:** Abstract the provider logic into a base `AIProvider` class or interface. Each vendor (Gemini, Anthropic, etc.) should implement this interface, allowing `ai_client.py` to dispatch calls polymorphically.
-
-### 2. Tool Name Redundancy (`src/mcp_client.py` & `src/models.py`)
-**Observation:** The list of available agent tools was defined in multiple places:
-- `mcp_client.TOOL_NAMES` (Hardcoded set)
-- `models.AGENT_TOOL_NAMES` (Hardcoded list)
-- `mcp_client.MCP_TOOL_SPECS` (Canonical source for tool definitions)
-
-**Action Taken:** `mcp_client.TOOL_NAMES` was refactored to be dynamically generated from `MCP_TOOL_SPECS`.
-**Recommendation:** Consolidate `models.AGENT_TOOL_NAMES` to also derive from `mcp_client` or a shared tool registry to ensure synchronization when new tools are added.
-
-### 3. Orchestrator Wrapper Redundancy (`src/native_orchestrator.py`)
-**Observation:** The `NativeOrchestrator` class methods (e.g., `load_plan`, `save_track`) were found to be thin wrappers around module-level helper functions. 
-
-**Action Taken:** Replaced hardcoded paths in these helpers with calls to the standardized `src.paths` module.
-**Recommendation:** Evaluate if the `NativeOrchestrator` class is necessary if it remains state-free, or move the helper logic entirely into class methods.
-
-## Documentation Improvements
-
-- Added missing docstrings to critical public functions in `ai_client.py`, `mcp_client.py`, `native_orchestrator.py`, `api_hook_client.py`, and `api_hooks.py`.
-- Consolidated module-level docstrings in `multi_agent_conductor.py`.
-- Ensured consistent 1-space indentation and CRLF line endings across all modified files.
-
-## Conclusion
-The core orchestration and AI client layers are functionally robust but would benefit from an abstraction pass to reduce the maintenance burden of adding new providers or tools.

conductor/archive/codebase_curation_20260507/CURATION_PROTOCOL.md

@@ -1,25 +0,0 @@
-# Granular Review Protocol: Codebase Curation
-
-This protocol defines the mandatory procedure for auditing and modifying files during the Phase 5 Heavy Curation. It is designed to minimize entropy and prevent regression propagation.
-
-## 1. File-by-File Audit Cycle
-
-For every `.py` file identified for curation:
-
-1.  **Dependency Check:** Use `derive_code_path` and `py_get_imports` to identify all upstream and downstream dependencies.
-2.  **State Verification:** Consult the `MUTATION_MATRIX_PHASE5.md` to identify any global state modifications performed by the file.
-3.  **Redundancy Identification:** Cross-reference the file against `CULLING_CANDIDATES_PHASE5.md`.
-4.  **Proposed Change Log:** Before editing, document the specific lines/symbols to be removed or refactored and the technical justification (e.g., "Superseded by theme_2.py").
-5.  **Surgical Edit:** Use the `replace` tool for targeted deletions. Avoid bulk file overwrites.
-
-## 2. Regression Guardrails
-
-- **Functional Parity:** After every major deletion (e.g., removing a redundant module), run the associated unit tests (if any).
-- **Simulation Verification:** For changes to core pipelines (AI loop, Aggregation), run at least one relevant simulation (e.g., `simulation/ping_pong.py`) to verify end-to-end behavior.
-- **Human-in-the-Loop:** Significant refactors (e.g., the `aggregate.py` rework) MUST be presented to the user with a detailed diff before final commitment.
-
-## 3. Culling Justification Standards
-
-- **"Unused"**: Symbol has 0 project-wide references in the audit.
-- **"Redundant"**: Logic exists in a superior or more modern form elsewhere (e.g., `theme.py`).
-- **"Slop"**: Code that adds complexity without contributing to performance, configuration, or a specified feature.

conductor/archive/codebase_curation_20260507/index.md

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

conductor/archive/codebase_curation_20260507/metadata.json

@@ -1,8 +0,0 @@
-{
-  "track_id": "codebase_curation_20260507",
-  "type": "chore",
-  "status": "new",
-  "created_at": "2026-05-07T15:00:00Z",
-  "updated_at": "2026-05-07T15:00:00Z",
-  "description": "Exhaustive review of all .py files. Remove redundancies, eliminate unnecessary code/data/processing, and strictly align with project standards."
-}

conductor/archive/codebase_curation_20260507/plan.md

@@ -1,29 +0,0 @@
-# Implementation Plan: Comprehensive Codebase Curation & Style Alignment (codebase_curation_20260507)
-
-## Phase 0: Context Integration & Strategy
-- [x] Task: Review all Phase 5 analysis reports in `./docs` to internalize the curation roadmap.
-- [x] Task: Define a "Granular Review Protocol" for file-by-file auditing and culling.
-- [x] Task: Conductor - User Manual Verification 'Curation Strategy' (Protocol in workflow.md)
-
-## Phase 1: Automated Standardization & Audit
-- [~] Task: Run `scripts/ai_style_formatter.py` and `scripts/force_1space.py` on all files in `./src` and `./simulation`.
-- [ ] Task: Conduct an automated entropy audit to identify potential redundancy "hotspots".
-- [ ] Task: Conductor - User Manual Verification 'Standardization' (Protocol in workflow.md)
-
-## Phase 2: Surgical Curation of `./src`
-- [ ] Task: Comprehensive rework of `src/aggregate.py`. Modernize context assembly to leverage MCP tools, snapshots, and file caching. Consolidate tier-specific boilerplate.
-- [ ] Task: Review and trim `gui_2.py` and `app_controller.py` based on pipeline maps.
-- [ ] Task: Consolidate data models in `models.py` and remove redundant state in `aggregate.py`.
-- [ ] Task: Refactor `ai_client.py` to ensure lean processing of provider responses.
-- [ ] Task: Conductor - User Manual Verification 'Source Curation' (Protocol in workflow.md)
-
-## Phase 3: Surgical Curation of `./simulation`
-- [ ] Task: Review and trim `./simulation/` base classes and utility scripts.
-- [ ] Task: Eliminate redundant setup logic in `sim_context.py` and `workflow_sim.py`.
-- [ ] Task: Conductor - User Manual Verification 'Simulation Curation' (Protocol in workflow.md)
-
-## Phase 4: Final Integrity Pass
-- [ ] Task: Verify all tests pass with the trimmed codebase.
-- [ ] Task: Final comparison against `product-guidelines.md` for architectural purity.
-- [ ] Task: Final performance baseline check to ensure no regressions.
-- [ ] Task: Conductor - User Manual Verification 'Final Review' (Protocol in workflow.md)

conductor/archive/codebase_curation_20260507/spec.md

@@ -1,35 +0,0 @@
-# Specification: Comprehensive Codebase Curation & Style Alignment (codebase_curation_20260507)
-
-## Overview
-Aggressive pruning, optimization, and standardization of the codebase. This track uses the findings from the Code Path Analysis and other Phase 5 audits to trim away non-essential logic, data, and processing while strictly enforcing the project's technical integrity standards.
-
-## Foundational Context (MANDATORY REVIEW)
-All curation efforts MUST be informed by the following Phase 5 analysis reports:
-- `docs/PIPELINE_ANALYSIS_PHASE5_INIT.md`: Processing route and pipeline mapping.
-- `docs/STATE_INVENTORY_PHASE5.md`: Core data structure and property inventory.
-- `docs/MUTATION_MATRIX_PHASE5.md`: Thread-safe state modification and lock map.
-- `docs/CULLING_CANDIDATES_PHASE5.md`: Identified redundant symbols, modules, and structures.
-
-## Granular Care & Regression Guardrails
-- **Surgical Execution:** Changes must be applied file-by-file with extreme granularity. No bulk culling without individual justification.
-- **Regression Monitoring:** Continuous verification of behavioral integrity. Any unintended entropy or performance degradation must trigger an immediate halt and review.
-- **Traceability:** Every removed line must be cross-referenced against the culling audit or pipeline map.
-
-## Scope
-- **Target Files:** All `.py` files in `./src` and `./simulation`.
-- **Primary Goal:** Trimming the "slop" (redundancies, dead code, excessive complexity).
-
-## Functional Requirements
-1.  **Redundancy Pruning:** Eliminate duplicate logic across different data pipelines.
-2.  **Dead Code Removal:** Strip out legacy "just-in-case" code and unused processing paths.
-3.  **Strict Style Enforcement:**
-    - Universal 1-space indentation.
-    - CRLF line endings.
-    - Standardized type hinting.
-4.  **Guideline Alignment:** Refactor any code that deviates from `product-guidelines.md` (e.g., ensuring explicit composition over complex inheritance).
-5.  **Validation:** Ensure no loss of functionality or performance degradation.
-
-## Acceptance Criteria
-- [ ] Significant reduction in total codebase line count (where applicable).
-- [ ] 100% pass on style audit (`scripts/ai_style_formatter.py`).
-- [ ] All remaining code is mapped to a necessary functional requirement or performance goal.

conductor/archive/command_palette_and_performance_20260602/index.md

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

conductor/archive/command_palette_and_performance_20260602/metadata.json

@@ -1,8 +0,0 @@
-{
-  "track_id": "command_palette_and_performance_20260602",
-  "type": "feature",
-  "status": "new",
-  "created_at": "2026-06-02T00:00:00Z",
-  "updated_at": "2026-06-02T00:00:00Z",
-  "description": "Implement Async Context Preview to fix UI hangs and add an 'Everything' Command Palette."
-}

conductor/archive/command_palette_and_performance_20260602/plan.md

@@ -1,24 +0,0 @@
-# Implementation Plan: Command Palette & UI Performance Fixes
-
-## Phase 1: Offloading Performance Fixes
-- [x] Task: Async Context Preview
-    - [x] Add `self._is_generating_preview = False` to `App.__init__`.
-    - [x] Modify `_check_auto_refresh_context_preview` in `src/gui_2.py` to use a background thread.
-- [ ] Task: Incremental AST Selection (Future/Nuance)
-    - [ ] Investigate if `_do_generate` can accept a partial update flag to avoid full project re-render.
-
-## Phase 2: Command Palette Implementation
-- [ ] Task: Define Command Registry
-    - [ ] Create a list of dictionaries in `App` containing `name`, `desc`, and `callback`.
-- [ ] Task: Render Command Palette UI
-    - [ ] Handle `Ctrl+P` (or `Cmd+P`) to toggle `self.show_command_palette`.
-    - [ ] Use `imgui.begin_popup_modal` for the palette feel.
-- [ ] Task: Keyboard Interactivity
-    - [ ] Implement fuzzy search and keyboard navigation.
-
-
-## Phase 3: Verification
-- [ ] Task: Verification
-    - [ ] Verify no UI hang when toggling AST nodes.
-    - [ ] Verify Command Palette opens, filters correctly, and executes actions.
-- [ ] Task: Conductor - User Manual Verification 'Phase 3: Verification' (Protocol in workflow.md)

conductor/archive/command_palette_and_performance_20260602/spec.md

@@ -1,28 +0,0 @@
-# Specification: Command Palette & UI Performance Fixes
-
-## 1. Overview
-This track addresses two distinct but critical areas:
-1.  **UI Performance (Fix):** The application currently hangs when users adjust AST or slice configurations. This is because the context preview is regenerated synchronously on the GUI thread, blocking all interactions.
-2.  **Command Palette (Feature):** A central, keyboard-driven interface for all application actions, similar to professional editors like VSCode or Sublime Text.
-
-## 2. Functional Requirements
-### 2.1 Async Context Preview
-*   **Background Generation:** The `_do_generate` call within `_check_auto_refresh_context_preview` must be offloaded to an asynchronous worker thread.
-*   **State Locking:** Prevent multiple concurrent generation threads from running if a preview refresh is already in progress.
-*   **Incremental Signaling:** (Optional future goal) Investigate ways to only re-parse the affected file, but offloading is the immediate priority.
-
-### 2.2 Everything Command Palette
-*   **Shortcut Trigger:** Triggered by `Ctrl+P` (global project context).
-*   **Fuzzy Search:** An input field that filters a global list of available commands.
-*   **Action Mapping:** Includes actions like "Generate Response", "Clear Discussion", "Toggle Diagnostics", "Add All Files to Context", etc.
-*   **Keyboard Navigation:** Use Up/Down arrows to navigate results and Enter to select/execute.
-*   **Modal UX:** A centered, floating popup that dismisses on selection or Escape.
-
-## 3. Non-Functional Requirements
-*   **Smooth GUI Loop:** Offloading the generation must eliminate the UI hang.
-*   **Low Latency Palette:** Search and filtering must feel instantaneous.
-
-## 4. Acceptance Criteria
-*   Toggling "Def", "Sig", or "Hide" on an AST node no longer causes the GUI to stutter or hang.
-*   Pressing `Ctrl+P` opens the Command Palette.
-*   Typing "Reset" shows "Reset Session" and executing it successfully resets the discussion.

conductor/archive/context_batch_operations_ux_20260510/index.md

@@ -1,4 +0,0 @@
-# Track: Context Batch Operations UX
-
-- [Specification](./spec.md)
-- [Plan](./plan.md)

conductor/archive/context_batch_operations_ux_20260510/metadata.json

@@ -1,5 +0,0 @@
-{
-  "id": "context_batch_operations_ux_20260510",
-  "title": "Context Batch Operations UX",
-  "status": "planned"
-}

conductor/archive/context_batch_operations_ux_20260510/plan.md

@@ -1,9 +0,0 @@
-# Implementation Plan: Context Batch Operations UX
-
-## Phase 1: Selection State
-- [x] Introduce a `selected_files` set in the `AppController` state.
-- [x] Update `_render_context_panel` in `src/gui_2.py` to support clicking/checkboxes to modify the selection state.
-
-## Phase 2: Batch Actions
-- [x] Add a 'Batch Actions' sub-menu or inline bar in the Context Panel.
-- [x] Implement controller methods to apply state changes to all items in `selected_files`.

conductor/archive/context_batch_operations_ux_20260510/spec.md

@@ -1,9 +0,0 @@
-# Specification: Context Batch Operations UX
-
-## Overview
-Add multi-select and batch state modification capabilities to the Context Panel to allow rapid wrangling of large numbers of files (e.g., setting 20 C++ files to 'AST Signatures' at once).
-
-## Acceptance Criteria
-- [ ] Context panel supports multi-select (Shift-click, Ctrl-click, or checkboxes).
-- [ ] A batch operations context menu or action bar allows applying states (Force Full, Summary, AST Signatures, Remove) to all selected items.
-- [ ] Selections persist correctly during UI refreshes.

conductor/archive/context_comp_decouple_20260510/metadata.json

@@ -1,11 +0,0 @@
-{
-  "id": "context_comp_decouple_20260510",
-  "title": "Context Composition Decoupling",
-  "phase": 6,
-  "created": "2026-05-10",
-  "status": "pending",
-  "spec_file": "spec.md",
-  "plan_file": "plan.md",
-  "depends_on": [],
-  "completion_checkpoints": []
-}

conductor/archive/context_comp_decouple_20260510/plan.md

@@ -1,48 +0,0 @@
-# Implementation Plan: Context Composition Decoupling
-
-## Phase 1: Core Data Model Changes
-Focus: Add view_mode field to FileItem, understand current coupling
-
-- [x] Task 1.1: Audit FileItem model in models.py - add view_mode and custom_slices fields [8addb97]
-- [x] Task 1.2: Audit _render_context_composition_panel() to understand current coupling [8addb97]
-- [x] Task 1.3: Audit _render_files_panel() to understand how Files & Media populates context [8addb97]
-- [x] Task 1.4: Write tests for FileItem with view_mode and custom_slices [8addb97]
-
-## Phase 2: Decouple Context Composition from Files & Media
-Focus: Remove auto-population inheritance, make Context Composition independent
-
-- [x] Task 2.1: Remove auto-population of context from Files & Media in context composition [9b3a4d6]
-- [x] Task 2.2: Add manual "Add Files" button to Context Composition (file picker from project whitelist) [9b3a4d6]
-- [x] Task 2.3: Implement "Add All" batch operation [9b3a4d6]
-- [x] Task 2.4: Write tests for decoupled context composition state [9b3a4d6]
-
-## Phase 3: Directory Grouping + File Stats
-Focus: Compact file listing with stats
-
-- [x] Task 3.1: Implement directory grouping helper to group files by relative path prefix [5112deb]
-- [x] Task 3.2: Add file stats computation (line count, AST element count) - async [5112deb]
-- [x] Task 3.3: Render file list with collapsible directory headers [5112deb]
-- [x] Task 3.4: Display aggregate stats (total files, lines, AST elements) [5112deb]
-- [x] Task 3.5: Write tests for directory grouping and stats [5112deb]
-
-## Phase 4: View Mode Selection UI
-Focus: Per-file view mode dropdown (full/sig/def/custom)
-
-- [x] Task 4.1: Add view_mode dropdown to each file entry in Context Composition [fb1b72c]
-- [x] Task 4.2: Implement custom view mode indicator (enabled when custom slices exist) [fb1b72c]
-- [x] Task 4.3: Batch view mode change operations [fb1b72c]
-- [x] Task 4.4: Write tests for view mode selection [fb1b72c]
-
-## Phase 5: Context Presets Infrastructure
-Focus: Data structures for save/load (without UI)
-
-- [x] Task 5.1: Create ContextPreset and FileViewPreset data models [78c009f]
-- [x] Task 5.2: Implement serialization for context presets (TOML) [78c009f]
-- [x] Task 5.3: Write tests for context preset models [78c009f]
-
-## Phase 6: Integration + Bug Fixes
-Focus: Ensure aggregate respects new view modes, fix any issues
-
-- [x] Task 6.1: Verify aggregate.py respects view_mode when composing context [4dc801e]
-- [x] Task 6.2: Test with gencpp project files [4dc801e]
-- [x] Task 6.3: Conductor - User Manual Verification [4dc801e]

conductor/archive/context_comp_decouple_20260510/spec.md

@@ -1,52 +0,0 @@
-# Track Specification: Context Composition Decoupling
-
-## Overview
-Decouple Files & Media from Context Composition, add directory grouping, file stats, and view mode selection per file. This is Phase 1 of the Context Composition Redesign per spec at `docs/superpowers/specs/2026-05-10-context-composition-redesign-design.md`.
-
-## Current State Audit (as of 2026-05-10)
-### Already Implemented
-- Files & Media panel lists project files with wildcards
-- Context Composition panel inherits files from Files & Media
-- View flags (agg/full/sig/def) sync visually between panels
-- `_render_context_composition_panel()` in gui_2.py:2794-2964
-
-### Gaps to Fill (This Track's Scope)
-- Files & Media populates Context Composition automatically (coupled)
-- No directory grouping in file listings
-- No file stats (line count, AST element count)
-- View mode selection is limited (no custom view presets)
-- Context Composition is NOT independent selection - it's derived from Files & Media
-
-## Goals
-1. Make Files & Media and Context Composition independent data sources
-2. Add directory grouping to file listings for compact display
-3. Add file stats per file and aggregate
-4. Implement proper view mode selection (full/sig/def/custom)
-5. User can add/remove files from Context Composition independently
-6. "Add all" and bulk add/remove operations
-
-## Functional Requirements
-- Context Composition starts empty or from saved preset on discussion switch
-- User manually adds files FROM project whitelist (not auto-inherited)
-- Each file entry has: path, view_mode, custom_slices
-- Directory grouping with collapsible headers (`📁 relative/path/`)
-- File stats displayed: line count, AST element count per file
-- Aggregate stats for selection: total files, lines, AST elements
-- View mode dropdown per file: full, sig, def, custom
-- Batch operations: add all from whitelist, remove selected, etc.
-
-## Non-Functional Requirements
-- No horizontal scrolling in file lists (directory grouping enables this)
-- Stats computed asynchronously to not block UI
-- FileItem model may need extension for view_mode field
-
-## Architecture Reference
-- `src/gui_2.py:_render_context_composition_panel()` - main panel
-- `src/models.py:FileItem` - needs view_mode field extension
-- `src/aggregate.py` - respects view modes when composing context
-- `docs/superpowers/specs/2026-05-10-context-composition-redesign-design.md`
-
-## Out of Scope
-- Slice visualization and annotations (Phase 2)
-- Context preset save/load (Phase 3)
-- Context preview before send (Phase 3)

conductor/archive/context_comp_presets_20260510/metadata.json

@@ -1,11 +0,0 @@
-{
-  "id": "context_comp_presets_20260510",
-  "title": "Context Composition Presets",
-  "phase": 6,
-  "created": "2026-05-10",
-  "status": "pending",
-  "spec_file": "spec.md",
-  "plan_file": "plan.md",
-  "depends_on": ["context_comp_slices_20260510"],
-  "completion_checkpoints": []
-}

conductor/archive/context_comp_presets_20260510/plan.md

@@ -1,49 +0,0 @@
-# Implementation Plan: Context Composition Presets
-
-## Phase 1: Context Preset Data Models [checkpoint: ebd78bb]
-Focus: Create models and serialization
-
-- [x] Task 1.1: Create ContextPreset and ContextFileEntry models 8467cdd
-- [x] Task 1.2: Implement relative path storage (relative to project root) 8467cdd
-- [x] Task 1.3: Add to_dict() and from_dict() methods 8467cdd
-- [x] Task 1.4: Write tests for preset models 8467cdd
-
-## Phase 2: Preset Persistence [checkpoint: 338eae7]
-Focus: Save/load presets to project config
-
-- [x] Task 2.1: Add ContextPresetManager class (follows PresetManager pattern) e3d84bc
-- [x] Task 2.2: Add save_context_preset() to AppController e3d84bc
-- [x] Task 2.3: Add load_context_preset() to AppController e3d84bc
-- [x] Task 2.4: Write tests for preset persistence e3d84bc
-
-## Phase 3: Save Preset UI
-Focus: UI for saving presets with validation
-
-- [x] Task 3.1: Add [Save] button and dialog to Context Composition c52e461
-- [x] Task 3.2: Implement validation (check files exist before save) c52e461
-- [x] Task 3.3: Warning dialog for missing files with options c52e461
-- [x] Task 3.4: Write tests for save UI c52e461
-
-## Phase 4: Load Preset UI
-Focus: UI for loading presets with validation
-
-- [x] Task 4.1: Add preset selector dropdown to Context Composition c52e461
-- [x] Task 4.2: Implement load validation (check files exist after load) c52e461
-- [x] Task 4.3: Missing file highlighting in red c52e461
-- [x] Task 4.4: Write tests for load UI c52e461
-
-## Phase 5: Context Preview
-Focus: Show what will be sent to agent
-
-- [x] Task 5.1: Add [Preview] button to Context Composition e3d84bc
-- [x] Task 5.2: Collapsed preview: file list + view modes e3d84bc
-- [x] Task 5.3: Expanded preview: actual text/slices e3d84bc
-- [x] Task 5.4: Token estimate display e3d84bc
-- [x] Task 5.5: Write tests for preview e3d84bc
-
-## Phase 6: Integration + Validation
-Focus: End-to-end testing
-
-- [x] Task 6.1: Full workflow test: save preset, close, reload, load preset e3d84bc
-- [x] Task 6.2: Test with gencpp project files e3d84bc
-- [x] Task 6.3: Conductor - User Manual Verification e3d84bc

conductor/archive/context_comp_presets_20260510/spec.md

@@ -1,66 +0,0 @@
-# Track Specification: Context Composition Presets
-
-## Overview
-Implement Context Preset save/load with validation, and Context Preview before sending to agent. This is Phase 3 of the Context Composition Redesign per spec at `docs/superpowers/specs/2026-05-10-context-composition-redesign-design.md`.
-
-## Current State Audit (as of 2026-05-10)
-### Already Implemented
-- Preset system exists for system prompts, tool presets, personas
-- ProjectManager handles TOML save/load
-- Context Composition stores FileItem entries with flags
-
-### Gaps to Fill (This Track's Scope)
-- No Context Preset model for saving file+view+slices compositions
-- No save/load UI for Context Presets in Context Composition panel
-- No validation when loading preset (missing files warn user)
-- No Context Preview showing what will be sent to agent
-
-## Goals
-1. Context Preset model with name, description, files list
-2. Save Context Preset to project config
-3. Load Context Preset populates Context Composition
-4. Missing file validation on load with user choice
-5. Context Preview before send showing exact context text
-
-## Functional Requirements
-### Context Preset Model
-- Contains: name, description, list of ContextFileEntry
-- ContextFileEntry: relative_path, view_mode, custom_slices
-- All paths stored as relative to project root
-- Serializes to TOML in project config
-
-### Save Preset UI
-- [Save] button in Context Composition
-- Dialog: enter preset name + optional description
-- Validation before save:
-  - Check all files exist in project
-  - If files missing: warn user, offer to save without or cancel
-
-### Load Preset UI
-- Dropdown selector for preset selection
-- On load: clear Context Composition, populate from preset
-- If file missing from preset: highlight in red, warn user
-- User can proceed with missing files or re-path
-
-### Context Preview
-- "Preview" button/tab showing what will be sent
-- Per file: view mode, line ranges, tags, comments
-- Collapsed view: just file list + view modes
-- Expanded view: actual text/slices that will be sent
-- Token estimate for total context
-
-### Stale Preset Handling
-- If project changes and preset references moved/renamed files:
-  - On load: detect and warn
-  - User can save preset without invalid files
-  - Or ignore warning and proceed
-
-## Architecture Reference
-- `src/project_manager.py` - existing preset save/load patterns
-- `src/presets.py` - existing preset manager patterns to follow
-- `docs/superpowers/specs/2026-05-10-context-composition-redesign-design.md`
-
-## Out of Scope
-- Slice visualization (Phase 2)
-- Files & Media changes (Phase 1)
-- RAG configuration changes

conductor/archive/context_comp_slices_20260510/metadata.json

@@ -1,11 +0,0 @@
-{
-  "id": "context_comp_slices_20260510",
-  "title": "Context Composition Slice Visualization",
-  "phase": 6,
-  "created": "2026-05-10",
-  "status": "pending",
-  "spec_file": "spec.md",
-  "plan_file": "plan.md",
-  "depends_on": ["context_comp_decouple_20260510"],
-  "completion_checkpoints": []
-}

conductor/archive/context_comp_slices_20260510/plan.md

@@ -1,48 +0,0 @@
-# Implementation Plan: Context Composition Slice Visualization
-
-## Phase 1: Slice Data Model Extension [checkpoint: 4a20489]
-Focus: Extend custom_slices to support tags and comments
-
-- [x] Task 1.1: Extend custom_slices schema to include tag and comment fields [976879d]
-- [x] Task 1.2: Update FileItem.to_dict() and from_dict() for new fields [976879d]
-- [x] Task 1.3: Write tests for custom_slices with annotations [976879d]
-
-## Phase 2: Slice Inspector Enhancement [checkpoint: 31ecbe5]
-Focus: Visual AST highlighting with file content
-
-- [x] Task 2.1: Modify _render_ast_inspector_modal() to show file content with highlighted slices [976b241]
-- [x] Task 2.2: Add color coding for Sig vs Def elements in file content view [976b241]
-- [x] Task 2.3: Implement toggle buttons for each AST element in the content view [976b241]
-- [x] Task 2.4: Write tests for slice inspector rendering [976b241]
-
-## Phase 3: Slice Editor Visual Enhancement [checkpoint: 4f0f436]
-Focus: Visual slice editor with colored overlays
-
-- [x] Task 3.1: Enhance slice editor to show file content (not just line list) [3614e11]
-- [x] Task 3.2: Add colored overlays for custom slices on the content [3614e11]
-- [x] Task 3.3: Implement click-drag line range selection [3614e11]
-- [x] Task 3.4: Add tag/comment input for custom slices [3614e11]
-- [x] Task 3.5: Write tests for slice editor [3614e11]
-
-## Phase 4: View Presets [checkpoint: 8073938]
-Focus: Named view configurations
-
-- [x] Task 4.1: Create FileViewPreset model [cb0fa89]
-- [x] Task 4.2: Add preset selection dropdown to context composition [cb0fa89]
-- [x] Task 4.3: Implement preset save/load to project config [cb0fa89]
-- [x] Task 4.4: Write tests for view presets [cb0fa89]
-
-## Phase 5: AST Slice Pre-population [checkpoint: 2ebe0c6]
-Focus: Show auto-resolved slices before user customizes
-
-- [x] Task 5.1: On file add to context, compute AST slices automatically [a669f92]
-- [x] Task 5.2: Store pre-computed slices in FileItem for display [a669f92]
-- [x] Task 5.3: User can modify/remove auto-slices [a669f92]
-- [x] Task 5.4: Write tests for auto-slices [a669f92]
-
-## Phase 6: Integration
-Focus: Connect all pieces together
-
-- [x] Task 6.1: Verify slice data flows correctly through context composition [1303fc1]
-- [x] Task 6.2: Test with C++ files from gencpp [1303fc1]
-- [x] Task 6.3: Conductor - User Manual Verification [1303fc1]

conductor/archive/context_comp_slices_20260510/spec.md

@@ -1,63 +0,0 @@
-# Track Specification: Context Composition Slice Visualization
-
-## Overview
-Enhance slice visualization with visual editor, annotation support (tags/comments), and view presets. This is Phase 2 of the Context Composition Redesign per spec at `docs/superpowers/specs/2026-05-10-context-composition-redesign-design.md`.
-
-## Current State Audit (as of 2026-05-10)
-### Already Implemented
-- [Inspect] button opens AST inspector modal showing AST tree with Def/Sig/Hide toggles
-- [Slices] button opens Text Viewer with file content for slice management
-- FileItem.ast_mask stores mask per AST path (Def/Sig/Hide)
-- FileItem.custom_slices stores user-defined slices with line ranges
-
-### Gaps to Fill (This Track's Scope)
-- Inspect popup shows AST but doesn't show file content with highlighted slices
-- Slices editor is just a list of line ranges - no visual representation
-- No annotation support (tags/comments) for custom slices
-- No view presets (named combinations of view settings)
-- AST-derived slices not shown before user creates custom slice
-
-## Goals
-1. Slice inspector shows file content with AST-derived slices visually highlighted
-2. Custom slices have visual representation (colored ranges) in slice editor
-3. Each slice can have optional tag and comment annotation
-4. View presets allow naming and reusing view configurations
-5. User can toggle which AST elements are included in each view
-
-## Functional Requirements
-### Slice Inspector (replaces Inspect button)
-- Opens as popup showing full file content with line numbers
-- AST-derived slices highlighted with distinct colors:
-  - Sig elements: one color
-  - Def elements: another color
-- User can toggle visibility of each AST element (Def/Sig/Hide)
-- Changes persist to FileItem.ast_mask
-
-### Slice Editor (extends Slices button)
-- Visual file content display (not just line number list)
-- Custom slices shown as colored overlays on the content
-- Click-drag to select line range for new slice
-- Each custom slice has:
-  - Line range
-  - Tag (optional, e.g., "performance", "api", "bug")
-  - Comment (optional, free-text explanation)
-- Remove/edit existing custom slices
-
-### View Presets
-- Named presets defining default view + default slices per file type
-- Examples:
-  - "Debug View" = full text + error-prone line slices
-  - "API Surface" = sig + public API function slices
-- Presets project-scoped, saved in project config
-- User can select preset, then override for specific file
-
-## Architecture Reference
-- `src/gui_2.py:_render_ast_inspector_modal()` - needs enhancement
-- `src/models.py:FileItem.ast_mask` - existing mask storage
-- `src/models.py:FileItem.custom_slices` - needs tag/comment support
-- `docs/superpowers/specs/2026-05-10-context-composition-redesign-design.md`
-
-## Out of Scope
-- Context preset save/load UI (Phase 3)
-- Context preview before send (Phase 3)
-- Changes to Files & Media panel (Phase 1)