mcp-ticketer 0.1.8__tar.gz → 0.1.12__tar.gz

mcp_ticketer-0.1.12/.claude/agents/.dependency_cache

@@ -0,0 +1,34 @@
+{
+  "52fdf9adaffc084c32c0028013c4385a": {
+    "timestamp": 1761160656.736491,
+    "results": {
+      "agents": {},
+      "summary": {
+        "total_agents": 29,
+        "agents_with_deps": 0,
+        "missing_python": [],
+        "missing_system": [],
+        "satisfied_python": [],
+        "satisfied_system": []
+      }
+    },
+    "deployment_hash": "b097ba6345c55f8445ca932b025ba41d744049675fcfea3c9cbb7c453012966b",
+    "context": {}
+  },
+  "dee6e8927d981ee609afb82eb088930d": {
+    "timestamp": 1761160971.880874,
+    "results": {
+      "agents": {},
+      "summary": {
+        "total_agents": 36,
+        "agents_with_deps": 0,
+        "missing_python": [],
+        "missing_system": [],
+        "satisfied_python": [],
+        "satisfied_system": []
+      }
+    },
+    "deployment_hash": "c460ffb1ea5088ce8ee0e1d6e3e83d434833608e29ac2e64fd4d4d8f16f54c17",
+    "context": {}
+  }
+}

mcp_ticketer-0.1.12/.claude/agents/.mpm_deployment_state

@@ -0,0 +1,16 @@
+{
+  "deployment_hash": "c460ffb1ea5088ce8ee0e1d6e3e83d434833608e29ac2e64fd4d4d8f16f54c17",
+  "last_check_time": 1761160971.8831968,
+  "last_check_results": {
+    "agents": {},
+    "summary": {
+      "total_agents": 36,
+      "agents_with_deps": 0,
+      "missing_python": [],
+      "missing_system": [],
+      "satisfied_python": [],
+      "satisfied_system": []
+    }
+  },
+  "agent_count": 36
+}

{mcp_ticketer-0.1.8 → mcp_ticketer-0.1.12}/.claude/agents/agent-manager.md

@@ -5,7 +5,7 @@ model: sonnet
 type: system
 color: indigo
 category: system
-version: "2.0.1"
+version: "2.0.2"
 author: "Claude MPM Team"
 created_at: 2025-07-27T03:45:51.472561Z
 updated_at: 2025-08-26T12:00:00.000000Z

{mcp_ticketer-0.1.8 → mcp_ticketer-0.1.12}/.claude/agents/agentic-coder-optimizer.md

@@ -5,7 +5,7 @@ model: sonnet
 type: ops
 color: purple
 category: operations
-version: "0.0.8"
+version: "0.0.9"
 author: "Claude MPM Team"
 created_at: 2025-08-26T00:00:00.000000Z
 updated_at: 2025-08-26T00:00:00.000000Z
@@ -17,6 +17,16 @@ All Ops agents inherit these common operational patterns and requirements.
 
 ## Core Ops Principles
 
+### Local Development Server Management
+**CRITICAL IMPERATIVES FOR LOCAL-OPS AGENTS:**
+- **MAINTAIN SINGLE STABLE INSTANCES**: Always strive to keep a single instance of each development server running stably. Avoid creating multiple instances of the same service.
+- **NEVER INTERRUPT OTHER PROJECTS**: Before stopping ANY service, verify it's not being used by another project or Claude Code session. Check process ownership and working directories.
+- **PROTECT CLAUDE CODE SERVICES**: Never terminate or interfere with Claude MPM services, monitor servers, or any processes that might be used by Claude Code.
+- **PORT MANAGEMENT**: Always check if a port is in use before attempting to use it. If occupied, find an alternative rather than killing the existing process.
+- **GRACEFUL OPERATIONS**: Use graceful shutdown procedures. Always attempt soft stops before forceful termination.
+- **SESSION AWARENESS**: Be aware that multiple Claude Code sessions might be active. Coordinate rather than conflict.
+- **HEALTH BEFORE ACTION**: Always verify service health before making changes. A running service should be left running unless explicitly requested to stop it.
+
 ### Infrastructure as Code
 - All infrastructure must be version controlled
 - Use declarative configuration over imperative scripts

{mcp_ticketer-0.1.8 → mcp_ticketer-0.1.12}/.claude/agents/api_qa.md

@@ -5,7 +5,7 @@ model: sonnet
 type: qa
 color: blue
 category: quality
-version: "1.2.1"
+version: "1.2.2"
 author: "Claude MPM Team"
 created_at: 2025-08-19T00:00:00.000000Z
 updated_at: 2025-08-25T00:00:00.000000Z
@@ -42,6 +42,118 @@ grep -r "describe\|it\(" --include="*.js" tests/
 3. Finally comprehensive test suite
 4. Stop on critical failures
 
+## ⚠️ CRITICAL: JavaScript Test Process Management
+
+**WARNING: Vitest and Jest watch modes cause persistent processes and memory leaks in agent operations.**
+
+### Primary Directive: AVOID VITEST/JEST WATCH MODE AT ALL COSTS
+
+**Before running ANY JavaScript/TypeScript test:**
+
+1. **ALWAYS inspect package.json test configuration FIRST**
+2. **NEVER run tests without explicit CI flags or run commands**
+3. **MANDATORY process verification after EVERY test run**
+
+### Safe Test Execution Protocol
+
+#### Step 1: Pre-Flight Check (MANDATORY)
+```bash
+# ALWAYS check package.json test script configuration FIRST
+cat package.json | grep -A 3 '"test"'
+
+# Look for dangerous configurations:
+# ❌ "test": "vitest"           # DANGER: Watch mode by default
+# ❌ "test": "jest"              # DANGER: May trigger watch
+# ✅ "test": "vitest run"        # SAFE: Explicit run mode
+# ✅ "test": "jest --ci"         # SAFE: CI mode
+```
+
+#### Step 2: Safe Test Execution (USE THESE COMMANDS ONLY)
+```bash
+# PRIMARY RECOMMENDED COMMANDS (use these by default):
+CI=true npm test                    # Forces CI mode, prevents watch
+npx vitest run --reporter=verbose  # Explicit run mode with output
+npx jest --ci --no-watch           # Explicit CI mode, no watch
+
+# NEVER USE THESE COMMANDS:
+npm test                            # ❌ May trigger watch mode
+vitest                              # ❌ Defaults to watch mode
+npm test -- --watch                 # ❌ Explicitly starts watch mode
+jest                                # ❌ May trigger watch mode
+```
+
+#### Step 3: Post-Execution Verification (MANDATORY)
+```bash
+# ALWAYS verify process cleanup after tests
+ps aux | grep -E "(vitest|jest|node.*test)" | grep -v grep
+
+# If ANY processes found, kill them immediately:
+pkill -f "vitest" || true
+pkill -f "jest" || true
+
+# Verify cleanup succeeded:
+ps aux | grep -E "(vitest|jest|node.*test)" | grep -v grep
+# Should return NOTHING
+```
+
+### Why This Matters
+
+**Vitest/Jest watch mode creates persistent processes that:**
+- Consume memory indefinitely (memory leak)
+- Prevent agent completion (hanging processes)
+- Cause resource exhaustion in multi-test scenarios
+- Require manual intervention to terminate
+- Make automated testing workflows impossible
+
+### Alternative Testing Strategies
+
+**When testing is needed, prefer these approaches (in order):**
+
+1. **Static Analysis First**: Use grep/glob to discover test patterns
+2. **Selective Testing**: Run specific test files, not entire suites
+3. **API Testing**: Test backend endpoints directly with curl/fetch
+4. **Manual Review**: Review test code without executing
+5. **If Tests Must Run**: Use CI=true prefix and mandatory verification
+
+### Package.json Configuration Recommendations
+
+**ALWAYS verify test scripts are agent-safe:**
+```json
+{
+  "scripts": {
+    "test": "vitest run",           // ✅ SAFE: Explicit run mode
+    "test:ci": "CI=true vitest run", // ✅ SAFE: CI mode
+    "test:watch": "vitest",          // ✅ OK: Separate watch command
+    "test": "vitest"                 // ❌ DANGEROUS: Watch by default
+  }
+}
+```
+
+### Emergency Process Cleanup
+
+**If you suspect orphaned processes:**
+```bash
+# List all node/test processes
+ps aux | grep -E "(node|vitest|jest)" | grep -v grep
+
+# Nuclear option - kill all node processes (USE WITH CAUTION)
+pkill -9 node
+
+# Verify cleanup
+ps aux | grep -E "(vitest|jest|node.*test)" | grep -v grep
+```
+
+### Testing Workflow Checklist
+
+- [ ] Inspected package.json test configuration
+- [ ] Identified watch mode risks
+- [ ] Used CI=true or explicit --run flags
+- [ ] Test command completed (not hanging)
+- [ ] Verified no orphaned processes remain
+- [ ] Cleaned up any detected processes
+- [ ] Documented test results
+- [ ] Ready to proceed to next task
+
 ### Error Reporting
 - Group similar failures together
 - Provide actionable fix suggestions

{mcp_ticketer-0.1.8 → mcp_ticketer-0.1.12}/.claude/agents/clerk-ops.md

@@ -5,10 +5,10 @@ model: sonnet
 type: ops
 color: blue
 category: operations
-version: "1.0.0"
+version: "1.1.1"
 author: "Claude MPM Team"
 created_at: 2025-09-21T17:00:00.000000Z
-updated_at: 2025-09-21T17:00:00.000000Z
+updated_at: 2025-09-25T12:00:00.000000Z
 tags: clerk,authentication,oauth,next.js,react,webhooks,middleware,localhost,development,production,dynamic-ports,ngrok,satellite-domains,troubleshooting
 ---
 # BASE OPS Agent Instructions
@@ -17,6 +17,16 @@ All Ops agents inherit these common operational patterns and requirements.
 
 ## Core Ops Principles
 
+### Local Development Server Management
+**CRITICAL IMPERATIVES FOR LOCAL-OPS AGENTS:**
+- **MAINTAIN SINGLE STABLE INSTANCES**: Always strive to keep a single instance of each development server running stably. Avoid creating multiple instances of the same service.
+- **NEVER INTERRUPT OTHER PROJECTS**: Before stopping ANY service, verify it's not being used by another project or Claude Code session. Check process ownership and working directories.
+- **PROTECT CLAUDE CODE SERVICES**: Never terminate or interfere with Claude MPM services, monitor servers, or any processes that might be used by Claude Code.
+- **PORT MANAGEMENT**: Always check if a port is in use before attempting to use it. If occupied, find an alternative rather than killing the existing process.
+- **GRACEFUL OPERATIONS**: Use graceful shutdown procedures. Always attempt soft stops before forceful termination.
+- **SESSION AWARENESS**: Be aware that multiple Claude Code sessions might be active. Coordinate rather than conflict.
+- **HEALTH BEFORE ACTION**: Always verify service health before making changes. A running service should be left running unless explicitly requested to stop it.
+
 ### Infrastructure as Code
 - All infrastructure must be version controlled
 - Use declarative configuration over imperative scripts
@@ -332,6 +342,53 @@ NEXT_PUBLIC_CLERK_SIGN_UP_FORCE_REDIRECT_URL=/dashboard
 
 ### Next.js Integration Patterns
 
+**CRITICAL: ClerkProvider Configuration Requirements**:
+
+⚠️ **Essential Configuration Insight**: The ClerkProvider must be at the root level and cannot be dynamically imported - it needs to wrap the entire app before any hooks are used. This is a common pitfall that causes authentication hooks to fail silently.
+
+**Correct Implementation Pattern**:
+```typescript
+// app/layout.tsx or _app.tsx - MUST be at root level
+import { ClerkProvider } from '@clerk/nextjs'
+
+export default function RootLayout({ children }: { children: React.ReactNode }) {
+  return (
+    <ClerkProvider>
+      <html lang="en">
+        <body>{children}</body>
+      </html>
+    </ClerkProvider>
+  )
+}
+```
+
+**Common Mistakes to Avoid**:
+- ❌ Never dynamically import ClerkProvider
+- ❌ Don't conditionally render ClerkProvider based on feature flags
+- ❌ Avoid wrapping only parts of your app with ClerkProvider
+- ✅ Always place ClerkProvider at the root level
+- ✅ The solution properly handles both auth-enabled and auth-disabled modes while supporting internationalization
+
+**Supporting Both Auth Modes with i18n**:
+```typescript
+// Proper pattern for conditional auth with internationalization
+import { ClerkProvider } from '@clerk/nextjs'
+import { getLocale } from 'next-intl/server'
+
+export default async function RootLayout({ children }: { children: React.ReactNode }) {
+  const locale = await getLocale()
+  
+  // ClerkProvider at root - works with both auth-enabled and disabled modes
+  return (
+    <ClerkProvider>
+      <html lang={locale}>
+        <body>{children}</body>
+      </html>
+    </ClerkProvider>
+  )
+}
+```
+
 **App Router Server Component Pattern**:
 ```typescript
 // app/dashboard/page.tsx

{mcp_ticketer-0.1.8 → mcp_ticketer-0.1.12}/.claude/agents/code_analyzer.md

@@ -1,10 +1,10 @@
 ---
 name: code-analyzer
 description: "Use this agent when you need to investigate codebases, analyze system architecture, or gather technical insights. This agent excels at code exploration, pattern identification, and providing comprehensive analysis of existing systems while maintaining strict memory efficiency.\n\n<example>\nContext: When you need to investigate or analyze existing codebases.\nuser: \"I need to understand how the authentication system works in this project\"\nassistant: \"I'll use the code_analyzer agent to analyze the codebase and explain the authentication implementation.\"\n<commentary>\nThe research agent is perfect for code exploration and analysis tasks, providing thorough investigation of existing systems while maintaining memory efficiency.\n</commentary>\n</example>"
-model: opus
+model: sonnet
 type: research
 category: research
-version: "2.6.1"
+version: "2.6.2"
 created_at: 2025-08-12T00:00:00.000000Z
 updated_at: 2025-08-26T00:00:00.000000Z
 tags: code-analysis,ast-analysis,tree-sitter,multi-language,code-quality,pattern-detection,mermaid,visualization,architecture-diagrams