claude-mpm 3.7.1__tar.gz → 3.7.4__tar.gz

{claude_mpm-3.7.1 → claude_mpm-3.7.4}/.ai-trackdown/config.yaml

@@ -11,7 +11,7 @@ tasks:
   directory: tickets
   auto_id: true
   id_format: TSK-{counter:04d}
-  counter: 8
+  counter: 12
 git:
   auto_commit: false
   commit_prefix: '[ai-trackdown]'
@@ -25,4 +25,4 @@ epics:
   directory: tickets/epics
   auto_id: true
   id_format: EP-{counter:04d}
-  counter: 5
+  counter: 7

{claude_mpm-3.7.1 → claude_mpm-3.7.4}/.claude/.claude.json.backup

@@ -20,13 +20,13 @@
       "hasClaudeMdExternalIncludesWarningShown": false,
       "lastTotalWebSearchRequests": 0,
       "exampleFiles": [
-        "dashboard.js",
         "hook_handler.py",
-        "cli.py",
         "parser.py",
-        "socketio_server.py"
+        "dashboard.js",
+        "socketio_server.py",
+        "claude_runner.py"
       ],
-      "exampleFilesGeneratedAt": 1754364832434
+      "exampleFilesGeneratedAt": 1755029183702
     }
   },
   "userID": "383a95b8b162203b90ea3857e612516301e775203cbfc294a8d762290e958697",

{claude_mpm-3.7.1 → claude_mpm-3.7.4}/.claude/agents/data_engineer.md

@@ -1,7 +1,12 @@
 ---
-name: data_engineer
-version: 1.0.0
+name: data_engineer_agent
+description: Data engineering with quality validation, ETL patterns, and profiling
+version: 2.0.1
+base_version: 0.1.0
 author: claude-mpm
+tools: Read,Write,Edit,Bash,Grep,Glob,LS,WebSearch,TodoWrite
+model: opus
+color: yellow
 ---
 
 # Data Engineer Agent
@@ -271,4 +276,4 @@ Document performance problems and optimization attempts:
 - Note data quality issues that may affect QA testing and validation processes
 - Update todos immediately when data engineering changes impact other system components
 - Use clear, specific descriptions that help other agents understand data architecture and constraints
-- Coordinate with security agents for data protection and compliance requirements
+- Coordinate with security agents for data protection and compliance requirements

{claude_mpm-3.7.1 → claude_mpm-3.7.4}/.claude/agents/documentation.md

@@ -1,7 +1,12 @@
 ---
-name: documentation
-version: 1.0.0
+name: documentation_agent
+description: Documentation generation with API docs, diagrams, and docstring validation
+version: 2.0.0
+base_version: 0.1.0
 author: claude-mpm
+tools: Read,Write,Edit,MultiEdit,Grep,Glob,LS,WebSearch,TodoWrite
+model: sonnet
+color: cyan
 ---
 
 # Documentation Agent
@@ -206,4 +211,4 @@ Specify the type of documentation being created:
 - Include version and feature information when coordinating with version control
 - Note dependencies on QA testing completion for accuracy verification
 - Update todos immediately when documentation is ready for review by other agents
-- Use clear, specific descriptions that help other agents understand documentation scope and purpose
+- Use clear, specific descriptions that help other agents understand documentation scope and purpose

{claude_mpm-3.7.1 → claude_mpm-3.7.4}/.claude/agents/engineer.md

@@ -1,12 +1,17 @@
 ---
-name: engineer
-version: 1.0.0
+name: engineer_agent
+description: Advanced code implementation with AST-based refactoring and security scanning
+version: 2.0.1
+base_version: 0.1.0
 author: claude-mpm
+tools: Read,Write,Edit,MultiEdit,Bash,Grep,Glob,LS,WebSearch,TodoWrite
+model: opus
+color: blue
 ---
 
 # Engineer Agent - RESEARCH-GUIDED IMPLEMENTATION
 
-Implement code solutions based on tree-sitter research analysis and codebase pattern discovery. Focus on production-quality implementation that adheres to discovered patterns and constraints.
+Implement code solutions based on AST research analysis and codebase pattern discovery. Focus on production-quality implementation that adheres to discovered patterns and constraints.
 
 ## Memory Integration and Learning
 
@@ -102,7 +107,7 @@ Following strategy memory: "Implement exponential backoff for retry logic"
 ## Implementation Protocol
 
 ### Phase 1: Research Validation (2-3 min)
-- **Verify Research Context**: Confirm tree-sitter analysis findings are current and accurate
+- **Verify Research Context**: Confirm AST analysis findings are current and accurate
 - **Pattern Confirmation**: Validate discovered patterns against current codebase state
 - **Constraint Assessment**: Understand integration requirements and architectural limitations
 - **Security Review**: Note research-identified security concerns and mitigation strategies
@@ -332,4 +337,4 @@ Always include the blocking reason and next steps:
 ### Coordination with Other Agents
 - Reference handoff requirements in todos when work depends on other agents
 - Update todos immediately when passing work to QA, Security, or Documentation agents
-- Use clear, descriptive task names that other agents can understand
+- Use clear, descriptive task names that other agents can understand

{claude_mpm-3.7.1 → claude_mpm-3.7.4}/.claude/agents/ops.md

@@ -1,7 +1,12 @@
 ---
-name: ops
-version: 1.0.0
+name: ops_agent
+description: Infrastructure automation with IaC validation and container security
+version: 2.0.0
+base_version: 0.1.0
 author: claude-mpm
+tools: Read,Write,Edit,Bash,Grep,Glob,LS,TodoWrite
+model: opus
+color: orange
 ---
 
 # Ops Agent
@@ -243,4 +248,4 @@ Document incident management and resolution:
 - Note security compliance requirements when coordinating with security agents
 - Update todos immediately when infrastructure changes affect other system components
 - Use clear, specific descriptions that help other agents understand operational constraints and timelines
-- Coordinate with QA agents for deployment testing and validation requirements
+- Coordinate with QA agents for deployment testing and validation requirements

{claude_mpm-3.7.1 → claude_mpm-3.7.4}/.claude/agents/qa.md

@@ -1,7 +1,12 @@
 ---
-name: qa
-version: 1.0.0
+name: qa_agent
+description: Advanced testing with mutation testing, property-based testing, and coverage analysis
+version: 3.0.0
+base_version: 0.1.0
 author: claude-mpm
+tools: Read,Write,Edit,Bash,Grep,Glob,LS,TodoWrite
+model: sonnet
+color: green
 ---
 
 # QA Agent
@@ -188,4 +193,4 @@ All QA sign-offs must follow this format:
 - Reference specific test failures when creating todos for Engineer agents
 - Update todos immediately when providing QA sign-off to other agents
 - Include test evidence and metrics in handoff communications
-- Use clear, specific descriptions that help other agents understand quality status
+- Use clear, specific descriptions that help other agents understand quality status

{claude_mpm-3.7.1 → claude_mpm-3.7.4}/.claude/agents/research.md

@@ -1,7 +1,12 @@
 ---
-name: research
-version: 1.0.0
+name: research_agent
+description: Advanced codebase analysis with tree-sitter multi-language AST support (41+ languages), Python AST tools, semantic search, complexity metrics, and architecture visualization
+version: 3.0.1
+base_version: 0.1.0
 author: claude-mpm
+tools: Read,Grep,Glob,LS,WebSearch,WebFetch,Bash,TodoWrite
+model: sonnet
+color: purple
 ---
 
 # Research Agent - PRESCRIPTIVE ANALYSIS WITH CONFIDENCE VALIDATION
@@ -19,7 +24,7 @@ Include the following in your response:
   - Format: ["Learning 1", "Learning 2"] or null
 
 Example:
-**Remember**: ["Always validate confidence before agent delegation", "Document tree-sitter patterns for reuse"] or null
+**Remember**: ["Always validate confidence before agent delegation", "Document AST analysis patterns for reuse"] or null
 
 ## Memory Integration and Learning
 
@@ -44,7 +49,7 @@ Content: [Your learning in 5-100 characters]
 ### Research Memory Categories
 
 **Pattern Memories** (Type: pattern):
-- Code patterns discovered through tree-sitter analysis
+- Code patterns discovered through AST analysis
 - Recurring architectural patterns across similar projects
 - Common implementation patterns for specific technologies
 - Design patterns that solve recurring problems effectively
@@ -100,7 +105,7 @@ Applying strategy memory: "Start with entry points and trace data flow"
 Avoiding mistake memory: "Don't assume patterns without AST validation"
 ```
 
-**During tree-sitter analysis:**
+**During AST analysis:**
 ```
 Applying architecture memory: "Check for microservice boundaries in monoliths"
 Following guideline memory: "Document confidence levels for each finding"
@@ -170,10 +175,31 @@ tree -I 'node_modules|.git|dist|build|vendor|gems' -L 3
 # Required: Framework identification, file organization, entry points
 ```
 
-### Phase 2: Tree-sitter Structural Extraction (10-15 min)
+### Phase 2: AST Structural Extraction (10-15 min)
 ```bash
-# Parse key files for structural data
-tree-sitter parse [file] --quiet | grep -E "(function_declaration|class_declaration|interface_declaration|import_statement)"
+# For multi-language AST analysis using tree-sitter (pure Python)
+python -c "
+import tree_sitter_language_pack as tslp
+from tree_sitter import Language, Parser
+import sys
+
+# Auto-detect language from file extension
+file = '[file]'
+ext = file.split('.')[-1]
+lang_map = {'py': 'python', 'js': 'javascript', 'ts': 'typescript', 'go': 'go', 'java': 'java', 'rb': 'ruby'}
+lang = tslp.get_language(lang_map.get(ext, 'python'))
+parser = Parser(lang)
+
+with open(file, 'rb') as f:
+    tree = parser.parse(f.read())
+    print(tree.root_node.sexp())
+"
+
+# For Python-specific deep analysis - use native ast module
+python -c "import ast; import sys; tree = ast.parse(open('[file]').read()); print(ast.dump(tree))" | grep -E "FunctionDef|ClassDef|Import"
+
+# For complexity analysis
+radon cc [file] -s
 
 # CONFIDENCE CHECK 2: Do I understand the code patterns and architecture?
 # Required: Component relationships, data flow, integration points
@@ -222,7 +248,7 @@ grep -r "try.*catch\|throw\|Error\|rescue\|panic\|recover" --include="*.ts" --in
 ## Enhanced Output Format
 
 ```markdown
-# Tree-sitter Code Analysis Report
+# Code Analysis Report
 
 ## CONFIDENCE ASSESSMENT
 - **Overall Confidence**: [X]% 
@@ -306,4 +332,4 @@ grep -r "try.*catch\|throw\|Error\|rescue\|panic\|recover" --include="*.ts" --in
 - Unclear success criteria or acceptance criteria
 - Unknown integration constraints or dependencies
 - Security implications not fully understood
-- Performance requirements unclear or unmeasurable
+- Performance requirements unclear or unmeasurable

{claude_mpm-3.7.1 → claude_mpm-3.7.4}/.claude/agents/security.md

@@ -1,7 +1,12 @@
 ---
-name: security
-version: 1.0.0
+name: security_agent
+description: Advanced security scanning with SAST, dependency auditing, and secret detection
+version: 2.0.1
+base_version: 0.1.0
 author: claude-mpm
+tools: Read,Grep,Glob,LS,WebSearch,TodoWrite
+model: sonnet
+color: red
 ---
 
 # Security Agent - AUTO-ROUTED
@@ -212,4 +217,4 @@ Security analysis todos should specify expected outputs:
 - Provide detailed security requirements and constraints for implementation
 - Include risk assessment and remediation timeline in handoff communications
 - Reference specific security standards and compliance requirements
-- Update todos immediately when security sign-off is provided to other agents
+- Update todos immediately when security sign-off is provided to other agents

{claude_mpm-3.7.1 → claude_mpm-3.7.4}/.claude/agents/version_control.md

@@ -1,7 +1,12 @@
 ---
-name: version_control
-version: 1.0.0
+name: version_control_agent
+description: Git operations with commit validation and branch strategy enforcement
+version: 2.0.0
+base_version: 0.1.0
 author: claude-mpm
+tools: Read,Bash,Grep,Glob,LS,TodoWrite
+model: sonnet
+color: pink
 ---
 
 # Version Control Agent
@@ -199,4 +204,4 @@ Include specific git commands and rationale:
 - Include deployment timeline requirements when coordinating with ops agents
 - Note documentation update needs when coordinating release communications
 - Update todos immediately when version control operations affect other agents
-- Use clear branch names and commit messages that help other agents understand changes
+- Use clear branch names and commit messages that help other agents understand changes

{claude_mpm-3.7.1 → claude_mpm-3.7.4}/CHANGELOG.md

@@ -5,35 +5,21 @@ All notable changes to claude-mpm will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## [3.7.1] - 2025-08-12
+## [3.7.4] - 2025-08-13
 
-### Documentation Update
+## [3.7.3] - 2025-08-13
 
-This patch release updates the documentation to properly acknowledge contributors and highlight the new Code Analyzer agent.
+## [3.7.2] - 2025-08-13
 
-#### Changes
-- Updated acknowledgments for WhatsApp support group members
-- Added comprehensive documentation for the Code Analyzer agent in release notes
-- Improved roadmap section to encourage community feedback
-- Enhanced CHANGELOG with Code Analyzer details and contributor acknowledgments
 
-#### Previous Commits
-- update package.json version to 3.7.0 ([a518e05])
-## [3.7.0] - 2025-08-12
-
-
-### Documentation
-
-- update CHANGELOG with 3.6.0 release notes ([e17f8fc])
-
-### Chores
+### Bug Fixes
 
-- prepare for 3.6.0 release - add new features and test files ([b8a2fde])
-## [3.6.0] - 2025-08-12
+- update internal VERSION file to 3.7.1 ([8e2a865])
+## [3.7.1] - 2025-08-13
 
 ### Executive Summary
 
-Claude MPM 3.6.0 introduces **three major architectural improvements** that significantly enhance performance, maintainability, and developer experience:
+Claude MPM 3.7.1 introduces **three major architectural improvements** that significantly enhance performance, maintainability, and developer experience:
 
 1. **Dynamic Agent Dependencies** - Smart dependency loading that only checks and installs packages for deployed agents, reducing installation size by up to 90%
 2. **Enhanced PM Instructions** - Separation of framework requirements from customizable PM instructions with structured response formats
@@ -84,12 +70,21 @@ Claude MPM 3.6.0 introduces **three major architectural improvements** that sign
 ### Bug Fixes
 - Fixed duplication issues in agent deployment process
 - Resolved path resolution problems in `.claude/agents/` directory
+- Prevented PM agent from being deployed as subagent
 - Fixed configuration file validation edge cases
 - Enhanced agent memory routing with clearer error messages
 - Resolved hook integration issues causing missed responses
+- Resolved version numbering discrepancy (corrected from 3.7.1 to 3.6.2)
+
+### Documentation Updates
+- Enhanced PM architecture documentation
+- Updated response logging configuration
+- Improved technical references for agent responses
+- Clarified TodoWrite format requirements across all agents
+- Updated acknowledgments and roadmap sections
 
 ### Migration Guide
-- Version 3.6.0 is fully backward compatible
+- Version 3.6.2 is fully backward compatible
 - After upgrade, run `claude-mpm agents deps-check` to verify dependencies
 - Run `claude-mpm agents deps-install` to install only required dependencies
 - Optionally update configuration for enhanced logging (debug mode now default)
@@ -108,7 +103,7 @@ Special thanks to our WhatsApp support group members for their invaluable contri
 - **Eddie Hudson**
 - **Oliver Anson**
 
-Their dedication to quality assurance and constructive feedback were instrumental in shaping version 3.6.0.
+Their dedication to quality assurance and constructive feedback were instrumental in shaping version 3.6.2.
 
 ## [3.5.6] - 2025-08-11
 

{claude_mpm-3.7.1/src/claude_mpm.egg-info → claude_mpm-3.7.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: claude-mpm
-Version: 3.7.1
+Version: 3.7.4
 Summary: Claude Multi-agent Project Manager - Clean orchestration with ticket management
 Home-page: https://github.com/bobmatnyc/claude-mpm
 Author: Claude MPM Team

claude_mpm-3.7.4/VERSION

@@ -0,0 +1 @@
+3.7.4

claude_mpm-3.7.4/src/claude_mpm/VERSION

@@ -0,0 +1 @@
+3.7.4

{claude_mpm-3.7.1 → claude_mpm-3.7.4}/src/claude_mpm/agents/frontmatter_validator.py

@@ -34,6 +34,7 @@ class ValidationResult:
     warnings: List[str]
     corrections: List[str]
     corrected_frontmatter: Optional[Dict[str, Any]] = None
+    field_corrections: Optional[Dict[str, Any]] = None  # Specific field-level corrections
 
 
 class FrontmatterValidator:
@@ -109,6 +110,7 @@ class FrontmatterValidator:
     def __init__(self):
         """Initialize the validator with schema if available."""
         self.schema = self._load_schema()
+        self.all_valid_fields = self._extract_valid_fields()
         
     def _load_schema(self) -> Optional[Dict[str, Any]]:
         """Load the frontmatter schema from JSON file."""
@@ -121,6 +123,17 @@ class FrontmatterValidator:
                 logger.warning(f"Failed to load frontmatter schema: {e}")
         return None
     
+    def _extract_valid_fields(self) -> set:
+        """Extract all valid field names from the schema."""
+        if self.schema and 'properties' in self.schema:
+            return set(self.schema['properties'].keys())
+        # Fallback to known fields if schema not available
+        return {
+            "name", "description", "version", "base_version", "author", 
+            "tools", "model", "tags", "category", "max_tokens", "temperature", 
+            "resource_tier", "dependencies", "capabilities", "color"
+        }
+    
     def validate_and_correct(self, frontmatter: Dict[str, Any]) -> ValidationResult:
         """
         Validate and automatically correct frontmatter.
@@ -135,9 +148,10 @@ class FrontmatterValidator:
         warnings = []
         corrections = []
         corrected = frontmatter.copy()
+        field_corrections = {}  # Track only the fields that actually need correction
         
-        # Required fields check
-        required_fields = ["name", "description", "version", "model"]
+        # Required fields check (from schema)
+        required_fields = self.schema.get('required', ["name", "description", "version", "model"]) if self.schema else ["name", "description", "version", "model"]
         for field in required_fields:
             if field not in corrected:
                 errors.append(f"Missing required field: {field}")
@@ -153,6 +167,7 @@ class FrontmatterValidator:
                 fixed_name = re.sub(r"[^a-z0-9_]", "", fixed_name)
                 if fixed_name and fixed_name[0].isalpha():
                     corrected["name"] = fixed_name
+                    field_corrections["name"] = fixed_name
                     corrections.append(f"Corrected name from '{name}' to '{fixed_name}'")
                 else:
                     errors.append(f"Invalid name format: {name}")
@@ -165,6 +180,7 @@ class FrontmatterValidator:
             if isinstance(model, (int, float)):
                 model = str(model)
                 corrected["model"] = model
+                field_corrections["model"] = model
                 corrections.append(f"Converted model from number to string: {model}")
             
             if not isinstance(model, str):
@@ -173,6 +189,7 @@ class FrontmatterValidator:
                 normalized_model = self._normalize_model(model)
                 if normalized_model != model:
                     corrected["model"] = normalized_model
+                    field_corrections["model"] = normalized_model
                     corrections.append(f"Normalized model from '{model}' to '{normalized_model}'")
                 
                 if normalized_model not in self.VALID_MODELS:
@@ -184,6 +201,7 @@ class FrontmatterValidator:
             corrected_tools, tool_corrections = self._correct_tools(tools)
             if tool_corrections:
                 corrected["tools"] = corrected_tools
+                field_corrections["tools"] = corrected_tools
                 corrections.extend(tool_corrections)
             
             # Validate tool names
@@ -195,6 +213,8 @@ class FrontmatterValidator:
                     if corrected_tool:
                         idx = corrected_tools.index(tool)
                         corrected_tools[idx] = corrected_tool
+                        corrected["tools"] = corrected_tools
+                        field_corrections["tools"] = corrected_tools
                         corrections.append(f"Corrected tool '{tool}' to '{corrected_tool}'")
                     else:
                         invalid_tools.append(tool)
@@ -214,10 +234,12 @@ class FrontmatterValidator:
                     if re.match(r"^\d+\.\d+$", version):
                         fixed_version = f"{version}.0"
                         corrected[field] = fixed_version
+                        field_corrections[field] = fixed_version
                         corrections.append(f"Fixed {field} from '{version}' to '{fixed_version}'")
                     elif re.match(r"^v?\d+\.\d+\.\d+$", version):
                         fixed_version = version.lstrip("v")
                         corrected[field] = fixed_version
+                        field_corrections[field] = fixed_version
                         corrections.append(f"Fixed {field} from '{version}' to '{fixed_version}'")
                     else:
                         errors.append(f"Invalid {field} format: {version}")
@@ -243,6 +265,44 @@ class FrontmatterValidator:
             if corrected["resource_tier"] not in valid_tiers:
                 warnings.append(f"Invalid resource_tier: {corrected['resource_tier']}")
         
+        # Validate color field
+        if "color" in corrected:
+            color = corrected["color"]
+            if not isinstance(color, str):
+                errors.append(f"Field 'color' must be a string, got {type(color).__name__}")
+            # Color validation could be expanded to check for valid color names/hex codes
+        
+        # Validate author field
+        if "author" in corrected:
+            author = corrected["author"]
+            if not isinstance(author, str):
+                errors.append(f"Field 'author' must be a string, got {type(author).__name__}")
+            elif len(author) > 100:
+                warnings.append(f"Author field too long ({len(author)} chars, maximum 100)")
+        
+        # Validate tags field
+        if "tags" in corrected:
+            tags = corrected["tags"]
+            if not isinstance(tags, list):
+                errors.append(f"Field 'tags' must be a list, got {type(tags).__name__}")
+            else:
+                for tag in tags:
+                    if not isinstance(tag, str):
+                        errors.append(f"All tags must be strings, found {type(tag).__name__}")
+                    elif not re.match(r"^[a-z][a-z0-9-]*$", tag):
+                        warnings.append(f"Tag '{tag}' doesn't match recommended pattern (lowercase, alphanumeric with hyphens)")
+        
+        # Validate numeric fields
+        for field_name, (min_val, max_val) in [("max_tokens", (1000, 200000)), ("temperature", (0, 1))]:
+            if field_name in corrected:
+                value = corrected[field_name]
+                if field_name == "temperature" and not isinstance(value, (int, float)):
+                    errors.append(f"Field '{field_name}' must be a number, got {type(value).__name__}")
+                elif field_name == "max_tokens" and not isinstance(value, int):
+                    errors.append(f"Field '{field_name}' must be an integer, got {type(value).__name__}")
+                elif isinstance(value, (int, float)) and not (min_val <= value <= max_val):
+                    warnings.append(f"Field '{field_name}' value {value} outside recommended range [{min_val}, {max_val}]")
+        
         # Determine if valid
         is_valid = len(errors) == 0
         
@@ -251,7 +311,8 @@ class FrontmatterValidator:
             errors=errors,
             warnings=warnings,
             corrections=corrections,
-            corrected_frontmatter=corrected if corrections else None
+            corrected_frontmatter=corrected if corrections else None,
+            field_corrections=field_corrections if field_corrections else None
         )
     
     def _normalize_model(self, model: str) -> str:
@@ -416,7 +477,7 @@ class FrontmatterValidator:
         """
         result = self.validate_file(file_path)
         
-        if result.corrected_frontmatter and not dry_run:
+        if result.field_corrections and not dry_run:
             try:
                 with open(file_path, 'r') as f:
                     content = f.read()
@@ -428,21 +489,59 @@ class FrontmatterValidator:
                         end_marker = content.find("\n---\r\n", 4)
                     
                     if end_marker != -1:
-                        # Reconstruct file with corrected frontmatter
-                        new_frontmatter = yaml.dump(
-                            result.corrected_frontmatter,
-                            default_flow_style=False,
-                            sort_keys=False
+                        # Apply field-level corrections to preserve structure
+                        frontmatter_content = content[4:end_marker]
+                        corrected_content = self._apply_field_corrections(
+                            frontmatter_content, result.field_corrections
                         )
-                        new_content = f"---\n{new_frontmatter}---\n{content[end_marker + 5:]}"
-                        
-                        with open(file_path, 'w') as f:
-                            f.write(new_content)
                         
-                        logger.info(f"Corrected frontmatter in {file_path}")
-                        for correction in result.corrections:
-                            logger.info(f"  - {correction}")
+                        if corrected_content != frontmatter_content:
+                            new_content = f"---\n{corrected_content}\n---\n{content[end_marker + 5:]}"
+                            
+                            with open(file_path, 'w') as f:
+                                f.write(new_content)
+                            
+                            logger.info(f"Corrected frontmatter in {file_path}")
+                            for correction in result.corrections:
+                                logger.info(f"  - {correction}")
             except Exception as e:
                 logger.error(f"Failed to write corrections to {file_path}: {e}")
         
-        return result
+        return result
+    
+    def _apply_field_corrections(self, frontmatter_content: str, field_corrections: Dict[str, Any]) -> str:
+        """
+        Apply field-level corrections while preserving structure and other fields.
+        
+        Args:
+            frontmatter_content: Original YAML frontmatter content
+            field_corrections: Dict of field corrections to apply
+            
+        Returns:
+            Corrected frontmatter content
+        """
+        lines = frontmatter_content.strip().split('\n')
+        corrected_lines = []
+        
+        for line in lines:
+            # Check if this line contains a field we need to correct
+            if ':' in line:
+                field_name = line.split(':')[0].strip()
+                if field_name in field_corrections:
+                    # Replace the field value while preserving structure
+                    corrected_value = field_corrections[field_name]
+                    if isinstance(corrected_value, list):
+                        # Handle list fields like tools
+                        if field_name == "tools" and isinstance(corrected_value, list):
+                            # Format as comma-separated string to preserve existing format
+                            corrected_lines.append(f"{field_name}: {','.join(corrected_value)}")
+                        else:
+                            corrected_lines.append(f"{field_name}: {corrected_value}")
+                    else:
+                        corrected_lines.append(f"{field_name}: {corrected_value}")
+                    continue
+            
+            # Keep the original line if no correction needed
+            corrected_lines.append(line)
+        
+        return '\n'.join(corrected_lines)

claude_mpm-3.7.4/src/claude_mpm/agents/templates/.claude-mpm/memories/engineer_agent.md

@@ -0,0 +1,39 @@
+# Engineer Agent Memory - templates
+
+<!-- MEMORY LIMITS: 8KB max | 10 sections max | 15 items per section -->
+<!-- Last Updated: 2025-08-13 14:34:34 | Auto-updated by: engineer -->
+
+## Project Context
+templates: mixed standard application
+
+## Project Architecture
+- Standard Application with mixed implementation
+
+## Coding Patterns Learned
+<!-- Items will be added as knowledge accumulates -->
+
+## Implementation Guidelines
+<!-- Items will be added as knowledge accumulates -->
+
+## Domain-Specific Knowledge
+<!-- Agent-specific knowledge for templates domain -->
+- Key project terms: templates
+- Focus on implementation patterns, coding standards, and best practices
+
+## Effective Strategies
+<!-- Successful approaches discovered through experience -->
+
+## Common Mistakes to Avoid
+<!-- Items will be added as knowledge accumulates -->
+
+## Integration Points
+<!-- Items will be added as knowledge accumulates -->
+
+## Performance Considerations
+<!-- Items will be added as knowledge accumulates -->
+
+## Current Technical Context
+<!-- Items will be added as knowledge accumulates -->
+
+## Recent Learnings
+<!-- Most recent discoveries and insights -->