mddd-cli 4.0.2 → 4.0.4

package/bin/cli.js

@@ -16,7 +16,7 @@ const program = new Command();
 program
   .name('md')
   .description('Manager for co-located specifications for Mermaid Diagram Driven Development (MDDD)')
-  .version('4.0.2');
+  .version('4.0.4');
 
 // ==========================================
 // COMMAND: md init

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mddd-cli",
-  "version": "4.0.2",
+  "version": "4.0.4",
   "description": "Official CLI for modular, co-located, and versioned Mermaid Diagram Driven Development (MDDD).",
   "type": "module",
   "exports": "./bin/cli.js",

package/src/skills/md-audit/content.js

@@ -1,7 +1,7 @@
 export default `[ROLE: SECURITY & QUALITY AUDITOR] [STRICT CONTRACT]
 
 \`\`\`mermaid
-%% @spec-version v1.3.1
+%% @spec-version v1.3.2
 stateDiagram-v2
     [*] --> Evaluation: Quality Assessment.
     Evaluation --> MakeSpec: Co-located .spec.md.
@@ -21,7 +21,7 @@ stateDiagram-v2
         CheckCode --> EvaluatedCodeIsChaotic: Draw BOTH current chaotic logic AND ideal target refactored graph (v1.0.0 - draft)
     }
     
-    RenderTopology --> CheckDiagram: Use npx @mermaid-js/mermaid-cli to Validate Syntax
+    RenderTopology --> CheckDiagram: Use mmdc -i <path/to/diagram.md> --checkSyntax to validate diagram syntax
 
     state CheckDiagram {
         [*] --> DiagramValid: Proceed to next step

package/src/skills/md-edit/content.js

@@ -22,7 +22,7 @@ stateDiagram-v2
         [*] --> IncrementMajor: Increment Major: Bump X in X.Y.Z
     }
 
-    IncrementVersion --> CheckDiagram: Use npx @mermaid-js/mermaid-cli to Validate Syntax
+    IncrementVersion --> CheckDiagram: Use mmdc -i <path/to/diagram.md> --checkSyntax to validate diagram syntax
 
     state CheckDiagram {
         [*] --> TryRender

package/src/skills/md-new/content.js

@@ -19,7 +19,7 @@ stateDiagram-v2
 
     EvaluateContext --> GenerateBlueprint: Create .spec.md from "src/templates/spec-template.md".
     GenerateBlueprint --> FormatSpecOutput: Format blueprint into target .spec.md structure
-    FormatSpecOutput --> CheckDiagram: Use npx @mermaid-js/mermaid-cli to Validate Syntax
+    FormatSpecOutput --> CheckDiagram: Use mmdc -i <path/to/diagram.md> --checkSyntax to validate diagram syntax
 
     state CheckDiagram {
         [*] --> DiagramValid: Proceed to next step

package/system_prompt.md

@@ -217,6 +217,8 @@ The UNIVERSAL RULE is now integrated into the main processing diagram at the top
 
 **Before ANY action, the system MUST verify that a `.spec.md` file exists for the target domain/feature.** If no spec exists, only `md-new` and `md-audit` skills are allowed to proceed (to create or propose a spec). All other skills (`md-impl`, `md-edit`, etc.) are DENIED without an existing specification.
 
+Diagrams: Always use npx @mermaid-js/mermaid-cli to Validate Diagrams Syntax (Mandatory)
+
 ```mermaid
 %% @spec-version v2.0.0
 %% @protocol-version 1.0.0
@@ -232,4 +234,5 @@ stateDiagram-v2
     Allowed --> Action: Execute requested skill.
     Action --> Verify: Validate output.
     Verify --> [*]: Success.
-    Verify --> Action: Retry if criteria not met.
+    Verify --> Action: Retry if criteria not met.
+ ```