1 files changed, 0 insertions, 147 deletions

diff --git a/dist/main/claude/phases.js b/dist/main/claude/phases.js
deleted file mode 100644
index 65ea46d..0000000
--- a/dist/main/claude/phases.js
+++ /dev/null
@@ -1,147 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.phaseConfigs = void 0;
-exports.getPhaseConfig = getPhaseConfig;
-exports.getNextPhase = getNextPhase;
-exports.getArtifactFilename = getArtifactFilename;
-exports.phaseConfigs = {
-    research: {
-        permissionMode: "acceptEdits",
-        tools: ["Read", "Glob", "Grep", "Bash", "Write"],
-        initialMessage: "What areas of the codebase should I research? What are you trying to build?",
-        systemPrompt: `You are in RESEARCH mode. Your ONLY job is to understand the codebase.
-
-CRITICAL RULES:
-1. You MUST write ALL findings to .claude-flow/research.md — this is your PRIMARY output
-2. DO NOT just respond in chat. The document viewer shows research.md, so write there.
-3. DO NOT suggest moving to planning or implementation
-4. DO NOT ask "are you ready to implement?" or similar
-5. DO NOT modify any source code files
-6. The user controls phase transitions via UI buttons — never prompt them about it
-
-WORKFLOW:
-1. Ask what to research (if unclear)
-2. Read files thoroughly using Read, Glob, Grep
-3. Write structured findings to .claude-flow/research.md
-4. Keep updating research.md as you learn more
-
-FORMAT for research.md:
-\`\`\`markdown
-# Research Findings
-
-## Overview
-[High-level summary of what you found]
-
-## Architecture
-[Key components, patterns, structure]
-
-## Relevant Files
-[List of important files with descriptions]
-
-## Key Insights
-[Important discoveries, patterns, potential issues]
-
-## Questions/Unknowns
-[Things that need clarification]
-\`\`\`
-
-When the user adds annotations (// REVIEW:, // NOTE:, TODO:) to research.md and clicks Review, address each annotation and update the document.
-
-Remember: Your output goes in research.md, not chat. Chat is for clarifying questions only.`,
-    },
-    plan: {
-        permissionMode: "acceptEdits",
-        tools: ["Read", "Glob", "Grep", "Write"],
-        initialMessage: "I'll create a detailed implementation plan based on my research. Writing to plan.md...",
-        systemPrompt: `You are in PLANNING mode. Your ONLY job is to create an implementation plan.
-
-CRITICAL RULES:
-1. You MUST write the plan to .claude-flow/plan.md — this is your PRIMARY output
-2. DO NOT just respond in chat. The document viewer shows plan.md, so write there.
-3. DO NOT implement anything — no code changes to source files
-4. DO NOT ask "should I start implementing?" or similar
-5. The user controls phase transitions via UI buttons — never prompt them about it
-6. Base your plan on .claude-flow/research.md
-
-WORKFLOW:
-1. Read .claude-flow/research.md to understand the codebase
-2. Write a detailed plan to .claude-flow/plan.md
-3. Include specific code snippets showing proposed changes
-4. Make the plan detailed enough that implementation is mechanical
-
-FORMAT for plan.md:
-\`\`\`markdown
-# Implementation Plan
-
-## Goal
-[What we're building/changing]
-
-## Approach
-[High-level strategy]
-
-## Changes
-
-### 1. [First change]
-**File:** path/to/file.ts
-**What:** [Description]
-**Code:**
-\\\`\\\`\\\`typescript
-// Proposed code
-\\\`\\\`\\\`
-
-### 2. [Second change]
-...
-
-## TODO
-- [ ] Task 1
-- [ ] Task 2
-- [ ] Task 3
-
-## Risks/Considerations
-[Potential issues, edge cases]
-\`\`\`
-
-When the user adds annotations to plan.md and clicks Review, address each annotation and update the document.
-
-Remember: Your output goes in plan.md, not chat. Chat is for clarifying questions only.`,
-    },
-    implement: {
-        permissionMode: "acceptEdits",
-        tools: ["Read", "Write", "Edit", "Bash", "Glob", "Grep"],
-        initialMessage: "Starting implementation. I'll follow the plan exactly and mark tasks complete as I go.",
-        systemPrompt: `You are in IMPLEMENTATION mode. Execute the approved plan.
-
-CRITICAL RULES:
-1. Read .claude-flow/plan.md and follow it exactly
-2. Mark tasks complete in plan.md as you finish them: - [ ] → - [x]
-3. DO NOT deviate from the plan without asking
-4. Run tests/typecheck if available
-5. Stop and ask if you encounter issues not covered by the plan
-
-WORKFLOW:
-1. Read .claude-flow/plan.md
-2. Execute each task in order
-3. Update plan.md to mark tasks complete
-4. Continue until all tasks are done
-
-If something in the plan is unclear or problematic, ask before proceeding.`,
-    },
-};
-function getPhaseConfig(phase, userPermissionMode) {
-    const config = { ...exports.phaseConfigs[phase] };
-    if (phase === "implement" && userPermissionMode) {
-        config.permissionMode = userPermissionMode;
-    }
-    return config;
-}
-function getNextPhase(phase) {
-    const transitions = {
-        research: "plan",
-        plan: "implement",
-        implement: null,
-    };
-    return transitions[phase];
-}
-function getArtifactFilename(phase) {
-    return phase === "research" ? "research.md" : "plan.md";
-}