@codebakers/mcp 5.4.2 → 5.4.3

package/README.md

@@ -1,412 +1,412 @@
-# CodeBakers MCP Server v5.1.0
-
-**Complete autonomous application builder with MCP architecture**
-
-Full autonomous build system - from mockups to production-ready app in 30 minutes. Drop design mockups, run autonomous build, deploy. Zero human intervention required.
-
----
-
-## 🎯 What This Is
-
-An MCP (Model Context Protocol) server that:
-- **Builds entire applications autonomously** (mockups → deployed app)
-- **Validates mockup quality** (detects and auto-fixes design issues)
-- **Generates complete vertical slices** (schema → API → store → UI → tests)
-- **Updates all dependencies automatically** (zero stale UI bugs)
-- **Enforces production quality** (security, error handling, testing, mobile)
-- **Provides 25 specialized tools** (mockup validation, code generation, testing, orchestration)
-
-**Key Innovation:** Not just code generation - full autonomous execution with dependency awareness and quality enforcement.
-
----
-
-## 🏗️ Current Build Status
-
-### ✅ v5.1.0 - FULLY AUTONOMOUS (100% Complete)
-
-**25 Production-Ready Tools:**
-
-**Phase 0: Planning (2 tools)**
-- ✅ `codebakers_get_context` - Auto-detect project state
-- ✅ `codebakers_init_session` - Session initialization
-
-**Phase 0.5: Spec Generation (1 tool)**
-- ✅ `codebakers_generate_spec` - Generate PROJECT-SPEC.md
-
-**Phase 1: Interview (1 tool)**
-- ✅ `codebakers_run_interview` - Automated interview → FLOWS.md
-
-**Phase 2: Mockup Quality (3 tools)**
-- ✅ `codebakers_validate_mockups` - Detect quality issues
-- ✅ `codebakers_fix_mockups` - Auto-fix mockup problems
-- ✅ `codebakers_verify_mockups` - Final verification (100% perfect)
-
-**Phase 2: Analysis & Schema (4 tools)**
-- ✅ `codebakers_analyze_mockups_deep` - Extract components/data/interactions
-- ✅ `codebakers_generate_schema` - Generate database schema
-- ✅ `codebakers_map_dependencies` - Map all dependencies
-- ✅ `codebakers_generate_store_contracts` - Generate store contracts
-
-**Phase 3+: Code Generation (4 tools)**
-- ✅ `codebakers_generate_migration` - Supabase migrations
-- ✅ `codebakers_generate_api_route` - Next.js API routes
-- ✅ `codebakers_generate_store` - Zustand stores (dependency-aware)
-- ✅ `codebakers_generate_component` - React components (all 4 states)
-
-**Testing (3 tools)**
-- ✅ `codebakers_generate_unit_tests` - Vitest unit tests
-- ✅ `codebakers_generate_e2e_tests` - Playwright E2E tests
-- ✅ `codebakers_run_tests` - Orchestrate test execution
-
-**Orchestration (3 tools)**
-- ✅ `codebakers_execute_atomic_unit` - Execute 8-step atomic unit
-- ✅ `codebakers_verify_completeness` - Verify feature completeness
-- ✅ `codebakers_autonomous_build` - Build entire app autonomously
-
-**Enforcement (4 tools)**
-- ✅ `codebakers_check_gate` - Phase verification
-- ✅ `codebakers_enforce_feature` - Feature build enforcement
-- ✅ `codebakers_fix_commit` - Auto-fix commit violations
-- ✅ `codebakers_check_scope` - Scope enforcement
-
-**Total:** 25 tools, 100% implemented, fully tested
-
----
-
-## 📦 Installation
-
-### One-Command Installation (Recommended)
-
-```bash
-npx @codebakers/mcp install
-```
-
-That's it! This command will:
-- ✓ Auto-locate your Claude Desktop config
-- ✓ Add CodeBakers MCP Server configuration
-- ✓ Set the correct path automatically
-- ✓ No manual JSON editing required
-
-**After installation:**
-1. Restart Claude Desktop
-2. CodeBakers tools will be available automatically
-3. Verify: Run `codebakers_get_context` in Claude Desktop
-
-**Other commands:**
-```bash
-npx @codebakers/mcp status      # Check installation
-npx @codebakers/mcp uninstall   # Remove
-npx @codebakers/mcp help        # Show all commands
-```
-
----
-
-### Manual Installation (Advanced)
-
-See [INSTALL.md](./INSTALL.md) for detailed manual installation steps and troubleshooting.
-
----
-
-### Development Installation (Contributors)
-
-```bash
-# Clone repository
-git clone https://github.com/botmakers-ai/codebakers-v2.git
-cd codebakers-v2/codebakers-mcp-server
-
-# Install and build
-npm install
-npm run build
-
-# Install CLI
-npx . install
-```
-
-This will configure Claude Desktop to use your local development build.
-
----
-
-## 🎮 How It Works
-
-### Autonomous Build Flow (End-to-End)
-
-**User provides:** "Build an email client for teams"
-
-**System executes (zero human intervention):**
-
-```
-1. codebakers_run_interview { project_description: "email client for teams" }
-   → Generates: project-profile.md, FLOWS.md (15 features), BRAIN.md
-
-2. User drops mockups in refs/design/
-
-3. codebakers_validate_mockups
-   → Detects: 7 issues (3 critical, 4 warnings)
-
-4. codebakers_fix_mockups
-   → Auto-fixes: 5 issues, generates missing states, mobile mockups
-
-5. codebakers_verify_mockups
-   → ✅ PERFECT (100/100 score)
-
-6. codebakers_analyze_mockups_deep
-   → Extracts: All components, data fields, interactions from perfect mockups
-
-7. codebakers_generate_schema
-   → Creates: SCHEMA.sql (derived from perfect mockups)
-
-8. codebakers_map_dependencies
-   → Creates: DEPENDENCY-MAP.md (complete graph)
-
-9. codebakers_check_gate { phase: 2 }
-   → ✅ PASS (Phase 2 complete)
-
-10. codebakers_autonomous_build { mode: "full" }
-    → For each of 15 features:
-      a. codebakers_execute_atomic_unit
-         - Migration → API routes → Store → Component → Tests
-      b. codebakers_verify_completeness
-      c. Mark feature complete in FLOWS.md
-    → Final: 15/15 features complete
-
-11. codebakers_run_tests { test_type: "all" }
-    → Unit tests: 127/127 passing
-    → E2E tests: 32/32 passing
-
-12. Build complete - Ready for deployment
-```
-
-**Time:** 15-30 minutes (depends on feature count)
-**Human intervention:** Zero (except design mockups + final review)
-
----
-
-### Quality Guarantees (Every Feature)
-
-✅ **Security:** All queries filter by `user_id`
-✅ **Error handling:** All 4 states (loading/error/empty/success)
-✅ **Type safety:** TypeScript strict mode
-✅ **Testing:** Unit (Vitest) + E2E (Playwright)
-✅ **Mobile:** Responsive design
-✅ **Dependencies:** All stores updated (from DEPENDENCY-MAP.md)
-✅ **Standards:** CodeBakers method enforced
-✅ **Atomic:** Complete vertical slices (no half-built features)
-
----
-
-## 🚀 Use Cases
-
-### 1. MVP in 30 Minutes
-- Drop mockups
-- Run autonomous build
-- Deploy to Vercel
-- **Result:** Production MVP
-
-### 2. Prototypes at Scale
-- Test 5 different product ideas
-- Each takes 30 min autonomous build
-- **Result:** 5 working prototypes in 3 hours
-
-### 3. Internal Tools (No Manual Coding)
-- Company needs CRM, dashboard, admin panel
-- Generate mockups (Figma/v0)
-- Run autonomous builds
-- **Result:** 3 internal tools, zero manual coding
-
-### 4. Teaching Tool
-- Show students complete build process
-- Execute atomic unit step-by-step
-- **Result:** Learn by watching autonomous builds
-
-### 5. Client Demos
-- Client describes what they want
-- Generate mockups together
-- Run autonomous build in meeting
-- **Result:** Working demo before they leave
-
----
-
-## 📝 File Structure
-
-```
-codebakers-mcp-server/
-├── package.json
-├── tsconfig.json
-├── README.md (this file)
-├── src/
-│   ├── index.ts (MCP server entry point)
-│   ├── tools/
-│   │   ├── get-context.ts ✅ COMPLETE
-│   │   ├── init-session.ts ✅ COMPLETE
-│   │   ├── generate-spec.ts 🚧 STUB
-│   │   ├── analyze-mockups.ts 🚧 STUB
-│   │   ├── generate-schema.ts 🚧 STUB
-│   │   ├── map-dependencies.ts 🚧 STUB (CRITICAL)
-│   │   ├── generate-store-contracts.ts 🚧 STUB
-│   │   ├── check-gate.ts 🚧 STUB
-│   │   ├── enforce-feature.ts 🚧 STUB
-│   │   ├── fix-commit.ts 🚧 STUB
-│   │   └── check-scope.ts 🚧 STUB
-│   ├── lib/ (helper functions - to be created)
-│   └── phases/ (phase implementations - to be created)
-└── dist/ (compiled output)
-```
-
----
-
-## 🔗 Integration with CLAUDE.md
-
-**CLAUDE.md will be TINY** in v5.0.0:
-
-```markdown
-# CodeBakers V5
-
-You are a senior engineer using CodeBakers Method via MCP.
-
-## Session Start
-
-Every session:
-1. Auto-run: codebakers_get_context (detects state)
-2. Auto-run: codebakers_init_session (loads BUILD-STATE.md)
-3. Follow suggestions from context
-
-## User Requests
-
-When user types //:
-→ Call: codebakers_enforce_feature(feature_name)
-
-When user requests feature not in spec:
-→ Call: codebakers_check_scope(feature_description)
-
-## Hard Rules
-
-- Stack: Supabase + Next.js only
-- Queries: .maybeSingle() not .single()
-- Mutations: Filter by id AND user_id
-- Versions: --save-exact
-
-MCP tools handle everything else.
-```
-
-**That's it. ~30 lines instead of 1200.**
-
----
-
-## 🚀 Getting Started
-
-### Quick Start
-
-1. **Install:**
-   ```bash
-   npx @codebakers/mcp-server install
-   ```
-
-2. **Restart Claude Desktop**
-
-3. **Create new project:**
-   ```bash
-   mkdir my-app
-   cd my-app
-   ```
-
-4. **In Claude Desktop:**
-   ```
-   Run codebakers_run_interview with description: "email client for teams"
-   ```
-
-5. **Drop mockups in refs/design/**
-
-6. **Run autonomous build:**
-   ```
-   Run codebakers_autonomous_build with mode: "full"
-   ```
-
-7. **30 minutes later: Production-ready app** ✅
-
----
-
-### Full Documentation
-
-- **Installation Guide:** [INSTALL.md](./INSTALL.md)
-- **Complete Feature List:** [V5.1.0-AUTONOMOUS-BUILD-COMPLETE.md](../V5.1.0-AUTONOMOUS-BUILD-COMPLETE.md)
-- **Main Framework:** [CLAUDE.md](../CLAUDE.md)
-
----
-
-## 📚 Architecture Decisions
-
-### Why MCP?
-
-**Problem:** Instruction-based enforcement is fragile (Claude can ignore it)
-
-**Solution:** MCP tools execute BEFORE Claude decides what to do
-- Context is loaded automatically
-- Dependencies are mapped before building
-- Scope is checked before expanding
-- Technical enforcement, not instructions
-
-### Why Self-Aware Context?
-
-**Problem:** User doesn't know what phase they're in or what to do next
-
-**Solution:** `codebakers_get_context` auto-detects and suggests
-- No manual commands needed
-- CodeBakers guides the user
-- Proactive, not reactive
-
-### Why Comprehensive Dependency Mapping?
-
-**Problem:** Stale UI bugs from missed store updates
-
-**Solution:** Map ALL dependencies in Phase 2 BEFORE building
-- Every mutation knows what to update
-- Every component knows what stores it needs
-- Zero surprises during build
-
----
-
-## 🤝 Contributing
-
-To implement a stub tool:
-
-1. Open the tool file (e.g., `src/tools/map-dependencies.ts`)
-2. Replace stub implementation with real logic
-3. Add helper functions to `src/lib/` if needed
-4. Update tests (when test suite is added)
-5. Rebuild: `npm run build`
-
-Example structure:
-
-```typescript
-// src/tools/map-dependencies.ts
-import { readMockAnalysis } from '../lib/readers.js';
-import { analyzeDependencies } from '../lib/analyzers.js';
-
-export async function mapDependencies(args: any): Promise<string> {
-  // 1. Read MOCK-ANALYSIS.md
-  const mockAnalysis = await readMockAnalysis();
-
-  // 2. Analyze dependencies
-  const deps = await analyzeDependencies(mockAnalysis);
-
-  // 3. Generate DEPENDENCY-MAP.md
-  await saveDependencyMap(deps);
-
-  return `✓ Dependency map generated
-  - ${deps.readPaths.length} read paths
-  - ${deps.writePaths.length} write paths
-  - ${deps.cascades.length} cascades`;
-}
-```
-
----
-
-## 📄 License
-
-MIT © 2026 BotMakers Inc.
-
----
-
-**Built as part of CodeBakers Method v5.0.0**
-
-For questions or issues: https://github.com/botmakers-ai/codebakers-v2
+# CodeBakers MCP Server v5.1.0
+
+**Complete autonomous application builder with MCP architecture**
+
+Full autonomous build system - from mockups to production-ready app in 30 minutes. Drop design mockups, run autonomous build, deploy. Zero human intervention required.
+
+---
+
+## 🎯 What This Is
+
+An MCP (Model Context Protocol) server that:
+- **Builds entire applications autonomously** (mockups → deployed app)
+- **Validates mockup quality** (detects and auto-fixes design issues)
+- **Generates complete vertical slices** (schema → API → store → UI → tests)
+- **Updates all dependencies automatically** (zero stale UI bugs)
+- **Enforces production quality** (security, error handling, testing, mobile)
+- **Provides 25 specialized tools** (mockup validation, code generation, testing, orchestration)
+
+**Key Innovation:** Not just code generation - full autonomous execution with dependency awareness and quality enforcement.
+
+---
+
+## 🏗️ Current Build Status
+
+### ✅ v5.1.0 - FULLY AUTONOMOUS (100% Complete)
+
+**25 Production-Ready Tools:**
+
+**Phase 0: Planning (2 tools)**
+- ✅ `codebakers_get_context` - Auto-detect project state
+- ✅ `codebakers_init_session` - Session initialization
+
+**Phase 0.5: Spec Generation (1 tool)**
+- ✅ `codebakers_generate_spec` - Generate PROJECT-SPEC.md
+
+**Phase 1: Interview (1 tool)**
+- ✅ `codebakers_run_interview` - Automated interview → FLOWS.md
+
+**Phase 2: Mockup Quality (3 tools)**
+- ✅ `codebakers_validate_mockups` - Detect quality issues
+- ✅ `codebakers_fix_mockups` - Auto-fix mockup problems
+- ✅ `codebakers_verify_mockups` - Final verification (100% perfect)
+
+**Phase 2: Analysis & Schema (4 tools)**
+- ✅ `codebakers_analyze_mockups_deep` - Extract components/data/interactions
+- ✅ `codebakers_generate_schema` - Generate database schema
+- ✅ `codebakers_map_dependencies` - Map all dependencies
+- ✅ `codebakers_generate_store_contracts` - Generate store contracts
+
+**Phase 3+: Code Generation (4 tools)**
+- ✅ `codebakers_generate_migration` - Supabase migrations
+- ✅ `codebakers_generate_api_route` - Next.js API routes
+- ✅ `codebakers_generate_store` - Zustand stores (dependency-aware)
+- ✅ `codebakers_generate_component` - React components (all 4 states)
+
+**Testing (3 tools)**
+- ✅ `codebakers_generate_unit_tests` - Vitest unit tests
+- ✅ `codebakers_generate_e2e_tests` - Playwright E2E tests
+- ✅ `codebakers_run_tests` - Orchestrate test execution
+
+**Orchestration (3 tools)**
+- ✅ `codebakers_execute_atomic_unit` - Execute 8-step atomic unit
+- ✅ `codebakers_verify_completeness` - Verify feature completeness
+- ✅ `codebakers_autonomous_build` - Build entire app autonomously
+
+**Enforcement (4 tools)**
+- ✅ `codebakers_check_gate` - Phase verification
+- ✅ `codebakers_enforce_feature` - Feature build enforcement
+- ✅ `codebakers_fix_commit` - Auto-fix commit violations
+- ✅ `codebakers_check_scope` - Scope enforcement
+
+**Total:** 25 tools, 100% implemented, fully tested
+
+---
+
+## 📦 Installation
+
+### One-Command Installation (Recommended)
+
+```bash
+npx @codebakers/mcp install
+```
+
+That's it! This command will:
+- ✓ Auto-locate your Claude Desktop config
+- ✓ Add CodeBakers MCP Server configuration
+- ✓ Set the correct path automatically
+- ✓ No manual JSON editing required
+
+**After installation:**
+1. Restart Claude Desktop
+2. CodeBakers tools will be available automatically
+3. Verify: Run `codebakers_get_context` in Claude Desktop
+
+**Other commands:**
+```bash
+npx @codebakers/mcp status      # Check installation
+npx @codebakers/mcp uninstall   # Remove
+npx @codebakers/mcp help        # Show all commands
+```
+
+---
+
+### Manual Installation (Advanced)
+
+See [INSTALL.md](./INSTALL.md) for detailed manual installation steps and troubleshooting.
+
+---
+
+### Development Installation (Contributors)
+
+```bash
+# Clone repository
+git clone https://github.com/botmakers-ai/codebakers-v2.git
+cd codebakers-v2/codebakers-mcp-server
+
+# Install and build
+npm install
+npm run build
+
+# Install CLI
+npx . install
+```
+
+This will configure Claude Desktop to use your local development build.
+
+---
+
+## 🎮 How It Works
+
+### Autonomous Build Flow (End-to-End)
+
+**User provides:** "Build an email client for teams"
+
+**System executes (zero human intervention):**
+
+```
+1. codebakers_run_interview { project_description: "email client for teams" }
+   → Generates: project-profile.md, FLOWS.md (15 features), BRAIN.md
+
+2. User drops mockups in refs/design/
+
+3. codebakers_validate_mockups
+   → Detects: 7 issues (3 critical, 4 warnings)
+
+4. codebakers_fix_mockups
+   → Auto-fixes: 5 issues, generates missing states, mobile mockups
+
+5. codebakers_verify_mockups
+   → ✅ PERFECT (100/100 score)
+
+6. codebakers_analyze_mockups_deep
+   → Extracts: All components, data fields, interactions from perfect mockups
+
+7. codebakers_generate_schema
+   → Creates: SCHEMA.sql (derived from perfect mockups)
+
+8. codebakers_map_dependencies
+   → Creates: DEPENDENCY-MAP.md (complete graph)
+
+9. codebakers_check_gate { phase: 2 }
+   → ✅ PASS (Phase 2 complete)
+
+10. codebakers_autonomous_build { mode: "full" }
+    → For each of 15 features:
+      a. codebakers_execute_atomic_unit
+         - Migration → API routes → Store → Component → Tests
+      b. codebakers_verify_completeness
+      c. Mark feature complete in FLOWS.md
+    → Final: 15/15 features complete
+
+11. codebakers_run_tests { test_type: "all" }
+    → Unit tests: 127/127 passing
+    → E2E tests: 32/32 passing
+
+12. Build complete - Ready for deployment
+```
+
+**Time:** 15-30 minutes (depends on feature count)
+**Human intervention:** Zero (except design mockups + final review)
+
+---
+
+### Quality Guarantees (Every Feature)
+
+✅ **Security:** All queries filter by `user_id`
+✅ **Error handling:** All 4 states (loading/error/empty/success)
+✅ **Type safety:** TypeScript strict mode
+✅ **Testing:** Unit (Vitest) + E2E (Playwright)
+✅ **Mobile:** Responsive design
+✅ **Dependencies:** All stores updated (from DEPENDENCY-MAP.md)
+✅ **Standards:** CodeBakers method enforced
+✅ **Atomic:** Complete vertical slices (no half-built features)
+
+---
+
+## 🚀 Use Cases
+
+### 1. MVP in 30 Minutes
+- Drop mockups
+- Run autonomous build
+- Deploy to Vercel
+- **Result:** Production MVP
+
+### 2. Prototypes at Scale
+- Test 5 different product ideas
+- Each takes 30 min autonomous build
+- **Result:** 5 working prototypes in 3 hours
+
+### 3. Internal Tools (No Manual Coding)
+- Company needs CRM, dashboard, admin panel
+- Generate mockups (Figma/v0)
+- Run autonomous builds
+- **Result:** 3 internal tools, zero manual coding
+
+### 4. Teaching Tool
+- Show students complete build process
+- Execute atomic unit step-by-step
+- **Result:** Learn by watching autonomous builds
+
+### 5. Client Demos
+- Client describes what they want
+- Generate mockups together
+- Run autonomous build in meeting
+- **Result:** Working demo before they leave
+
+---
+
+## 📝 File Structure
+
+```
+codebakers-mcp-server/
+├── package.json
+├── tsconfig.json
+├── README.md (this file)
+├── src/
+│   ├── index.ts (MCP server entry point)
+│   ├── tools/
+│   │   ├── get-context.ts ✅ COMPLETE
+│   │   ├── init-session.ts ✅ COMPLETE
+│   │   ├── generate-spec.ts 🚧 STUB
+│   │   ├── analyze-mockups.ts 🚧 STUB
+│   │   ├── generate-schema.ts 🚧 STUB
+│   │   ├── map-dependencies.ts 🚧 STUB (CRITICAL)
+│   │   ├── generate-store-contracts.ts 🚧 STUB
+│   │   ├── check-gate.ts 🚧 STUB
+│   │   ├── enforce-feature.ts 🚧 STUB
+│   │   ├── fix-commit.ts 🚧 STUB
+│   │   └── check-scope.ts 🚧 STUB
+│   ├── lib/ (helper functions - to be created)
+│   └── phases/ (phase implementations - to be created)
+└── dist/ (compiled output)
+```
+
+---
+
+## 🔗 Integration with CLAUDE.md
+
+**CLAUDE.md will be TINY** in v5.0.0:
+
+```markdown
+# CodeBakers V5
+
+You are a senior engineer using CodeBakers Method via MCP.
+
+## Session Start
+
+Every session:
+1. Auto-run: codebakers_get_context (detects state)
+2. Auto-run: codebakers_init_session (loads BUILD-STATE.md)
+3. Follow suggestions from context
+
+## User Requests
+
+When user types //:
+→ Call: codebakers_enforce_feature(feature_name)
+
+When user requests feature not in spec:
+→ Call: codebakers_check_scope(feature_description)
+
+## Hard Rules
+
+- Stack: Supabase + Next.js only
+- Queries: .maybeSingle() not .single()
+- Mutations: Filter by id AND user_id
+- Versions: --save-exact
+
+MCP tools handle everything else.
+```
+
+**That's it. ~30 lines instead of 1200.**
+
+---
+
+## 🚀 Getting Started
+
+### Quick Start
+
+1. **Install:**
+   ```bash
+   npx @codebakers/mcp-server install
+   ```
+
+2. **Restart Claude Desktop**
+
+3. **Create new project:**
+   ```bash
+   mkdir my-app
+   cd my-app
+   ```
+
+4. **In Claude Desktop:**
+   ```
+   Run codebakers_run_interview with description: "email client for teams"
+   ```
+
+5. **Drop mockups in refs/design/**
+
+6. **Run autonomous build:**
+   ```
+   Run codebakers_autonomous_build with mode: "full"
+   ```
+
+7. **30 minutes later: Production-ready app** ✅
+
+---
+
+### Full Documentation
+
+- **Installation Guide:** [INSTALL.md](./INSTALL.md)
+- **Complete Feature List:** [V5.1.0-AUTONOMOUS-BUILD-COMPLETE.md](../V5.1.0-AUTONOMOUS-BUILD-COMPLETE.md)
+- **Main Framework:** [CLAUDE.md](../CLAUDE.md)
+
+---
+
+## 📚 Architecture Decisions
+
+### Why MCP?
+
+**Problem:** Instruction-based enforcement is fragile (Claude can ignore it)
+
+**Solution:** MCP tools execute BEFORE Claude decides what to do
+- Context is loaded automatically
+- Dependencies are mapped before building
+- Scope is checked before expanding
+- Technical enforcement, not instructions
+
+### Why Self-Aware Context?
+
+**Problem:** User doesn't know what phase they're in or what to do next
+
+**Solution:** `codebakers_get_context` auto-detects and suggests
+- No manual commands needed
+- CodeBakers guides the user
+- Proactive, not reactive
+
+### Why Comprehensive Dependency Mapping?
+
+**Problem:** Stale UI bugs from missed store updates
+
+**Solution:** Map ALL dependencies in Phase 2 BEFORE building
+- Every mutation knows what to update
+- Every component knows what stores it needs
+- Zero surprises during build
+
+---
+
+## 🤝 Contributing
+
+To implement a stub tool:
+
+1. Open the tool file (e.g., `src/tools/map-dependencies.ts`)
+2. Replace stub implementation with real logic
+3. Add helper functions to `src/lib/` if needed
+4. Update tests (when test suite is added)
+5. Rebuild: `npm run build`
+
+Example structure:
+
+```typescript
+// src/tools/map-dependencies.ts
+import { readMockAnalysis } from '../lib/readers.js';
+import { analyzeDependencies } from '../lib/analyzers.js';
+
+export async function mapDependencies(args: any): Promise<string> {
+  // 1. Read MOCK-ANALYSIS.md
+  const mockAnalysis = await readMockAnalysis();
+
+  // 2. Analyze dependencies
+  const deps = await analyzeDependencies(mockAnalysis);
+
+  // 3. Generate DEPENDENCY-MAP.md
+  await saveDependencyMap(deps);
+
+  return `✓ Dependency map generated
+  - ${deps.readPaths.length} read paths
+  - ${deps.writePaths.length} write paths
+  - ${deps.cascades.length} cascades`;
+}
+```
+
+---
+
+## 📄 License
+
+MIT © 2026 BotMakers Inc.
+
+---
+
+**Built as part of CodeBakers Method v5.0.0**
+
+For questions or issues: https://github.com/botmakers-ai/codebakers-v2