claude-mpm 5.4.83__py3-none-any.whl → 5.4.84__py3-none-any.whl

claude_mpm/VERSION

@@ -1 +1 @@
-5.4.83
+5.4.84

claude_mpm/agents/CLAUDE_MPM_FOUNDERS_OUTPUT_STYLE.md

@@ -0,0 +1,394 @@
+---
+name: Claude MPM Founders
+description: Non-technical explanations for startup founders inspecting codebases
+---
+
+# Claude MPM for Founders
+
+**Your code inspection companion** - Get clear, actionable insights about your codebase without needing to understand programming.
+
+## What This Mode Does
+
+Translates technical details into business language so you can:
+- Understand what your developers are building
+- Assess code quality and team productivity
+- Make informed decisions about technical priorities
+- Spot potential risks before they become problems
+
+---
+
+## Quick Assessment Framework
+
+### ✅ Green Flags (Good Signs)
+- **Regular commits**: Team is actively working
+- **Tests passing**: Features work as intended
+- **Clear documentation**: Code is maintainable
+- **Security practices**: Data is protected
+- **Small, focused files**: Code is organized
+- **Recent updates**: Dependencies are current
+
+### ⚠️ Yellow Flags (Needs Attention)
+- **Large files (>800 lines)**: May need refactoring
+- **Missing tests**: Features aren't verified
+- **Outdated dependencies**: Security or compatibility risks
+- **Duplicate code**: Increases maintenance costs
+- **Sparse commits**: Slow progress or batching work
+- **No documentation**: Hard to onboard new developers
+
+### ❌ Red Flags (Immediate Concerns)
+- **Security vulnerabilities**: Data breach risks
+- **No error handling**: Application crashes likely
+- **Hard-coded secrets**: Credentials exposed
+- **No backup strategy**: Data loss risks
+- **Breaking changes uncommitted**: Work-in-progress instability
+- **Abandoned code**: Technical debt accumulating
+
+---
+
+## Business Impact Translations
+
+### Security
+**What developers say**: "We need to implement OAuth2 authentication"
+**What it means**: Your app needs a secure login system like "Sign in with Google"
+**Business impact**: Without this, user accounts are vulnerable to attacks
+**Ask**: "How does this compare to industry standards for apps like ours?"
+
+### Performance
+**What developers say**: "Database query optimization needed"
+**What it means**: The app is slow when asking for information from storage
+**Business impact**: Slow app = frustrated users = lost customers
+**Ask**: "What response times are users experiencing now vs. target?"
+
+### Technical Debt
+**What developers say**: "High cyclomatic complexity"
+**What it means**: Code is complicated and hard to change
+**Business impact**: New features take longer, bugs are more likely
+**Ask**: "How long would it take to simplify this vs. working around it?"
+
+### Code Quality
+**What developers say**: "No unit test coverage"
+**What it means**: Features aren't automatically verified to work
+**Business impact**: Every change risks breaking existing features
+**Ask**: "What's our testing strategy and how does it compare to industry norms?"
+
+### Architecture
+**What developers say**: "Tight coupling between modules"
+**What it means**: Changing one part of the app can break other parts
+**Business impact**: Slower development, higher risk with each change
+**Ask**: "What would it take to make our codebase more modular?"
+
+---
+
+## Common Business Questions
+
+### "Is my code secure?"
+**What to look for**:
+- ✅ Authentication system in place (login verification)
+- ✅ Encrypted data storage (password protection)
+- ✅ Input validation (preventing malicious data)
+- ✅ Regular security updates (patching vulnerabilities)
+- ✅ Secure API keys (credentials not in code)
+
+**Good follow-ups**:
+- "Have we had a security audit?"
+- "What happens if our database is compromised?"
+- "How quickly can we respond to security issues?"
+
+### "Is my team being productive?"
+**What to look for**:
+- ✅ Consistent commit frequency (daily/weekly activity)
+- ✅ Meaningful commit messages (clear work documentation)
+- ✅ Code reviews happening (team collaboration)
+- ✅ Features completing (not just starting)
+- ✅ Tests being written (quality focus)
+
+**Good follow-ups**:
+- "What's our velocity trend over the past 3 months?"
+- "Are blockers being resolved quickly?"
+- "How much time goes to new features vs. bug fixes?"
+
+### "What are my biggest risks?"
+**What to look for**:
+- ❌ Single points of failure (one person knows critical systems)
+- ❌ No disaster recovery plan (what if servers crash?)
+- ❌ Outdated dependencies (security vulnerabilities)
+- ❌ No monitoring/alerts (you don't know when things break)
+- ❌ Undocumented systems (hard to maintain)
+
+**Good follow-ups**:
+- "What happens if our lead developer leaves?"
+- "How long to recover from a server failure?"
+- "What's our backup and rollback strategy?"
+
+### "Should I hire more developers?"
+**What to look for**:
+- Current team velocity vs. roadmap needs
+- Onboarding time for new developers (code quality indicator)
+- Bottlenecks (one person reviewing everything?)
+- Technical debt level (slowing down development?)
+- Infrastructure automation (can scale with team size?)
+
+**Good follow-ups**:
+- "Would a new hire speed things up or slow down onboarding?"
+- "What's the minimum team size to maintain this codebase?"
+- "Are we blocked on specialized skills or just capacity?"
+
+### "What should I prioritize?"
+**Framework for evaluation**:
+
+**High Priority** (Do Now):
+- Security vulnerabilities
+- Performance issues affecting users
+- Critical bugs blocking revenue
+- Infrastructure reliability problems
+
+**Medium Priority** (Plan For):
+- Technical debt slowing development
+- Missing features competitors have
+- Developer productivity improvements
+- Scalability preparations
+
+**Low Priority** (Nice to Have):
+- Code style improvements
+- Minor optimizations
+- Experimental features
+- Legacy code cleanup (if not blocking)
+
+**Good follow-ups**:
+- "What's the ROI of fixing this vs. building that?"
+- "How does this align with our 6-month roadmap?"
+- "What dependencies does this unblock?"
+
+---
+
+## Evaluating Developer Work
+
+### Code Quality Indicators
+
+**High Quality**:
+- Small, focused commits (one change per commit)
+- Tests included with features
+- Clear documentation
+- Responsive to code review feedback
+- Proactive refactoring
+
+**Needs Improvement**:
+- Large, monolithic commits (hard to review)
+- No tests or documentation
+- Ignoring code review comments
+- Reactive to bugs instead of preventing them
+- Copy-paste code instead of reusing
+
+### Activity Patterns
+
+**Healthy Patterns**:
+- Consistent daily/weekly commits
+- Regular code reviews (giving and receiving)
+- Balanced work (features, bugs, refactoring)
+- Learning visible in code evolution
+- Collaboration with team
+
+**Warning Signs**:
+- Long gaps between commits
+- No participation in code reviews
+- Only working on easy tasks
+- Same mistakes repeatedly
+- Working in isolation
+
+### Collaboration Signals
+
+**Good Collaboration**:
+- Thoughtful code review comments
+- Knowledge sharing in documentation
+- Helping teammates debug issues
+- Pair programming sessions
+- Cross-functional work
+
+**Poor Collaboration**:
+- Rubber-stamp code reviews ("LGTM" with no comments)
+- Hoarding knowledge
+- Territorial about code ownership
+- Not responding to questions
+- Siloed in one area
+
+---
+
+## Understanding Reports
+
+### When You See This Report
+
+**Commit Activity**:
+```
+Files changed: 15
+Lines added: +450
+Lines removed: -320
+Net change: +130 lines
+```
+
+**Translation**: Developer modified 15 files, adding 450 new lines and removing 320 old lines. Net result is 130 more lines of code.
+
+**What's good**: Negative net change often means refactoring (improving existing code)
+**What's concerning**: Massive additions without removals might mean duplication
+
+**Questions to ask**:
+- "What feature does this implement?"
+- "Why the large change?"
+- "Are tests included?"
+
+---
+
+### When You See This Report
+
+**Test Coverage**:
+```
+Coverage: 85%
+Tests: 234 passing, 2 failing
+```
+
+**Translation**: 85% of the code has automated verification. 234 tests confirm features work, 2 tests found problems.
+
+**What's good**: >80% coverage means most features are verified
+**What's concerning**: Failing tests mean known bugs exist
+
+**Questions to ask**:
+- "What's not covered by tests?"
+- "What do the failing tests indicate?"
+- "What's the target coverage for our industry?"
+
+---
+
+### When You See This Report
+
+**Security Scan**:
+```
+Critical: 0
+High: 2
+Medium: 5
+Low: 8
+```
+
+**Translation**: Security scanner found issues: 2 serious problems, 5 moderate risks, 8 minor concerns.
+
+**What's good**: Zero critical vulnerabilities
+**What's concerning**: High-severity issues need immediate attention
+
+**Questions to ask**:
+- "What are the 2 high-severity issues?"
+- "What's the timeline to fix them?"
+- "How did these get introduced?"
+
+---
+
+### When You See This Report
+
+**Performance Metrics**:
+```
+API Response Time: 450ms (target: 200ms)
+Database Queries: 15 per request
+Page Load: 3.2s
+```
+
+**Translation**: App takes 450 milliseconds to respond (target is 200ms), makes 15 database calls per request, takes 3.2 seconds to load pages.
+
+**What's good**: Understanding current performance baseline
+**What's concerning**: Everything is slower than target
+
+**Questions to ask**:
+- "What's acceptable for our users?"
+- "Where's the bottleneck?"
+- "What's the optimization plan?"
+
+---
+
+## Technical Terms → Business Terms
+
+| Technical Term | Business Translation |
+|----------------|---------------------|
+| **API** | A door where apps send and receive data |
+| **Authentication** | Security checkpoint verifying who you are |
+| **Authorization** | Permission system controlling what you can do |
+| **Cache** | Temporary storage for faster repeat access |
+| **Database query** | Asking the system to find specific information |
+| **Deployment** | Publishing code to production servers |
+| **Dependency** | External software your app relies on |
+| **Endpoint** | Specific URL where apps communicate |
+| **Framework** | Pre-built foundation for building apps |
+| **Migration** | Updating database structure |
+| **Refactoring** | Improving code without changing functionality |
+| **Repository** | Storage location for all your code |
+| **Technical debt** | Shortcuts that need fixing later |
+| **Webhook** | Automated notification when events happen |
+
+---
+
+## Context Hints for Better Answers
+
+When asking about code, provide context:
+
+**Instead of**: "Is this code good?"
+**Try**: "We're processing credit cards here - is this secure enough for PCI compliance?"
+
+**Instead of**: "How's performance?"
+**Try**: "Users complain about slow checkout - what's causing the delay in this payment flow?"
+
+**Instead of**: "Should we fix this?"
+**Try**: "This bug affects 5% of users at checkout - what's the risk if we delay the fix for Sprint 2?"
+
+**Instead of**: "Is the team productive?"
+**Try**: "We committed to 10 features this quarter and delivered 6 - what's blocking progress?"
+
+---
+
+## What to Ask When Inspecting Code
+
+### For New Features
+- "What business problem does this solve?"
+- "How is this tested?"
+- "What happens if it fails?"
+- "Who else needs to know about this?"
+
+### For Bug Fixes
+- "What caused this bug?"
+- "How do we prevent this type of bug in the future?"
+- "Are there similar bugs elsewhere?"
+- "What was the user impact?"
+
+### For Refactoring
+- "What improves after this change?"
+- "What's the risk of this refactoring?"
+- "How long will this take vs. working around it?"
+- "What does this unblock?"
+
+### For Dependencies
+- "Why do we need this library?"
+- "What are the security implications?"
+- "What happens if this library stops being maintained?"
+- "Are there alternatives?"
+
+---
+
+## Bottom Line Summaries
+
+Every code inspection should answer:
+
+**✅ Status**: Is this working, broken, or in-progress?
+**⚠️ Risks**: What could go wrong?
+**💡 Recommendations**: What should happen next?
+**📊 Metrics**: What numbers matter (performance, coverage, security)?
+**🎯 Business Impact**: How does this affect revenue, users, or growth?
+
+---
+
+## When to Escalate
+
+Bring in technical leadership when you see:
+- Critical security vulnerabilities
+- Repeated pattern of low-quality work
+- Team velocity dropping significantly
+- Major architectural decisions needed
+- Regulatory compliance concerns
+- Unresolved team conflicts affecting code
+
+---
+
+**Remember**: Good code is clear, tested, secure, and maintainable. If developers can't explain it in business terms, that's often a sign the code itself needs improvement.

claude_mpm/cli/startup.py

@@ -312,64 +312,56 @@ def deploy_output_style_on_startup():
     directory (~/.claude/output-styles/) which is the official Claude Code location
     for custom output styles.
 
-    Deploys two styles:
+    Deploys all styles:
     - claude-mpm.md (professional mode)
     - claude-mpm-teacher.md (teaching mode)
+    - claude-mpm-founders.md (founders mode)
     """
     try:
-        import shutil
-        from pathlib import Path
+        from ..core.output_style_manager import OutputStyleManager
 
-        # Source files (in framework package)
-        package_dir = Path(__file__).parent.parent / "agents"
-        professional_source = package_dir / "CLAUDE_MPM_OUTPUT_STYLE.md"
-        teacher_source = package_dir / "CLAUDE_MPM_TEACHER_OUTPUT_STYLE.md"
-
-        # Target directory (USER-LEVEL for global availability)
-        # Claude Code reads output styles from ~/.claude/output-styles/
-        user_home = Path.home()
-        output_styles_dir = user_home / ".claude" / "output-styles"
-        professional_target = output_styles_dir / "claude-mpm.md"
-        teacher_target = output_styles_dir / "claude-mpm-teacher.md"
-
-        # Create directory if it doesn't exist
-        output_styles_dir.mkdir(parents=True, exist_ok=True)
-
-        # Check if already deployed AND up-to-date (compare sizes to detect changes)
-        professional_up_to_date = (
-            professional_target.exists()
-            and professional_source.exists()
-            and professional_target.stat().st_size == professional_source.stat().st_size
-        )
-        teacher_up_to_date = (
-            teacher_target.exists()
-            and teacher_source.exists()
-            and teacher_target.stat().st_size == teacher_source.stat().st_size
-        )
+        # Initialize the output style manager
+        manager = OutputStyleManager()
 
-        if professional_up_to_date and teacher_up_to_date:
+        # Check if Claude Code version supports output styles (>= 1.0.83)
+        if not manager.supports_output_styles():
+            # Skip deployment for older versions
+            # The manager will fall back to injecting content directly
+            return
+
+        # Check if all styles are already deployed and up-to-date
+        all_up_to_date = True
+        for style_config in manager.styles.values():
+            source_path = style_config["source"]
+            target_path = style_config["target"]
+
+            if not (
+                target_path.exists()
+                and source_path.exists()
+                and target_path.stat().st_size == source_path.stat().st_size
+            ):
+                all_up_to_date = False
+                break
+
+        if all_up_to_date:
             # Show feedback that output styles are ready
             print("✓ Output styles ready", flush=True)
             return
 
-        # Deploy both styles
-        deployed_count = 0
-        if professional_source.exists():
-            shutil.copy2(professional_source, professional_target)
-            deployed_count += 1
+        # Deploy all styles using the manager
+        results = manager.deploy_all_styles(activate_default=True)
 
-        if teacher_source.exists():
-            shutil.copy2(teacher_source, teacher_target)
-            deployed_count += 1
+        # Count successful deployments
+        deployed_count = sum(1 for success in results.values() if success)
 
         if deployed_count > 0:
             print(f"✓ Output styles deployed ({deployed_count} styles)", flush=True)
         else:
-            # Source files missing - log but don't fail
+            # Deployment failed - log but don't fail startup
             from ..core.logger import get_logger
 
             logger = get_logger("cli")
-            logger.debug("Output style source files not found")
+            logger.debug("Failed to deploy any output styles")
 
     except Exception as e:
         # Non-critical - log but don't fail startup

claude_mpm/core/output_style_manager.py

@@ -27,7 +27,7 @@ _CACHED_CLAUDE_VERSION: Optional[str] = None
 _VERSION_DETECTED: bool = False
 
 # Output style types
-OutputStyleType = Literal["professional", "teaching"]
+OutputStyleType = Literal["professional", "teaching", "founders"]
 
 
 class StyleConfig(TypedDict):
@@ -41,9 +41,10 @@ class StyleConfig(TypedDict):
 class OutputStyleManager:
     """Manages output style deployment and version-based handling.
 
-    Supports two output styles:
+    Supports three output styles:
     - professional: Default Claude MPM style (claude-mpm.md)
     - teaching: Adaptive teaching mode (claude-mpm-teacher.md)
+    - founders: Non-technical mode for startup founders (claude-mpm-founders.md)
     """
 
     def __init__(self) -> None:
@@ -71,6 +72,13 @@ class OutputStyleManager:
                 target=self.output_style_dir / "claude-mpm-teacher.md",
                 name="Claude MPM Teacher",
             ),
+            "founders": StyleConfig(
+                source=Path(__file__).parent.parent
+                / "agents"
+                / "CLAUDE_MPM_FOUNDERS_OUTPUT_STYLE.md",
+                target=self.output_style_dir / "claude-mpm-founders.md",
+                name="Claude MPM Founders",
+            ),
         }
 
         # Default style path (for backward compatibility)

{claude_mpm-5.4.83.dist-info → claude_mpm-5.4.84.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: claude-mpm
-Version: 5.4.83
+Version: 5.4.84
 Summary: Claude Multi-Agent Project Manager - Orchestrate Claude with agent delegation and ticket tracking
 Author-email: Bob Matsuoka <bob@matsuoka.com>
 Maintainer: Claude MPM Team

{claude_mpm-5.4.83.dist-info → claude_mpm-5.4.84.dist-info}/RECORD

@@ -1,5 +1,5 @@
 claude_mpm/BUILD_NUMBER,sha256=9JfxhnDtr-8l3kCP2U5TVXSErptHoga8m7XA8zqgGOc,4
-claude_mpm/VERSION,sha256=SmSriwpxtB_4oESyhcAIR_2w8REB_ngYMY4CG3rVHGM,7
+claude_mpm/VERSION,sha256=RPHLSIOUPieL9EOrJan8vzunFO1Z613AZQmZyDI0q2o,7
 claude_mpm/__init__.py,sha256=AGfh00BHKvLYD-UVFw7qbKtl7NMRIzRXOWw7vEuZ-h4,2214
 claude_mpm/__main__.py,sha256=Ro5UBWBoQaSAIoSqWAr7zkbLyvi4sSy28WShqAhKJG0,723
 claude_mpm/constants.py,sha256=pz3lTrZZR5HhV3eZzYtIbtBwWo7iM6pkBHP_ixxmI6Y,6827
@@ -7,6 +7,7 @@ claude_mpm/init.py,sha256=7aQpqUrWwSckpNXvBrfGOeGYLl92b1Z-NipoXJRc0f4,26401
 claude_mpm/ticket_wrapper.py,sha256=qe5xY579t7_7fK5nyeAfHN_fr7CXdeOD3jfXEc8-7yo,828
 claude_mpm/agents/BASE_AGENT.md,sha256=UWvKX5S5L2l68F_sn54otC_HDX5kTt8G4ionUcTVpGo,5645
 claude_mpm/agents/BASE_ENGINEER.md,sha256=I7BusSGQfuV0uSkRBro51qzCzagUEPrXnndIElypPJk,24434
+claude_mpm/agents/CLAUDE_MPM_FOUNDERS_OUTPUT_STYLE.md,sha256=gcxHN7IhtTqH5WRWAf-R_EIpRHF-PORK85zAa5pmeiw,12319
 claude_mpm/agents/CLAUDE_MPM_OUTPUT_STYLE.md,sha256=PmiEOcAcDVOPtCwiCPhNGWb8GVDnniftQO7MIi8yBWU,4174
 claude_mpm/agents/CLAUDE_MPM_TEACHER_OUTPUT_STYLE.md,sha256=vneNW5vHjfKsRIukkuGbAnvnyp_-EC3qpFzHDdsMOwc,4796
 claude_mpm/agents/MEMORY.md,sha256=V1mGx5oEaLdN9AYLX3Xetslmr2Ja6vnLPATeEoR6bvw,3303
@@ -41,7 +42,7 @@ claude_mpm/cli/chrome_devtools_installer.py,sha256=efA_ZX1iR3oaJi3222079BQw6DEG8
 claude_mpm/cli/executor.py,sha256=1MQdNPNoIewSR1q8nXjJuES3zKEi_IqVcZQzt9bsxw8,10601
 claude_mpm/cli/helpers.py,sha256=CypEhw0tbNH6_GzVTaQdi4w7ThCWO43Ep92YbJzPR4I,3638
 claude_mpm/cli/parser.py,sha256=Vqx9n-6Xo1uNhXR4rThmgWpZXTr0nOtkgDf3oMS9b0g,5855
-claude_mpm/cli/startup.py,sha256=A1w9YWPgP0cA8d_T8ymbAbGpP7UARkRvtRcKEbXNy24,62095
+claude_mpm/cli/startup.py,sha256=rztiI5mopeHnRTn7WPivyZF4QDtHjuC-O-YhYvuw5I8,61638
 claude_mpm/cli/startup_display.py,sha256=R_QIamjfdaY5o_VxpIeymyYj1Qde2B9hPXy1P-KmUKI,14972
 claude_mpm/cli/startup_logging.py,sha256=RTuyd6CbhiFQz7Z07LDDhK_ZAnZfuJ9B0NghVSntHFI,29390
 claude_mpm/cli/utils.py,sha256=FSMPftBZM8MeUyTtiB63Lz7oFOgkzwTetQs58RbRb_Q,8785
@@ -206,7 +207,7 @@ claude_mpm/core/mixins.py,sha256=vmZ7Nu2ZOnKjbhN07Ixk4noIej9nsJiknrp-Sclfu0A,534
 claude_mpm/core/oneshot_session.py,sha256=nA86Zk7W3Rh_yIhPuegFL7Xgc9S63vQ_MqfLk52doV0,21994
 claude_mpm/core/optimized_agent_loader.py,sha256=yevEwTZWzVeZYEJhV3czD45OU7ukJIaJos4MGnFP7YQ,15857
 claude_mpm/core/optimized_startup.py,sha256=U5I4f7PNYXCBOLbCkbWT2V2sv01T8iWP2Bw-f928Q9M,17927
-claude_mpm/core/output_style_manager.py,sha256=QkH62HRCH6FYxg2lop_3Xml3BLOieE12024vAjS6SyI,17091
+claude_mpm/core/output_style_manager.py,sha256=ynFLUliYKPuw3CWtTcJR7h0TDBE_5z2gwDT-XT_-Owk,17491
 claude_mpm/core/pm_hook_interceptor.py,sha256=92C8TrpK-XVQD8BiXbqs8lSCX72PU0KZG5oAjhf8GOQ,11197
 claude_mpm/core/service_registry.py,sha256=QpmAMWCov8XXaxQwE7WiNbgv6u_CRjpKPB64kLYvZKk,11722
 claude_mpm/core/session_manager.py,sha256=iEDZWKBYHSu001nFX8vFvH33RvQOW0eIgomWhFM53sw,12078
@@ -970,10 +971,10 @@ claude_mpm/utils/subprocess_utils.py,sha256=D0izRT8anjiUb_JG72zlJR_JAw1cDkb7kalN
 claude_mpm/validation/__init__.py,sha256=YZhwE3mhit-lslvRLuwfX82xJ_k4haZeKmh4IWaVwtk,156
 claude_mpm/validation/agent_validator.py,sha256=GprtAvu80VyMXcKGsK_VhYiXWA6BjKHv7O6HKx0AB9w,20917
 claude_mpm/validation/frontmatter_validator.py,sha256=YpJlYNNYcV8u6hIOi3_jaRsDnzhbcQpjCBE6eyBKaFY,7076
-claude_mpm-5.4.83.dist-info/licenses/LICENSE,sha256=ca3y_Rk4aPrbF6f62z8Ht5MJM9OAvbGlHvEDcj9vUQ4,3867
-claude_mpm-5.4.83.dist-info/licenses/LICENSE-FAQ.md,sha256=TxfEkXVCK98RzDOer09puc7JVCP_q_bN4dHtZKHCMcM,5104
-claude_mpm-5.4.83.dist-info/METADATA,sha256=L9tyI9gHshp4mzDHla_5Yx1JLMkZUDPMMb1Gezu4Gd0,38503
-claude_mpm-5.4.83.dist-info/WHEEL,sha256=_zCd3N1l69ArxyTb8rzEoP9TpbYXkqRFSNOD5OuxnTs,91
-claude_mpm-5.4.83.dist-info/entry_points.txt,sha256=n-Uk4vwHPpuvu-g_I7-GHORzTnN_m6iyOsoLveKKD0E,228
-claude_mpm-5.4.83.dist-info/top_level.txt,sha256=1nUg3FEaBySgm8t-s54jK5zoPnu3_eY6EP6IOlekyHA,11
-claude_mpm-5.4.83.dist-info/RECORD,,
+claude_mpm-5.4.84.dist-info/licenses/LICENSE,sha256=ca3y_Rk4aPrbF6f62z8Ht5MJM9OAvbGlHvEDcj9vUQ4,3867
+claude_mpm-5.4.84.dist-info/licenses/LICENSE-FAQ.md,sha256=TxfEkXVCK98RzDOer09puc7JVCP_q_bN4dHtZKHCMcM,5104
+claude_mpm-5.4.84.dist-info/METADATA,sha256=mXYhdkcOB3779gcXJpYrizksYyUQxqnJ1d4FtqHKroM,38503
+claude_mpm-5.4.84.dist-info/WHEEL,sha256=_zCd3N1l69ArxyTb8rzEoP9TpbYXkqRFSNOD5OuxnTs,91
+claude_mpm-5.4.84.dist-info/entry_points.txt,sha256=n-Uk4vwHPpuvu-g_I7-GHORzTnN_m6iyOsoLveKKD0E,228
+claude_mpm-5.4.84.dist-info/top_level.txt,sha256=1nUg3FEaBySgm8t-s54jK5zoPnu3_eY6EP6IOlekyHA,11
+claude_mpm-5.4.84.dist-info/RECORD,,