@polymorphism-tech/morph-spec 8.10.0 → 8.11.0

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:** 8.10.0  
+**Version:** 8.11.0  
 **Requires:** Node.js 22+, Claude Code
 
 ---
@@ -368,4 +368,4 @@ Code generated by morph-spec (contracts, templates, implementation output) belon
 
 ---
 
-*morph-spec v8.10.0 by [Polymorphism Tech](https://polymorphism.tech)*
+*morph-spec v8.11.0 by [Polymorphism Tech](https://polymorphism.tech)*

package/claude-plugin.json

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

@@ -185,4 +185,4 @@ Never edited directly — go through CLI commands or `morph-spec update` instead
 
 ---
 
-*morph-spec v8.10.0 by Polymorphism Tech*
+*morph-spec v8.11.0 by Polymorphism Tech*

package/docs/QUICKSTART.md

@@ -249,4 +249,4 @@ morph-spec doctor
 
 ---
 
-*morph-spec v8.10.0 by Polymorphism Tech*
+*morph-spec v8.11.0 by Polymorphism Tech*

package/framework/skills/core/create-umbraco-lp/SKILL.md

@@ -4,7 +4,7 @@ description: Guia a criação de uma landing page nova ponta-a-ponta a partir do
 version: core
 when-to-invoke: ao iniciar um novo projeto de LP com o template Umbraco genérico
 user-invokable: true
-cliVersion: "8.10.0"
+cliVersion: "8.11.0"
 ---
 
 # create-umbraco-lp

package/framework/skills/core/migrate-lp-to-umbraco/SKILL.md

@@ -4,7 +4,7 @@ description: Migra uma landing page existente (React/Vite, Next.js estático ou
 version: core
 when-to-invoke: ao receber instrução "use /migrate-lp-to-umbraco {projeto}" do usuário, ou quando o usuário descrever necessidade de migrar uma LP para Umbraco
 user-invokable: true
-cliVersion: "8.10.0"
+cliVersion: "8.11.0"
 ---
 
 # migrate-lp-to-umbraco

package/framework/skills/core/morph-apply/SKILL.md

@@ -4,7 +4,7 @@ description: Orquestra a execução autônoma de tasks de uma feature morph-spec
 version: core
 when-to-invoke: após Gate 2 aprovado, ao receber instrução "use /morph-apply" ou "implementar feature"
 user-invokable: true
-cliVersion: "8.10.0"
+cliVersion: "8.11.0"
 ---
 
 # morph-apply

package/framework/skills/core/morph-brainstorming/SKILL.md

@@ -4,7 +4,7 @@ description: Entende o negócio, os usuários e a arquitetura antes de qualquer
 version: core
 when-to-invoke: ao receber um novo request de feature, antes de morph-plan
 user-invokable: true
-cliVersion: "8.10.0"
+cliVersion: "8.11.0"
 ---
 
 # morph-brainstorming

package/framework/skills/core/morph-eval/SKILL.md

@@ -4,7 +4,7 @@ description: Avalia a qualidade de uma tarefa ou fase com rubricas graduadas 0-1
 version: core
 when-to-invoke: ao completar uma tarefa ou ao finalizar uma fase de implementação
 user-invokable: false
-cliVersion: "8.10.0"
+cliVersion: "8.11.0"
 ---
 
 # morph-eval

package/framework/skills/core/morph-hotfix/SKILL.md

@@ -4,7 +4,7 @@ description: ADW cirúrgico de hotfix — resolve uma queda/bug crítico de prod
 version: core
 when-to-invoke: ao receber "/morph-hotfix {feature}", quando a morph-proposal classifica o pedido como workType hotfix (Passo 0), ou o usuário diz "produção caiu / hotfix / urgente"
 user-invokable: true
-cliVersion: "8.10.0"
+cliVersion: "8.11.0"
 ---
 
 # morph-hotfix

package/framework/skills/core/morph-implement/SKILL.md

@@ -4,7 +4,7 @@ description: Guia a execução de cada tarefa de implementação com standard e
 version: core
 when-to-invoke: ao iniciar cada task de implementação listada em tasks.json
 user-invokable: false
-cliVersion: "8.10.0"
+cliVersion: "8.11.0"
 ---
 
 # morph-implement

package/framework/skills/core/morph-plan/SKILL.md

@@ -4,7 +4,7 @@ description: Guia a produção dos artefatos de planejamento de uma feature (use
 version: core
 when-to-invoke: ao iniciar a fase plan de uma feature, após o Gate 1 (proposal aprovado)
 user-invokable: true
-cliVersion: "8.10.0"
+cliVersion: "8.11.0"
 ---
 
 # morph-plan

package/framework/skills/core/morph-proposal/SKILL.md

@@ -4,7 +4,7 @@ description: Orquestra a fase de proposta+plano de uma feature morph-spec. Encad
 version: core
 when-to-invoke: ao receber instrução "use /morph-proposal" do usuário, ou ao iniciar uma nova feature
 user-invokable: true
-cliVersion: "8.10.0"
+cliVersion: "8.11.0"
 ---
 
 # morph-proposal

package/framework/skills/core/morph-review/SKILL.md

@@ -4,7 +4,7 @@ description: Conduz a fase de revisão e produz o review-report.md para o Gate 3
 version: core
 when-to-invoke: ao iniciar a fase review, após todas as tasks de tasks.json estarem com status `done`
 user-invokable: true
-cliVersion: "8.10.0"
+cliVersion: "8.11.0"
 ---
 
 # morph-review

package/framework/skills/core/morph-stack-scan/SKILL.md

@@ -4,7 +4,7 @@ description: Varre o codebase existente, detecta stack atual, compara com o stac
 version: core
 when-to-invoke: ao iniciar uma feature em projeto brownfield (codebase já existente)
 user-invokable: true
-cliVersion: "8.10.0"
+cliVersion: "8.11.0"
 ---
 
 # morph-stack-scan

package/framework/skills/core/morph-standards/SKILL.md

@@ -4,7 +4,7 @@ description: Localiza e carrega um standard específico do STANDARDS.json sob de
 version: core
 when-to-invoke: quando precisar consultar um standard específico durante a implementação
 user-invokable: true
-cliVersion: "8.10.0"
+cliVersion: "8.11.0"
 ---
 
 # morph-standards

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@polymorphism-tech/morph-spec",
-  "version": "8.10.0",
+  "version": "8.11.0",
   "description": "MORPH-SPEC: NLH (Natural Language Harness) for spec-driven development with Claude Code",
   "keywords": [
     "claude-code",

package/src/commands/mcp/mcp-setup.js

@@ -34,8 +34,13 @@ import { detectProject } from '../../lib/detectors/index.js';
 /**
  * Detect the current project's stack.
  * Prefers .morph/config/config.json (set during morph-spec init) over filesystem re-detection.
+ *
+ * Exported for testing: the stack decides which MCPs are relevant, and it is
+ * the one branch here worth pinning — `.morph/config/config.json` is the only
+ * place a compound stack (`dotnet-nextjs`) survives, since filesystem
+ * re-detection collapses it to whichever half it notices first.
  */
-async function detectStack(targetPath) {
+export async function detectStack(targetPath) {
   // 1. Prefer the authoritative config (handles compound stacks like nextjs+dotnet)
   try {
     const configPath = join(targetPath, '.morph', 'config', 'config.json');

package/src/core/templates/template-registry.js

@@ -151,65 +151,6 @@ export function getRequiredTemplates(stackId = null, projectPath = null) {
   return templates;
 }
 
-/**
- * Get infrastructure templates for a specific stack.
- *
- * @param {string} stackId - Stack identifier
- * @param {string} [projectPath] - Optional project path
- * @returns {Array} Infrastructure template array
- */
-export function getInfrastructureTemplates(stackId, projectPath = null) {
-  const registry = loadTemplateRegistry(projectPath);
-  return registry.infrastructureTemplates?.[stackId] || [];
-}
-
-/**
- * Get contract templates for a specific stack.
- *
- * @param {string} stackId - Stack identifier
- * @param {string} [projectPath] - Optional project path
- * @returns {Array} Contract template array
- */
-export function getContractTemplates(stackId, projectPath = null) {
-  const registry = loadTemplateRegistry(projectPath);
-  return registry.contractTemplates?.[stackId] || [];
-}
-
-/**
- * Get integration templates for a specific stack.
- *
- * @param {string} stackId - Stack identifier
- * @param {string} [projectPath] - Optional project path
- * @returns {Array} Integration template array
- */
-export function getIntegrationTemplates(stackId, projectPath = null) {
-  const registry = loadTemplateRegistry(projectPath);
-  return registry.integrationTemplates?.[stackId] || [];
-}
-
-/**
- * Get SaaS templates for a specific stack.
- *
- * @param {string} stackId - Stack identifier
- * @param {string} [projectPath] - Optional project path
- * @returns {Array} SaaS template array
- */
-export function getSaasTemplates(stackId, projectPath = null) {
-  const registry = loadTemplateRegistry(projectPath);
-  return registry.saasTemplates?.[stackId] || [];
-}
-
-/**
- * Get example templates.
- *
- * @param {string} [projectPath] - Optional project path
- * @returns {Array} Example template array
- */
-export function getExampleTemplates(projectPath = null) {
-  const registry = loadTemplateRegistry(projectPath);
-  return registry.exampleTemplates || [];
-}
-
 /**
  * Search templates by keyword (searches id, name, description).
  *

package/src/dashboard/scanner/hooks-scanner.js

@@ -1,5 +1,6 @@
 import { readFileSync, readdirSync, existsSync } from 'fs';
-import { join, basename, dirname } from 'path';
+import { join, basename } from 'path';
+import { getHookDefinitions } from '../../utils/hooks-installer.js';
 
 function findJsFiles(dir) {
   const results = [];
@@ -25,17 +26,74 @@ function extractImports(source) {
   return imports;
 }
 
+/**
+ * Claude Code event name → the kebab-case key the Hook Inspector groups by.
+ * `pre-compact` and `teammate-idle` have no MORPH hooks — those nodes render
+ * empty on purpose.
+ */
+const EVENT_KEYS = {
+  SessionStart: 'session-start',
+  UserPromptSubmit: 'user-prompt',
+  PreToolUse: 'pre-tool-use',
+  PostToolUse: 'post-tool-use',
+  Stop: 'stop',
+  SubagentStop: 'stop',
+  PreCompact: 'pre-compact',
+};
+
+/**
+ * Build filename → [{ event, matcher }] from the installer's MORPH_HOOKS.
+ *
+ * The event is NOT derivable from the path. Before the v4→v5 migration the
+ * hooks sat in per-event folders, so `basename(dirname(file))` produced the
+ * event key; the migration flattened everything into `core/`, and from then on
+ * every hook reported `event: 'core'`. Nothing crashed — the Inspector groups
+ * by event, found no key it knew, and rendered every node empty. Twelve hooks,
+ * zero shown.
+ *
+ * `getHookDefinitions()` is the single source of truth (the same array the
+ * installer writes into settings.local.json), so the registration and the
+ * drawing can no longer disagree.
+ */
+export function hookRegistrations(definitions = getHookDefinitions()) {
+  const byFile = new Map();
+  for (const def of definitions) {
+    const key = EVENT_KEYS[def.event];
+    if (!key) continue;
+    for (const h of def.hooks || []) {
+      const file = basename(String(h.command || '').trim());
+      if (!file.endsWith('.js')) continue;
+      if (!byFile.has(file)) byFile.set(file, []);
+      byFile.get(file).push({ event: key, rawEvent: def.event, matcher: def.matcher || null });
+    }
+  }
+  return byFile;
+}
+
 export function scanHooks(frameworkDir) {
   const hooksDir = join(frameworkDir, 'hooks', 'claude-code');
   if (!existsSync(hooksDir)) return [];
-  return findJsFiles(hooksDir).map(filePath => {
+
+  const registrations = hookRegistrations();
+
+  return findJsFiles(hooksDir).flatMap(filePath => {
     const source = readFileSync(filePath, 'utf8');
-    return {
-      event: basename(dirname(filePath)),
+    const filename = basename(filePath);
+    const base = {
       name: basename(filePath, '.js'),
-      filename: basename(filePath),
-      source, imports: extractImports(source),
+      filename,
+      source,
+      imports: extractImports(source),
       description: extractJsDocDescription(source),
     };
+
+    // One entry per (file × event): telemetry-log is registered on both
+    // PostToolUse and UserPromptSubmit, and must show under both.
+    const regs = registrations.get(filename);
+    if (!regs || regs.length === 0) {
+      // On disk but never registered — real dead weight, and worth seeing.
+      return [{ ...base, event: 'unregistered', matcher: null }];
+    }
+    return regs.map(r => ({ ...base, event: r.event, rawEvent: r.rawEvent, matcher: r.matcher }));
   });
 }

package/src/dashboard/scanner/standards-scanner.js

@@ -7,9 +7,21 @@ export function scanStandards(frameworkDir, agents) {
   const sJson = JSON.parse(readFileSync(standardsJsonPath, 'utf8'));
   const refMap = {};
   for (const agent of agents) {
-    for (const std of agent.standards) {
-      if (!refMap[std.id]) refMap[std.id] = [];
-      refMap[std.id].push({ agentId: agent.id, scope: std.scope, priority: std.priority });
+    for (const std of agent.standards || []) {
+      // agents.json stores standards as plain id STRINGS. Reading `std.id` off
+      // a string yields undefined, so every reference piled into refMap
+      // [undefined] and the lookup below missed all 60 — the Standards graph
+      // drew standards with no agent edge at all. The object form is the v4
+      // shape (`{ id, scope, priority }`); still accepted so a mixed or
+      // restored agents.json does not silently lose edges again.
+      const id = typeof std === 'string' ? std : std?.id;
+      if (!id) continue;
+      if (!refMap[id]) refMap[id] = [];
+      refMap[id].push({
+        agentId: agent.id,
+        scope: typeof std === 'string' ? null : (std.scope ?? null),
+        priority: typeof std === 'string' ? null : (std.priority ?? null),
+      });
     }
   }
   const list = sJson.standards.map(std => {

package/src/lib/stack/stack-profile.js

@@ -9,7 +9,6 @@ import { join } from 'path';
  * @property {boolean} isDotnet
  * @property {boolean} isNextjs
  * @property {string[]} defaultValidators
- * @property {string[]} checkpointValidators
  * @property {string|null} buildCommand
  */
 
@@ -21,19 +20,16 @@ const PROFILES = {
   dotnet: {
     isDotnet: true, isNextjs: false,
     defaultValidators: ['architecture', 'packages'],
-    checkpointValidators: ['architecture', 'packages', 'design-system', 'security'],
     buildCommand: 'dotnet build --no-restore',
   },
   nextjs: {
     isDotnet: false, isNextjs: true,
     defaultValidators: ['nextjs-component'],
-    checkpointValidators: ['nextjs-component', 'css'],
     buildCommand: 'npx tsc --noEmit',
   },
   empty: {
     isDotnet: false, isNextjs: false,
     defaultValidators: [],
-    checkpointValidators: [],
     buildCommand: null,
   },
 };
@@ -57,7 +53,6 @@ function mergeProfiles(profiles) {
     isDotnet: profiles.some((p) => p.isDotnet),
     isNextjs: profiles.some((p) => p.isNextjs),
     defaultValidators: [...new Set(profiles.flatMap((p) => p.defaultValidators))],
-    checkpointValidators: [...new Set(profiles.flatMap((p) => p.checkpointValidators))],
     buildCommand: profiles.map((p) => p.buildCommand).find(Boolean) ?? null,
   };
 }

package/src/lib/validators/validation-runner.js

@@ -16,7 +16,11 @@ import { aggregateScores, loadRubric } from './score-aggregator.js';
 
 /**
  * Heavy validators skipped in 'light' mode (checkpoint-only).
- * Light mode runs only spec, content, and stack-specific lightweight validators.
+ *
+ * What light mode actually leaves behind is whatever the stack contributes that
+ * is NOT in this set — in practice `contrast` and `nextjs-component`. There are
+ * no `spec` or `content` validators; the switch in runSingleValidator has no
+ * case for either, and the old comment here promised both.
  */
 const HEAVY_VALIDATORS = new Set([
   'architecture', 'packages', 'contract-compliance',
@@ -49,27 +53,38 @@ export async function runValidation(projectPath, featureName, options = {}) {
     validators: {} // No validator-specific constraints
   };
 
-  // Determine which validators to run
-  const validatorIds = options.validators || detectValidators(projectPath);
+  // Determine which validators to run.
+  // COPY: the mode filter below used to splice in place, and when the caller
+  // passed `options.validators` that array WAS this array — so a light run
+  // emptied the caller's own list, and running the same list twice validated
+  // less the second time.
+  const detected = options.validators || detectValidators(projectPath);
+  let validatorIds = [...detected];
 
   // Filter by mode: 'light' skips heavy validators, 'full' (default) runs all
   const mode = options.mode || 'full';
+  const droppedByMode = [];
   if (mode === 'light') {
-    const beforeCount = validatorIds.length;
-    for (let i = validatorIds.length - 1; i >= 0; i--) {
-      if (HEAVY_VALIDATORS.has(validatorIds[i])) {
-        validatorIds.splice(i, 1);
-      }
-    }
+    validatorIds = validatorIds.filter(id => {
+      if (HEAVY_VALIDATORS.has(id)) { droppedByMode.push(id); return false; }
+      return true;
+    });
   }
 
   // Merge constraint-enabled validators
   validatorIds.push(...constraints.enabledValidators);
 
   if (validatorIds.length === 0) {
-    result.summary = 'No validators ran — no validators configured for this stack';
-    console.log(chalk.gray('\n  ℹ️  No validators configured for this stack'));
+    // Say which of the two it is. On a pure `dotnet` project every default
+    // validator is heavy, so a light run legitimately runs none — but the old
+    // message blamed the stack ("no validators configured"), which reads as
+    // "your stack has nothing to check" when the full run has two.
+    result.summary = droppedByMode.length > 0
+      ? `No validators ran — light mode skipped ${droppedByMode.length} heavy validator(s): ${droppedByMode.join(', ')}`
+      : 'No validators ran — no validators configured for this stack';
+    console.log(chalk.gray(`\n  ℹ️  ${result.summary.replace('No validators ran — ', '')}`));
     result._skipReason = result.summary;
+    result._droppedByMode = droppedByMode;
     return result;
   }
 
@@ -87,7 +102,12 @@ export async function runValidation(projectPath, featureName, options = {}) {
     // Positive check on isDotnet (contract-compliance is a VSA/.NET concern) —
     // NOT `!isNextjs`, which used to wrongly suppress it for a compound
     // "dotnet-nextjs" stack that has a .NET backend but is ALSO isNextjs.
-    if (existsSync(contractsPath) && _profileForContracts.isDotnet) {
+    // `mode: 'light'` has to hold here too. This push sits AFTER the mode
+    // filter, so contract-compliance — which is in HEAVY_VALIDATORS — used to
+    // slip into every light run that had a contracts file, making light mode
+    // heavier than declared on exactly the compound stacks it matters for.
+    const contractsIsHeavyAndSkipped = mode === 'light' && HEAVY_VALIDATORS.has('contract-compliance');
+    if (existsSync(contractsPath) && _profileForContracts.isDotnet && !contractsIsHeavyAndSkipped) {
       validatorIds.push('contract-compliance');
     }
   }

package/src/lib/validators/content/content-validator.js

@@ -1,89 +0,0 @@
-import { readFileSync, existsSync } from 'fs';
-
-/**
- * Content Validator - Validates structure and content of output files
- *
- * Ensures spec.md, tasks.json, and other outputs have required sections
- * and proper structure before allowing phase transitions.
- */
-
-/**
- * Validate spec.md structure
- * @param {string} specPath - Path to spec.md file
- * @returns {Object} Validation result
- */
-export function validateSpecContent(specPath) {
-  if (!existsSync(specPath)) {
-    return {
-      valid: false,
-      missing: ['File does not exist'],
-      errors: ['Spec file not found at: ' + specPath]
-    };
-  }
-
-  const content = readFileSync(specPath, 'utf8');
-
-  // Required sections (flexible regex handles numbered variants like '## 1. Overview')
-  const requiredSections = [
-    { label: '## Overview',                pattern: /^##\s+(?:\d+\.?\s+)?Overview/i },
-    { label: '## Functional Requirements', pattern: /^##\s+(?:\d+\.?\s+)?Functional Requirements/i },
-    { label: '## Technical',              pattern: /^##\s+(?:\d+\.?\s+)?Technical/i },
-    { label: '## Data Model',             pattern: /^##\s+(?:\d+\.?\s+)?Data Model/i },
-  ];
-
-  const lines = content.split('\n');
-  const missing = requiredSections.filter(s =>
-    !lines.some(line => s.pattern.test(line))
-  );
-
-  // Additional quality checks
-  const errors = [];
-  const warnings = [];
-
-  // Missing sections are warnings, not errors — not every spec needs all sections
-  // (e.g., frontend-only features may not have Data Model, CLI tools may not have Technical Architecture)
-  if (missing.length > 0) {
-    missing.forEach(s => {
-      warnings.push(`Missing recommended section: ${s.label}`);
-    });
-  }
-
-  // Check minimum content length
-  if (content.length < 500) {
-    warnings.push('Spec seems very short (< 500 characters). Consider adding more detail.');
-  }
-
-  // Check for placeholder text that should be replaced
-  const placeholders = ['TODO', 'TBD', 'PLACEHOLDER', '{{'];
-  placeholders.forEach(placeholder => {
-    if (content.includes(placeholder)) {
-      warnings.push(`Spec contains "${placeholder}" - ensure all placeholders are replaced`);
-    }
-  });
-
-  // Check for anti-patterns mentioned in the plan
-  if (content.toLowerCase().includes('manual azure portal')) {
-    errors.push(
-      'Spec mentions manual Azure portal creation. ' +
-      'All infrastructure must be defined in Bicep (Infrastructure as Code).'
-    );
-  }
-
-  if (content.toLowerCase().includes('create resource manually')) {
-    errors.push(
-      'Spec mentions manual resource creation. ' +
-      'Use IaC (Bicep) for all infrastructure resources.'
-    );
-  }
-
-  return {
-    valid: errors.length === 0,
-    missing,
-    errors,
-    warnings,
-    sections: {
-      required: requiredSections.length,
-      found: requiredSections.length - missing.length
-    }
-  };
-}

package/src/lib/validators/content/index.js

@@ -1,7 +0,0 @@
-/**
- * Content Validators
- *
- * Content and spec validation.
- */
-
-export * from './content-validator.js';