@polymorphism-tech/morph-spec 4.10.0 → 4.10.2

package/README.md

@@ -3,7 +3,7 @@
 > Spec-driven development framework for multi-stack projects. Turns feature requests into implementation-ready code through structured, AI-orchestrated phases.
 
 **Package:** `@polymorphism-tech/morph-spec`
-**Version:** 4.10.0  
+**Version:** 4.10.2  
 **Requires:** Node.js 18+, Claude Code
 
 ---
@@ -376,4 +376,4 @@ Code generated by morph-spec (contracts, templates, implementation output) belon
 
 ---
 
-*morph-spec v4.10.0 by [Polymorphism Tech](https://polymorphism.tech)*
+*morph-spec v4.10.2 by [Polymorphism Tech](https://polymorphism.tech)*

package/claude-plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "morph-spec",
-  "version": "4.10.0",
+  "version": "4.10.2",
   "displayName": "MORPH-SPEC Framework",
   "description": "Spec-driven development with 38 agents and 8-phase workflow for .NET/Blazor/Next.js/Azure",
   "publisher": "polymorphism-tech",

package/docs/CHEATSHEET.md

@@ -198,4 +198,4 @@ These files are never edited directly. Use CLI commands or `morph-spec update` i
 
 ---
 
-*morph-spec v4.10.0 by Polymorphism Tech*
+*morph-spec v4.10.2 by Polymorphism Tech*

package/docs/QUICKSTART.md

@@ -203,4 +203,4 @@ morph-spec doctor
 
 ---
 
-*morph-spec v4.10.0 by Polymorphism Tech*
+*morph-spec v4.10.2 by Polymorphism Tech*

package/framework/CLAUDE.md

@@ -2,21 +2,14 @@
 
 > by Polymorphism Tech — Spec-driven development for .NET/Blazor/Next.js/Azure
 
----
-
-## Project Context
-
 @.morph/context/README.md
 
----
-
 ## Critical Rules
 
 **NEVER:**
 - Skip to code without a specification
 - Implement without design approval
 - Ignore standards in `.morph/framework/standards/`
-- Create infrastructure manually
 - Generate code without defined contracts
 - List questions as plain text — always use the `AskUserQuestion` tool
 
@@ -24,76 +17,19 @@
 - Follow the mandatory phases
 - Generate outputs in `.morph/features/{feature}/`
 - Document decisions in `decisions.md`
-- Checkpoint every 3 implemented tasks
-- Use Infrastructure as Code
-- Use `AskUserQuestion` tool whenever asking the user anything (1–4 questions per call; split into sequential calls if more)
-
----
+- Use `AskUserQuestion` tool whenever asking the user anything (1-4 questions per call)
 
 ## Quick Reference
 
 | Command | Purpose |
 |---------|---------|
-| `/morph-proposal {feature}` | Full spec pipeline (phases 1–4, pauses for approval) |
-| `/morph-apply {feature}` | Implement feature (phase 5) |
-| `/morph-status` | Feature status dashboard |
-| `/morph-preflight` | Pre-implementation validation |
-
----
-
-## State & Outputs
-
-| Path | Notes |
-|------|-------|
-| `.morph/state.json` | **READ-ONLY** — use `morph-spec` CLI to update |
-| `.morph/features/{feature}/{phase}/` | Feature outputs organized by phase |
-| `.morph/framework/` | **READ-ONLY** — framework files managed by morph-spec |
-| `.morph/config/config.json` | Project configuration (editable) |
-
-### mark-output types
-
-Use `morph-spec state mark-output <feature> <type>` with one of these exact type names:
-
-| Type | Phase | kebab alias |
-|------|-------|-------------|
-| `proposal` | proposal | — |
-| `schemaAnalysis` | design | `schema-analysis` |
-| `spec` | design | — |
-| `contracts` | design | — |
-| `contractsVsa` | design | `contracts-vsa` |
-| `decisions` | design | — |
-| `clarifications` | clarify | — |
-| `plan` | plan | — |
-| `tasks` | tasks | — |
-| `uiDesignSystem` | uiux | `ui-design-system` |
-| `uiMockups` | uiux | `ui-mockups` |
-| `uiComponents` | uiux | `ui-components` |
-| `uiFlows` | uiux | `ui-flows` |
-| `recap` | implement | — |
----
-
-## Phase Sequence
-
-```
-proposal → setup → [uiux] → design → clarify → plan → tasks → implement → [sync]
-```
-
-Use `morph-spec status {feature}` to see current phase and pending approval gates.
-
----
+| `/morph-proposal {feature}` | Full spec pipeline (pauses for approval) |
+| `/morph-apply {feature}` | Implement feature |
+| `/morph-status` | Status dashboard |
+| `/morph-preflight` | Pre-deploy validation |
 
 ## Agents
 
 Tier-1 and tier-2 MORPH agents are available as native subagents in `.claude/agents/`.
-They can be invoked directly by Claude Code during multi-agent workflows.
-
----
-
-## Context Window Tip
-
-When using 3+ MCPs, add `"experimental": { "mcpCliMode": true }` to `.claude/settings.json`.
-MCP tools load on-demand instead of all at startup — keeps context clean for actual work.
-
----
 
 *MORPH-SPEC by Polymorphism Tech*

package/framework/agents/backend/api-designer.md

@@ -2,6 +2,9 @@
 name: api-designer
 description: API Designer specialist for REST API design, OpenAPI/Swagger specs, endpoint architecture, and HTTP contract definitions. Use when designing API endpoints, creating OpenAPI specs, defining REST contracts, or implementing Minimal API controllers in .NET.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+stacks:
+  - dotnet
+  - nextjs
 ---
 
 # API Designer

package/framework/agents/backend/dotnet-senior.md

@@ -2,6 +2,9 @@
 name: dotnet-senior
 description: Senior .NET engineer and Backend Squad Leader for C#, Minimal API, async patterns, and Clean Architecture implementation. Use when implementing .NET/C# services, designing backend architecture, implementing async operations with CancellationToken, or coordinating backend domain specialists.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+stacks:
+  - dotnet
+  - blazor
 ---
 
 # .NET Senior Engineer

package/framework/agents/backend/ef-modeler.md

@@ -2,6 +2,8 @@
 name: ef-modeler
 description: Entity Framework Modeler specialist for database schema design, EF Core migrations, DbContext configuration, and ORM patterns including IDbContextFactory. Use when designing database models, creating EF Core migrations, configuring DbContext, or implementing repository patterns with EF Core.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+stacks:
+  - dotnet
 ---
 
 # EF Modeler

package/framework/agents/backend/hangfire-orchestrator.md

@@ -2,6 +2,8 @@
 name: hangfire-orchestrator
 description: Hangfire Orchestrator specialist for background job design, recurring task scheduling, queue management, and idempotent job patterns in .NET. Use when implementing background jobs, scheduling recurring tasks, managing job queues, or integrating Hangfire with .NET services.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+stacks:
+  - dotnet
 ---
 
 # Hangfire Orchestrator

package/framework/agents/backend/ms-agent-expert.md

@@ -2,6 +2,8 @@
 name: ms-agent-expert
 description: Microsoft Agent Framework Expert for Semantic Kernel, AI extensions, function calling, MCP/A2A protocols, and agentic pipeline implementation. Use when building AI agents with Semantic Kernel, implementing tool/plugin calling, designing multi-agent workflows, or integrating LLMs with .NET services.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+stacks:
+  - dotnet
 ---
 
 # Agent Framework Expert

package/framework/agents/frontend/blazor-builder.md

@@ -2,6 +2,8 @@
 name: blazor-builder
 description: Blazor Builder specialist for .NET + Blazor Server stack, Razor components, Fluent UI Blazor, MudBlazor, and .NET 10 patterns. Use when implementing Blazor components and pages, configuring Program.cs, handling Blazor lifecycle patterns, or choosing between Fluent UI and MudBlazor libraries.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+stacks:
+  - blazor
 ---
 
 # .NET + Blazor Stack

package/framework/agents/frontend/nextjs-expert.md

@@ -2,6 +2,8 @@
 name: nextjs-expert
 description: Next.js specialist for App Router, shadcn/ui, TanStack Query, react-hook-form/Zod, and EasyPanel deployment. Use when building Next.js pages or components, implementing forms, setting up data fetching from a .NET API, or configuring TypeScript/Docker for Next.js.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+stacks:
+  - nextjs
 ---
 
 # Next.js Expert

package/framework/agents/infrastructure/azure-architect.md

@@ -2,6 +2,8 @@
 name: azure-architect
 description: Azure Architect specialist for designing Azure infrastructure, creating Bicep IaC templates, estimating resource costs, and enforcing zero-portal policy. Use when designing Azure architecture, provisioning cloud resources, creating Bicep templates, or planning multi-environment deployments.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+stacks:
+  - azure
 ---
 
 # Azure Architect

package/framework/agents/infrastructure/azure-deploy-specialist.md

@@ -2,6 +2,8 @@
 name: azure-deploy-specialist
 description: Azure Deploy Specialist for end-to-end deployments to Azure Container Apps using systematic playbooks, validation checklists, and accumulated deployment knowledge. Use when deploying to Azure Container Apps, debugging deployment failures, configuring CI/CD pipelines, or performing pre-flight deployment validation.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+stacks:
+  - azure
 ---
 
 # Azure Deploy Specialist

package/framework/agents/infrastructure/bicep-architect.md

@@ -2,6 +2,8 @@
 name: bicep-architect
 description: Bicep Architect specialist for Azure Infrastructure as Code, modular Bicep templates, ARM deployments, and resource configuration. Use when writing Bicep templates, structuring IaC modules, validating Azure deployments with what-if, or converting ARM JSON to Bicep.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+stacks:
+  - azure
 ---
 
 # Bicep Architect

package/framework/agents/infrastructure/container-specialist.md

@@ -2,6 +2,8 @@
 name: container-specialist
 description: Container Specialist for Docker, Compose, Azure Container Registry, and containerized .NET application patterns. Use when creating Dockerfiles, configuring multi-stage builds, setting up container registries, or containerizing .NET applications for Azure Container Apps.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+stacks:
+  - docker
 ---
 
 # Container Specialist

package/framework/agents/infrastructure/devops-engineer.md

@@ -2,6 +2,9 @@
 name: devops-engineer
 description: DevOps Engineer (Tier 2 Domain Leader) for CI/CD pipeline strategy, GitHub Actions workflows, Azure DevOps, monitoring, and release automation. Use when designing deployment pipelines, configuring GitHub Actions, setting up Azure DevOps, or planning release strategies.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+stacks:
+  - azure
+  - docker
 ---
 
 # DevOps Engineer

package/framework/agents/infrastructure/infra-architect.md

@@ -2,6 +2,9 @@
 name: infra-architect
 description: Infrastructure Squad Leader for cloud-agnostic infrastructure coordination. Use when planning deployments, provisioning any cloud resources, setting up CI/CD pipelines, containerizing applications, or designing infrastructure architecture regardless of cloud provider.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+stacks:
+  - azure
+  - docker
 ---
 
 # Infrastructure Squad Leader

package/framework/agents/integrations/asaas-financial.md

@@ -2,6 +2,8 @@
 name: asaas-financial
 description: Asaas Financial specialist for Asaas API integration, payment processing, Pix/boleto billing, and subscription management in Brazilian projects. Use when integrating Asaas payments, implementing billing flows, handling payment webhooks, or building subscription management features.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+stacks:
+  - dotnet
 ---
 
 # Asaas Financial

package/framework/agents/integrations/azure-identity.md

@@ -2,6 +2,8 @@
 name: azure-identity
 description: Azure Identity specialist for Microsoft Entra ID, OAuth 2.0/OIDC, MSAL, JWT authentication, and enterprise SSO patterns. Use when implementing Microsoft authentication, configuring Entra ID app registrations, securing APIs with OAuth/JWT, or setting up enterprise SSO with Azure AD.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+stacks:
+  - azure
 ---
 
 # Azure Identity (Microsoft Identity)

package/framework/agents/integrations/clerk-auth.md

@@ -2,6 +2,9 @@
 name: clerk-auth
 description: Clerk Auth specialist for Clerk SDK integration, social login, JWT session management, and user management in Next.js and .NET projects. Use when integrating Clerk authentication, implementing social login flows, managing user sessions with Clerk JWT, or protecting routes with Clerk middleware.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+stacks:
+  - dotnet
+  - nextjs
 ---
 
 # Clerk Auth

package/framework/agents/integrations/hangfire-integration.md

@@ -2,6 +2,8 @@
 name: hangfire-orchestrator-integration
 description: Hangfire integration specialist for connecting background jobs with external services, implementing webhook handlers, and building event-driven workflows in .NET. Use when integrating Hangfire with third-party APIs, processing webhooks asynchronously, or designing event-driven job pipelines.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+stacks:
+  - dotnet
 ---
 
 # Hangfire Orchestrator

package/framework/agents/integrations/resend-email.md

@@ -2,6 +2,8 @@
 name: resend-email
 description: Resend Email specialist for transactional email, HTML/React email templates, Resend API integration, and notification systems in .NET and Next.js. Use when implementing email notifications, integrating Resend API, creating transactional email templates, or configuring email delivery in MORPH-SPEC projects.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+stacks:
+  - dotnet
 ---
 
 # Resend Email