@polymorphism-tech/morph-spec 4.10.6 → 4.10.8

package/framework/agents.json

@@ -1,2567 +1,2268 @@
-{
-  "$schema": "./agent-schema.json",
-  "version": "3.3.0-hierarchical",
-  "total_agents": 43,
-  "tiers": {
-    "tier_1_orchestrators": 3,
-    "tier_2_leaders": 4,
-    "tier_3_specialists": 29,
-    "tier_4_validators": 7
-  },
-  "agents": {
-    "_comment_tier_1": "=== TIER 1: ORCHESTRATORS (3) ===",
-    "standards-architect": {
-      "tier": 1,
-      "role": "orchestrator",
-      "title": "Chief Architect",
-      "domains": [
-        "architecture",
-        "developer-experience"
-      ],
-      "keywords": [],
-      "always_active": true,
-      "validators": [],
-      "relationships": {
-        "reports_to": "user",
-        "coordinates": [
-          "dotnet-senior",
-          "infra-architect",
-          "ui-designer",
-          "domain-architect",
-          "testing-specialist",
-          "code-analyzer",
-          "troubleshooting-expert",
-          "documentation-specialist",
-          "load-testing-expert",
-          "vsa-architect"
-        ],
-        "escalates_to": "user",
-        "team_role": "lead"
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "backend-dotnet-program-cs-checklist",
-          "scope": "implement",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Team Lead (Delegate Mode)",
-        "icon": "🎯",
-        "spawn_prompt": "You are the Chief Architect and Team Lead in delegate mode. Coordinate Domain Leaders, resolve conflicts, synthesize results. DO NOT implement code yourself. Escalate conflicts to user when teammates disagree on architecture/tech choices."
-      }
-    },
-    "ai-system-architect": {
-      "tier": 1,
-      "role": "orchestrator",
-      "title": "AI/Agent Architect",
-      "domains": [
-        "ai-orchestration",
-        "architecture"
-      ],
-      "keywords": [
-        "agent system",
-        "ai architecture",
-        "orchestration",
-        "multi-agent",
-        "agent workflow"
-      ],
-      "always_active": false,
-      "validators": [],
-      "relationships": {
-        "reports_to": "standards-architect",
-        "coordinates": [
-          "ms-agent-expert"
-        ],
-        "escalates_to": "standards-architect",
-        "collaborates_with": [
-          "dotnet-senior"
-        ],
-        "team_role": "orchestrator",
-        "active_phases": [
-          "design",
-          "tasks"
-        ]
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "ai-agents-setup",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "ai-agents-workflows",
-          "scope": "design",
-          "priority": "required"
-        },
-        {
-          "id": "ai-agents-production",
-          "scope": "implement",
-          "priority": "required"
-        },
-        {
-          "id": "ai-agents-blazor-ui",
-          "scope": "implement",
-          "priority": "reference"
-        }
-      ],
-      "teammate": {
-        "role": "AI Architect",
-        "icon": "🤖",
-        "spawn_prompt": "You are the AI/Agent System Architect. Design agent workflows, tool integrations, and orchestration patterns. Coordinate with ms-agent-expert for implementation."
-      }
-    },
-    "popm-advisor": {
-      "tier": 1,
-      "role": "orchestrator",
-      "title": "Product/Project Advisor",
-      "domains": [
-        "requirements",
-        "business-value"
-      ],
-      "keywords": [
-        "unclear",
-        "requirements",
-        "priority",
-        "roi",
-        "business value",
-        "user story"
-      ],
-      "always_active": false,
-      "validators": [],
-      "relationships": {
-        "reports_to": "user",
-        "coordinates": [],
-        "team_role": "planning_only",
-        "active_phases": [
-          "proposal",
-          "setup",
-          "design"
-        ]
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": null
-    },
-    "_comment_tier_2": "=== TIER 2: DOMAIN LEADERS (4) ===",
-    "dotnet-senior": {
-      "tier": 2,
-      "role": "domain-leader",
-      "title": "Backend Squad Leader",
-      "stacks": ["dotnet", "blazor"],
-      "domains": [
-        "backend"
-      ],
-      "keywords": [
-        "backend",
-        "api",
-        "dotnet",
-        ".net",
-        "csharp",
-        "c#",
-        "web api",
-        "minimal api"
-      ],
-      "always_active": true,
-      "validators": [
-        "architecture",
-        "packages"
-      ],
-      "relationships": {
-        "reports_to": "standards-architect",
-        "coordinates": [
-          "ef-modeler",
-          "event-architect",
-          "api-designer",
-          "nosql-cache-expert",
-          "hangfire-orchestrator",
-          "ms-agent-expert",
-          "asaas-financial",
-          "clerk-auth",
-          "resend-email"
-        ],
-        "escalates_to": "standards-architect",
-        "collaborates_with": [
-          "infra-architect",
-          "blazor-builder",
-          "nextjs-expert"
-        ],
-        "team_role": "domain_leader"
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "backend-dotnet-core",
-          "scope": "implement",
-          "priority": "required"
-        },
-        {
-          "id": "backend-dotnet-program-cs-checklist",
-          "scope": "implement",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Backend Squad Leader",
-        "icon": "⚙️",
-        "spawn_prompt": "You are the Backend Squad Leader. Coordinate backend specialists (ef-modeler, event-architect, api-designer, etc.). Assign tasks, review designs, enforce backend standards. Escalate cross-domain conflicts to standards-architect."
-      }
-    },
-    "infra-architect": {
-      "tier": 2,
-      "role": "domain-leader",
-      "title": "Infrastructure Squad Leader",
-      "stacks": ["azure", "docker"],
-      "domains": [
-        "infrastructure"
-      ],
-      "keywords": [
-        "infrastructure",
-        "infra",
-        "cloud",
-        "deployment",
-        "hosting",
-        "ci/cd",
-        "container",
-        "iac",
-        "pipeline",
-        "vercel",
-        "neon",
-        "planetscale",
-        "serverless database",
-        "serverless postgres"
-      ],
-      "always_active": true,
-      "validators": [],
-      "relationships": {
-        "reports_to": "standards-architect",
-        "coordinates": [
-          "azure-architect",
-          "devops-engineer",
-          "container-specialist",
-          "observability-expert"
-        ],
-        "escalates_to": "standards-architect",
-        "collaborates_with": [
-          "dotnet-senior",
-          "ui-designer"
-        ],
-        "team_role": "domain_leader"
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "infrastructure-vercel-database",
-          "scope": "design",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Infrastructure Squad Leader",
-        "icon": "🏗️",
-        "spawn_prompt": "You are the Infrastructure Squad Leader. Coordinate infra specialists regardless of cloud provider (azure-architect, devops-engineer, container-specialist, observability-expert). Focus on IaC, CI/CD, containerization, cost optimization. Delegate to azure-architect for Azure-specific work. IMPORTANT: When deployment target is Vercel, ALWAYS enforce serverless database (Neon, Supabase/PgBouncer, PlanetScale) — never TCP connection pools. Escalate to standards-architect on conflicts."
-      }
-    },
-    "azure-architect": {
-      "tier": 3,
-      "role": "specialist",
-      "title": "Azure Infrastructure Specialist",
-      "domains": [
-        "infrastructure"
-      ],
-      "keywords": [
-        "azure",
-        "bicep",
-        "arm template",
-        "azure resources",
-        "container apps",
-        "azure sql",
-        "key vault",
-        "app insights"
-      ],
-      "always_active": false,
-      "validators": [
-        "architecture"
-      ],
-      "relationships": {
-        "reports_to": "infra-architect",
-        "coordinates": [
-          "bicep-architect",
-          "devops-engineer",
-          "container-specialist",
-          "observability-expert",
-          "azure-identity"
-        ],
-        "escalates_to": "infra-architect",
-        "collaborates_with": [
-          "bicep-architect",
-          "devops-engineer",
-          "container-specialist"
-        ],
-        "team_role": "specialist",
-        "active_phases": [
-          "design",
-          "implement"
-        ]
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "infrastructure-azure-azure",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Infrastructure Squad Leader",
-        "icon": "☁️",
-        "spawn_prompt": "You are the Azure Infrastructure Specialist (tier-3). Focus exclusively on Azure resources, Bicep IaC templates, Azure cost optimization, and zero-portal policy. Report to infra-architect. Coordinate with bicep-architect for IaC, devops-engineer for Azure pipelines, container-specialist for Container Apps."
-      }
-    },
-    "ui-designer": {
-      "tier": 2,
-      "role": "domain-leader",
-      "title": "UI/UX Squad Leader",
-      "domains": [
-        "frontend-design"
-      ],
-      "keywords": [
-        "wireframe",
-        "mockup",
-        "user flow",
-        "ux",
-        "design",
-        "interface design",
-        "user experience",
-        "page",
-        "dashboard",
-        "form",
-        "UI",
-        "settings",
-        "interface",
-        "screen",
-        "panel",
-        "portal",
-        "view"
-      ],
-      "always_active": false,
-      "validators": [
-        "design-system",
-        "contrast"
-      ],
-      "relationships": {
-        "reports_to": "standards-architect",
-        "coordinates": [
-          "blazor-builder",
-          "nextjs-expert",
-          "css-specialist"
-        ],
-        "escalates_to": "standards-architect",
-        "collaborates_with": [
-          "dotnet-senior"
-        ],
-        "team_role": "domain_leader",
-        "active_phases": [
-          "uiux"
-        ]
-      },
-      "standards": [
-        {
-          "id": "frontend-blazor-fluent-ui",
-          "scope": "uiux",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-design-system-naming",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-design-system-animations",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "UI/UX Squad Leader (FASE 1.5)",
-        "icon": "🎨",
-        "spawn_prompt": "You are the UI/UX Squad Leader for FASE 1.5. Create wireframes, mockups, user flows. Define design system (colors, typography, spacing). Coordinate with blazor-builder or nextjs-expert for stack-specific patterns. Work is AGNOSTIC (no implementation code)."
-      }
-    },
-    "_comment_tier_3_backend": "=== TIER 3: BACKEND SPECIALISTS (10) ===",
-    "ef-modeler": {
-      "tier": 3,
-      "role": "specialist",
-      "title": "Data Persistence Specialist (Relational)",
-      "domains": [
-        "backend-data"
-      ],
-      "keywords": [
-        "entity",
-        "database",
-        "migration",
-        "ef core",
-        "entity framework",
-        "sql",
-        "dbcontext"
-      ],
-      "always_active": false,
-      "validators": [
-        "architecture",
-        "blazor-concurrency"
-      ],
-      "relationships": {
-        "reports_to": "dotnet-senior",
-        "coordinates": [],
-        "escalates_to": "dotnet-senior",
-        "collaborates_with": [
-          "blazor-builder",
-          "nextjs-expert",
-          "api-designer",
-          "nosql-cache-expert"
-        ],
-        "team_role": "specialist",
-        "active_phases": [
-          "design",
-          "implement"
-        ]
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "backend-database-ef-core",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "backend-dotnet-core",
-          "scope": "implement",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Data Persistence Specialist",
-        "icon": "🗄️",
-        "spawn_prompt": "You are the Data Persistence Specialist (EF Core). Focus on Models/, Migrations/, DbContext. Follow blazor-efcore.md standards. Use IDbContextFactory for background ops. Message blazor-builder when entities ready for UI binding."
-      }
-    },
-    "event-architect": {
-      "tier": 3,
-      "role": "specialist",
-      "title": "Event-Driven Architecture Specialist",
-      "domains": [
-        "backend-events"
-      ],
-      "keywords": [
-        "event",
-        "service bus",
-        "rabbitmq",
-        "cqrs",
-        "event sourcing",
-        "messaging",
-        "pub/sub",
-        "domain events",
-        "saga",
-        "real-time",
-        "realtime",
-        "websocket",
-        "live updates"
-      ],
-      "always_active": false,
-      "validators": [
-        "architecture",
-        "event-driven"
-      ],
-      "relationships": {
-        "reports_to": "dotnet-senior",
-        "coordinates": [],
-        "escalates_to": "dotnet-senior",
-        "collaborates_with": [
-          "domain-architect",
-          "api-designer",
-          "infra-architect"
-        ],
-        "team_role": "specialist",
-        "active_phases": [
-          "design",
-          "implement"
-        ]
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Event-Driven Architecture Specialist",
-        "icon": "📨",
-        "spawn_prompt": "You are the Event-Driven Architecture Specialist. Implement Azure Service Bus queues/topics, CQRS patterns, Event Sourcing, Domain Events. Design idempotent handlers, dead letter queues, saga patterns. Collaborate with domain-architect for event design."
-      }
-    },
-    "api-designer": {
-      "tier": 3,
-      "role": "specialist",
-      "title": "API Design Specialist",
-      "domains": [
-        "backend-api"
-      ],
-      "keywords": [
-        "rest",
-        "graphql",
-        "grpc",
-        "api",
-        "openapi",
-        "swagger",
-        "versioning",
-        "rate limiting",
-        "hot chocolate",
-        "endpoint"
-      ],
-      "always_active": false,
-      "validators": [],
-      "relationships": {
-        "reports_to": "dotnet-senior",
-        "coordinates": [],
-        "escalates_to": "dotnet-senior",
-        "collaborates_with": [
-          "ef-modeler",
-          "event-architect",
-          "blazor-builder",
-          "nextjs-expert"
-        ],
-        "team_role": "specialist",
-        "active_phases": [
-          "design",
-          "implement"
-        ]
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "API Design Specialist",
-        "icon": "🔌",
-        "spawn_prompt": "You are the API Design Specialist. Design REST APIs (resource naming, HTTP verbs, status codes), GraphQL schemas with Hot Chocolate, gRPC .proto files. Add OpenAPI/Swagger annotations. Implement API versioning, rate limiting. Review with frontend specialists."
-      }
-    },
-    "nosql-cache-expert": {
-      "tier": 3,
-      "role": "specialist",
-      "title": "NoSQL & Cache Specialist",
-      "domains": [
-        "backend-nosql"
-      ],
-      "keywords": [
-        "cosmos",
-        "cosmosdb",
-        "redis",
-        "cache",
-        "blob storage",
-        "nosql",
-        "document db",
-        "key-value",
-        "azure storage"
-      ],
-      "always_active": false,
-      "validators": [],
-      "relationships": {
-        "reports_to": "dotnet-senior",
-        "coordinates": [],
-        "escalates_to": "dotnet-senior",
-        "collaborates_with": [
-          "ef-modeler",
-          "infra-architect"
-        ],
-        "team_role": "specialist",
-        "active_phases": [
-          "design",
-          "implement"
-        ]
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "NoSQL & Cache Specialist",
-        "icon": "💾",
-        "spawn_prompt": "You are the NoSQL & Cache Specialist. Implement Azure Cosmos DB (SQL API, partition keys, RUs), Redis Cache (cache-aside, read-through, write-behind), Blob Storage (hot/cool/archive tiers). Design cache invalidation strategies."
-      }
-    },
-    "domain-architect": {
-      "tier": 2,
-      "role": "domain-leader",
-      "title": "Domain Modeling Leader",
-      "domains": [
-        "backend-ddd"
-      ],
-      "keywords": [
-        "ddd",
-        "domain driven design",
-        "aggregate",
-        "aggregate root",
-        "entity",
-        "value object",
-        "domain event",
-        "bounded context",
-        "ubiquitous language",
-        "domain modeling",
-        "aggregateroot",
-        "domainevents",
-        "integration event"
-      ],
-      "always_active": false,
-      "validators": [
-        "architecture"
-      ],
-      "relationships": {
-        "reports_to": "standards-architect",
-        "coordinates": [
-          "ef-modeler",
-          "event-architect"
-        ],
-        "escalates_to": "standards-architect",
-        "collaborates_with": [
-          "dotnet-senior",
-          "api-designer"
-        ],
-        "team_role": "domain_leader"
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "architecture-ddd-complexity-levels",
-          "scope": "design",
-          "priority": "required"
-        },
-        {
-          "id": "architecture-ddd-aggregates",
-          "scope": "design",
-          "priority": "required"
-        },
-        {
-          "id": "architecture-ddd-entities",
-          "scope": "design",
-          "priority": "required"
-        },
-        {
-          "id": "architecture-ddd-value-objects",
-          "scope": "design",
-          "priority": "required"
-        },
-        {
-          "id": "architecture-ddd-bounded-contexts",
-          "scope": "design",
-          "priority": "required"
-        },
-        {
-          "id": "architecture-ddd-ubiquitous-language",
-          "scope": "design",
-          "priority": "required"
-        }
-      ],
-      "active_phases": [
-        "design",
-        "implement"
-      ],
-      "teammate": {
-        "role": "Domain Modeling Leader",
-        "icon": "📐",
-        "spawn_prompt": "You are the Domain Modeling Leader for MORPH-SPEC. Your primary responsibility is detecting the correct domain complexity level and producing the Aggregate Blueprint before any contracts are generated.\n\nALWAYS start with the 5-question complexity detection:\n1. Does the main entity have state transitions? (Draft → Confirmed → Shipped) → Yes = Level 2+\n2. Are there business invariants? (\"can only cancel if Active\") → Yes = Level 2+\n3. Are there derived calculations? (Total, Balance, Discount) → Yes = Level 2+\n4. Do other modules need to react to changes? (Domain Events with consumers) → Yes = Level 2+\n5. Did the user explicitly declare a Bounded Context? Or are there 3+ domains with conflicting models? → Yes = Level 3\nIf none of the above: Level 1 (CRUD)\n\nFor Level 1: Use contracts-level1.cs template. No AggregateRoot, no Domain Events.\nFor Level 2: Use contracts-level2.cs template. Design AggregateRoot with factory methods, invariants, Value Objects, Domain Events.\nFor Level 3: Use contracts-level3.cs template. Add BOUNDED_CONTEXT namespace, Integration Events, cross-BC ID references only.\n\nDocument in spec.md under ## Domain Complexity and ## Aggregate Blueprint (Level 2+).\nCoordinate ef-modeler for persistence design and event-architect for Domain Event patterns.\nRef: framework/standards/architecture/ddd/complexity-levels.md"
-      }
-    },
-    "hangfire-orchestrator": {
-      "tier": 3,
-      "role": "specialist",
-      "title": "Background Jobs Specialist",
-      "domains": [
-        "backend-jobs"
-      ],
-      "keywords": [
-        "scheduled",
-        "job",
-        "background",
-        "cron",
-        "hangfire",
-        "recurring",
-        "fire and forget",
-        "delayed"
-      ],
-      "always_active": false,
-      "validators": [
-        "architecture",
-        "blazor-concurrency"
-      ],
-      "relationships": {
-        "reports_to": "dotnet-senior",
-        "coordinates": [],
-        "escalates_to": "dotnet-senior",
-        "collaborates_with": [
-          "ef-modeler",
-          "infra-architect"
-        ],
-        "team_role": "specialist",
-        "active_phases": [
-          "implement"
-        ]
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Background Jobs Specialist",
-        "icon": "⏰",
-        "spawn_prompt": "You are the Background Jobs Specialist (Hangfire). Implement fire-and-forget jobs, delayed jobs, recurring jobs (cron), continuations (chaining). Configure retry policies, queue management. Use IDbContextFactory for scoped operations."
-      }
-    },
-    "ms-agent-expert": {
-      "tier": 3,
-      "role": "specialist",
-      "title": "Microsoft Agent Framework Expert",
-      "domains": [
-        "ai-agents"
-      ],
-      "keywords": [
-        "agent",
-        "ai",
-        "llm",
-        "rag",
-        "embedding",
-        "mcp",
-        "a2a",
-        "middleware",
-        "microsoft agent framework",
-        "ichatclient"
-      ],
-      "always_active": false,
-      "validators": [
-        "architecture",
-        "packages"
-      ],
-      "relationships": {
-        "reports_to": "ai-system-architect",
-        "coordinates": [],
-        "escalates_to": "ai-system-architect",
-        "collaborates_with": [
-          "dotnet-senior",
-          "infra-architect"
-        ],
-        "team_role": "specialist",
-        "active_phases": [
-          "design",
-          "implement"
-        ]
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "ai-agents-setup",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "ai-agents-workflows",
-          "scope": "design",
-          "priority": "required"
-        },
-        {
-          "id": "ai-agents-production",
-          "scope": "implement",
-          "priority": "required"
-        },
-        {
-          "id": "ai-agents-blazor-ui",
-          "scope": "implement",
-          "priority": "reference"
-        }
-      ],
-      "teammate": {
-        "role": "Microsoft Agent Framework Expert",
-        "icon": "🤖",
-        "spawn_prompt": "You are the Microsoft Agent Framework Expert. Implement ChatClientAgent, AIFunctionFactory, agent workflows (sequential, handoff, group chat). Integrate MCP tools (McpClientFactory, ListToolsAsync, Cast<AITool>). Host agents via A2A protocol (MapA2A, agent cards). Add middleware pipeline, observability (WithOpenTelemetry)."
-      }
-    },
-    "supabase-expert": {
-      "tier": 3,
-      "role": "specialist",
-      "title": "Supabase & PostgreSQL Specialist",
-      "domains": [
-        "backend-supabase"
-      ],
-      "keywords": [
-        "supabase",
-        "postgresql",
-        "rls",
-        "realtime",
-        "pgvector",
-        "row level security",
-        "edge functions"
-      ],
-      "always_active": false,
-      "validators": [],
-      "relationships": {
-        "reports_to": "dotnet-senior",
-        "coordinates": [],
-        "escalates_to": "dotnet-senior",
-        "collaborates_with": [
-          "nextjs-expert",
-          "vector-search-expert",
-          "ef-modeler"
-        ],
-        "team_role": "specialist",
-        "active_phases": [
-          "design",
-          "implement"
-        ]
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Supabase & PostgreSQL Specialist",
-        "icon": "🐘",
-        "spawn_prompt": "You are the Supabase & PostgreSQL Specialist. Implement Supabase Auth (magic links, OAuth, JWT), Row Level Security (RLS policies), Realtime subscriptions, Edge Functions (Deno/TypeScript). Use pgvector for embeddings/similarity search. Design efficient schemas with proper indexing. Coordinate with nextjs-expert for frontend integration."
-      }
-    },
-    "vector-search-expert": {
-      "tier": 3,
-      "role": "specialist",
-      "title": "Vector Search & RAG Specialist",
-      "domains": [
-        "ai-vector"
-      ],
-      "keywords": [
-        "vector db",
-        "embeddings",
-        "semantic search",
-        "rag",
-        "pgvector",
-        "similarity search",
-        "retrieval augmented"
-      ],
-      "always_active": false,
-      "validators": [],
-      "relationships": {
-        "reports_to": "ai-system-architect",
-        "coordinates": [],
-        "escalates_to": "ai-system-architect",
-        "collaborates_with": [
-          "ms-agent-expert",
-          "supabase-expert",
-          "context-optimizer"
-        ],
-        "team_role": "specialist",
-        "active_phases": [
-          "design",
-          "implement"
-        ]
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "ai-agents-setup",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "ai-agents-workflows",
-          "scope": "design",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Vector Search & RAG Specialist",
-        "icon": "🔎",
-        "spawn_prompt": "You are the Vector Search & RAG Specialist. Implement vector embeddings (OpenAI, Azure AI), similarity search (pgvector, Azure AI Search), RAG pipelines (chunking, embedding, retrieval). Design hybrid search (vector + full-text). Optimize embedding dimensions and index types (HNSW, IVFFlat). Collaborate with ms-agent-expert for agent integration and supabase-expert for pgvector storage."
-      }
-    },
-    "context-optimizer": {
-      "tier": 3,
-      "role": "specialist",
-      "title": "Context & Token Optimization Specialist",
-      "domains": [
-        "ai-context"
-      ],
-      "keywords": [
-        "context window",
-        "token optimization",
-        "chunking",
-        "context compression",
-        "summarization",
-        "token budget"
-      ],
-      "always_active": false,
-      "validators": [],
-      "relationships": {
-        "reports_to": "ai-system-architect",
-        "coordinates": [],
-        "escalates_to": "ai-system-architect",
-        "collaborates_with": [
-          "ms-agent-expert",
-          "vector-search-expert"
-        ],
-        "team_role": "specialist",
-        "active_phases": [
-          "implement"
-        ]
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "ai-agents-workflows",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Context & Token Optimization Specialist",
-        "icon": "🧠",
-        "spawn_prompt": "You are the Context & Token Optimization Specialist. Optimize context windows (sliding window, summarization, selective inclusion), implement token counting and budget management, design chunking strategies (semantic, fixed-size, recursive). Reduce costs through prompt caching, context compression. Coordinate with vector-search-expert for retrieval-based context building."
-      }
-    },
-    "asaas-financial": {
-      "tier": 3,
-      "role": "specialist",
-      "title": "Payment Integration Specialist (Brazil)",
-      "domains": [
-        "integration-payment"
-      ],
-      "keywords": [
-        "asaas",
-        "payment",
-        "pix",
-        "boleto",
-        "credit card",
-        "subscription",
-        "pagamento"
-      ],
-      "always_active": false,
-      "validators": [
-        "architecture",
-        "contract-compliance"
-      ],
-      "relationships": {
-        "reports_to": "dotnet-senior",
-        "coordinates": [],
-        "escalates_to": "dotnet-senior",
-        "collaborates_with": [
-          "blazor-builder",
-          "nextjs-expert"
-        ],
-        "team_role": "specialist",
-        "active_phases": [
-          "design",
-          "implement"
-        ]
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Payment Integration Specialist",
-        "icon": "💳",
-        "spawn_prompt": "You are the Payment Integration Specialist (Asaas SDK for Brazil). Implement PIX payments, Boleto generation, Credit Card processing, Subscription management. Follow contract-compliance validator patterns for SDK usage."
-      }
-    },
-    "clerk-auth": {
-      "tier": 3,
-      "role": "specialist",
-      "title": "Auth SaaS Integration Specialist",
-      "domains": [
-        "integration-auth"
-      ],
-      "keywords": [
-        "clerk",
-        "clerk auth",
-        "add auth",
-        "implement auth",
-        "login",
-        "signup",
-        "oauth"
-      ],
-      "negativeKeywords": [
-        "existing auth",
-        "current auth",
-        "integrate with auth",
-        "already have auth"
-      ],
-      "always_active": false,
-      "validators": [],
-      "relationships": {
-        "reports_to": "dotnet-senior",
-        "coordinates": [],
-        "escalates_to": "dotnet-senior",
-        "collaborates_with": [
-          "blazor-builder",
-          "nextjs-expert",
-          "azure-identity"
-        ],
-        "team_role": "specialist",
-        "active_phases": [
-          "design",
-          "implement"
-        ]
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Auth SaaS Integration Specialist",
-        "icon": "🔐",
-        "spawn_prompt": "You are the Auth SaaS Integration Specialist (Clerk SDK). Implement Clerk authentication flows (login, signup, OAuth), session management, user profile. Integrate with Blazor or Next.js frontend."
-      }
-    },
-    "resend-email": {
-      "tier": 3,
-      "role": "specialist",
-      "title": "Email Integration Specialist",
-      "domains": [
-        "integration-email"
-      ],
-      "keywords": [
-        "resend",
-        "email",
-        "transactional email",
-        "email notification",
-        "send email",
-        "email template",
-        "smtp"
-      ],
-      "negativeKeywords": [
-        "push notification",
-        "in-app notification",
-        "notification preference",
-        "notification settings"
-      ],
-      "always_active": false,
-      "validators": [
-        "architecture",
-        "contract-compliance"
-      ],
-      "relationships": {
-        "reports_to": "dotnet-senior",
-        "coordinates": [],
-        "escalates_to": "dotnet-senior",
-        "collaborates_with": [
-          "hangfire-orchestrator"
-        ],
-        "team_role": "specialist",
-        "active_phases": [
-          "implement"
-        ]
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Email Integration Specialist",
-        "icon": "📧",
-        "spawn_prompt": "You are the Email Integration Specialist (Resend SDK). Implement transactional emails, email templates, notification sending. Follow contract-compliance validator for SDK usage patterns."
-      }
-    },
-    "_comment_tier_3_frontend": "=== TIER 3: FRONTEND SPECIALISTS (3) ===",
-    "blazor-builder": {
-      "tier": 3,
-      "role": "specialist",
-      "title": "Blazor Development Specialist",
-      "domains": [
-        "frontend-blazor"
-      ],
-      "keywords": [
-        "blazor",
-        "razor",
-        "server-side",
-        "component",
-        "fluent ui",
-        "mudblazor",
-        "signalr",
-        "page",
-        "view",
-        "form"
-      ],
-      "always_active": false,
-      "validators": [
-        "architecture",
-        "blazor",
-        "blazor-concurrency",
-        "blazor-state",
-        "css",
-        "design-system"
-      ],
-      "relationships": {
-        "reports_to": "ui-designer",
-        "coordinates": [],
-        "escalates_to": "standards-architect",
-        "collaborates_with": [
-          "ef-modeler",
-          "api-designer",
-          "css-specialist"
-        ],
-        "team_role": "specialist",
-        "active_phases": [
-          "uiux",
-          "tasks",
-          "implement"
-        ]
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-blazor-lifecycle",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-blazor-state",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-blazor-pitfalls",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "backend-database-ef-core",
-          "scope": "implement",
-          "priority": "reference"
-        },
-        {
-          "id": "frontend-blazor-fluent-ui",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Blazor Development Specialist",
-        "icon": "⚡",
-        "spawn_prompt": "You are the Blazor Development Specialist. Build Blazor Server components (Fluent UI or MudBlazor). Follow component-per-file pattern, use @inject for DI, implement loading states and error boundaries. Integrate SignalR for real-time features. Message ef-modeler for data, css-specialist for design system validation."
-      }
-    },
-    "nextjs-expert": {
-      "tier": 3,
-      "role": "specialist",
-      "title": "Next.js Development Specialist",
-      "domains": [
-        "frontend-nextjs"
-      ],
-      "keywords": [
-        "next.js",
-        "nextjs",
-        "react",
-        "tsx",
-        "shadcn",
-        "tailwind",
-        "tanstack",
-        "react-query",
-        "zod",
-        "react-hook-form",
-        "app router",
-        "server component",
-        "client component",
-        "vercel",
-        "neon",
-        "planetscale"
-      ],
-      "always_active": false,
-      "validators": [
-        "nextjs-component"
-      ],
-      "relationships": {
-        "reports_to": "ui-designer",
-        "coordinates": [],
-        "escalates_to": "standards-architect",
-        "collaborates_with": [
-          "api-designer",
-          "css-specialist"
-        ],
-        "team_role": "specialist",
-        "active_phases": [
-          "uiux",
-          "tasks",
-          "implement"
-        ]
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-nextjs-naming-conventions",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-nextjs-project-structure",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-nextjs-app-router",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-nextjs-components",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-nextjs-data-fetching",
-          "scope": "implement",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-nextjs-forms",
-          "scope": "implement",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-nextjs-state-management",
-          "scope": "implement",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-nextjs-testing",
-          "scope": "implement",
-          "priority": "reference"
-        },
-        {
-          "id": "frontend-nextjs-nextjs-patterns",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "infrastructure-vercel-database",
-          "scope": "design",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Next.js Development Specialist",
-        "icon": "⚛️",
-        "spawn_prompt": "You are the Next.js Development Specialist. Build Next.js 14+ applications with shadcn/ui components, TanStack Query for data fetching, Server Actions for mutations. Implement Route Handlers for API routes. Message api-designer for backend endpoints, css-specialist for design system. IMPORTANT: When deployment target is Vercel, database must be serverless (Neon, Supabase/PgBouncer port 6543, PlanetScale) — never a plain TCP connection pool."
-      }
-    },
-    "css-specialist": {
-      "tier": 3,
-      "role": "specialist",
-      "title": "CSS & Design System Specialist",
-      "domains": [
-        "frontend-css"
-      ],
-      "keywords": [
-        "css",
-        "design system",
-        "styling",
-        "theme",
-        "design tokens",
-        "palette"
-      ],
-      "always_active": false,
-      "validators": [
-        "css",
-        "contrast",
-        "design-system"
-      ],
-      "relationships": {
-        "reports_to": "ui-designer",
-        "coordinates": [],
-        "escalates_to": "ui-designer",
-        "collaborates_with": [
-          "blazor-builder",
-          "nextjs-expert"
-        ],
-        "team_role": "specialist",
-        "active_phases": [
-          "implement"
-        ]
-      },
-      "standards": [
-        {
-          "id": "frontend-design-system-naming",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-design-system-animations",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "CSS & Design System Specialist",
-        "icon": "🎨",
-        "spawn_prompt": "You are the CSS & Design System Specialist (FASE 5 only). Validate CSS follows design system (no off-palette colors), review naming conventions (BEM), ensure no inline styles with hardcoded values. Run design-system, css, contrast validators."
-      }
-    },
-    "_comment_tier_3_infra": "=== TIER 3: INFRASTRUCTURE SPECIALISTS (6) ===",
-    "bicep-architect": {
-      "tier": 3,
-      "role": "specialist",
-      "title": "Infrastructure as Code Specialist",
-      "domains": [
-        "infrastructure-iac"
-      ],
-      "keywords": [
-        "bicep",
-        "iac",
-        "infra",
-        "provision",
-        "arm template",
-        "infrastructure as code"
-      ],
-      "always_active": false,
-      "validators": [
-        "architecture"
-      ],
-      "relationships": {
-        "reports_to": "azure-architect",
-        "coordinates": [],
-        "escalates_to": "azure-architect",
-        "collaborates_with": [
-          "devops-engineer",
-          "container-specialist"
-        ],
-        "team_role": "specialist",
-        "active_phases": [
-          "design",
-          "implement"
-        ]
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "infrastructure-azure-azure",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Infrastructure as Code Specialist",
-        "icon": "📜",
-        "spawn_prompt": "You are the Infrastructure as Code Specialist (Bicep). Write main.bicep, modules/*.bicep, parameters.{env}.json. Never create Azure resources manually. Collaborate with azure-architect for resource design, devops-engineer for CI/CD integration."
-      }
-    },
-    "devops-engineer": {
-      "tier": 3,
-      "role": "specialist",
-      "title": "CI/CD Specialist",
-      "domains": [
-        "infrastructure-cicd"
-      ],
-      "keywords": [
-        "pipeline",
-        "ci/cd",
-        "deploy",
-        "release",
-        "github actions",
-        "azure pipelines",
-        "deployment"
-      ],
-      "always_active": false,
-      "validators": [],
-      "relationships": {
-        "reports_to": "infra-architect",
-        "coordinates": [],
-        "escalates_to": "infra-architect",
-        "collaborates_with": [
-          "bicep-architect",
-          "container-specialist"
-        ],
-        "team_role": "specialist",
-        "active_phases": [
-          "implement"
-        ]
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "CI/CD Specialist",
-        "icon": "🚀",
-        "spawn_prompt": "You are the CI/CD Specialist. Build Azure Pipelines or GitHub Actions workflows. Implement Blue-Green, Canary, Rolling deployment strategies. Integrate with bicep-architect for IaC deployment, container-specialist for image builds."
-      }
-    },
-    "container-specialist": {
-      "tier": 3,
-      "role": "specialist",
-      "title": "Containerization Specialist",
-      "domains": [
-        "infrastructure-containers"
-      ],
-      "keywords": [
-        "docker",
-        "container",
-        "containerize",
-        "dockerfile",
-        "multi-stage",
-        "container apps"
-      ],
-      "always_active": false,
-      "validators": [],
-      "relationships": {
-        "reports_to": "infra-architect",
-        "coordinates": [],
-        "escalates_to": "infra-architect",
-        "collaborates_with": [
-          "bicep-architect",
-          "devops-engineer"
-        ],
-        "team_role": "specialist",
-        "active_phases": [
-          "implement"
-        ]
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Containerization Specialist",
-        "icon": "🐳",
-        "spawn_prompt": "You are the Containerization Specialist. Write Dockerfiles (multi-stage builds), .dockerignore. Deploy to Azure Container Apps (scale-to-zero, KEDA scaling). Optimize image size, configure health checks."
-      }
-    },
-    "observability-expert": {
-      "tier": 3,
-      "role": "specialist",
-      "title": "Observability Specialist",
-      "domains": [
-        "infrastructure-observability"
-      ],
-      "keywords": [
-        "monitoring",
-        "logging",
-        "tracing",
-        "metrics",
-        "app insights",
-        "serilog",
-        "opentelemetry",
-        "dashboards",
-        "alerts"
-      ],
-      "always_active": false,
-      "validators": [
-        "observability"
-      ],
-      "relationships": {
-        "reports_to": "infra-architect",
-        "coordinates": [],
-        "escalates_to": "infra-architect",
-        "collaborates_with": [
-          "dotnet-senior",
-          "ms-agent-expert"
-        ],
-        "team_role": "specialist",
-        "active_phases": [
-          "implement"
-        ]
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Observability Specialist",
-        "icon": "📊",
-        "spawn_prompt": "You are the Observability Specialist. Setup Application Insights (connection strings, sampling), configure Serilog (sinks, enrichers), instrument OpenTelemetry (.NET SDK). Create custom metrics, dashboards, alert rules. Write Log Analytics queries (KQL)."
-      }
-    },
-    "azure-identity": {
-      "tier": 3,
-      "role": "specialist",
-      "title": "Microsoft Identity Specialist",
-      "domains": [
-        "infrastructure-identity"
-      ],
-      "keywords": [
-        "identity",
-        "entra",
-        "microsoft auth",
-        "azure ad",
-        "b2c",
-        "passkeys",
-        "webauthn",
-        "managed identity"
-      ],
-      "always_active": false,
-      "validators": [],
-      "relationships": {
-        "reports_to": "infra-architect",
-        "coordinates": [],
-        "escalates_to": "infra-architect",
-        "collaborates_with": [
-          "blazor-builder",
-          "nextjs-expert",
-          "clerk-auth"
-        ],
-        "team_role": "specialist",
-        "active_phases": [
-          "design",
-          "implement"
-        ]
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Microsoft Identity Specialist",
-        "icon": "🔑",
-        "spawn_prompt": "You are the Microsoft Identity Specialist. Implement Azure AD B2C, Entra External ID, Managed Identity for Azure resources. Add WebAuthn/Passkeys support (FIDO2 registration/authentication flows). Collaborate with frontend specialists for UI integration."
-      }
-    },
-    "_comment_tier_3_quality": "=== TIER 3: QUALITY SPECIALISTS (6) ===",
-    "testing-specialist": {
-      "tier": 3,
-      "role": "specialist",
-      "title": "Testing Specialist",
-      "domains": [
-        "quality-testing"
-      ],
-      "keywords": [
-        "test",
-        "testing",
-        "unit",
-        "integration",
-        "e2e",
-        "xunit",
-        "moq",
-        "testcontainers",
-        "bunit"
-      ],
-      "always_active": false,
-      "validators": [],
-      "relationships": {
-        "reports_to": "standards-architect",
-        "coordinates": [],
-        "escalates_to": "standards-architect",
-        "collaborates_with": [
-          "dotnet-senior",
-          "blazor-builder",
-          "nextjs-expert"
-        ],
-        "team_role": "specialist",
-        "active_phases": [
-          "implement"
-        ]
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Testing Specialist",
-        "icon": "🧪",
-        "spawn_prompt": "You are the Testing Specialist. Write unit tests (xUnit, Moq/NSubstitute, FluentAssertions), integration tests (TestContainers, Respawn for DB reset), Blazor component tests (bUnit), HTTP mocking (WireMock). Follow Arrange-Act-Assert (AAA) pattern."
-      }
-    },
-    "code-analyzer": {
-      "tier": 3,
-      "role": "specialist",
-      "title": "Code Quality Analyst",
-      "domains": [
-        "quality-review"
-      ],
-      "keywords": [
-        "analyze",
-        "review",
-        "refactor",
-        "clean code",
-        "smell",
-        "duplicate",
-        "solid",
-        "architecture review"
-      ],
-      "always_active": false,
-      "validators": [],
-      "relationships": {
-        "reports_to": "standards-architect",
-        "coordinates": [],
-        "escalates_to": "standards-architect",
-        "collaborates_with": [
-          "dotnet-senior",
-          "troubleshooting-expert"
-        ],
-        "team_role": "specialist",
-        "active_phases": [
-          "implement"
-        ]
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Code Quality Analyst",
-        "icon": "🔍",
-        "spawn_prompt": "You are the Code Quality Analyst. Review code for architecture violations, clean code principles (naming, complexity, duplication), SOLID principles. Identify code smells, suggest refactorings. Run architecture and packages validators."
-      }
-    },
-    "troubleshooting-expert": {
-      "tier": 3,
-      "role": "specialist",
-      "title": "Troubleshooting & Debug Expert",
-      "domains": [
-        "quality-debug"
-      ],
-      "keywords": [
-        "debug",
-        "troubleshoot",
-        "root cause",
-        "analyze error",
-        "investigate",
-        "diagnose"
-      ],
-      "always_active": false,
-      "validators": [],
-      "relationships": {
-        "reports_to": "standards-architect",
-        "coordinates": [],
-        "escalates_to": "standards-architect",
-        "collaborates_with": [
-          "code-analyzer",
-          "testing-specialist"
-        ],
-        "team_role": "escalation_specialist",
-        "spawn_trigger": "escalation_after_3_failures",
-        "active_phases": [
-          "implement"
-        ]
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Troubleshooting Expert (Escalation)",
-        "icon": "🔧",
-        "spawn_prompt": "You are the Troubleshooting Expert (spawned after 3 failed attempts). Analyze root cause of failures: validation errors, compilation errors, runtime exceptions. Review attempt logs from recovery-tracker. Propose alternative approaches. Message standards-architect with findings."
-      }
-    },
-    "load-testing-expert": {
-      "tier": 3,
-      "role": "specialist",
-      "title": "Load Testing & Performance Specialist",
-      "domains": [
-        "quality-performance"
-      ],
-      "keywords": [
-        "load test",
-        "performance test",
-        "k6",
-        "jmeter",
-        "stress test",
-        "capacity planning",
-        "bottleneck",
-        "scalability",
-        "concurrent users"
-      ],
-      "always_active": false,
-      "validators": [
-        "performance"
-      ],
-      "relationships": {
-        "reports_to": "standards-architect",
-        "coordinates": [],
-        "escalates_to": "standards-architect",
-        "collaborates_with": [
-          "infra-architect",
-          "observability-expert"
-        ],
-        "team_role": "specialist",
-        "active_phases": [
-          "implement"
-        ]
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Load Testing Specialist",
-        "icon": "📈",
-        "spawn_prompt": "You are the Load Testing Specialist. Write k6 scripts (stress test, spike test, soak test), JMeter test plans. Analyze bottlenecks (DB, CPU, memory). Recommend capacity planning (how many users system supports). Collaborate with observability-expert for metrics."
-      }
-    },
-    "documentation-specialist": {
-      "tier": 3,
-      "role": "specialist",
-      "title": "Documentation Specialist",
-      "domains": [
-        "developer-experience-docs"
-      ],
-      "keywords": [
-        "readme",
-        "documentation",
-        "api docs",
-        "contributing",
-        "deployment guide",
-        "onboarding"
-      ],
-      "always_active": false,
-      "validators": [],
-      "relationships": {
-        "reports_to": "standards-architect",
-        "coordinates": [],
-        "escalates_to": "standards-architect",
-        "collaborates_with": [
-          "api-designer",
-          "devops-engineer"
-        ],
-        "team_role": "post_implementation",
-        "spawn_trigger": "post_fase_5",
-        "active_phases": [
-          "implement"
-        ]
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Documentation Specialist (Post-FASE 5)",
-        "icon": "📝",
-        "spawn_prompt": "You are the Documentation Specialist (runs after FASE 5). Generate README.md (how to run project), CONTRIBUTING.md (contributor guide), API documentation (Swagger annotations, markdown docs), deployment guides (infra setup). Update existing docs with new features."
-      }
-    },
-    "vsa-architect": {
-      "tier": 3,
-      "role": "specialist",
-      "title": "Vertical Slice Architecture Specialist",
-      "domains": [
-        "architecture",
-        "backend"
-      ],
-      "keywords": [
-        "vertical slice",
-        "vertical-slice",
-        "vsa",
-        "minimal api",
-        "minimal apis",
-        "ihandler",
-        "result pattern",
-        "feature slice",
-        "scrutor",
-        "vertical slice architecture"
-      ],
-      "always_active": false,
-      "active_phases": [
-        "design",
-        "implement"
-      ],
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "architecture-vertical-slice-vertical-slice",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "VSA Architecture Specialist",
-        "icon": "🍕",
-        "spawn_prompt": "Você é o VSA Specialist. Analise a proposta e produza um VSA Blueprint:\n1. ENTITY FIELDS: todos os campos com tipos C# corretos (sem AggregateRoot, sem Value Objects)\n2. OPERATIONS: slices necessários (Create, GetAll, GetById, Update, Delete + operações customizadas)\n3. ROUTES: HTTP method + rota por operação (ex: POST /api/products, GET /api/products/{id:guid})\n4. ERROR TYPES: Error factory methods para {Entity}Errors (apenas NotFound e casos específicos)\n5. VALIDATION RULES: regras FluentValidation por campo por operação\n\nNão use AggregateRoot, DomainEvent, CQRS formal, MediatR, Application Service layer.\nCada operação é um slice autônomo: Request + Response + Handler + Validator + Endpoint.\nRef: framework/standards/architecture/vertical-slice/vertical-slice.md"
-      }
-    },
-    "_comment_tier_3_nodejs": "=== TIER 3: NODEJS/CLI SPECIALISTS (2) ===",
-    "morph-spec-architect": {
-      "tier": 3,
-      "role": "specialist",
-      "title": "Morph-Spec Architect",
-      "domains": [
-        "cli",
-        "framework-design",
-        "nodejs",
-        "architecture"
-      ],
-      "keywords": [
-        "morph-spec",
-        "framework feature",
-        "new command",
-        "cli architecture",
-        "plugin",
-        "hook design"
-      ],
-      "negativeKeywords": [
-        "blazor",
-        "dotnet",
-        "react",
-        "frontend"
-      ],
-      "always_active": false,
-      "validators": [],
-      "relationships": {
-        "reports_to": "feature-lead",
-        "coordinates": [
-          "nodejs-cli-expert",
-          "morph-spec-validator"
-        ],
-        "active_phases": [
-          "design",
-          "tasks"
-        ]
-      },
-      "standards": [],
-      "teammate": {
-        "role": "specialist",
-        "icon": "🔧",
-        "spawn_prompt": "You are the Morph-Spec Architect. You deeply understand the morph-spec-framework codebase: its 4-tier agent hierarchy, state machine (with filesystem-based phase derivation), Commander.js CLI surface (~25 commands registered in bin/morph-spec.js), hooks system, skills system, and the .morph/ directory layout. Your job is to design new features that fit naturally into the existing architecture. Before proposing implementation, always: (1) identify which existing modules can be reused, (2) determine where the new command should live in src/commands/, (3) define the state impact (does it need new state fields?), (4) list which tests need to be written. Follow ESM module patterns throughout."
-      }
-    },
-    "nodejs-cli-expert": {
-      "tier": 3,
-      "role": "specialist",
-      "title": "Node.js CLI Expert",
-      "domains": [
-        "nodejs",
-        "cli",
-        "javascript",
-        "esm",
-        "testing"
-      ],
-      "keywords": [
-        "nodejs",
-        "javascript",
-        "esm",
-        "commander",
-        "node --test",
-        "cli command",
-        "morph-spec implementation"
-      ],
-      "negativeKeywords": [
-        "blazor",
-        "dotnet",
-        "react",
-        "typescript"
-      ],
-      "always_active": false,
-      "validators": [],
-      "relationships": {
-        "reports_to": "feature-lead",
-        "coordinates": [
-          "morph-spec-architect"
-        ],
-        "escalates_to": "morph-spec-validator",
-        "active_phases": [
-          "implement"
-        ]
-      },
-      "standards": [],
-      "teammate": {
-        "role": "specialist",
-        "icon": "🟢",
-        "spawn_prompt": "You are the Node.js CLI Expert for the morph-spec-framework. You implement features in Node.js ESM following the project's conventions: (1) All imports use ESM syntax with .js extensions on relative paths; (2) Commands are registered in bin/morph-spec.js after being defined in src/commands/<domain>/<command>.js; (3) Tests use native node:test runner with mock.fn() for mocking — no external test libraries; (4) Error handling: hooks are fail-open (catch+exit 0), CLI commands exit(1) on fatal errors; (5) Never use require() or module.exports. When implementing a feature, always write the tests alongside the implementation. The test command is: node --test --test-concurrency=1"
-      }
-    },
-    "_comment_tier_4": "=== TIER 4: VALIDATORS (6) ===",
-    "security-expert": {
-      "tier": 4,
-      "role": "validator",
-      "title": "Security Validator",
-      "domains": [
-        "security"
-      ],
-      "keywords": [
-        "sql injection",
-        "xss",
-        "secrets",
-        "security scan",
-        "vulnerability",
-        "csrf",
-        "insecure deserialization"
-      ],
-      "always_active": true,
-      "validators": [
-        "security"
-      ],
-      "relationships": {
-        "reports_to": "standards-architect",
-        "coordinates": [],
-        "runs_in": "hooks",
-        "hook_triggers": [
-          "TeammateIdle",
-          "TaskCompleted"
-        ],
-        "team_role": "validator"
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "icon": "🛡️",
-        "role": "Security Validator (read-only)",
-        "spawn_prompt": "You are the Security Validator (Tier 4, READ-ONLY). Scan ALL source files (.cs, .razor, .tsx, .ts, .js) in the project for security vulnerabilities:\n\n1. SQL injection — string concatenation in queries (look for $\"...{var}...\" inside SQL/EF raw queries)\n2. Hardcoded secrets — API keys, passwords, connection strings in source code (not in appsettings)\n3. XSS — @Html.Raw usage in Razor/Blazor without sanitization\n4. Insecure deserialization — BinaryFormatter usage\n5. CSRF — POST forms/endpoints missing anti-forgery tokens ([ValidateAntiForgeryToken] or @Html.AntiForgeryToken)\n\nUse Grep and Glob to scan. Do NOT modify any files.\n\nOutput a JSON object: { \"passed\": boolean, \"issues\": [{ \"file\": string, \"line\": number, \"message\": string, \"severity\": \"error\" }] }"
-      },
-      "hook_behavior": {
-        "validates": [
-          "SQL injection (string concatenation in queries)",
-          "Hardcoded secrets (API keys, passwords, connection strings)",
-          "XSS (@Html.Raw usage in Razor/Blazor)",
-          "Insecure deserialization (BinaryFormatter)",
-          "CSRF (missing anti-forgery tokens)"
-        ],
-        "severity": "error",
-        "blocks_on_fail": true
-      }
-    },
-    "architecture-expert": {
-      "tier": 4,
-      "role": "validator",
-      "title": "Architecture Validator",
-      "domains": [
-        "architecture"
-      ],
-      "keywords": [
-        "architecture",
-        "clean code",
-        "solid",
-        "dependency injection"
-      ],
-      "always_active": true,
-      "validators": [
-        "architecture"
-      ],
-      "relationships": {
-        "reports_to": "standards-architect",
-        "coordinates": [],
-        "runs_in": "hooks",
-        "hook_triggers": [
-          "TeammateIdle",
-          "TaskCompleted"
-        ],
-        "team_role": "validator"
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "icon": "🏗️",
-        "role": "Architecture Validator (read-only)",
-        "spawn_prompt": "You are the Architecture Validator (Tier 4, READ-ONLY). Scan the project for architectural violations:\n\n1. DbContext injection — look for direct DbContext injection instead of IDbContextFactory in Blazor components (.razor, .razor.cs)\n2. Async/await anti-patterns — search for .Result, .Wait(), .GetAwaiter().GetResult() in async code\n3. DI registration order — in Program.cs, verify services are registered before middleware (app.Use*/Map*)\n4. Blazor render mode — verify InteractiveServer/InteractiveWebAssembly components don't use incompatible patterns\n5. Layer violations — Domain/Application projects must not reference Infrastructure or Web projects\n\nUse Grep and Glob to scan. Do NOT modify any files.\n\nOutput a JSON object: { \"passed\": boolean, \"issues\": [{ \"file\": string, \"line\": number, \"message\": string, \"severity\": \"error\" }] }"
-      },
-      "hook_behavior": {
-        "validates": [
-          "DbContext injection (IDbContextFactory required)",
-          "Async/await patterns (no .Result or .Wait)",
-          "DI registration order (services before middleware)",
-          "Blazor render mode compatibility"
-        ],
-        "severity": "error",
-        "blocks_on_fail": true
-      }
-    },
-    "packages-validator": {
-      "tier": 4,
-      "role": "validator",
-      "title": "Packages Validator",
-      "domains": [
-        "packages"
-      ],
-      "keywords": [
-        "nuget",
-        "packages",
-        "dependencies",
-        "version conflict"
-      ],
-      "always_active": true,
-      "validators": [
-        "packages"
-      ],
-      "relationships": {
-        "reports_to": "standards-architect",
-        "coordinates": [],
-        "runs_in": "hooks",
-        "hook_triggers": [
-          "TaskCompleted"
-        ],
-        "team_role": "validator"
-      },
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "icon": "📦",
-        "role": "Packages Validator (read-only)",
-        "spawn_prompt": "You are the Packages Validator (Tier 4, READ-ONLY). Scan all project files for package issues:\n\n1. NuGet version conflicts — search *.csproj files for the same PackageReference appearing with different versions across projects\n2. Incompatible .NET 10 packages — check that major package versions are compatible with the target framework\n3. Security vulnerabilities — look for known outdated packages (Newtonsoft.Json < 13.0.1, System.Text.Json < 8.0.5, etc.)\n4. For npm projects: check package.json for duplicate dependencies, outdated major versions\n\nUse Grep and Glob to scan. Do NOT modify any files.\n\nOutput a JSON object: { \"passed\": boolean, \"issues\": [{ \"file\": string, \"message\": string, \"severity\": \"error\" }] }"
-      },
-      "hook_behavior": {
-        "validates": [
-          "NuGet version conflicts (same package, different versions)",
-          "Incompatible .NET 10 packages",
-          "Security vulnerabilities (outdated packages)"
-        ],
-        "severity": "error",
-        "blocks_on_fail": true
-      }
-    },
-    "design-system-validator": {
-      "tier": 4,
-      "role": "validator",
-      "title": "Design System Validator",
-      "domains": [
-        "design-system"
-      ],
-      "keywords": [
-        "design system",
-        "css",
-        "color palette",
-        "spacing"
-      ],
-      "always_active": true,
-      "validators": [
-        "design-system"
-      ],
-      "relationships": {
-        "reports_to": "ui-designer",
-        "coordinates": [],
-        "runs_in": "hooks",
-        "hook_triggers": [
-          "TeammateIdle"
-        ],
-        "team_role": "validator"
-      },
-      "standards": [
-        {
-          "id": "frontend-design-system-naming",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-design-system-animations",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "icon": "🎨",
-        "role": "Design System Validator (read-only)",
-        "spawn_prompt": "You are the Design System Validator (Tier 4, READ-ONLY). Scan CSS/SCSS and component files for design system compliance:\n\n1. Color palette — look for hardcoded hex/rgb colors instead of CSS variables (var(--color-primary), var(--color-secondary), etc.)\n2. Spacing — look for hardcoded px/rem values instead of spacing variables (var(--spacing-*))\n3. Typography — look for hardcoded font-size/font-family instead of typography variables (var(--font-*))\n4. Component naming — verify PascalCase for Blazor components (.razor) and kebab-case for CSS classes\n5. Check .morph/context/design-system.md if it exists for project-specific design tokens\n\nUse Grep and Glob to scan. Do NOT modify any files.\n\nOutput a JSON object: { \"passed\": boolean, \"issues\": [{ \"file\": string, \"line\": number, \"message\": string, \"severity\": \"warning\" }] }"
-      },
-      "hook_behavior": {
-        "validates": [
-          "CSS color palette compliance (primary, secondary, accent)",
-          "Spacing values (use var(--spacing-*))",
-          "Typography scale (use var(--font-*))",
-          "Component naming (PascalCase for Blazor, kebab-case for CSS)"
-        ],
-        "severity": "warning",
-        "blocks_on_fail": false
-      }
-    },
-    "blazor-concurrency-validator": {
-      "tier": 4,
-      "role": "validator",
-      "title": "Blazor Concurrency Validator",
-      "stacks": ["blazor"],
-      "domains": [
-        "blazor-concurrency"
-      ],
-      "keywords": [
-        "blazor",
-        "dbcontext",
-        "lifecycle",
-        "async",
-        "concurrency"
-      ],
-      "always_active": false,
-      "validators": [
-        "blazor-concurrency"
-      ],
-      "relationships": {
-        "reports_to": "blazor-builder",
-        "coordinates": [],
-        "runs_in": "hooks",
-        "hook_triggers": [
-          "TaskCompleted"
-        ],
-        "team_role": "validator"
-      },
-      "standards": [
-        {
-          "id": "frontend-blazor-lifecycle",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-blazor-pitfalls",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-blazor-state",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "icon": "⚡",
-        "role": "Blazor Concurrency Validator (read-only)",
-        "spawn_prompt": "You are the Blazor Concurrency Validator (Tier 4, READ-ONLY). Scan all Blazor component files (.razor, .razor.cs) for concurrency and lifecycle violations:\n\n1. DbContext lifecycle — look for injected DbContext (not IDbContextFactory), disposed context usage, scope issues\n2. Async void — search for 'async void' methods (must be 'async Task' except event handlers)\n3. JSInterop in OnInitialized — look for IJSRuntime calls in OnInitialized/OnInitializedAsync (must be in OnAfterRender/OnAfterRenderAsync)\n4. State mutation — look for property changes without calling StateHasChanged() or InvokeAsync(StateHasChanged)\n5. Thread safety — look for shared mutable state without synchronization in Blazor Server components\n\nUse Grep and Glob to scan. Do NOT modify any files.\n\nOutput a JSON object: { \"passed\": boolean, \"issues\": [{ \"file\": string, \"line\": number, \"message\": string, \"severity\": \"error\" }] }"
-      },
-      "hook_behavior": {
-        "validates": [
-          "DbContext lifecycle violations (dispose, scope issues)",
-          "Async void methods (use async Task instead)",
-          "JSInterop in OnInitialized (move to OnAfterRender)",
-          "State mutation without StateHasChanged"
-        ],
-        "severity": "error",
-        "blocks_on_fail": true
-      }
-    },
-    "morph-spec-validator": {
-      "tier": 4,
-      "role": "validator",
-      "title": "Morph-Spec Validator",
-      "domains": [
-        "nodejs",
-        "cli",
-        "testing",
-        "validation"
-      ],
-      "keywords": [
-        "validate morph-spec",
-        "node.js validation",
-        "cli test"
-      ],
-      "always_active": false,
-      "validators": [
-        "morph-spec-standards"
-      ],
-      "relationships": {
-        "reports_to": "qa-lead",
-        "runs_in": "post-implement",
-        "active_phases": [
-          "implement",
-          "validate"
-        ]
-      },
-      "standards": [],
-      "teammate": {
-        "icon": "🔬",
-        "role": "Morph-Spec Validator (read-only)",
-        "tools": "Read, Glob, Grep, Bash",
-        "maxTurns": 12,
-        "spawn_prompt": "You are the Morph-Spec Validator (Tier 4, READ-ONLY). Scan the morph-spec framework codebase for standards compliance:\n\n1. ESM imports — all relative imports must use .js extensions (e.g., './foo.js' not './foo')\n2. Command registration — new commands in src/commands/ must be imported and registered in bin/morph-spec.js\n3. Test coverage — each module in src/ should have a corresponding test file in tests/\n4. No CommonJS — search for require() or module.exports (must use import/export)\n5. Hook fail-open — all hooks in framework/hooks/ must have try/catch with exit(0) fallback\n6. Run 'npm test' to verify all tests pass\n\nUse Grep, Glob, and Bash to scan. Do NOT modify any files.\n\nOutput a JSON object: { \"passed\": boolean, \"issues\": [{ \"file\": string, \"line\": number, \"message\": string, \"severity\": \"error\" }] }"
-      },
-      "hook_behavior": {
-        "validates": [
-          "ESM imports use .js extensions on relative paths",
-          "New commands are registered in bin/morph-spec.js",
-          "Tests exist for new modules (one test file per module)",
-          "npm test passes with no failures",
-          "No require() or module.exports used",
-          "Error handling follows fail-open pattern for hooks"
-        ],
-        "severity": "error",
-        "blocks_on_fail": true
-      }
-    },
-    "nextjs-component-validator": {
-      "tier": 4,
-      "stacks": ["nextjs"],
-      "title": "Next.js Component Validator",
-      "description": "Tier-4 validator for Next.js Server/Client component patterns",
-      "keywords": [
-        "nextjs",
-        "tsx",
-        "use client",
-        "server component",
-        "app router"
-      ],
-      "validators": [
-        "nextjs-component"
-      ],
-      "always_active": false,
-      "hook_behavior": {
-        "severity": "warning",
-        "blocks_on_fail": false,
-        "validates": [
-          "use-client directive",
-          "hook usage",
-          "file naming"
-        ]
-      },
-      "teammate": {
-        "icon": "⚛️",
-        "role": "Next.js Component Validator (read-only)",
-        "spawn_prompt": "You are the Next.js Component Validator (Tier 4, READ-ONLY). Scan all .tsx/.ts files under src/ and validate:\n\n1. \"use client\" directive — must be present when React hooks (useState, useEffect, etc.) are used\n2. Server Components — \"use client\" must be absent for pure Server Components (no hooks, no event handlers)\n3. File naming — component files must use kebab-case naming convention\n4. Import patterns — client components should not import server-only modules\n\nUse Grep and Glob to scan. Do NOT modify any files.\n\nOutput a JSON object: { \"passed\": boolean, \"issues\": [{ \"file\": string, \"message\": string, \"suggestion\": string, \"severity\": \"warning\" }] }"
-      }
-    }
-  },
-  "squads": {
-    "backend_squad": {
-      "leader": "dotnet-senior",
-      "members": [
-        "ef-modeler",
-        "event-architect",
-        "api-designer",
-        "nosql-cache-expert",
-        "hangfire-orchestrator",
-        "ms-agent-expert",
-        "supabase-expert",
-        "vector-search-expert",
-        "context-optimizer",
-        "asaas-financial",
-        "clerk-auth",
-        "resend-email"
-      ],
-      "domains": [
-        "backend",
-        "backend-data",
-        "backend-events",
-        "backend-api",
-        "backend-nosql",
-        "backend-ddd",
-        "backend-jobs",
-        "ai-agents",
-        "backend-supabase",
-        "ai-vector",
-        "ai-context",
-        "integration-payment",
-        "integration-auth",
-        "integration-email"
-      ]
-    },
-    "frontend_squad": {
-      "leader": "ui-designer",
-      "members": [
-        "blazor-builder",
-        "nextjs-expert",
-        "css-specialist"
-      ],
-      "domains": [
-        "frontend-design",
-        "frontend-blazor",
-        "frontend-nextjs",
-        "frontend-css"
-      ],
-      "active_phases": {
-        "design": [
-          "ui-designer"
-        ],
-        "implement": [
-          "blazor-builder",
-          "nextjs-expert",
-          "css-specialist"
-        ]
-      }
-    },
-    "infrastructure_squad": {
-      "leader": "infra-architect",
-      "members": [
-        "bicep-architect",
-        "devops-engineer",
-        "container-specialist",
-        "observability-expert",
-        "azure-identity"
-      ],
-      "domains": [
-        "infrastructure",
-        "infrastructure-iac",
-        "infrastructure-cicd",
-        "infrastructure-containers",
-        "infrastructure-observability",
-        "infrastructure-identity"
-      ]
-    },
-    "quality_squad": {
-      "leader": "standards-architect",
-      "members": [
-        "testing-specialist",
-        "code-analyzer",
-        "troubleshooting-expert",
-        "load-testing-expert",
-        "documentation-specialist"
-      ],
-      "domains": [
-        "quality-testing",
-        "quality-review",
-        "quality-debug",
-        "quality-performance",
-        "developer-experience-docs"
-      ],
-      "note": "No permanent leader — standards-architect coordinates directly"
-    }
-  },
-  "relationship_types": {
-    "reports_to": "Hierarchical manager relationship",
-    "coordinates": "Manages/leads these agents",
-    "escalates_to": "Where to escalate unresolved issues",
-    "collaborates_with": "Peer agents for cross-domain work",
-    "runs_in": "Execution context (hooks, not teammates)",
-    "team_role": "Role in Agent Teams (lead, domain_leader, specialist, validator, escalation_specialist, post_implementation, planning_only)"
-  }
-}
+{
+  "$schema": "./agent-schema.json",
+  "version": "4.0.0",
+  "total_agents": 46,
+  "tiers": {
+    "tier_1_orchestrators": 3,
+    "tier_2_leaders": 4,
+    "tier_3_specialists": 31,
+    "tier_4_validators": 7
+  },
+  "agents": {
+    "standards-architect": {
+      "tier": 1,
+      "title": "Chief Architect",
+      "group": "domain-analysis",
+      "active_phases": [
+        "*"
+      ],
+      "reports_to": "user",
+      "domains": [
+        "architecture",
+        "developer-experience"
+      ],
+      "keywords": [],
+      "validators": [],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "core-architecture",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "backend-dotnet-program-cs-checklist",
+          "scope": "implement",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "Team Lead (Delegate Mode)",
+        "icon": "🎯",
+        "spawn_prompt": "You are the Chief Architect and Team Lead in delegate mode. Coordinate Domain Leaders, resolve conflicts, synthesize results. DO NOT implement code yourself. Escalate conflicts to user when teammates disagree on architecture/tech choices."
+      }
+    },
+    "ai-system-architect": {
+      "tier": 1,
+      "title": "AI/Agent Architect",
+      "group": "domain-analysis",
+      "active_phases": [
+        "design",
+        "tasks"
+      ],
+      "reports_to": "standards-architect",
+      "domains": [
+        "ai-orchestration",
+        "architecture"
+      ],
+      "keywords": [
+        "agent system",
+        "ai architecture",
+        "orchestration",
+        "multi-agent",
+        "agent workflow"
+      ],
+      "validators": [],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "core-architecture",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "ai-agents-setup",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "ai-agents-workflows",
+          "scope": "design",
+          "priority": "required"
+        },
+        {
+          "id": "ai-agents-production",
+          "scope": "implement",
+          "priority": "required"
+        },
+        {
+          "id": "ai-agents-blazor-ui",
+          "scope": "implement",
+          "priority": "reference"
+        }
+      ],
+      "teammate": {
+        "role": "AI Architect",
+        "icon": "🤖",
+        "spawn_prompt": "You are the AI/Agent System Architect. Design agent workflows, tool integrations, and orchestration patterns."
+      }
+    },
+    "popm-advisor": {
+      "tier": 1,
+      "title": "Product/Project Advisor",
+      "group": "domain-analysis",
+      "active_phases": [
+        "proposal",
+        "setup",
+        "design"
+      ],
+      "reports_to": "user",
+      "domains": [
+        "requirements",
+        "business-value"
+      ],
+      "keywords": [
+        "unclear",
+        "requirements",
+        "priority",
+        "roi",
+        "business value",
+        "user story"
+      ],
+      "validators": [],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "core-architecture",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": null
+    },
+    "dotnet-senior": {
+      "tier": 2,
+      "title": "Backend Squad Leader",
+      "group": "backend",
+      "active_phases": [
+        "*"
+      ],
+      "reports_to": "standards-architect",
+      "domains": [
+        "backend"
+      ],
+      "keywords": [
+        "backend",
+        "api",
+        "dotnet",
+        ".net",
+        "csharp",
+        "c#",
+        "web api",
+        "minimal api"
+      ],
+      "validators": [
+        "architecture",
+        "packages"
+      ],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "core-architecture",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "backend-dotnet-core",
+          "scope": "implement",
+          "priority": "required"
+        },
+        {
+          "id": "backend-dotnet-program-cs-checklist",
+          "scope": "implement",
+          "priority": "required"
+        }
+      ],
+      "stacks": [
+        "dotnet",
+        "blazor"
+      ],
+      "teammate": {
+        "role": "Backend Squad Leader",
+        "icon": "⚙️",
+        "spawn_prompt": "You are the Backend Squad Leader. Coordinate backend specialists (ef-modeler, event-architect, api-designer, etc.). Assign tasks, review designs, enforce backend standards. Escalate cross-domain conflicts to standards-architect."
+      }
+    },
+    "infra-architect": {
+      "tier": 2,
+      "title": "Infrastructure Squad Leader",
+      "group": "infra",
+      "active_phases": [
+        "*"
+      ],
+      "reports_to": "standards-architect",
+      "domains": [
+        "infrastructure"
+      ],
+      "keywords": [
+        "infrastructure",
+        "infra",
+        "cloud",
+        "deployment",
+        "hosting",
+        "ci/cd",
+        "container",
+        "iac",
+        "pipeline",
+        "vercel",
+        "neon",
+        "planetscale",
+        "serverless database",
+        "serverless postgres"
+      ],
+      "validators": [],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "core-architecture",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "infrastructure-vercel-database",
+          "scope": "design",
+          "priority": "required"
+        }
+      ],
+      "stacks": [
+        "azure",
+        "docker"
+      ],
+      "teammate": {
+        "role": "Infrastructure Squad Leader",
+        "icon": "🏗️",
+        "spawn_prompt": "You are the Infrastructure Squad Leader. Coordinate infra specialists regardless of cloud provider (azure-architect, devops-engineer, container-specialist, observability-expert). Focus on IaC, CI/CD, containerization, cost optimization. Delegate to azure-architect for Azure-specific work. IMPORTANT: When deployment target is Vercel, ALWAYS enforce serverless database (Neon, Supabase/PgBouncer, PlanetScale) — never TCP connection pools. Escalate to standards-architect on conflicts."
+      }
+    },
+    "azure-architect": {
+      "tier": 3,
+      "title": "Azure Infrastructure Specialist",
+      "group": "infra",
+      "active_phases": [
+        "design",
+        "implement"
+      ],
+      "reports_to": "infra-architect",
+      "domains": [
+        "infrastructure"
+      ],
+      "keywords": [
+        "azure",
+        "bicep",
+        "arm template",
+        "azure resources",
+        "container apps",
+        "azure sql",
+        "key vault",
+        "app insights"
+      ],
+      "validators": [
+        "architecture"
+      ],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "core-architecture",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "infrastructure-azure-azure",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "Infrastructure Squad Leader",
+        "icon": "☁️",
+        "spawn_prompt": "You are the Azure Infrastructure Specialist (tier-3). Focus exclusively on Azure resources, Bicep IaC templates, Azure cost optimization, and zero-portal policy. Report to infra-architect."
+      }
+    },
+    "ui-designer": {
+      "tier": 2,
+      "title": "UI/UX Squad Leader",
+      "group": "frontend",
+      "active_phases": [
+        "uiux"
+      ],
+      "reports_to": "standards-architect",
+      "domains": [
+        "frontend-design"
+      ],
+      "keywords": [
+        "wireframe",
+        "mockup",
+        "user flow",
+        "ux",
+        "design",
+        "interface design",
+        "user experience",
+        "page",
+        "dashboard",
+        "form",
+        "UI",
+        "settings",
+        "interface",
+        "screen",
+        "panel",
+        "portal",
+        "view"
+      ],
+      "validators": [
+        "design-system",
+        "contrast"
+      ],
+      "standards": [
+        {
+          "id": "frontend-blazor-fluent-ui",
+          "scope": "uiux",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-design-system-naming",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-design-system-animations",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "UI/UX Squad Leader (FASE 1.5)",
+        "icon": "🎨",
+        "spawn_prompt": "You are the UI/UX Squad Leader for FASE 1.5. Create wireframes, mockups, user flows. Define design system (colors, typography, spacing). Work is AGNOSTIC (no implementation code). Apply modern design trends (glassmorphism, gradients, soft shadows, micro-interactions). Guide Fluent UI vs MudBlazor selection. Enforce WCAG AA accessibility (4.5:1 contrast, focus visible, ARIA)."
+      }
+    },
+    "ef-modeler": {
+      "tier": 3,
+      "title": "Data Persistence Specialist (Relational)",
+      "group": "backend",
+      "active_phases": [
+        "design",
+        "implement"
+      ],
+      "reports_to": "dotnet-senior",
+      "domains": [
+        "backend-data"
+      ],
+      "keywords": [
+        "entity",
+        "database",
+        "migration",
+        "ef core",
+        "entity framework",
+        "sql",
+        "dbcontext"
+      ],
+      "validators": [
+        "architecture",
+        "blazor-concurrency"
+      ],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "backend-database-ef-core",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "backend-dotnet-core",
+          "scope": "implement",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "Data Persistence Specialist",
+        "icon": "🗄️",
+        "spawn_prompt": "You are the Data Persistence Specialist (EF Core). Focus on Models/, Migrations/, DbContext. Follow blazor-efcore.md standards. Use IDbContextFactory for background ops. Message blazor-builder when entities ready for UI binding."
+      }
+    },
+    "event-architect": {
+      "tier": 3,
+      "title": "Event-Driven Architecture Specialist",
+      "group": "backend",
+      "active_phases": [
+        "design",
+        "implement"
+      ],
+      "reports_to": "dotnet-senior",
+      "domains": [
+        "backend-events"
+      ],
+      "keywords": [
+        "event",
+        "service bus",
+        "rabbitmq",
+        "cqrs",
+        "event sourcing",
+        "messaging",
+        "pub/sub",
+        "domain events",
+        "saga",
+        "real-time",
+        "realtime",
+        "websocket",
+        "live updates"
+      ],
+      "validators": [
+        "architecture",
+        "event-driven"
+      ],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "core-architecture",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "Event-Driven Architecture Specialist",
+        "icon": "📨",
+        "spawn_prompt": "You are the Event-Driven Architecture Specialist. Implement Azure Service Bus queues/topics, CQRS patterns, Event Sourcing, Domain Events. Design idempotent handlers, dead letter queues, saga patterns."
+      }
+    },
+    "api-designer": {
+      "tier": 3,
+      "title": "API Design Specialist",
+      "group": "backend",
+      "active_phases": [
+        "design",
+        "implement"
+      ],
+      "reports_to": "dotnet-senior",
+      "domains": [
+        "backend-api"
+      ],
+      "keywords": [
+        "rest",
+        "graphql",
+        "grpc",
+        "api",
+        "openapi",
+        "swagger",
+        "versioning",
+        "rate limiting",
+        "hot chocolate",
+        "endpoint"
+      ],
+      "validators": [],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "core-architecture",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "API Design Specialist",
+        "icon": "🔌",
+        "spawn_prompt": "You are the API Design Specialist. Design REST APIs (resource naming, HTTP verbs, status codes), GraphQL schemas with Hot Chocolate, gRPC .proto files. Add OpenAPI/Swagger annotations. Implement API versioning, rate limiting. Review with frontend specialists."
+      }
+    },
+    "nosql-cache-expert": {
+      "tier": 3,
+      "title": "NoSQL & Cache Specialist",
+      "group": "backend",
+      "active_phases": [
+        "design",
+        "implement"
+      ],
+      "reports_to": "dotnet-senior",
+      "domains": [
+        "backend-nosql"
+      ],
+      "keywords": [
+        "cosmos",
+        "cosmosdb",
+        "redis",
+        "cache",
+        "blob storage",
+        "nosql",
+        "document db",
+        "key-value",
+        "azure storage"
+      ],
+      "validators": [],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "core-architecture",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "NoSQL & Cache Specialist",
+        "icon": "💾",
+        "spawn_prompt": "You are the NoSQL & Cache Specialist. Implement Azure Cosmos DB (SQL API, partition keys, RUs), Redis Cache (cache-aside, read-through, write-behind), Blob Storage (hot/cool/archive tiers). Design cache invalidation strategies."
+      }
+    },
+    "domain-architect": {
+      "tier": 2,
+      "title": "Domain Modeling Leader",
+      "group": "domain-analysis",
+      "active_phases": [
+        "design",
+        "implement"
+      ],
+      "reports_to": "standards-architect",
+      "domains": [
+        "backend-ddd"
+      ],
+      "keywords": [
+        "ddd",
+        "domain driven design",
+        "aggregate",
+        "aggregate root",
+        "entity",
+        "value object",
+        "domain event",
+        "bounded context",
+        "ubiquitous language",
+        "domain modeling",
+        "aggregateroot",
+        "domainevents",
+        "integration event"
+      ],
+      "validators": [
+        "architecture"
+      ],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "core-architecture",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "architecture-ddd-complexity-levels",
+          "scope": "design",
+          "priority": "required"
+        },
+        {
+          "id": "architecture-ddd-aggregates",
+          "scope": "design",
+          "priority": "required"
+        },
+        {
+          "id": "architecture-ddd-entities",
+          "scope": "design",
+          "priority": "required"
+        },
+        {
+          "id": "architecture-ddd-value-objects",
+          "scope": "design",
+          "priority": "required"
+        },
+        {
+          "id": "architecture-ddd-bounded-contexts",
+          "scope": "design",
+          "priority": "required"
+        },
+        {
+          "id": "architecture-ddd-ubiquitous-language",
+          "scope": "design",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "Domain Modeling Leader",
+        "icon": "📐",
+        "spawn_prompt": "You are the Domain Modeling Leader for MORPH-SPEC. Your primary responsibility is detecting the correct domain complexity level and producing the Aggregate Blueprint before any contracts are generated.\n\nALWAYS start with the 5-question complexity detection:\n1. Does the main entity have state transitions? (Draft → Confirmed → Shipped) → Yes = Level 2+\n2. Are there business invariants? (\"can only cancel if Active\") → Yes = Level 2+\n3. Are there derived calculations? (Total, Balance, Discount) → Yes = Level 2+\n4. Do other modules need to react to changes? (Domain Events with consumers) → Yes = Level 2+\n5. Did the user explicitly declare a Bounded Context? Or are there 3+ domains with conflicting models? → Yes = Level 3\nIf none of the above: Level 1 (CRUD)\n\nFor Level 1: Use contracts-level1.cs template. No AggregateRoot, no Domain Events.\nFor Level 2: Use contracts-level2.cs template. Design AggregateRoot with factory methods, invariants, Value Objects, Domain Events.\nFor Level 3: Use contracts-level3.cs template. Add BOUNDED_CONTEXT namespace, Integration Events, cross-BC ID references only.\n\nDocument in spec.md under ## Domain Complexity and ## Aggregate Blueprint (Level 2+).\nCoordinate ef-modeler for persistence design and event-architect for Domain Event patterns.\nRef: framework/standards/architecture/ddd/complexity-levels.md"
+      }
+    },
+    "hangfire-orchestrator": {
+      "tier": 3,
+      "title": "Background Jobs Specialist",
+      "group": "backend",
+      "active_phases": [
+        "implement"
+      ],
+      "reports_to": "dotnet-senior",
+      "domains": [
+        "backend-jobs"
+      ],
+      "keywords": [
+        "scheduled",
+        "job",
+        "background",
+        "cron",
+        "hangfire",
+        "recurring",
+        "fire and forget",
+        "delayed"
+      ],
+      "validators": [
+        "architecture",
+        "blazor-concurrency"
+      ],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "core-architecture",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "Background Jobs Specialist",
+        "icon": "⏰",
+        "spawn_prompt": "You are the Background Jobs Specialist (Hangfire). Implement fire-and-forget jobs, delayed jobs, recurring jobs (cron), continuations (chaining). Configure retry policies, queue management. Use IDbContextFactory/IRepositoryFactory for scoped operations in background jobs (NOT direct DbContext injection). Also handles webhook integration, event-driven job pipelines, and async processing of external service callbacks."
+      }
+    },
+    "ms-agent-expert": {
+      "tier": 3,
+      "title": "Microsoft Agent Framework Expert",
+      "group": "ai",
+      "active_phases": [
+        "design",
+        "implement"
+      ],
+      "reports_to": "ai-system-architect",
+      "domains": [
+        "ai-agents"
+      ],
+      "keywords": [
+        "agent",
+        "ai",
+        "llm",
+        "rag",
+        "embedding",
+        "mcp",
+        "a2a",
+        "middleware",
+        "microsoft agent framework",
+        "ichatclient"
+      ],
+      "validators": [
+        "architecture",
+        "packages"
+      ],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "ai-agents-setup",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "ai-agents-workflows",
+          "scope": "design",
+          "priority": "required"
+        },
+        {
+          "id": "ai-agents-production",
+          "scope": "implement",
+          "priority": "required"
+        },
+        {
+          "id": "ai-agents-blazor-ui",
+          "scope": "implement",
+          "priority": "reference"
+        }
+      ],
+      "teammate": {
+        "role": "Microsoft Agent Framework Expert",
+        "icon": "🤖",
+        "spawn_prompt": "You are the Microsoft Agent Framework Expert. Implement ChatClientAgent, AIFunctionFactory, agent workflows (sequential, handoff, group chat). Integrate MCP tools (McpClientFactory, ListToolsAsync, Cast<AITool>). Host agents via A2A protocol (MapA2A, agent cards). Add middleware pipeline, observability (WithOpenTelemetry)."
+      }
+    },
+    "supabase-expert": {
+      "tier": 3,
+      "title": "Supabase & PostgreSQL Specialist",
+      "group": "backend",
+      "active_phases": [
+        "design",
+        "implement"
+      ],
+      "reports_to": "dotnet-senior",
+      "domains": [
+        "backend-supabase"
+      ],
+      "keywords": [
+        "supabase",
+        "postgresql",
+        "rls",
+        "realtime",
+        "pgvector",
+        "row level security",
+        "edge functions"
+      ],
+      "validators": [],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "core-architecture",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "Supabase & PostgreSQL Specialist",
+        "icon": "🐘",
+        "spawn_prompt": "You are the Supabase & PostgreSQL Specialist. Implement Supabase Auth (magic links, OAuth, JWT), Row Level Security (RLS policies), Realtime subscriptions, Edge Functions (Deno/TypeScript). Use pgvector for embeddings/similarity search. Design efficient schemas with proper indexing."
+      }
+    },
+    "vector-search-expert": {
+      "tier": 3,
+      "title": "Vector Search & RAG Specialist",
+      "group": "ai",
+      "active_phases": [
+        "design",
+        "implement"
+      ],
+      "reports_to": "ai-system-architect",
+      "domains": [
+        "ai-vector"
+      ],
+      "keywords": [
+        "vector db",
+        "embeddings",
+        "semantic search",
+        "rag",
+        "pgvector",
+        "similarity search",
+        "retrieval augmented"
+      ],
+      "validators": [],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "ai-agents-setup",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "ai-agents-workflows",
+          "scope": "design",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "Vector Search & RAG Specialist",
+        "icon": "🔎",
+        "spawn_prompt": "You are the Vector Search & RAG Specialist. Implement vector embeddings (OpenAI, Azure AI), similarity search (pgvector, Azure AI Search), RAG pipelines (chunking, embedding, retrieval). Design hybrid search (vector + full-text). Optimize embedding dimensions and index types (HNSW, IVFFlat)."
+      }
+    },
+    "context-optimizer": {
+      "tier": 3,
+      "title": "Context & Token Optimization Specialist",
+      "group": "ai",
+      "active_phases": [
+        "implement"
+      ],
+      "reports_to": "ai-system-architect",
+      "domains": [
+        "ai-context"
+      ],
+      "keywords": [
+        "context window",
+        "token optimization",
+        "chunking",
+        "context compression",
+        "summarization",
+        "token budget"
+      ],
+      "validators": [],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "ai-agents-workflows",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "Context & Token Optimization Specialist",
+        "icon": "🧠",
+        "spawn_prompt": "You are the Context & Token Optimization Specialist. Optimize context windows (sliding window, summarization, selective inclusion), implement token counting and budget management, design chunking strategies (semantic, fixed-size, recursive). Reduce costs through prompt caching, context compression."
+      }
+    },
+    "prompt-engineer": {
+      "tier": 3,
+      "title": "Prompt Engineer",
+      "group": "ai",
+      "active_phases": [
+        "design",
+        "implement"
+      ],
+      "reports_to": "ai-system-architect",
+      "domains": [
+        "ai-prompts"
+      ],
+      "keywords": [
+        "prompt",
+        "prompting",
+        "system prompt",
+        "few-shot",
+        "chain-of-thought",
+        "llm prompt",
+        "agent prompt"
+      ],
+      "validators": [],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "Prompt Engineer",
+        "icon": "✍️",
+        "spawn_prompt": "You are the Prompt Engineer (tier-3). Design system prompts, few-shot examples, chain-of-thought patterns, and optimize LLM interactions. Always show the full prompt text — never just describe it. Apply techniques: constitutional AI, recursive prompting, tree of thoughts, self-consistency."
+      }
+    },
+    "asaas-financial": {
+      "tier": 3,
+      "title": "Payment Integration Specialist (Brazil)",
+      "group": "backend",
+      "active_phases": [
+        "design",
+        "implement"
+      ],
+      "reports_to": "dotnet-senior",
+      "domains": [
+        "integration-payment"
+      ],
+      "keywords": [
+        "asaas",
+        "payment",
+        "pix",
+        "boleto",
+        "credit card",
+        "subscription",
+        "pagamento"
+      ],
+      "validators": [
+        "architecture",
+        "contract-compliance"
+      ],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "core-architecture",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "Payment Integration Specialist",
+        "icon": "💳",
+        "spawn_prompt": "You are the Payment Integration Specialist (Asaas SDK for Brazil). Implement PIX payments, Boleto generation, Credit Card processing, Subscription management. Follow contract-compliance validator patterns for SDK usage."
+      }
+    },
+    "clerk-auth": {
+      "tier": 3,
+      "title": "Auth SaaS Integration Specialist",
+      "group": "backend",
+      "active_phases": [
+        "design",
+        "implement"
+      ],
+      "reports_to": "dotnet-senior",
+      "domains": [
+        "integration-auth"
+      ],
+      "keywords": [
+        "clerk",
+        "clerk auth",
+        "add auth",
+        "implement auth",
+        "login",
+        "signup",
+        "oauth"
+      ],
+      "validators": [],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "core-architecture",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "Auth SaaS Integration Specialist",
+        "icon": "🔐",
+        "spawn_prompt": "You are the Auth SaaS Integration Specialist (Clerk SDK). Implement Clerk authentication flows (login, signup, OAuth), session management, user profile. Integrate with Blazor or Next.js frontend."
+      }
+    },
+    "resend-email": {
+      "tier": 3,
+      "title": "Email Integration Specialist",
+      "group": "backend",
+      "active_phases": [
+        "implement"
+      ],
+      "reports_to": "dotnet-senior",
+      "domains": [
+        "integration-email"
+      ],
+      "keywords": [
+        "resend",
+        "email",
+        "transactional email",
+        "email notification",
+        "send email",
+        "email template",
+        "smtp"
+      ],
+      "validators": [
+        "architecture",
+        "contract-compliance"
+      ],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "core-architecture",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "Email Integration Specialist",
+        "icon": "📧",
+        "spawn_prompt": "You are the Email Integration Specialist (Resend SDK). Implement transactional emails, email templates, notification sending. Follow contract-compliance validator for SDK usage patterns."
+      }
+    },
+    "blazor-builder": {
+      "tier": 3,
+      "title": "Blazor Development Specialist",
+      "group": "frontend",
+      "active_phases": [
+        "uiux",
+        "tasks",
+        "implement"
+      ],
+      "reports_to": "ui-designer",
+      "domains": [
+        "frontend-blazor"
+      ],
+      "keywords": [
+        "blazor",
+        "razor",
+        "server-side",
+        "component",
+        "fluent ui",
+        "mudblazor",
+        "signalr",
+        "page",
+        "view",
+        "form"
+      ],
+      "validators": [
+        "architecture",
+        "blazor",
+        "blazor-concurrency",
+        "blazor-state",
+        "css",
+        "design-system"
+      ],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-blazor-lifecycle",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-blazor-state",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-blazor-pitfalls",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "backend-database-ef-core",
+          "scope": "implement",
+          "priority": "reference"
+        },
+        {
+          "id": "frontend-blazor-fluent-ui",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "Blazor Development Specialist",
+        "icon": "⚡",
+        "spawn_prompt": "You are the Blazor Development Specialist. Build Blazor Server components (Fluent UI or MudBlazor). Follow component-per-file pattern, use @inject for DI, implement loading states and error boundaries. Integrate SignalR for real-time features. Message ef-modeler for data, css-specialist for design system validation."
+      }
+    },
+    "nextjs-expert": {
+      "tier": 3,
+      "title": "Next.js Development Specialist",
+      "group": "frontend",
+      "active_phases": [
+        "uiux",
+        "tasks",
+        "implement"
+      ],
+      "reports_to": "ui-designer",
+      "domains": [
+        "frontend-nextjs"
+      ],
+      "keywords": [
+        "next.js",
+        "nextjs",
+        "react",
+        "tsx",
+        "shadcn",
+        "tailwind",
+        "tanstack",
+        "react-query",
+        "zod",
+        "react-hook-form",
+        "app router",
+        "server component",
+        "client component",
+        "vercel",
+        "neon",
+        "planetscale"
+      ],
+      "validators": [
+        "nextjs-component"
+      ],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "core-architecture",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-nextjs-naming-conventions",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-nextjs-project-structure",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-nextjs-app-router",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-nextjs-components",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-nextjs-data-fetching",
+          "scope": "implement",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-nextjs-forms",
+          "scope": "implement",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-nextjs-state-management",
+          "scope": "implement",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-nextjs-testing",
+          "scope": "implement",
+          "priority": "reference"
+        },
+        {
+          "id": "frontend-nextjs-nextjs-patterns",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "infrastructure-vercel-database",
+          "scope": "design",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "Next.js Development Specialist",
+        "icon": "⚛️",
+        "spawn_prompt": "You are the Next.js Development Specialist. Build Next.js 14+ applications with shadcn/ui components, TanStack Query for data fetching, Server Actions for mutations. Implement Route Handlers for API routes. Message api-designer for backend endpoints, css-specialist for design system. IMPORTANT: When deployment target is Vercel, database must be serverless (Neon, Supabase/PgBouncer port 6543, PlanetScale) — never a plain TCP connection pool."
+      }
+    },
+    "nextjs-ui-specialist": {
+      "tier": 3,
+      "title": "Next.js UI Specialist",
+      "group": "frontend",
+      "active_phases": [
+        "design",
+        "tasks",
+        "implement"
+      ],
+      "reports_to": "ui-designer",
+      "domains": [
+        "frontend-nextjs-ui"
+      ],
+      "keywords": [
+        "framer-motion",
+        "animation",
+        "transition",
+        "motion design",
+        "shadcn theme",
+        "tailwind tokens",
+        "tailwind config",
+        "design system",
+        "icon system",
+        "lucide",
+        "animated",
+        "micro-interaction",
+        "hover effect",
+        "scroll animation",
+        "page transition",
+        "variants",
+        "AnimatePresence"
+      ],
+      "validators": [
+        "design-system",
+        "nextjs-component"
+      ],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-nextjs-components",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-nextjs-nextjs-patterns",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-nextjs-motion-patterns",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "Next.js UI Specialist",
+        "icon": "✨",
+        "spawn_prompt": "You are the Next.js UI Specialist (Tier 3). Focus exclusively on the visual layer: Framer Motion animations (variants, AnimatePresence, useInView, gestures), shadcn/ui theming via CSS vars without editing primitives, Tailwind token bridging from design-system.md, and Lucide icon consistency. ALWAYS read .morph/context/design-system.md first and use only defined tokens. ALWAYS implement useReducedMotion() for WCAG compliance. Do NOT handle data-fetching, routing, or API routes — that's nextjs-expert's domain."
+      }
+    },
+    "css-specialist": {
+      "tier": 3,
+      "title": "CSS & Design System Specialist",
+      "group": "frontend",
+      "active_phases": [
+        "implement"
+      ],
+      "reports_to": "ui-designer",
+      "domains": [
+        "frontend-css"
+      ],
+      "keywords": [
+        "css",
+        "design system",
+        "styling",
+        "theme",
+        "design tokens",
+        "palette"
+      ],
+      "validators": [
+        "css",
+        "contrast",
+        "design-system"
+      ],
+      "standards": [
+        {
+          "id": "frontend-design-system-naming",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-design-system-animations",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "CSS & Design System Specialist",
+        "icon": "🎨",
+        "spawn_prompt": "You are the CSS & Design System Specialist (FASE 5 only). MANDATORY FIRST STEP: Read .morph/context/design-system.md. Validate all CSS follows the design system (no off-palette hardcoded colors, no inline styles with raw values). Enforce naming conventions (BEM for custom classes). Verify WCAG AA contrast (4.5:1 text, 3:1 UI). Run design-system, css, contrast validators. Any missing tokens must be added to design-system.md before proceeding."
+      }
+    },
+    "seo-growth-hacker": {
+      "tier": 3,
+      "title": "SEO & Growth Specialist",
+      "group": "frontend",
+      "active_phases": [
+        "implement"
+      ],
+      "reports_to": "ui-designer",
+      "domains": [
+        "seo"
+      ],
+      "keywords": [
+        "seo",
+        "landing page",
+        "meta tags",
+        "core web vitals",
+        "schema markup",
+        "organic traffic",
+        "content marketing"
+      ],
+      "validators": [],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "SEO & Growth Specialist",
+        "icon": "📈",
+        "spawn_prompt": "You are the SEO & Growth Specialist (tier-3). Audit technical SEO (Core Web Vitals, meta tags, schema markup JSON-LD), optimize content for search engines, implement structured data (Product, Article, FAQ, HowTo, Organization). Focus on Next.js/Blazor page optimization, Lighthouse scores, and organic traffic growth."
+      }
+    },
+    "bicep-architect": {
+      "tier": 3,
+      "title": "Infrastructure as Code Specialist",
+      "group": "infra",
+      "active_phases": [
+        "design",
+        "implement"
+      ],
+      "reports_to": "azure-architect",
+      "domains": [
+        "infrastructure-iac"
+      ],
+      "keywords": [
+        "bicep",
+        "iac",
+        "infra",
+        "provision",
+        "arm template",
+        "infrastructure as code"
+      ],
+      "validators": [
+        "architecture"
+      ],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "core-architecture",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "infrastructure-azure-azure",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "Infrastructure as Code Specialist",
+        "icon": "📜",
+        "spawn_prompt": "You are the Infrastructure as Code Specialist (Bicep). Write main.bicep, modules/*.bicep, parameters.{env}.json. Never create Azure resources manually. Also handles Azure Container Apps deployment: env var mapping (config:path → DOUBLE__UNDERSCORE), what-if validation before deploy, Blazor Server sticky sessions, rollback via revision activation, and cost validation."
+      }
+    },
+    "devops-engineer": {
+      "tier": 3,
+      "title": "CI/CD Specialist",
+      "group": "infra",
+      "active_phases": [
+        "implement"
+      ],
+      "reports_to": "infra-architect",
+      "domains": [
+        "infrastructure-cicd"
+      ],
+      "keywords": [
+        "pipeline",
+        "ci/cd",
+        "deploy",
+        "release",
+        "github actions",
+        "azure pipelines",
+        "deployment"
+      ],
+      "validators": [],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "core-architecture",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "CI/CD Specialist",
+        "icon": "🚀",
+        "spawn_prompt": "You are the CI/CD Specialist. Build Azure Pipelines or GitHub Actions workflows. Implement Blue-Green, Canary, Rolling deployment strategies. Integrate with bicep-architect for IaC deployment, container-specialist for image builds."
+      }
+    },
+    "container-specialist": {
+      "tier": 3,
+      "title": "Containerization Specialist",
+      "group": "infra",
+      "active_phases": [
+        "implement"
+      ],
+      "reports_to": "infra-architect",
+      "domains": [
+        "infrastructure-containers"
+      ],
+      "keywords": [
+        "docker",
+        "container",
+        "containerize",
+        "dockerfile",
+        "multi-stage",
+        "container apps"
+      ],
+      "validators": [],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "core-architecture",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "Containerization Specialist",
+        "icon": "🐳",
+        "spawn_prompt": "You are the Containerization Specialist. Write Dockerfiles (multi-stage builds), .dockerignore. Deploy to Azure Container Apps (scale-to-zero, KEDA scaling). Optimize image size, configure health checks."
+      }
+    },
+    "observability-expert": {
+      "tier": 3,
+      "title": "Observability Specialist",
+      "group": "infra",
+      "active_phases": [
+        "implement"
+      ],
+      "reports_to": "infra-architect",
+      "domains": [
+        "infrastructure-observability"
+      ],
+      "keywords": [
+        "monitoring",
+        "logging",
+        "tracing",
+        "metrics",
+        "app insights",
+        "serilog",
+        "opentelemetry",
+        "dashboards",
+        "alerts"
+      ],
+      "validators": [
+        "observability"
+      ],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "core-architecture",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "Observability Specialist",
+        "icon": "📊",
+        "spawn_prompt": "You are the Observability Specialist. Setup Application Insights (connection strings, sampling), configure Serilog (sinks, enrichers), instrument OpenTelemetry (.NET SDK). Create custom metrics, dashboards, alert rules. Write Log Analytics queries (KQL)."
+      }
+    },
+    "azure-identity": {
+      "tier": 3,
+      "title": "Microsoft Identity Specialist",
+      "group": "infra",
+      "active_phases": [
+        "design",
+        "implement"
+      ],
+      "reports_to": "infra-architect",
+      "domains": [
+        "infrastructure-identity"
+      ],
+      "keywords": [
+        "identity",
+        "entra",
+        "microsoft auth",
+        "azure ad",
+        "b2c",
+        "passkeys",
+        "webauthn",
+        "managed identity"
+      ],
+      "validators": [],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "core-architecture",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "Microsoft Identity Specialist",
+        "icon": "🔑",
+        "spawn_prompt": "You are the Microsoft Identity Specialist. Implement Azure AD B2C, Entra External ID, Managed Identity for Azure resources. Add WebAuthn/Passkeys support (FIDO2 registration/authentication flows)."
+      }
+    },
+    "testing-specialist": {
+      "tier": 3,
+      "title": "Testing Specialist",
+      "group": "testing",
+      "active_phases": [
+        "implement"
+      ],
+      "reports_to": "standards-architect",
+      "domains": [
+        "quality-testing"
+      ],
+      "keywords": [
+        "test",
+        "testing",
+        "unit",
+        "integration",
+        "e2e",
+        "xunit",
+        "moq",
+        "testcontainers",
+        "bunit"
+      ],
+      "validators": [],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "core-architecture",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "Testing Specialist",
+        "icon": "🧪",
+        "spawn_prompt": "You are the Testing Specialist. Write unit tests (xUnit, Moq/NSubstitute, FluentAssertions), integration tests (TestContainers, Respawn for DB reset), Blazor component tests (bUnit), HTTP mocking (WireMock). Follow Arrange-Act-Assert (AAA) pattern."
+      }
+    },
+    "code-analyzer": {
+      "tier": 3,
+      "title": "Code Quality Analyst",
+      "group": "testing",
+      "active_phases": [
+        "implement"
+      ],
+      "reports_to": "standards-architect",
+      "domains": [
+        "quality-review"
+      ],
+      "keywords": [
+        "analyze",
+        "review",
+        "refactor",
+        "clean code",
+        "smell",
+        "duplicate",
+        "solid",
+        "architecture review"
+      ],
+      "validators": [],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "core-architecture",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "Code Quality Analyst",
+        "icon": "🔍",
+        "spawn_prompt": "You are the Code Quality Analyst. Review code for architecture violations, clean code principles (naming, complexity, duplication), SOLID principles. Identify code smells, suggest refactorings. Run architecture and packages validators."
+      }
+    },
+    "troubleshooting-expert": {
+      "tier": 3,
+      "title": "Troubleshooting & Debug Expert",
+      "group": "support",
+      "active_phases": [
+        "implement"
+      ],
+      "reports_to": "standards-architect",
+      "domains": [
+        "quality-debug"
+      ],
+      "keywords": [
+        "debug",
+        "troubleshoot",
+        "root cause",
+        "analyze error",
+        "investigate",
+        "diagnose"
+      ],
+      "validators": [],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "core-architecture",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "Troubleshooting Expert (Escalation)",
+        "icon": "🔧",
+        "spawn_prompt": "You are the Troubleshooting Expert (spawned after 3 failed attempts). Analyze root cause of failures: validation errors, compilation errors, runtime exceptions. Review attempt logs from recovery-tracker. Propose alternative approaches. Message standards-architect with findings."
+      }
+    },
+    "load-testing-expert": {
+      "tier": 3,
+      "title": "Load Testing & Performance Specialist",
+      "group": "testing",
+      "active_phases": [
+        "implement"
+      ],
+      "reports_to": "standards-architect",
+      "domains": [
+        "quality-performance"
+      ],
+      "keywords": [
+        "load test",
+        "performance test",
+        "k6",
+        "jmeter",
+        "stress test",
+        "capacity planning",
+        "bottleneck",
+        "scalability",
+        "concurrent users"
+      ],
+      "validators": [
+        "performance"
+      ],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "core-architecture",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "Load Testing Specialist",
+        "icon": "📈",
+        "spawn_prompt": "You are the Load Testing Specialist. Write k6 scripts (stress test, spike test, soak test), JMeter test plans. Analyze bottlenecks (DB, CPU, memory). Recommend capacity planning (how many users system supports)."
+      }
+    },
+    "documentation-specialist": {
+      "tier": 3,
+      "title": "Documentation Specialist",
+      "group": "docs",
+      "active_phases": [
+        "implement"
+      ],
+      "reports_to": "standards-architect",
+      "domains": [
+        "developer-experience-docs"
+      ],
+      "keywords": [
+        "readme",
+        "documentation",
+        "api docs",
+        "contributing",
+        "deployment guide",
+        "onboarding"
+      ],
+      "validators": [],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "core-architecture",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "Documentation Specialist (Post-FASE 5)",
+        "icon": "📝",
+        "spawn_prompt": "You are the Documentation Specialist (runs after FASE 5). Generate README.md (how to run project), CONTRIBUTING.md (contributor guide), API documentation (Swagger annotations, markdown docs), deployment guides (infra setup). Update existing docs with new features."
+      }
+    },
+    "vsa-architect": {
+      "tier": 3,
+      "title": "Vertical Slice Architecture Specialist",
+      "group": "domain-analysis",
+      "active_phases": [
+        "design",
+        "implement"
+      ],
+      "domains": [
+        "architecture",
+        "backend"
+      ],
+      "keywords": [
+        "vertical slice",
+        "vertical-slice",
+        "vsa",
+        "minimal api",
+        "minimal apis",
+        "ihandler",
+        "result pattern",
+        "feature slice",
+        "scrutor",
+        "vertical slice architecture"
+      ],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "architecture-vertical-slice-vertical-slice",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "VSA Architecture Specialist",
+        "icon": "🍕",
+        "spawn_prompt": "Você é o VSA Specialist. Analise a proposta e produza um VSA Blueprint:\n1. ENTITY FIELDS: todos os campos com tipos C# corretos (sem AggregateRoot, sem Value Objects)\n2. OPERATIONS: slices necessários (Create, GetAll, GetById, Update, Delete + operações customizadas)\n3. ROUTES: HTTP method + rota por operação (ex: POST /api/products, GET /api/products/{id:guid})\n4. ERROR TYPES: Error factory methods para {Entity}Errors (apenas NotFound e casos específicos)\n5. VALIDATION RULES: regras FluentValidation por campo por operação\n\nNão use AggregateRoot, DomainEvent, CQRS formal, MediatR, Application Service layer.\nCada operação é um slice autônomo: Request + Response + Handler + Validator + Endpoint.\nRef: framework/standards/architecture/vertical-slice/vertical-slice.md"
+      }
+    },
+    "morph-spec-architect": {
+      "tier": 3,
+      "title": "Morph-Spec Architect",
+      "group": "domain-analysis",
+      "active_phases": [
+        "design",
+        "tasks"
+      ],
+      "reports_to": "feature-lead",
+      "domains": [
+        "cli",
+        "framework-design",
+        "nodejs",
+        "architecture"
+      ],
+      "keywords": [
+        "morph-spec",
+        "framework feature",
+        "new command",
+        "cli architecture",
+        "plugin",
+        "hook design"
+      ],
+      "validators": [],
+      "standards": [],
+      "teammate": {
+        "role": "specialist",
+        "icon": "🔧",
+        "spawn_prompt": "You are the Morph-Spec Architect. You deeply understand the morph-spec-framework codebase: its 4-tier agent hierarchy, state machine (with filesystem-based phase derivation), Commander.js CLI surface (~25 commands registered in bin/morph-spec.js), hooks system, skills system, and the .morph/ directory layout. Your job is to design new features that fit naturally into the existing architecture. Before proposing implementation, always: (1) identify which existing modules can be reused, (2) determine where the new command should live in src/commands/, (3) define the state impact (does it need new state fields?), (4) list which tests need to be written. Follow ESM module patterns throughout."
+      }
+    },
+    "nodejs-cli-expert": {
+      "tier": 3,
+      "title": "Node.js CLI Expert",
+      "group": "testing",
+      "active_phases": [
+        "implement"
+      ],
+      "reports_to": "feature-lead",
+      "domains": [
+        "nodejs",
+        "cli",
+        "javascript",
+        "esm",
+        "testing"
+      ],
+      "keywords": [
+        "nodejs",
+        "javascript",
+        "esm",
+        "commander",
+        "node --test",
+        "cli command",
+        "morph-spec implementation"
+      ],
+      "validators": [],
+      "standards": [],
+      "teammate": {
+        "role": "specialist",
+        "icon": "🟢",
+        "spawn_prompt": "You are the Node.js CLI Expert for the morph-spec-framework. You implement features in Node.js ESM following the project's conventions: (1) All imports use ESM syntax with .js extensions on relative paths; (2) Commands are registered in bin/morph-spec.js after being defined in src/commands/<domain>/<command>.js; (3) Tests use native node:test runner with mock.fn() for mocking — no external test libraries; (4) Error handling: hooks are fail-open (catch+exit 0), CLI commands exit(1) on fatal errors; (5) Never use require() or module.exports. When implementing a feature, always write the tests alongside the implementation. The test command is: node --test --test-concurrency=1"
+      }
+    },
+    "security-expert": {
+      "tier": 4,
+      "title": "Security Validator",
+      "group": "testing",
+      "active_phases": [
+        "*"
+      ],
+      "reports_to": "standards-architect",
+      "domains": [
+        "security"
+      ],
+      "keywords": [
+        "sql injection",
+        "xss",
+        "secrets",
+        "security scan",
+        "vulnerability",
+        "csrf",
+        "insecure deserialization"
+      ],
+      "validators": [
+        "security"
+      ],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "core-architecture",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "icon": "🛡️",
+        "role": "Security Validator (read-only)",
+        "spawn_prompt": "You are the Security Validator (Tier 4, READ-ONLY). Scan ALL source files (.cs, .razor, .tsx, .ts, .js) in the project for security vulnerabilities:\n\n1. SQL injection — string concatenation in queries (look for $\"...{var}...\" inside SQL/EF raw queries)\n2. Hardcoded secrets — API keys, passwords, connection strings in source code (not in appsettings)\n3. XSS — @Html.Raw usage in Razor/Blazor without sanitization\n4. Insecure deserialization — BinaryFormatter usage\n5. CSRF — POST forms/endpoints missing anti-forgery tokens ([ValidateAntiForgeryToken] or @Html.AntiForgeryToken)\n\nUse Grep and Glob to scan. Do NOT modify any files.\n\nOutput a JSON object: { \"passed\": boolean, \"issues\": [{ \"file\": string, \"line\": number, \"message\": string, \"severity\": \"error\" }] }"
+      },
+      "hook_behavior": {
+        "validates": [
+          "SQL injection (string concatenation in queries)",
+          "Hardcoded secrets (API keys, passwords, connection strings)",
+          "XSS (@Html.Raw usage in Razor/Blazor)",
+          "Insecure deserialization (BinaryFormatter)",
+          "CSRF (missing anti-forgery tokens)"
+        ],
+        "severity": "error",
+        "blocks_on_fail": true
+      }
+    },
+    "architecture-expert": {
+      "tier": 4,
+      "title": "Architecture Validator",
+      "group": "domain-analysis",
+      "active_phases": [
+        "*"
+      ],
+      "reports_to": "standards-architect",
+      "domains": [
+        "architecture"
+      ],
+      "keywords": [
+        "architecture",
+        "clean code",
+        "solid",
+        "dependency injection"
+      ],
+      "validators": [
+        "architecture"
+      ],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "core-architecture",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "icon": "🏗️",
+        "role": "Architecture Validator (read-only)",
+        "spawn_prompt": "You are the Architecture Validator (Tier 4, READ-ONLY). Scan the project for architectural violations:\n\n1. DbContext injection — look for direct DbContext injection instead of IDbContextFactory in Blazor components (.razor, .razor.cs)\n2. Async/await anti-patterns — search for .Result, .Wait(), .GetAwaiter().GetResult() in async code\n3. DI registration order — in Program.cs, verify services are registered before middleware (app.Use*/Map*)\n4. Blazor render mode — verify InteractiveServer/InteractiveWebAssembly components don't use incompatible patterns\n5. Layer violations — Domain/Application projects must not reference Infrastructure or Web projects\n\nUse Grep and Glob to scan. Do NOT modify any files.\n\nOutput a JSON object: { \"passed\": boolean, \"issues\": [{ \"file\": string, \"line\": number, \"message\": string, \"severity\": \"error\" }] }"
+      },
+      "hook_behavior": {
+        "validates": [
+          "DbContext injection (IDbContextFactory required)",
+          "Async/await patterns (no .Result or .Wait)",
+          "DI registration order (services before middleware)",
+          "Blazor render mode compatibility"
+        ],
+        "severity": "error",
+        "blocks_on_fail": true
+      }
+    },
+    "packages-validator": {
+      "tier": 4,
+      "title": "Packages Validator",
+      "group": "testing",
+      "active_phases": [
+        "*"
+      ],
+      "reports_to": "standards-architect",
+      "domains": [
+        "packages"
+      ],
+      "keywords": [
+        "nuget",
+        "packages",
+        "dependencies",
+        "version conflict"
+      ],
+      "validators": [
+        "packages"
+      ],
+      "standards": [
+        {
+          "id": "core-coding",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "icon": "📦",
+        "role": "Packages Validator (read-only)",
+        "spawn_prompt": "You are the Packages Validator (Tier 4, READ-ONLY). Scan all project files for package issues:\n\n1. NuGet version conflicts — search *.csproj files for the same PackageReference appearing with different versions across projects\n2. Incompatible .NET 10 packages — check that major package versions are compatible with the target framework\n3. Security vulnerabilities — look for known outdated packages (Newtonsoft.Json < 13.0.1, System.Text.Json < 8.0.5, etc.)\n4. For npm projects: check package.json for duplicate dependencies, outdated major versions\n\nUse Grep and Glob to scan. Do NOT modify any files.\n\nOutput a JSON object: { \"passed\": boolean, \"issues\": [{ \"file\": string, \"message\": string, \"severity\": \"error\" }] }"
+      },
+      "hook_behavior": {
+        "validates": [
+          "NuGet version conflicts (same package, different versions)",
+          "Incompatible .NET 10 packages",
+          "Security vulnerabilities (outdated packages)"
+        ],
+        "severity": "error",
+        "blocks_on_fail": true
+      }
+    },
+    "design-system-validator": {
+      "tier": 4,
+      "title": "Design System Validator",
+      "group": "frontend",
+      "active_phases": [
+        "*"
+      ],
+      "reports_to": "ui-designer",
+      "domains": [
+        "design-system"
+      ],
+      "keywords": [
+        "design system",
+        "css",
+        "color palette",
+        "spacing"
+      ],
+      "validators": [
+        "design-system"
+      ],
+      "standards": [
+        {
+          "id": "frontend-design-system-naming",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-design-system-animations",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "icon": "🎨",
+        "role": "Design System Validator (read-only)",
+        "spawn_prompt": "You are the Design System Validator (Tier 4, READ-ONLY). Scan CSS/SCSS and component files for design system compliance:\n\n1. Color palette — look for hardcoded hex/rgb colors instead of CSS variables (var(--color-primary), var(--color-secondary), etc.)\n2. Spacing — look for hardcoded px/rem values instead of spacing variables (var(--spacing-*))\n3. Typography — look for hardcoded font-size/font-family instead of typography variables (var(--font-*))\n4. Component naming — verify PascalCase for Blazor components (.razor) and kebab-case for CSS classes\n5. Check .morph/context/design-system.md if it exists for project-specific design tokens\n\nUse Grep and Glob to scan. Do NOT modify any files.\n\nOutput a JSON object: { \"passed\": boolean, \"issues\": [{ \"file\": string, \"line\": number, \"message\": string, \"severity\": \"warning\" }] }"
+      },
+      "hook_behavior": {
+        "validates": [
+          "CSS color palette compliance (primary, secondary, accent)",
+          "Spacing values (use var(--spacing-*))",
+          "Typography scale (use var(--font-*))",
+          "Component naming (PascalCase for Blazor, kebab-case for CSS)"
+        ],
+        "severity": "warning",
+        "blocks_on_fail": false
+      }
+    },
+    "blazor-concurrency-validator": {
+      "tier": 4,
+      "title": "Blazor Concurrency Validator",
+      "group": "frontend",
+      "active_phases": [
+        "implement"
+      ],
+      "reports_to": "blazor-builder",
+      "domains": [
+        "blazor-concurrency"
+      ],
+      "keywords": [
+        "blazor",
+        "dbcontext",
+        "lifecycle",
+        "async",
+        "concurrency"
+      ],
+      "validators": [
+        "blazor-concurrency"
+      ],
+      "standards": [
+        {
+          "id": "frontend-blazor-lifecycle",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-blazor-pitfalls",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-blazor-state",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "stacks": [
+        "blazor"
+      ],
+      "teammate": {
+        "icon": "⚡",
+        "role": "Blazor Concurrency Validator (read-only)",
+        "spawn_prompt": "You are the Blazor Concurrency Validator (Tier 4, READ-ONLY). Scan all Blazor component files (.razor, .razor.cs) for concurrency and lifecycle violations:\n\n1. DbContext lifecycle — look for injected DbContext (not IDbContextFactory), disposed context usage, scope issues\n2. Async void — search for 'async void' methods (must be 'async Task' except event handlers)\n3. JSInterop in OnInitialized — look for IJSRuntime calls in OnInitialized/OnInitializedAsync (must be in OnAfterRender/OnAfterRenderAsync)\n4. State mutation — look for property changes without calling StateHasChanged() or InvokeAsync(StateHasChanged)\n5. Thread safety — look for shared mutable state without synchronization in Blazor Server components\n\nUse Grep and Glob to scan. Do NOT modify any files.\n\nOutput a JSON object: { \"passed\": boolean, \"issues\": [{ \"file\": string, \"line\": number, \"message\": string, \"severity\": \"error\" }] }"
+      },
+      "hook_behavior": {
+        "validates": [
+          "DbContext lifecycle violations (dispose, scope issues)",
+          "Async void methods (use async Task instead)",
+          "JSInterop in OnInitialized (move to OnAfterRender)",
+          "State mutation without StateHasChanged"
+        ],
+        "severity": "error",
+        "blocks_on_fail": true
+      }
+    },
+    "morph-spec-validator": {
+      "tier": 4,
+      "title": "Morph-Spec Validator",
+      "group": "testing",
+      "active_phases": [
+        "implement",
+        "validate"
+      ],
+      "reports_to": "qa-lead",
+      "domains": [
+        "nodejs",
+        "cli",
+        "testing",
+        "validation"
+      ],
+      "keywords": [
+        "validate morph-spec",
+        "node.js validation",
+        "cli test"
+      ],
+      "validators": [
+        "morph-spec-standards"
+      ],
+      "standards": [],
+      "teammate": {
+        "icon": "🔬",
+        "role": "Morph-Spec Validator (read-only)",
+        "tools": "Read, Glob, Grep, Bash",
+        "maxTurns": 12,
+        "spawn_prompt": "You are the Morph-Spec Validator (Tier 4, READ-ONLY). Scan the morph-spec framework codebase for standards compliance:\n\n1. ESM imports — all relative imports must use .js extensions (e.g., './foo.js' not './foo')\n2. Command registration — new commands in src/commands/ must be imported and registered in bin/morph-spec.js\n3. Test coverage — each module in src/ should have a corresponding test file in tests/\n4. No CommonJS — search for require() or module.exports (must use import/export)\n5. Hook fail-open — all hooks in framework/hooks/ must have try/catch with exit(0) fallback\n6. Run 'npm test' to verify all tests pass\n\nUse Grep, Glob, and Bash to scan. Do NOT modify any files.\n\nOutput a JSON object: { \"passed\": boolean, \"issues\": [{ \"file\": string, \"line\": number, \"message\": string, \"severity\": \"error\" }] }"
+      },
+      "hook_behavior": {
+        "validates": [
+          "ESM imports use .js extensions on relative paths",
+          "New commands are registered in bin/morph-spec.js",
+          "Tests exist for new modules (one test file per module)",
+          "npm test passes with no failures",
+          "No require() or module.exports used",
+          "Error handling follows fail-open pattern for hooks"
+        ],
+        "severity": "error",
+        "blocks_on_fail": true
+      }
+    },
+    "nextjs-component-validator": {
+      "tier": 4,
+      "title": "Next.js Component Validator",
+      "group": "frontend",
+      "active_phases": [
+        "implement"
+      ],
+      "keywords": [
+        "nextjs",
+        "tsx",
+        "use client",
+        "server component",
+        "app router"
+      ],
+      "validators": [
+        "nextjs-component"
+      ],
+      "stacks": [
+        "nextjs"
+      ],
+      "teammate": {
+        "icon": "⚛️",
+        "role": "Next.js Component Validator (read-only)",
+        "spawn_prompt": "You are the Next.js Component Validator (Tier 4, READ-ONLY). Scan all .tsx/.ts files under src/ and validate:\n\n1. \"use client\" directive — must be present when React hooks (useState, useEffect, etc.) are used\n2. Server Components — \"use client\" must be absent for pure Server Components (no hooks, no event handlers)\n3. File naming — component files must use kebab-case naming convention\n4. Import patterns — client components should not import server-only modules\n\nUse Grep and Glob to scan. Do NOT modify any files.\n\nOutput a JSON object: { \"passed\": boolean, \"issues\": [{ \"file\": string, \"message\": string, \"suggestion\": string, \"severity\": \"warning\" }] }"
+      },
+      "hook_behavior": {
+        "severity": "warning",
+        "blocks_on_fail": false,
+        "validates": [
+          "use-client directive",
+          "hook usage",
+          "file naming"
+        ]
+      }
+    }
+  },
+  "squads": {
+    "backend_squad": {
+      "leader": "dotnet-senior",
+      "members": [
+        "ef-modeler",
+        "event-architect",
+        "api-designer",
+        "nosql-cache-expert",
+        "hangfire-orchestrator",
+        "ms-agent-expert",
+        "supabase-expert",
+        "vector-search-expert",
+        "context-optimizer",
+        "prompt-engineer",
+        "asaas-financial",
+        "clerk-auth",
+        "resend-email"
+      ],
+      "domains": [
+        "backend",
+        "backend-data",
+        "backend-events",
+        "backend-api",
+        "backend-nosql",
+        "backend-ddd",
+        "backend-jobs",
+        "ai-agents",
+        "backend-supabase",
+        "ai-vector",
+        "ai-context",
+        "integration-payment",
+        "integration-auth",
+        "integration-email"
+      ]
+    },
+    "frontend_squad": {
+      "leader": "ui-designer",
+      "members": [
+        "blazor-builder",
+        "nextjs-expert",
+        "css-specialist",
+        "seo-growth-hacker"
+      ],
+      "domains": [
+        "frontend-design",
+        "frontend-blazor",
+        "frontend-nextjs",
+        "frontend-css",
+        "seo"
+      ],
+      "active_phases": {
+        "design": [
+          "ui-designer"
+        ],
+        "implement": [
+          "blazor-builder",
+          "nextjs-expert",
+          "css-specialist",
+          "seo-growth-hacker"
+        ]
+      }
+    },
+    "infrastructure_squad": {
+      "leader": "infra-architect",
+      "members": [
+        "bicep-architect",
+        "devops-engineer",
+        "container-specialist",
+        "observability-expert",
+        "azure-identity"
+      ],
+      "domains": [
+        "infrastructure",
+        "infrastructure-iac",
+        "infrastructure-cicd",
+        "infrastructure-containers",
+        "infrastructure-observability",
+        "infrastructure-identity"
+      ]
+    },
+    "quality_squad": {
+      "leader": "standards-architect",
+      "members": [
+        "testing-specialist",
+        "code-analyzer",
+        "troubleshooting-expert",
+        "load-testing-expert",
+        "documentation-specialist"
+      ],
+      "domains": [
+        "quality-testing",
+        "quality-review",
+        "quality-debug",
+        "quality-performance",
+        "developer-experience-docs"
+      ],
+      "note": "No permanent leader — standards-architect coordinates directly"
+    }
+  },
+  "relationship_types": {
+    "reports_to": "Hierarchical manager relationship",
+    "coordinates": "Manages/leads these agents",
+    "escalates_to": "Where to escalate unresolved issues",
+    "collaborates_with": "Peer agents for cross-domain work",
+    "runs_in": "Execution context (hooks, not teammates)",
+    "team_role": "Role in Agent Teams (lead, domain_leader, specialist, validator, escalation_specialist, post_implementation, planning_only)"
+  }
+}