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.
fix(shader): Use custom_background callback to render blurred texture
2026-03-13 21:45:51 -04:00 · 2026-03-13 21:44:55 -04:00 · 2026-03-13 21:35:23 -04:00 · 2026-03-13 21:28:39 -04:00 · 2026-03-13 21:24:14 -04:00 · 2026-03-13 21:08:13 -04:00
398 changed files with 14979 additions and 1106 deletions
@@ -2,8 +2,7 @@
 description: Fast, read-only agent for exploring the codebase structure
 mode: subagent
 model: MiniMax-M2.5
-temperature: 0.0
-steps: 8
+temperature: 0.2
 permission:
  edit: deny
  bash:
@@ -22,6 +21,7 @@ You are a fast, read-only agent specialized for exploring codebases. Use this wh
 You MUST use Manual Slop's MCP tools. Native OpenCode tools are unreliable.

 ### Read-Only MCP Tools (USE THESE)
+
 | Native Tool | MCP Tool |
 |-------------|----------|
 | `read` | `manual-slop_read_file` |
@@ -34,12 +34,14 @@ You MUST use Manual Slop's MCP tools. Native OpenCode tools are unreliable.
 | - | `manual-slop_get_tree` (directory structure) |

 ## Capabilities
+
 - Find files by name patterns or glob
 - Search code content with regex
 - Navigate directory structures
 - Summarize file contents

 ## Limitations
+
 - **READ-ONLY**: Cannot modify any files
 - **NO EXECUTION**: Cannot run tests or scripts
 - **EXPLORATION ONLY**: Use for discovery, not implementation
@@ -62,7 +64,9 @@ Use: `manual-slop_get_tree` or `manual-slop_list_directory`
 Use: `manual-slop_get_file_summary` for heuristic summary

 ## Report Format
+
 Return concise findings with file:line references:
+
 ```
 ## Findings

@@ -2,8 +2,7 @@
 description: General-purpose agent for researching complex questions and executing multi-step tasks
 mode: subagent
 model: MiniMax-M2.5
-temperature: 0.2
-steps: 15
+temperature: 0.3
 ---

 A general-purpose agent for researching complex questions and executing multi-step tasks. Has full tool access (except todo), so it can make file changes when needed.
@@ -13,6 +12,7 @@ A general-purpose agent for researching complex questions and executing multi-st
 You MUST use Manual Slop's MCP tools. Native OpenCode tools are unreliable.

 ### Read MCP Tools (USE THESE)
+
 | Native Tool | MCP Tool |
 |-------------|----------|
 | `read` | `manual-slop_read_file` |
@@ -26,6 +26,7 @@ You MUST use Manual Slop's MCP tools. Native OpenCode tools are unreliable.
 | - | `manual-slop_get_tree` (directory structure) |

 ### Edit MCP Tools (USE THESE)
+
 | Native Tool | MCP Tool |
 |-------------|----------|
 | `edit` | `manual-slop_edit_file` (find/replace, preserves indentation) |
@@ -35,11 +36,13 @@ You MUST use Manual Slop's MCP tools. Native OpenCode tools are unreliable.
 | `edit` | `manual-slop_py_set_var_declaration` (replace variable) |

 ### Shell Commands
+
 | Native Tool | MCP Tool |
 |-------------|----------|
 | `bash` | `manual-slop_run_powershell` |

 ## Capabilities
+
 - Research and answer complex questions
 - Execute multi-step tasks autonomously
 - Read and write files as needed
@@ -47,13 +50,22 @@ You MUST use Manual Slop's MCP tools. Native OpenCode tools are unreliable.
 - Coordinate multiple operations

 ## When to Use
+
 - Complex research requiring multiple file reads
 - Multi-step implementation tasks
 - Tasks requiring autonomous decision-making
 - Parallel execution of related operations

+## Code Style (for Python)
+
+- 1-space indentation
+- NO COMMENTS unless explicitly requested
+- Type hints where appropriate
+
 ## Report Format
+
 Return detailed findings with evidence:
+
 ```
 ## Task: [Original task]

@@ -2,8 +2,7 @@
 description: Tier 1 Orchestrator for product alignment, high-level planning, and track initialization
 mode: primary
 model: MiniMax-M2.5
-temperature: 0.4
-steps: 50
+temperature: 0.5
 permission:
  edit: ask
  bash:
@@ -17,6 +16,12 @@ 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.

+## Context Management
+
+**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.
+
 ## CRITICAL: MCP Tools Only (Native Tools Banned)

 You MUST use Manual Slop's MCP tools. Native OpenCode tools are unreliable.
@@ -69,7 +74,7 @@ Before ANY other action:

 Read at session start:

- All immediate files in ./conductor, a listing of all direcotires within ./conductor/tracks, ./conductor/archive.
+- All immediate files in ./conductor, a listing of all directories within ./conductor/tracks, ./conductor/archive.
 - All docs in ./docs
 - AST Skeleton summaries of: ./src, ./simulation, ./tests, ./scripts python files.

@@ -90,7 +95,7 @@ When planning tracks that touch core systems, consult the deep-dive docs:
 - Set up the project environment (`/conductor-setup`)
 - Delegate track execution to the Tier 2 Tech Lead

-## The Surgical Methodology
+## The Surgical Methodology (MANDATORY)

 ### 1. MANDATORY: Audit Before Specifying

@@ -100,10 +105,16 @@ 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
+asked to implement features that already existed.
+
 ### 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 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:
@@ -162,6 +173,6 @@ Focus: {One-sentence scope}
 - Do NOT batch commits - commit per-task
 - Do NOT skip phase verification
 - Do NOT use native `edit` tool - use MCP tools
- 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.
+- 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.
@@ -1,9 +1,7 @@
 ---
 description: Tier 2 Tech Lead for architectural design and track execution with persistent memory
 mode: primary
-model: MiniMax-M2.5
-temperature: 0.2
-steps: 100
+temperature: 0.4
 permission:
  edit: ask
  bash: ask
@@ -13,6 +11,12 @@ STRICT SYSTEM DIRECTIVE: You are a Tier 2 Tech Lead.
 Focused on architectural design and track execution.
 ONLY output the requested text. No pleasantries.

+## Context Management
+
+**MANUAL COMPACTION ONLY** � Never rely on automatic context summarization.
+Use `/compact` command explicitly when context needs reduction.
+You maintain PERSISTENT MEMORY throughout track execution � do NOT apply Context Amnesia to your own session.
+
 ## CRITICAL: MCP Tools Only (Native Tools Banned)

 You MUST use Manual Slop's MCP tools. Native OpenCode tools are unreliable.
@@ -84,6 +88,16 @@ Before ANY other action:
 3. Delegate to Tier 3 via Task tool
 4. Verify result

+## Pre-Delegation Checkpoint (MANDATORY)
+
+Before delegating ANY dangerous or non-trivial change to Tier 3:
+
+```powershell
+git add .
+```
+
+**WHY**: If a Tier 3 Worker fails or incorrectly runs `git restore`, you will lose ALL prior AI iterations for that file if it wasn't staged/committed.
+
 ## Architecture Fallback

 When implementing tracks that touch core systems, consult the deep-dive docs:
@@ -92,6 +106,7 @@ When implementing tracks that touch core systems, consult the deep-dive docs:
 - `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, mock provider
+- `docs/guide_meta_boundary.md`: Clarification of ai agent tools making the application vs the application itself.

 ## Responsibilities

@@ -114,16 +129,18 @@ Before implementing:

 ### 2. Red Phase: Write Failing Tests

- Pre-delegation checkpoint: Stage current progress (`git add .`)
+- **Pre-delegation checkpoint**: Stage current progress (`git add .`)
 - Zero-assertion ban: Tests MUST have meaningful assertions
 - Delegate test creation to Tier 3 Worker via Task tool
 - Run tests and confirm they FAIL as expected
+- **CONFIRM FAILURE** � this is the Red phase

 ### 3. Green Phase: Implement to Pass

- Pre-delegation checkpoint: Stage current progress
+- **Pre-delegation checkpoint**: Stage current progress (`git add .`)
 - Delegate implementation to Tier 3 Worker via Task tool
 - Run tests and confirm they PASS
+- **CONFIRM PASS** � this is the Green phase

 ### 4. Refactor Phase (Optional)

@@ -134,12 +151,12 @@ Before implementing:

 After completing each task:

-1. Stage changes: `git add .`
+1. Stage changes: `manual-slop_run_powershell` with `git add .`
 2. Commit with clear message: `feat(scope): description`
 3. Get commit hash: `git log -1 --format="%H"`
 4. Attach git note: `git notes add -m "summary" <hash>`
 5. Update plan.md: Mark task `[x]` with commit SHA
-6. Commit plan update
+6. Commit plan update: `git add plan.md && git commit -m "conductor(plan): Mark task complete"`

 ## Delegation via Task Tool

@@ -193,6 +210,6 @@ When all tasks in a phase are complete:
 - Do NOT batch commits - commit per-task
 - Do NOT skip phase verification
 - Do NOT use native `edit` tool - use MCP tools
- 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.
+- 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.
@@ -2,8 +2,7 @@
 description: Stateless Tier 3 Worker for surgical code implementation and TDD
 mode: subagent
 model: MiniMax-M2.5
-temperature: 0.1
-steps: 20
+temperature: 0.3
 permission:
  edit: allow
  bash: allow
@@ -13,11 +12,17 @@ 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.

+## Context Amnesia
+
+You operate statelessly. Each task starts fresh with only the context provided.
+Do not assume knowledge from previous tasks or sessions.
+
 ## CRITICAL: MCP Tools Only (Native Tools Banned)

 You MUST use Manual Slop's MCP tools. Native OpenCode tools are unreliable.

 ### Read MCP Tools (USE THESE)
+
 | Native Tool | MCP Tool |
 |-------------|----------|
 | `read` | `manual-slop_read_file` |
@@ -30,6 +35,7 @@ You MUST use Manual Slop's MCP tools. Native OpenCode tools are unreliable.
 | - | `manual-slop_get_file_slice` (read specific line range) |

 ### Edit MCP Tools (USE THESE - BAN NATIVE EDIT)
+
 | Native Tool | MCP Tool |
 |-------------|----------|
 | `edit` | `manual-slop_edit_file` (find/replace, preserves indentation) |
@@ -39,17 +45,15 @@ You MUST use Manual Slop's MCP tools. Native OpenCode tools are unreliable.
 | `edit` | `manual-slop_py_set_var_declaration` (replace variable) |

 ### Shell Commands
+
 | Native Tool | MCP Tool |
 |-------------|----------|
 | `bash` | `manual-slop_run_powershell` |

-## Context Amnesia
-You operate statelessly. Each task starts fresh with only the context provided.
-Do not assume knowledge from previous tasks or sessions.
-
 ## Task Start Checklist (MANDATORY)

 Before implementing:
+
 1. [ ] Read task prompt - identify WHERE/WHAT/HOW/SAFETY
 2. [ ] Use skeleton tools for files >50 lines (`manual-slop_py_get_skeleton`, `manual-slop_get_file_summary`)
 3. [ ] Verify target file and line range exists
@@ -58,19 +62,24 @@ Before implementing:
 ## Task Execution Protocol

 ### 1. Understand the Task
+
 Read the task prompt carefully. It specifies:
+
 - **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

 ### 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
@@ -78,31 +87,39 @@ Use MCP tools to understand the context:
 - 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:
+
 - What was changed
 - Where it was changed
 - Any issues encountered

 ## Code Style Requirements
+
 - **NO COMMENTS** unless explicitly requested
 - 1-space indentation for Python code
 - Type hints where appropriate
 - Internal methods/variables prefixed with underscore

 ## Quality Checklist
+
 Before reporting completion:
+
 - [ ] Change matches the specification exactly
 - [ ] No unintended modifications
 - [ ] No syntax errors
 - [ ] Tests pass (if applicable)

 ## Blocking Protocol
+
 If you cannot complete the task:
+
 1. Start your response with `BLOCKED:`
 2. Explain exactly why you cannot proceed
 3. List what information or changes would unblock you
@@ -110,11 +127,10 @@ If you cannot complete the task:

 ## Anti-Patterns (Avoid)

- Do NOT implement code directly - delegate to Tier 3 Workers
- Do NOT skip TDD phases
- Do NOT batch commits - commit per-task
- Do NOT skip phase verification
 - Do NOT use native `edit` tool - use MCP tools
- 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.
+- Do NOT read full large files - use skeleton tools first
+- Do NOT add comments unless requested
+- 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.
@@ -2,8 +2,7 @@
 description: Stateless Tier 4 QA Agent for error analysis and diagnostics
 mode: subagent
 model: MiniMax-M2.5
-temperature: 0.0
-steps: 5
+temperature: 0.2
 permission:
  edit: deny
  bash:
@@ -17,11 +16,17 @@ STRICT SYSTEM DIRECTIVE: You are a stateless Tier 4 QA Agent.
 Your goal is to analyze errors, summarize logs, or verify tests.
 ONLY output the requested analysis. No pleasantries.

+## Context Amnesia
+
+You operate statelessly. Each analysis starts fresh.
+Do not assume knowledge from previous analyses or sessions.
+
 ## CRITICAL: MCP Tools Only (Native Tools Banned)

 You MUST use Manual Slop's MCP tools. Native OpenCode tools are unreliable.

 ### Read-Only MCP Tools (USE THESE)
+
 | Native Tool | MCP Tool |
 |-------------|----------|
 | `read` | `manual-slop_read_file` |
@@ -35,17 +40,15 @@ You MUST use Manual Slop's MCP tools. Native OpenCode tools are unreliable.
 | - | `manual-slop_get_file_slice` (read specific line range) |

 ### Shell Commands
+
 | Native Tool | MCP Tool |
 |-------------|----------|
 | `bash` | `manual-slop_run_powershell` |

-## Context Amnesia
-You operate statelessly. Each analysis starts fresh.
-Do not assume knowledge from previous analyses or sessions.
-
 ## Analysis Start Checklist (MANDATORY)

 Before analyzing:
+
 1. [ ] Read error output/test failure completely
 2. [ ] Identify affected files from traceback
 3. [ ] Use skeleton tools for files >50 lines (`manual-slop_py_get_skeleton`)
@@ -54,16 +57,20 @@ Before analyzing:
 ## Analysis Protocol

 ### 1. Understand the Error
+
 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
 - `manual-slop_get_git_diff` - Check recent changes

 ### 3. Root Cause Analysis
+
 Provide a structured analysis:

 ```
@@ -86,28 +93,30 @@ Provide a structured analysis:
 ```

 ## Limitations
+
 - **READ-ONLY**: Do NOT modify any files
 - **ANALYSIS ONLY**: Do NOT implement fixes
 - **NO ASSUMPTIONS**: Base analysis only on provided context and tool output

 ## Quality Checklist
+
 - [ ] Analysis is based on actual code/file content
 - [ ] Root cause is specific, not generic
 - [ ] Evidence includes file:line references
 - [ ] Recommendations are actionable but not implemented

 ## Blocking Protocol
+
 If you cannot analyze the error:
+
 1. Start your response with `CANNOT ANALYZE:`
 2. Explain what information is missing
 3. List what would be needed to complete the analysis

 ## Anti-Patterns (Avoid)

- Do NOT implement code directly - delegate to Tier 3 Workers
- Do NOT skip TDD phases
- Do NOT batch commits - commit per-task
- Do NOT skip phase verification
- 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.
+- Do NOT implement fixes - analysis only
+- 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.
@@ -1,11 +1,33 @@
 ---
-description: Invoke Tier 1 Orchestrator for product alignment and track initialization
+description: Invoke Tier 1 Orchestrator for product alignment, high-level planning, and track initialization
 agent: tier1-orchestrator
-subtask: true
 ---

 $ARGUMENTS

 ---

-Invoke the Tier 1 Orchestrator with the above context. Focus on product alignment, high-level planning, and track initialization. Follow the Surgical Methodology: audit existing code before specifying, identify gaps not features, and write worker-ready tasks.
+## Context
+
+You are now acting as Tier 1 Orchestrator.
+
+### Primary Responsibilities
+- Product alignment and strategic planning
+- Track initialization (`/conductor-new-track`)
+- Session setup (`/conductor-setup`)
+- Delegate execution to Tier 2 Tech Lead
+
+### The Surgical Methodology (MANDATORY)
+
+1. **AUDIT BEFORE SPECIFYING**: Never write a spec without first reading actual code using MCP tools. Document existing implementations with file:line references.
+
+2. **IDENTIFY GAPS, NOT FEATURES**: Frame requirements around what's MISSING.
+
+3. **WRITE WORKER-READY TASKS**: Each task must specify WHERE/WHAT/HOW/SAFETY.
+
+4. **REFERENCE ARCHITECTURE DOCS**: Link to `docs/guide_*.md` sections.
+
+### Limitations
+- READ-ONLY: Do NOT write code or edit files (except track spec/plan/metadata)
+- Do NOT execute tracks — delegate to Tier 2
+- Do NOT implement features — delegate to Tier 3 Workers
@@ -7,4 +7,67 @@ $ARGUMENTS

 ---

-Invoke the Tier 2 Tech Lead with the above context. Follow TDD protocol (Red -> Green -> Refactor), delegate implementation to Tier 3 Workers, and maintain persistent memory throughout track execution. Commit atomically per-task.
+## Context
+
+You are now acting as Tier 2 Tech Lead.
+
+### Primary Responsibilities
+- Track execution (`/conductor-implement`)
+- Architectural oversight
+- Delegate to Tier 3 Workers via Task tool
+- Delegate error analysis to Tier 4 QA via Task tool
+- Maintain persistent memory throughout track execution
+
+### Context Management
+
+**MANUAL COMPACTION ONLY** — Never rely on automatic context summarization.
+You maintain PERSISTENT MEMORY throughout track execution — do NOT apply Context Amnesia to your own session.
+
+### Pre-Delegation Checkpoint (MANDATORY)
+
+Before delegating ANY dangerous or non-trivial change to Tier 3:
+
+```
+git add .
+```
+
+**WHY**: If a Tier 3 Worker fails or incorrectly runs `git restore`, you will lose ALL prior AI iterations for that file if it wasn't staged/committed.
+
+### TDD Protocol (MANDATORY)
+
+1. **Red Phase**: Write failing tests first — CONFIRM FAILURE
+2. **Green Phase**: Implement to pass — CONFIRM PASS
+3. **Refactor Phase**: Optional, with passing tests
+
+### Commit Protocol (ATOMIC PER-TASK)
+
+After completing each task:
+1. Stage: `git add .`
+2. Commit: `feat(scope): description`
+3. Get hash: `git log -1 --format="%H"`
+4. Attach note: `git notes add -m "summary" <hash>`
+5. Update plan.md: Mark `[x]` with SHA
+6. Commit plan update: `git add plan.md && git commit -m "conductor(plan): Mark task complete"`
+
+### Delegation Pattern
+
+**Tier 3 Worker** (Task tool):
+```
+subagent_type: "tier3-worker"
+description: "Brief task name"
+prompt: |
+ WHERE: file.py:line-range
+ WHAT: specific change
+ HOW: API calls/patterns
+ SAFETY: thread constraints
+ Use 1-space indentation.
+```
+
+**Tier 4 QA** (Task tool):
+```
+subagent_type: "tier4-qa"
+description: "Analyze failure"
+prompt: |
+ [Error output]
+ DO NOT fix - provide root cause analysis only.
+```
@@ -7,4 +7,49 @@ $ARGUMENTS

 ---

-Invoke the Tier 3 Worker with the above task. Operate statelessly with context amnesia. Implement the specified change exactly as described. Use 1-space indentation for Python code. Do NOT add comments unless requested.
+## Context
+
+You are now acting as Tier 3 Worker.
+
+### Key Constraints
+
+- **STATELESS**: Context Amnesia — each task starts fresh
+- **MCP TOOLS ONLY**: Use `manual-slop_*` tools, NEVER native tools
+- **SURGICAL**: Follow WHERE/WHAT/HOW/SAFETY exactly
+- **1-SPACE INDENTATION**: For all Python code
+
+### Task Execution Protocol
+
+1. **Read Task Prompt**: Identify WHERE/WHAT/HOW/SAFETY
+2. **Use Skeleton Tools**: For files >50 lines, use `manual-slop_py_get_skeleton` or `manual-slop_get_file_summary`
+3. **Implement Exactly**: Follow specifications precisely
+4. **Verify**: Run tests if specified via `manual-slop_run_powershell`
+5. **Report**: Return concise summary (what, where, issues)
+
+### Edit MCP Tools (USE THESE - BAN NATIVE EDIT)
+
+| Native Tool | MCP Tool |
+|-------------|----------|
+| `edit` | `manual-slop_edit_file` (find/replace, preserves indentation) |
+| `edit` | `manual-slop_py_update_definition` (replace function/class) |
+| `edit` | `manual-slop_set_file_slice` (replace line range) |
+| `edit` | `manual-slop_py_set_signature` (replace signature only) |
+| `edit` | `manual-slop_py_set_var_declaration` (replace variable) |
+
+**CRITICAL**: The native `edit` tool DESTROYS 1-space indentation. ALWAYS use MCP tools.
+
+### Blocking Protocol
+
+If you cannot complete the task:
+
+1. Start 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
+
+### Code Style (Python)
+
+- 1-space indentation
+- NO COMMENTS unless explicitly requested
+- Type hints where appropriate
+- Internal methods/variables prefixed with underscore
@@ -1,5 +1,5 @@
 ---
-description: Invoke Tier 4 QA for error analysis and diagnostics
+description: Invoke Tier 4 QA Agent for error analysis
 agent: tier4-qa
 ---

@@ -7,4 +7,69 @@ $ARGUMENTS

 ---

-Invoke the Tier 4 QA Agent with the above context. Analyze errors, summarize logs, or verify tests. Provide root cause analysis with file:line evidence. DO NOT implement fixes - analysis only.
+## Context
+
+You are now acting as Tier 4 QA Agent.
+
+### Key Constraints
+
+- **STATELESS**: Context Amnesia — each analysis starts fresh
+- **READ-ONLY**: Do NOT modify any files
+- **ANALYSIS ONLY**: Do NOT implement fixes
+
+### Read-Only MCP Tools (USE THESE)
+
+| Native Tool | MCP Tool |
+|-------------|----------|
+| `read` | `manual-slop_read_file` |
+| `glob` | `manual-slop_search_files` or `manual-slop_list_directory` |
+| `grep` | `manual-slop_py_find_usages` |
+| - | `manual-slop_get_file_summary` (heuristic summary) |
+| - | `manual-slop_py_get_code_outline` (classes/functions with line ranges) |
+| - | `manual-slop_py_get_skeleton` (signatures + docstrings only) |
+| - | `manual-slop_py_get_definition` (specific function/class source) |
+| - | `manual-slop_get_git_diff` (file changes) |
+| - | `manual-slop_get_file_slice` (read specific line range) |
+
+### Analysis Protocol
+
+1. **Read Error Completely**: Understand the full error/test failure
+2. **Identify Affected Files**: Parse traceback for file:line references
+3. **Use Skeleton Tools**: For files >50 lines, use `manual-slop_py_get_skeleton` first
+4. **Announce**: "Analyzing: [error summary]"
+
+### Structured Output Format
+
+```
+## Error Analysis
+
+### Summary
+[One-sentence description of the error]
+
+### Root Cause
+[Detailed explanation of why the error occurred]
+
+### Evidence
+[File:line references supporting the analysis]
+
+### Impact
+[What functionality is affected]
+
+### Recommendations
+[Suggested fixes or next steps - but DO NOT implement them]
+```
+
+### Quality Checklist
+
+- [ ] Analysis based on actual code/file content
+- [ ] Root cause is specific, not generic
+- [ ] Evidence includes file:line references
+- [ ] Recommendations are actionable but not implemented
+
+### Blocking Protocol
+
+If you cannot analyze the error:
+
+1. Start response with `CANNOT ANALYZE:`
+2. Explain what information is missing
+3. List what would be needed to complete the analysis
@@ -10,7 +10,7 @@ A high-density GUI orchestrator for local LLM-driven coding sessions. Manual Slo
 **Providers**: Gemini API, Anthropic API, DeepSeek, Gemini CLI (headless), MiniMax
 **Platform**: Windows (PowerShell) — single developer, local use

-![img](./gallery/python_2026-03-07_14-32-50.png)
+![img](./gallery/python_2026-03-11_00-37-21.png)

 ---

@@ -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}")
@@ -0,0 +1,5 @@
+# Track external_mcp_support_20260308 Context
+
+- [Specification](./spec.md)
+- [Implementation Plan](./plan.md)
+- [Metadata](./metadata.json)
@@ -0,0 +1,8 @@
+{
+  "track_id": "external_mcp_support_20260308",
+  "type": "feature",
+  "status": "new",
+  "created_at": "2026-03-08T14:00:00Z",
+  "updated_at": "2026-03-08T14:00:00Z",
+  "description": "Add support for external MCP servers (Local Stdio and Remote SSE/WS) with flexible configuration and lifecycle management."
+}
@@ -0,0 +1,42 @@
+# Implementation Plan: External MCP Server Support
+
+## Phase 1: Configuration & Data Modeling [checkpoint: 4ba1bd9]
+- [x] Task: Define the schema for external MCP server configuration. [1c863f0]
+    - [x] Update `src/models.py` to include `MCPServerConfig` and `MCPConfiguration` classes.
+    - [x] Implement logic to load `mcp_config.json` from global and project-specific paths.
+- [x] Task: Integrate configuration loading into `AppController`. [c09e0f5]
+    - [x] Ensure the MCP config path is correctly resolved from `config.toml` and `manual_slop.toml`.
+- [x] Task: Write unit tests for configuration loading and validation. [c09e0f5]
+- [x] Task: Conductor - User Manual Verification 'Phase 1: Configuration & Data Modeling' [4ba1bd9]
+
+## Phase 2: MCP Client Extension [checkpoint: 828fadf]
+- [x] Task: Implement `ExternalMCPManager` in `src/mcp_client.py`. [828fadf]
+    - [x] Add support for managing multiple MCP server sessions.
+    - [x] Implement the `StdioMCPClient` for local subprocess communication.
+    - [x] Implement the `RemoteMCPClient` for SSE/WebSocket communication (stub).
+- [x] Task: Update Tool Discovery. [828fadf]
+    - [x] Implement `list_external_tools()` to aggregate tools from all active external servers.
+- [x] Task: Update Tool Dispatch. [828fadf]
+    - [x] Modify `mcp_client.dispatch()` and `mcp_client.async_dispatch()` to route tool calls to either native tools or the appropriate external server.
+- [x] Task: Write integration tests for stdio and remote MCP client communication (using mock servers). [828fadf]
+- [x] Task: Conductor - User Manual Verification 'Phase 2: MCP Client Extension' [828fadf]
+
+## Phase 3: GUI Integration & Lifecycle [checkpoint: 3b2588a]
+- [x] Task: Update the **Operations** panel in `src/gui_2.py`. [3b2588a]
+    - [x] Create a new "External Tools" section.
+    - [x] List discovered tools from active external servers.
+    - [x] Add a "Refresh External MCPs" button to reload configuration and rediscover tools.
+- [x] Task: Implement Lifecycle Management. [3b2588a]
+    - [x] Add the "Auto-start on Project Load" logic to start servers when a project is initialized.
+    - [x] Add status indicators (e.g., color-coded dots) for each external server in the GUI.
+- [x] Task: Write visual regression tests or simulation scripts to verify the updated Operations panel. [3b2588a]
+- [x] Task: Conductor - User Manual Verification 'Phase 3: GUI Integration & Lifecycle' [3b2588a]
+
+## Phase 4: Agent Integration & HITL [checkpoint: f4c5a0b]
+- [x] Task: Update AI tool declarations. [f4c5a0b]
+    - [x] Ensure `ai_client.py` includes external tools in the tool definitions sent to Gemini/Anthropic.
+- [x] Task: Verify HITL Approval Flow. [f4c5a0b]
+    - [x] Ensure that calling an external tool correctly triggers the `ConfirmDialog` modal.
+    - [x] Verify that approved external tool results are correctly returned to the AI.
+- [x] Task: Perform a final end-to-end verification with a real external MCP server. [f4c5a0b]
+- [x] Task: Conductor - User Manual Verification 'Phase 4: Agent Integration & HITL' [f4c5a0b]
@@ -0,0 +1,39 @@
+# Specification: External MCP Server Support
+
+## Overview
+This feature adds support for integrating external Model Context Protocol (MCP) servers into Manual Slop. This allows agents to utilize tools from a wide ecosystem of MCP servers (like those for databases, APIs, or specialized utilities) alongside the application's native tools.
+
+## Functional Requirements
+- **Server Protocol Support:**
+    - **Local Stdio:** Support for launching local subprocesses and communicating via JSON-RPC over stdio.
+    - **Remote (SSE/WS):** Support for connecting to remote MCP servers via Server-Sent Events or WebSockets.
+- **Flexible Configuration:**
+    - The path to the MCP configuration file (e.g., `mcp_config.json`) must be configurable globally in `config.toml`.
+    - Support for per-project overrides in `manual_slop.toml` to specify a project-specific MCP configuration.
+- **Lifecycle Management:**
+    - Provide a "Auto-start on Project Load" checkbox for each configured MCP server (or as a global/per-project default).
+    - If enabled, the server starts automatically when the project is loaded.
+    - If disabled, servers should be initialized on-demand or via a manual "Start" button in the GUI.
+- **Tool Discovery & UI Integration:**
+    - Automatically discover tools from configured servers using the MCP `listTools` capability.
+    - Display discovered tools in a unified "External Tools" section within the **Operations** panel.
+    - Ensure external tools are correctly mapped to agent tool declarations (Gemini, Anthropic, etc.).
+- **Security & HITL:**
+    - All tool calls from external MCP servers must adhere to the application's existing Human-in-the-Loop (HITL) approval mechanism.
+    - Users must review and approve the parameters of any external tool call before execution.
+
+## Non-Functional Requirements
+- **Performance:** Asynchronous communication with MCP servers to avoid blocking the main GUI thread.
+- **Robustness:** Gracefully handle server connection failures, timeouts, and process crashes.
+- **Scalability:** Support for multiple external MCP servers simultaneously.
+
+## Acceptance Criteria
+- [ ] Users can specify an MCP config path in `config.toml` and `manual_slop.toml`.
+- [ ] The GUI lists tools from configured external servers in a unified section.
+- [ ] Selecting an external tool correctly generates a tool call for the AI.
+- [ ] Approving an external tool call successfully executes it via the MCP bridge and returns the output to the AI.
+- [ ] Local stdio servers and remote SSE/WS servers are both functional.
+
+## Out of Scope
+- Support for MCP Resources or Prompts (focusing strictly on Tools for this track).
+- Managing installation of external MCP server dependencies (e.g., `npm install`, `pip install`).
@@ -3,13 +3,13 @@
 ## Phase 1: Path Info Display
 Focus: Show current path resolution in GUI

- [ ] Task 1.1: Add path info functions to paths.py
+- [x] Task 1.1: Add path info functions to paths.py [d237d3b]
  - WHERE: src/paths.py
  - WHAT: Add functions to get path resolution source (default/env/config)
  - HOW: Return tuple of (resolved_path, source)
  - SAFETY: New functions, no modifications

- [ ] Task 1.2: Create path display helper
+- [x] Task 1.2: Create path display helper [d237d3b]
  - WHERE: src/paths.py
  - WHAT: Function to get all paths with resolution info
  - HOW: Returns dict of path_name -> (resolved, source)
@@ -18,25 +18,25 @@ Focus: Show current path resolution in GUI
 ## Phase 2: Context Hub Panel
 Focus: Add Path Configuration panel to GUI

- [ ] Task 2.1: Add Paths tab to Context Hub
+- [x] Task 2.1: Add Paths tab to Context Hub [d237d3b]
  - WHERE: src/gui_2.py (Context Hub section)
  - WHAT: New tab/section for path configuration
  - HOW: Add ImGui tab item, follow existing panel patterns
  - SAFETY: New panel, no modifications to existing

- [ ] Task 2.2: Display current paths
+- [x] Task 2.2: Display current paths [d237d3b]
  - WHERE: src/gui_2.py (new paths panel)
  - WHAT: Show resolved paths and their sources
  - HOW: Call paths.py functions, display in read-only text
  - SAFETY: New code

- [ ] Task 2.3: Add path text inputs
+- [x] Task 2.3: Add path text inputs [d237d3b]
  - WHERE: src/gui_2.py (paths panel)
  - WHAT: Editable text inputs for each path
  - HOW: ImGui input_text for conductor_dir, logs_dir, scripts_dir
  - SAFETY: New code

- [ ] Task 2.4: Add browse buttons
+- [x] Task 2.4: Add browse buttons [d237d3b]
  - WHERE: src/gui_2.py (paths panel)
  - WHAT: File dialog buttons to browse for directories
  - HOW: Use existing file dialog patterns in gui_2.py
@@ -45,19 +45,19 @@ Focus: Add Path Configuration panel to GUI
 ## Phase 3: Persistence
 Focus: Save path changes to config.toml

- [ ] Task 3.1: Add config write function
+- [x] Task 3.1: Add config write function [d237d3b]
  - WHERE: src/gui_2.py or new utility
  - WHAT: Write [paths] section to config.toml
  - HOW: Read existing config, update paths section, write back
  - SAFETY: Backup before write, handle errors

- [ ] Task 3.2: Add Apply button
+- [x] Task 3.2: Add Apply button [d237d3b]
  - WHERE: src/gui_2.py (paths panel)
  - WHAT: Button to save changes
  - HOW: Call config write function, show success/error message
  - SAFETY: Confirmation dialog

- [ ] Task 3.3: Add Reset button
+- [x] Task 3.3: Add Reset button [d237d3b]
  - WHERE: src/gui_2.py (paths panel)
  - WHAT: Reset paths to defaults
  - HOW: Clear custom values, show confirmation
@@ -66,13 +66,13 @@ Focus: Save path changes to config.toml
 ## Phase 4: UX Polish
 Focus: Improve user experience

- [ ] Task 4.1: Add restart warning
+- [x] Task 4.1: Add restart warning [d237d3b]
  - WHERE: src/gui_2.py (paths panel)
  - WHAT: Show warning that changes require restart
  - HOW: Text label after Apply
  - SAFETY: New code

- [ ] Task 4.2: Add tooltips
+- [x] Task 4.2: Add tooltips [d237d3b]
  - WHERE: src/gui_2.py (paths panel)
  - WHAT: Explain each path and resolution order
  - HOW: ImGui set_tooltip on hover
@@ -81,7 +81,7 @@ Focus: Improve user experience
 ## Phase 5: Tests
 Focus: Verify GUI path configuration

- [ ] Task 5.1: Test path display
+- [x] Task 5.1: Test path display [d237d3b]
  - WHERE: tests/test_gui_paths.py (new file)
  - WHAT: Verify paths panel shows correct values
  - HOW: Mock paths.py, verify display
@@ -0,0 +1,5 @@
+# Track nerv_ui_theme_20260309 Context
+
+- [Specification](./spec.md)
+- [Implementation Plan](./plan.md)
+- [Metadata](./metadata.json)
@@ -0,0 +1,8 @@
+{
+    "description":  "Implement a NERV UI theme for ImGui/Dear PyGui, inspired by technical/military consoles, with CRT effects and a black-void aesthetic.",
+    "track_id":  "nerv_ui_theme_20260309",
+    "type":  "feature",
+    "created_at":  "2026-03-09T00:35:48Z",
+    "status":  "new",
+    "updated_at":  "2026-03-09T00:35:48Z"
+}
@@ -0,0 +1,43 @@
+# Implementation Plan: NERV UI Theme
+
+## Phase 1: Research & Theme Infrastructure [checkpoint: 4b78e77]
+- [x] Task: Research existing theme implementation in src/theme.py and src/theme_2.py. 3fa4f64
+- [x] Task: Create a new src/theme_nerv.py to house the NERV color constants and theme application logic. 3fa4f64
+- [x] Task: Conductor - User Manual Verification 'Phase 1: Research & Theme Infrastructure' (Protocol in workflow.md) 4b78e77
+
+## Phase 2: Base NERV Theme Implementation (Colors & Geometry) [checkpoint: 9c38ea7]
+- [x] Task: Implement the "Black Void" and "Phosphor" color palette in src/theme_nerv.py. 3fa4f64
+- [x] Task: Implement "Hard Edges" by setting all rounding parameters to 0.0 in the NERV theme. 3fa4f64
+- [x] Task: Write unit tests to verify that the NERV theme correctly applies colors and geometry settings. de0d9f3
+- [x] Task: Conductor - User Manual Verification 'Phase 2: Base NERV Theme Implementation' (Protocol in workflow.md) 9c38ea7
+
+## Phase 3: Visual Effects (Scanlines & Status Flickering) [checkpoint: ceb0c7d]
+- [x] Task: Research how to implement a scanline overlay in ImGui (e.g., using a full-screen transparent texture or a custom draw list). 05a2b8e
+- [x] Task: Implement the subtle scanline overlay (6% opacity). 05a2b8e
+- [x] Task: Implement "Status Flickering" logic for active system indicators (e.g., a periodic alpha modification for specific text elements). 05a2b8e
+- [x] Task: Write tests to verify the visual effect triggers (e.g., checking if the scanline overlay is rendered). 4f4fa10
+- [x] Task: Conductor - User Manual Verification 'Phase 3: Visual Effects' (Protocol in workflow.md) ceb0c7d
+
+## Phase 4: Alert Pulsing & Error States [checkpoint: d9495f6]
+- [x] Task: Implement "Alert Pulsing" logic that can be triggered by application error events. d9495f6
+- [x] Task: Integrate Alert Pulsing with the NERV theme (shifting borders/background to Alert Red). d9495f6
+- [x] Task: Write tests to verify that an error state triggers the pulsing effect in the NERV theme. d9495f6
+- [x] Task: Conductor - User Manual Verification 'Phase 4: Alert Pulsing & Error States' (Protocol in workflow.md) d9495f6
+
+## Phase 5: Integration & Theme Selector [checkpoint: afcb1bf]
+- [x] Task: Add "NERV" to the theme selection dropdown in src/gui_2.py. afcb1bf
+- [x] Task: Ensure that switching to the NERV theme correctly initializes all visual effects (scanlines, etc.). afcb1bf
+- [x] Task: Final UX verification and performance check of the NERV theme. afcb1bf
+- [x] Task: Conductor - User Manual Verification 'Phase 5: Integration & Theme Selector' (Protocol in workflow.md) afcb1bf
+
+## Phase 6: NERV Theme Refinement (Contrast & Readability) [checkpoint: 9facecb]
+- [x] Task: Fix text readability by ensuring high-contrast text on bright backgrounds (e.g., black text on orange title bars). 9facecb
+- [x] Task: Adjust the NERV palette to use Data Green or Steel for standard text, reserving Orange for accents and backgrounds. 9facecb
+- [x] Task: Update gui_2.py to push/pop style colors for headers if necessary to maintain readability. 9facecb
+- [x] Task: Conductor - User Manual Verification 'Phase 6: NERV Theme Refinement' (Protocol in workflow.md) 9facecb
+
+## Phase 7: CRT Filter Implementation [checkpoint: e635c29]
+- [x] Task: Research and implement a more sophisticated "CRT Filter" beyond simple scanlines (e.g., adding a vignette, noise, or subtle color aberration). e635c29
+- [x] Task: Implement a "CRT Filter" toggle in the theme settings. e635c29
+- [x] Task: Integrate the new CRT filter into the gui_2.py rendering loop. e635c29
+- [x] Task: Conductor - User Manual Verification 'Phase 7: CRT Filter Implementation' (Protocol in workflow.md) e635c29
@@ -0,0 +1,37 @@
+# Specification: NERV UI Theme Integration
+
+## Overview
+This track aims to implement a new "NERV" visual theme for the manual_slop application, inspired by the aesthetic of technical/military consoles (e.g., Evangelion's NERV UI). The theme will be added as a selectable option within the application, allowing users to switch between the existing theme and the new NERV style without altering the core user experience or layout.
+
+## Functional Requirements
+- **Theme Selection:** Integrate a "NERV" theme option into the existing UI (e.g., in the configuration or theme settings).
+- **Color Palette:** Implement the "Black Void" aesthetic using absolute black (#000000) for the background and CRT-inspired phosphor colors:
+    - **NERV Orange (#FF9830):** Primary accents, headers, active borders.
+    - **Data Green (#50FF50):** Terminal output, "Nominal" status, standard data.
+    - **Wire Cyan (#20F0FF):** Structural separators, inactive borders.
+    - **Alert Red (#FF4840):** Error states, critical alerts.
+    - **Steel (#E0E0D8):** Secondary text, timestamps.
+- **Hard Edges:** Configure all UI elements (windows, frames, buttons) to have zero rounded corners (Rounding = 0.0).
+- **Typography:** Utilize a monospace font (e.g., IBM Plex Mono or the project's current monospace font) for all text to maintain a technical look.
+- **Visual Effects:**
+    - **Scanline Overlay:** Implement a subtle CRT-style scanline overlay (approx. 6% opacity).
+    - **Status Flickering:** Add subtle flickering effects to active system status indicators.
+    - **Alert Pulsing:** Implement red background or border pulsing during error or critical system states.
+
+## Non-Functional Requirements
+- **Performance:** Ensure the scanline overlay and status flickering do not significantly degrade UI responsiveness or increase CPU usage.
+- **Maintainability:** The theme should be implemented in a way that is consistent with the existing theme.py or theme_2.py architecture.
+
+## Acceptance Criteria
+- [ ] Users can select "NERV" from the theme selector.
+- [ ] The background is solid black (#000000).
+- [ ] All borders and buttons have zero rounded corners.
+- [ ] The NERV color palette is correctly applied to all UI elements.
+- [ ] The scanline overlay is visible and subtle.
+- [ ] Active status indicators exhibit the "Status Flickering" effect.
+- [ ] Errors trigger the "Alert Pulsing" effect.
+
+## Out of Scope
+- **Bilingual Labels:** Japanese sub-labels will not be implemented.
+- **Layout Changes:** No radical changes to window positioning or spacing.
+- **New Features:** This track is purely visual and does not add new application functionality.
@@ -0,0 +1,10 @@
+{
+  "id": "opencode_config_overhaul_20260310",
+  "title": "OpenCode Configuration Overhaul",
+  "type": "fix",
+  "status": "completed",
+  "priority": "high",
+  "created": "2026-03-10",
+  "depends_on": [],
+  "blocks": []
+}
@@ -0,0 +1,23 @@
+# Implementation Plan: OpenCode Configuration Overhaul
+
+## Phase 1: Core Config and Agent Temperature/Step Fixes [checkpoint: 02abfc4]
+
+- [x] Task 1.1: Update `opencode.json` - set `compaction.auto: false`, `compaction.prune: false`
+- [x] Task 1.2: Update `.opencode/agents/tier1-orchestrator.md` - remove `steps: 50`, change `temperature: 0.4` to `0.5`, add "Context Management" section
+- [x] Task 1.3: Update `.opencode/agents/tier2-tech-lead.md` - remove `steps: 100`, change `temperature: 0.2` to `0.4`, add "Context Management" and "Pre-Delegation Checkpoint" sections
+- [x] Task 1.4: Update `.opencode/agents/tier3-worker.md` - remove `steps: 20`, change `temperature: 0.1` to `0.3`
+- [x] Task 1.5: Update `.opencode/agents/tier4-qa.md` - remove `steps: 5`, change `temperature: 0.0` to `0.2`
+- [x] Task 1.6: Update `.opencode/agents/general.md` - remove `steps: 15`, change `temperature: 0.2` to `0.3`
+- [x] Task 1.7: Update `.opencode/agents/explore.md` - remove `steps: 8`, change `temperature: 0.0` to `0.2`
+- [x] Task 1.8: Conductor - User Manual Verification (verified)
+
+## Phase 2: MMA Tier Command Expansion [checkpoint: 02abfc4]
+
+- [x] Task 2.1: Expand `.opencode/commands/mma-tier1-orchestrator.md` - add full Surgical Methodology, limitations, context section
+- [x] Task 2.2: Expand `.opencode/commands/mma-tier2-tech-lead.md` - add TDD protocol, Pre-Delegation Checkpoint, delegation patterns
+- [x] Task 2.3: Expand `.opencode/commands/mma-tier3-worker.md` - add key constraints, task execution, blocking protocol
+- [x] Task 2.4: Expand `.opencode/commands/mma-tier4-qa.md` - add key constraints, analysis protocol, structured output format
+- [x] Task 2.5: Conductor - User Manual Verification (verified)
+
+## Phase: Review Fixes
+- [x] Task: Apply review suggestions 8c5b5d3
@@ -0,0 +1,54 @@
+# Track Specification: OpenCode Configuration Overhaul
+
+## Overview
+Fix critical gaps in OpenCode agent configuration that cause MMA workflow failures. Remove step limits that prematurely terminate complex tracks, disable automatic context compaction that loses critical session state, raise temperature for better problem-solving, and expand thin command wrappers into full protocol documentation.
+
+## Current State Audit (as of HEAD)
+
+### Already Implemented (DO NOT re-implement)
+- OpenCode MCP integration working (`opencode.json:17-25`)
+- Agent persona files exist for all 4 MMA tiers (`.opencode/agents/tier*.md`)
+- Conductor commands exist (`.opencode/commands/conductor-*.md`)
+- MMA tier commands exist but are thin wrappers (`.opencode/commands/mma-tier*.md`)
+
+### Gaps to Fill (This Track's Scope)
+
+1. **Step Limits**: All agents have restrictive `steps` limits:
+   - tier1: 50, tier2: 100, tier3: 20, tier4: 5
+   - These terminate complex track implementations prematurely
+
+2. **Auto-Compaction**: `opencode.json` has `compaction.auto: true` which loses session context without user control
+
+3. **Temperature Too Low**: 
+   - tier2: 0.2, tier3: 0.1, tier4: 0.0
+   - Reduces creative problem-solving for complex tracks
+
+4. **Thin Command Wrappers**: `mma-tier*.md` commands are 3-4 lines, lacking:
+   - Pre-delegation checkpoint protocol
+   - TDD phase confirmation requirements
+   - Blocking protocol
+   - Context management guidance
+
+## Goals
+- Remove all step limits from agent configurations
+- Disable automatic compaction, enforce manual-only via `/compact`
+- Raise temperatures to 0.2-0.5 range for better reasoning
+- Expand MMA tier commands with full protocol documentation
+
+## Functional Requirements
+- All 6 agent files updated with removed `steps` and adjusted `temperature`
+- `opencode.json` updated with `compaction.auto: false, prune: false`
+- All 4 MMA tier commands expanded with context, protocols, and patterns
+
+## Non-Functional Requirements
+- No functional changes to MCP tool usage or permissions
+- Maintain backward compatibility with existing workflow
+
+## Architecture Reference
+- `docs/guide_mma.md` - 4-tier architecture, worker lifecycle, context amnesia
+- `docs/guide_meta_boundary.md` - Application vs Meta-Tooling distinction
+
+## Out of Scope
+- Model tiering (using different models per tier)
+- Changes to Gemini CLI configuration
+- Changes to conductor workflow itself
@@ -3,13 +3,13 @@
 ## Phase 1: Extend paths.py
 Focus: Add project-specific path resolution

- [ ] Task 1.1: Add project-aware conductor path functions
+- [x] Task 1.1: Add project-aware conductor path functions [48e2ed8]
  - WHERE: src/paths.py
  - WHAT: Add optional project_path parameter to get_conductor_dir, get_tracks_dir, get_track_state_dir
  - HOW: If project_path provided, resolve relative to project root; otherwise use global
  - SAFETY: Maintain backward compatibility with no-arg calls

- [ ] Task 1.2: Add project conductor path resolution
+- [x] Task 1.2: Add project conductor path resolution [48e2ed8]
  - WHERE: src/paths.py
  - WHAT: New function `_resolve_project_conductor_dir(project_path)` that reads from project TOML
  - HOW: Load project TOML, check `[conductor].dir` key
@@ -18,18 +18,18 @@ Focus: Add project-specific path resolution
 ## Phase 2: Update project_manager.py
 Focus: Use project-specific paths for track operations

- [ ] Task 2.1: Update save_track_state to use project conductor dir
+- [x] Task 2.1: Update save_track_state to use project conductor dir [3999e9c]
  - WHERE: src/project_manager.py (around line 240)
  - WHAT: Pass project base_dir to paths.get_track_state_dir()
  - HOW: Get base_dir from project_path, call paths with project_path param
  - SAFETY: Maintain existing function signature compatibility

- [ ] Task 2.2: Update load_track_state to use project conductor dir
+- [x] Task 2.2: Update load_track_state to use project conductor dir [3999e9c]
  - WHERE: src/project_manager.py (around line 252)
  - WHAT: Load track state from project-specific directory
  - HOW: Same as above

- [ ] Task 2.3: Update get_all_tracks to use project conductor dir
+- [x] Task 2.3: Update get_all_tracks to use project conductor dir [3999e9c]
  - WHERE: src/project_manager.py (around line 297)
  - WHAT: List tracks from project-specific directory
  - HOW: Accept optional project_path param
@@ -37,7 +37,7 @@ Focus: Use project-specific paths for track operations
 ## Phase 3: Update app_controller.py
 Focus: Pass project path to track operations

- [ ] Task 3.1: Update track creation to use project conductor dir
+- [x] Task 3.1: Update track creation to use project conductor dir [3999e9c]
  - WHERE: src/app_controller.py (around line 1907, 1937)
  - WHAT: Pass active_project_path to track path functions
  - HOW: Get active_project_path, pass to paths.get_tracks_dir()
@@ -46,13 +46,13 @@ Focus: Pass project path to track operations
 ## Phase 4: Tests
 Focus: Verify project-specific behavior

- [ ] Task 4.1: Write test for project-specific conductor dir
+- [x] Task 4.1: Write test for project-specific conductor dir [48e2ed8]
  - WHERE: tests/test_project_paths.py (new file)
  - WHAT: Create mock project with custom conductor dir, verify tracks saved there
  - HOW: Mock project_manager, verify path resolution
  - SAFETY: New test file

- [ ] Task 4.2: Test backward compatibility
+- [x] Task 4.2: Test backward compatibility [3999e9c]
  - WHERE: tests/test_project_paths.py
  - WHAT: Verify global paths still work without project_path
  - HOW: Call functions without project_path, verify defaults
--- a/Show More
+++ b/Show More