@polymorphism-tech/morph-spec 4.12.0 → 4.13.0

package/bin/validate.js

@@ -45,7 +45,7 @@ async function buildValidators(stack) {
     };
     validators.architecture = {
       name: 'Architecture Patterns',
-      description: 'Detects DI anti-patterns and lifecycle issues in Blazor',
+      description: 'Detects DI anti-patterns, middleware issues, and configuration problems in .NET',
       run: validateArchitecture
     };
     validators.contrast = {

package/claude-plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "morph-spec",
-  "version": "4.12.0",
+  "version": "4.13.0",
   "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

@@ -26,9 +26,9 @@ Phases in brackets are optional.
 |-------|-----------|--------------|------|
 | proposal | `0-proposal/` | `proposal.md` | ✅ Approval |
 | setup | *(no output)* | context loaded | — |
-| uiux *(optional)* | `2-ui/` | `design-system.md`, `mockups.md`, `components.md`, `flows.md` | ✅ Approval |
-| design | `1-design/` | `spec.md`, `contracts.cs`, `decisions.md` | ✅ Approval |
-| clarify | `1-design/` | spec updated | — |
+| uiux *(optional)* | `1-ui/` | `design-system.md`, `mockups.md`, `components.md`, `flows.md` | ✅ Approval |
+| design | `2-design/` | `spec.md`, `contracts.cs`, `decisions.md` | ✅ Approval |
+| clarify | `2-design/` | spec updated | — |
 | tasks | `3-tasks/` | `tasks.md` | ✅ Approval |
 | implement | `4-implement/` | code + `recap.md` | — |
 | sync *(optional)* | `.morph/context/` | standards updated | — |
@@ -65,8 +65,7 @@ morph-spec state set {feature} {key} {value}   # update property
 morph-spec phase advance {feature}             # advance to next phase
 morph-spec status {feature} [--json] [--verbose]
 morph-spec task done {feature} {task-id}        # mark task complete
-morph-spec task start {feature} {task-id}      # start a task
-morph-spec task next {feature}                 # preview next task
+morph-spec task start {feature} {task-id}      # start a task (dispatch gate)
 ```
 
 ---
@@ -147,7 +146,7 @@ morph-spec approval-status {feature}           # show gate status
 ├── config/
 │   └── config.json               # project config (editable)
 ├── framework/                    # READ-ONLY
-│   ├── agents.json               # 42 agents, 4 tiers
+│   ├── agents.json               # 22 agents, 4 tiers
 │   ├── standards/                # 82 standards across 11 categories
 │   └── templates/                # code and IaC templates
 ├── context/                      # project context (editable)
@@ -156,8 +155,8 @@ morph-spec approval-status {feature}           # show gate status
 ├── features/
 │   └── {feature}/
 │       ├── 0-proposal/proposal.md
-│       ├── 1-design/spec.md, contracts.cs, decisions.md
-│       ├── 2-ui/design-system.md, mockups.md, components.md, flows.md
+│       ├── 1-ui/design-system.md, mockups.md, components.md, flows.md
+│       ├── 2-design/spec.md, contracts.cs, decisions.md
 │       ├── 3-tasks/tasks.md
 │       └── 4-implement/recap.md
 ├── checkpoints/
@@ -167,11 +166,11 @@ morph-spec approval-status {feature}           # show gate status
 .claude/
 ├── commands/                     # slash commands
 ├── skills/                       # framework skills (SKILL.md per dir)
-├── agents/                       # native subagents (38)
+├── agents/                       # native subagents (22)
 │   ├── morph-{id}.md             # tier 1-2 agents
 │   └── morph-domain-{name}.md   # tier 3 domain agents
 ├── rules/                        # path-scoped rules (6 files)
-└── settings.local.json           # hooks (11)
+└── settings.local.json           # hooks (10)
 ```
 
 ---
@@ -198,4 +197,4 @@ These files are never edited directly. Use CLI commands or `morph-spec update` i
 
 ---
 
-*morph-spec v4.12.0 by Polymorphism Tech*
+*morph-spec v4.13.0 by Polymorphism Tech*

package/docs/QUICKSTART.md

@@ -44,7 +44,7 @@ Open your project in Claude Code and run:
 
 Replace `my-feature` with a short kebab-case name for your feature (e.g., `user-notifications`, `payment-flow`).
 
-The proposal pipeline runs phases 0–4 with three approval gates:
+The proposal pipeline runs phases 0–6 with three approval gates:
 
 ### Phase 0 — Proposal
 
@@ -54,30 +54,30 @@ Claude analyzes your request, detects which agents are relevant, and produces `0
 
 Loads project context from `.morph/context/`, confirms stack and active agents. No approval needed.
 
-### Phase 1.5 — UI/UX (conditional)
+### Phase 2 — UI/UX (conditional)
 
 Only runs if frontend agents are active. Claude generates:
-- `2-ui/design-system.md` — colors, typography, spacing
-- `2-ui/mockups.md` — ASCII wireframes
-- `2-ui/components.md` — component specs
-- `2-ui/flows.md` — user flows and edge cases
+- `1-ui/design-system.md` — colors, typography, spacing
+- `1-ui/mockups.md` — ASCII wireframes
+- `1-ui/components.md` — component specs
+- `1-ui/flows.md` — user flows and edge cases
 
 You approve the UI design before design phase begins.
 
-### Phase 2 — Design
+### Phase 3 — Design
 
 Claude produces the technical specification:
-- `1-design/spec.md` — full requirements, use cases, validations
-- `1-design/contracts.cs` — C# interfaces, DTOs, enums
-- `1-design/decisions.md` — architectural decision records (ADRs)
+- `2-design/spec.md` — full requirements, use cases, validations
+- `2-design/contracts.cs` — C# interfaces, DTOs, enums
+- `2-design/decisions.md` — architectural decision records (ADRs)
 
 You review and approve the design.
 
-### Phase 3 — Clarify
+### Phase 4 — Clarify
 
 Claude identifies 3–7 ambiguities in the spec, asks you to resolve them, then updates the spec. No gate.
 
-### Phase 4 — Tasks
+### Phase 6 — Tasks
 
 Claude breaks the spec into atomic tasks (`T001`, `T002`, …) saved to `3-tasks/tasks.md`. You approve the task list.
 
@@ -142,11 +142,11 @@ You can have multiple features in progress simultaneously. Each has its own dire
 .morph/features/
 ├── user-notifications/
 │   ├── 0-proposal/
-│   ├── 1-design/
+│   ├── 2-design/
 │   └── 3-tasks/
 └── payment-flow/
     ├── 0-proposal/
-    └── 1-design/
+    └── 2-design/
 ```
 
 See all feature states:
@@ -197,4 +197,4 @@ morph-spec doctor
 
 ---
 
-*morph-spec v4.12.0 by Polymorphism Tech*
+*morph-spec v4.13.0 by Polymorphism Tech*

package/framework/CLAUDE.md

@@ -1,6 +1,6 @@
 # MORPH-SPEC Runtime Instructions
 
-> by Polymorphism Tech — Spec-driven development for .NET/Blazor/Next.js/Azure
+> by Polymorphism Tech — Spec-driven development framework
 
 @.morph/context/README.md
 
@@ -18,6 +18,8 @@
 - Generate outputs in `.morph/features/{feature}/`
 - Document decisions in `decisions.md`
 - Use `AskUserQuestion` tool whenever asking the user anything (1-4 questions per call)
+- Read spec.md FR sections before implementing each task
+- Reference FR IDs in task descriptions and commit messages
 
 ## Quick Reference
 
@@ -27,9 +29,10 @@
 | `/morph-apply {feature}` | Implement feature |
 | `/morph-status` | Status dashboard |
 | `/morph-preflight` | Pre-deploy validation |
+| `morph-spec context refresh` | Scan architecture & update context |
 
 ## Agents
 
-Tier-1 and tier-2 MORPH agents are available as native subagents in `.claude/agents/`.
+MORPH agents (tiers 1-4) are available as native subagents in `.claude/agents/`.
 
 *MORPH-SPEC by Polymorphism Tech*

package/framework/agents/README.md

@@ -2,13 +2,12 @@
 
 Domain expertise skills organized by squad.
 
-**Purpose:** Skills that provide deep domain knowledge (backend, frontend, infra, quality, ai-agents, integrations).
+**Purpose:** Skills that provide deep domain knowledge (backend, frontend, infra, ai-agents, integrations, architecture).
 
 **Squads:**
 - backend/ - Backend Squad (led by dotnet-senior)
-- frontend/ - Frontend Squad (led by ui-designer)
+- frontend/ - Frontend Squad (led by nextjs-expert)
 - infrastructure/ - Infrastructure Squad (led by infra-architect)
-- quality/ - Quality Squad (coordinated by standards-architect)
 - ai-agents/ - AI/Agent specialists
 - integrations/ - External integration specialists
-- architecture/ - Architecture and planning
+- architecture/ - Architecture, standards, and SEO

package/framework/agents/ai-agents/ai-system-architect.md

@@ -108,7 +108,7 @@ Design principle: each agent has one clear responsibility, composed via workflow
 ### Architecture
 
 ```
-Extraction → Staging (Blob) → Chunking → Embedding → Indexing (AI Search) → Retrieval
+Extraction → Staging → Chunking → Embedding → Indexing (Vector DB) → Retrieval
 ```
 
 ### Chunking Strategies
@@ -130,15 +130,12 @@ public async Task<SearchResult[]> SearchKnowledgeAsync(
     [Description("Search query")] string query, CancellationToken ct = default)
 {
     var embedding = await _embeddings.GenerateAsync(query, ct);
-    var results = await _searchClient.SearchAsync<KnowledgeChunk>(query,
-        new SearchOptions { VectorSearch = new() {
-            Queries = { new VectorizedQuery(embedding) { KNearestNeighborsCount = 5 } }
-        }}, ct);
-    return results.Value.GetResults().ToArray();
+    var results = await _vectorStore.SearchAsync(embedding, topK: 5, ct);
+    return results.ToArray();
 }
 ```
 
-### Why Staging in Blob Storage?
+### Why Staging?
 
 Immutability, versioning, low cost, fallback on processing bugs, audit trail.
 
@@ -168,9 +165,9 @@ Immutability, versioning, low cost, fallback on processing bugs, audit trail.
 
 ### RAG Pipeline (if applicable)
 - [ ] Data source identified and accessible
-- [ ] Staging in Blob Storage configured
+- [ ] Staging storage configured
 - [ ] Multiple chunking strategies tested and ranked
-- [ ] Azure AI Search index configured (vector + hybrid)
+- [ ] Vector DB index configured (vector + hybrid search)
 
 ### Orchestration
 - [ ] Workflow built with `AgentWorkflowBuilder`
@@ -187,7 +184,6 @@ Immutability, versioning, low cost, fallback on processing bugs, audit trail.
 ## References
 
 - [Microsoft Agent Framework](https://learn.microsoft.com/agent-framework/)
-- [Azure AI Search](https://learn.microsoft.com/azure/search/)
 - [GitHub: microsoft/agent-framework](https://github.com/microsoft/agent-framework)
 - `.wiki/ai/20-agentic-design-patterns.md` — Full 20 patterns reference