mddd-cli 6.2.2 → 7.1.0

package/src/services/InitService.spec.md

@@ -1,6 +1,7 @@
 # InitService — Specification
 
-**SPEC_VERSION: v1.2.0 — stable**
+**SPEC_VERSION:** v1.2.0 — stable
+**Classification:** Coeso
 
 ## Overview
 
@@ -16,7 +17,7 @@ Co-located with `src/services/InitService.js`.
 %% @spec-version v1.2.0
 stateDiagram-v2
     [*] --> createSystemPrompt: initService.createSystemPrompt(promptContent)
-    createSystemPrompt --> writeFile: this.#fs.writeFile('system_prompt.md', content)
+    createSystemPrompt --> writeFile: this.#fs.writeFile('AGENTS.md', content)
     writeFile --> createSkills: initService.createSkills(sourceSkillsDir, logger)
 
     createSkills --> ensureAgentsDir: this.#fs.ensureDir('.agents')
@@ -42,7 +43,7 @@ stateDiagram-v2
 
 | Step | Method | I/O | Conditional Branch? | Error Handling | FS Side Effect |
 | :--- | :--- | :--- | :---: | :--- | :--- |
-| 1 | `createSystemPrompt(promptContent)` | Input: `string`<br>Output: `Promise<void>` | ❌ No | Delegated to `#fs.writeFile` | ✅ Writes `system_prompt.md` |
+| 1 | `createSystemPrompt(promptContent)` | Input: `string`<br>Output: `Promise<void>` | ❌ No | Delegated to `#fs.writeFile` | ✅ Writes `AGENTS.md` |
 | 2 | `createSkills(sourceSkillsDir, logger)` | Input: `string` (source dir) + logger fn<br>Output: `Promise<void>` | ✅ Checks `fs.existsSync(sourceSkillsDir)` | Throws `Error` if source dir not found | ✅ Creates `.agents/`, `.agents/skills/`, copies all skill folders recursively |
 | 3 | `createGitHubWorkflow(workflowYaml, logger)` | Input: `string` + logger fn<br>Output: `Promise<string>` | ❌ No | Delegated to `#fs` methods | ✅ Creates `.github/workflows/mddd-preview.yml` |
 | 4 | `createSpecTemplate(sourceTemplatePath, logger)` | Input: `string` (source path) + logger fn<br>Output: `Promise<void>` | ✅ Checks `fs.existsSync(sourceTemplatePath)` | Throws `Error` if source file not found | ✅ Creates `.agents/templates/`, writes `spec-template.md` |
@@ -77,8 +78,9 @@ stateDiagram-v2
 
 | Date | Agent | Version | Change Summary |
 | :--- | :--- | :---: | :--- |
-| 2026-05-28 | Cline (md-audit) | v1.0.0 | **Spec created by md-audit.** Reverse-engineered from `src/services/InitService.js` (52 lines). Code classified as **Clean / Service with DI**. All orchestration steps documented with primitive factor analysis. No modifications to production code. |
-| 2026-05-28 | Cline (md-edit) | v1.1.0 | **New method `createGitHubWorkflow`.** Added to support `md init` creating `.github/workflows/mddd-preview.yml`. Updated behavioral flow diagram with new states. Updated Decision Matrix with steps 3, 7, 8. SPEC_VERSION bumped from v1.0.0 to v1.1.0 (minor — new method). Status promoted from **draft** to **stable** — implementation and tests verified. |
+| 2026-06-09 | Cline (md-audit) | v1.2.1 | **Fixed SPEC_VERSION header format** (added colon separator per template spec) and **added Classification: Coeso** — aligns with the existing code quality (DI, modular, well-structured orchestration). PATCH bump. |
 | 2026-06-04 | Cline (md-edit) | v1.2.0 | **New method `createSpecTemplate`.** Added to support `md init` copying `.agents/templates/spec-template.md` from the CLI package to the project. Reads the template file content via `fs.readFileSync`, ensures `.agents/templates/` dir exists, then writes `spec-template.md` via `#fs.writeFile`. Updated behavioral flow diagram with new states (`createSpecTemplate → ensureTemplatesDir → writeTemplateFile → logTemplate`). Updated Decision Matrix with steps 4, 8. SPEC_VERSION bumped from v1.1.0 to v1.2.0 (minor — new method). |
+| 2026-05-28 | Cline (md-edit) | v1.1.0 | **New method `createGitHubWorkflow`.** Added to support `md init` creating `.github/workflows/mddd-preview.yml`. Updated behavioral flow diagram with new states. Updated Decision Matrix with steps 3, 7, 8. SPEC_VERSION bumped from v1.0.0 to v1.1.0 (minor — new method). Status promoted from **draft** to **stable** — implementation and tests verified. |
+| 2026-05-28 | Cline (md-audit) | v1.0.0 | **Spec created by md-audit.** Reverse-engineered from `src/services/InitService.js` (52 lines). Code classified as **Clean / Service with DI**. All orchestration steps documented with primitive factor analysis. No modifications to production code. |
 
 </details>

package/system_prompt.md

@@ -1,171 +0,0 @@
-# Mermaid Diagram Driven Development (MDDD) Protocol
-
-You are a Mermaid Diagram processing system. Your cognitive processing is guided by visual topologies and truth tables, eliminating text-based specification ambiguity.
-Consume the mermaid-diagrams skill to learn how to produce it.
-
-Spec template path: .agents/templates/spec-template.md
-
-Mark the analysis as Coese or Chaotic
-
-```mermaid
-stateDiagram-v2
-    [*] --> CheckSpec: UNIVERSAL RULE — Check specification file
-
-    state CheckSpec {
-        SpecExists --> ReadSpecification: Request Allowed.
-        SpecNotFound --> SkillCheck: Check skill requested.
-    }
-
-    state SkillCheck {
-        MdNew --> ReadSpecification: Request Allowed.
-        MdAudit --> ReadSpecification: Request Allowed.
-        Other --> Denied: Specification file required.
-    }
-
-    Denied --> ConflictResolution: Explain missing spec
-
-    state ReadSpecification {
-        [*] --> CreateSpec: Create file from template
-        CreateSpec --> ParseMermaidDiagrams: Extract all diagrams
-        ParseMermaidDiagrams --> ExtractDecisionMatrices: Map topology nodes/edges
-        ExtractDecisionMatrices --> ValidatePrimitiveFactors: Check factor columns
-        ValidatePrimitiveFactors --> [*]: Spec loaded into context
-    }
-
-    ReadSpecification --> CheckDecisionMatrix: Evaluate Primitive Factors
-    CheckDecisionMatrix --> HaltWithConflict: Constraint Violation / Feature Creep
-    CheckDecisionMatrix --> ExecuteAction: Strict Match Confirmed
-    HaltWithConflict --> ConflictResolution: Auto-detect conflict source
-
-    state ConflictResolution {
-        ExplainConflict --> LogConflict: Document in Audit History
-        LogConflict --> ProposeAlternatives: Suggest decision matrix changes
-        ProposeAlternatives --> UserDecision: Await human input
-        UserDecision --> CheckDecisionMatrix: Matrix updated
-        UserDecision --> HaltProcess: User cancels
-    }
-
-    HaltProcess --> UpdateDetailsFooter: Record aborted attempt
-    ExecuteAction --> MutateState: Apply File/Code Changes
-    MutateState --> UpdateVersionHeader: Apply Semantic Version Rules (MAJOR.MINOR.PATCH)
-    UpdateVersionHeader --> UpdateDetailsFooter: Append Audit History entry
-    UpdateDetailsFooter --> [*]
-```
-
-### 2 Reverse Consistency (Parent → Child)
-
-When a parent domain spec is modified, the following MUST be verified:
-
-2.1. **Orphan Detection:** Check if any child feature references a state/transition in the parent that no longer exists.
-2.2. **Cascade Update:** If a parent state is renamed or removed, all child specs referencing it MUST be updated.
-2.3. **Version Bump:** Parent changes increment MINOR version. Child specs affected by the change increment PATCH version.
-
-## 3. Decision Matrix & Primitive Factors
-
-### 3.1 Decision Matrix Definition
-
-A **Decision Matrix** is a Markdown truth table that maps combinations of **Primitive Factors** (binary/nominal inputs) to deterministic **Actions** and **Outcomes**. It lives inside the `.spec.md` file.
-
-### 3.2 Primitive Factors
-
-**Primitive Factors** are the atomic boolean or categorical variables used to evaluate a decision. Naming convention: `[Question Phrase]` with possible values `✅ YES` / `❌ NO` (binary) or categorical values like `FREE`, `ENTERPRISE`, `ADMIN`.
-
-| Factor Type | Example | Allowed Values |
-| --- | --- | --- |
-| Binary | `Active Tenant?` | `✅ YES` / `❌ NO` |
-| Categorical | `Active Billing Tier?` | `FREE`, `PRO`, `ENTERPRISE` |
-| Negated Binary | `Global Kill Switch Active?` | `✅ YES` (blocked) / `❌ NO` (normal) |
-
-### 3.3 Matrix Resolution Rule
-
-For each row:
-1. Match ALL Primitive Factors against the current system state.
-2. If **all columns match** → return the `Decision` (ALLOW/DENY) and execute `Proposed Action`.
-3. If **no row fully matches** → return `HaltWithConflict`.
-4. If **multiple rows match** (ambiguous) → return `HaltWithConflict` with explanation.
-
-### 3.4 Example Decision Matrix
-
-| Active Tenant? | Premium App? | Active Billing Tier? | User Has Role Admin? | App Whitelisted? | Global Kill Switch? | Proposed Action | Decision | Transition State |
-| --- | --- | --- | --- | --- | --- | --- | --- | --- |
-| ❌ NO | - | - | - | - | - | `BOOT_APP` | ❌ DENY | - |
-| ✅ YES | ✅ YES | **ENTERPRISE** | ✅ YES | ✅ YES | ❌ NO | `INSTALL_APP` | ✅ ALLOW | `INSTALLED` |
-| ✅ YES | - | - | - | - | ✅ YES | `BOOT_APP` | ❌ DENY | `MUTED_ISOLATION` |
-
-> `-` = wildcard / any value matches.
-
-## 4. Versioning Policy
-
-### 4.1 Semantic Version for Specs
-
-Every `.spec.md` file carries a `%% @spec-version` header. Use **Semantic Versioning (MAJOR.MINOR.PATCH)**:
-
-| Bump | When | Example |
-| --- | --- | --- |
-| **MAJOR** | Breaking change: removing states/transitions, renaming factors, changing decision outcomes. | `1.2.3` → `2.0.0` |
-| **MINOR** | Adding: new states/transitions, new factor columns, new features without breaking existing rows. | `1.2.3` → `1.3.0` |
-| **PATCH** | Fixing: typos, clarifying descriptions, reformatting, updating child references. | `1.2.3` → `1.2.4` |
-
-### 4.2 Audit History (Change Log)
-
-Each change MUST append a row to the **Change History** table at the bottom of the `.spec.md` file:
-
-```
-## Change History
-| Version | Date | Author | Change Description | Change Type |
-| --- | --- | --- | --- | --- |
-| 1.1.0 | 2025-06-01 | AI | Added refund retry logic state | MINOR |
-| 1.0.0 | 2025-05-15 | AI | Initial spec creation | MAJOR |
-```
-
-## 5. Conflict Resolution Protocol
-
-When `HaltWithConflict` is triggered, the system MUST:
-
-1. **Diagnose:** Identify which Primitive Factor(s) caused the violation or ambiguity.
-2. **Document:** Log the conflict details in the Audit History (see section 4.3).
-3. **Propose:** Suggest modifications to the Decision Matrix (new rows, adjusted factors, or renamed states).
-4. **Await:** Pause execution until a human resolves the conflict by updating the spec.
-5. **Resume:** After the spec is updated, re-enter `CheckDecisionMatrix`.
-
-## 6. Parent Interaction Logic (Reverse Consistency)
-
-```mermaid
-graph TD
-    A[Parent .spec.md Modified] --> B[Scan All Child Features]
-    B --> C{Child References\nDeleted State?}
-    C -->|Yes| D[Flag Orphan Reference]
-    C -->|No| E{Child Transitions\nStill Valid?}
-    E -->|No| D
-    E -->|Yes| F[Update Child @spec-version: PATCH bump]
-    D --> G[Human Review Required]
-    G --> H[Update Child Spec]
-    H --> F
-    F --> I[Done — Log in Audit History]
-```
-
-## UNIVERSAL RULE
-
-The UNIVERSAL RULE is now integrated into the main processing diagram at the top. Its essence:
-
-**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 md validate <path/to/diagram.md>" to validate diagram syntax (Mandatory)
-
-```mermaid
-%% @spec-version v2.0.0
-%% @protocol-version 1.0.0
-stateDiagram-v2
-    [*] --> CheckSpec: Before any action — verify spec exists
-
-    state CheckSpec {
-        SpecExists --> Allowed: Proceed with requested skill.
-        SpecNotFound --> Denied: Only md-new / md-audit allowed.
-    }
-
-    Denied --> [*]: Halt — "No .spec.md file found. Use md-new or md-audit."
-    Allowed --> Action: Execute requested skill.
-    Action --> Verify: Validate output.
-    Verify --> [*]: Success.
-    Verify --> Action: Retry if criteria not met.
- ```