fix(plugins): address PR 222 review feedback

- Correct generator script name references (build-cc-plugin.py → build-plugins.py)
- Fix glossary plan paths to match actual phase-specific locations
- Escape nested mermaid fence in content-validation example
- Update Cursor README orchestrator path to .cursor/rules/ prefix

Canonical sources updated; plugins regenerated via scripts/build-plugins.py.

Author: Ray Smets

aidlc-rules/aws-aidlc-rule-details/common/content-validation.md

@@ -38,7 +38,7 @@
 ```
 
 ### Implementation Pattern
-```markdown
+````markdown
 ## Workflow Visualization
 
 ### Mermaid Diagram (if syntax valid)
@@ -53,6 +53,7 @@ Phase 1: INCEPTION
 - Stage 2: Requirements Analysis (COMPLETED)
 [continue with text representation]
 ```
+````
 
 ## General Content Validation
 

aidlc-rules/aws-aidlc-rule-details/common/terminology.md

@@ -165,7 +165,7 @@ Examples (these are internal sub-steps within a single stage, not separate stage
 
 ### Plans
 Documents with checkboxes and questions that guide execution.
-- Located in `aidlc-docs/plans/`
+- Located in phase-specific plan directories such as `aidlc-docs/inception/plans/` and `aidlc-docs/construction/plans/`
 - Examples: `story-generation-plan.md`, `unit-of-work-plan.md`
 
 ### Artifacts

plugins/claude-code-aidlc/README.md

@@ -7,7 +7,7 @@ commands, and progressive-disclosure skills.
 
 **Version**: 0.1.8
 **Source of truth**: `aidlc-rules/` in this repository
-**Generator**: `scripts/build-cc-plugin.py`
+**Generator**: `scripts/build-plugins.py`
 
 > This directory is **generated**. Do not edit files here directly — edit the
 > canonical sources in `aidlc-rules/` and run the generator. CI enforces sync.
@@ -119,7 +119,7 @@ Do not edit files in this directory directly. Edit the canonical source in
 `aidlc-rules/` at the repository root, then regenerate:
 
 ```bash
-python scripts/build-cc-plugin.py
+python scripts/build-plugins.py
 ```
 
 CI (`plugin-sync` job) runs the generator on every PR and fails if the

plugins/claude-code-aidlc/skills/aidlc-common/references/common/content-validation.md

@@ -38,7 +38,7 @@
 ```
 
 ### Implementation Pattern
-```markdown
+````markdown
 ## Workflow Visualization
 
 ### Mermaid Diagram (if syntax valid)
@@ -53,6 +53,7 @@ Phase 1: INCEPTION
 - Stage 2: Requirements Analysis (COMPLETED)
 [continue with text representation]
 ```
+````
 
 ## General Content Validation
 

plugins/claude-code-aidlc/skills/aidlc-common/references/common/terminology.md

@@ -165,7 +165,7 @@ Examples (these are internal sub-steps within a single stage, not separate stage
 
 ### Plans
 Documents with checkboxes and questions that guide execution.
-- Located in `aidlc-docs/plans/`
+- Located in phase-specific plan directories such as `aidlc-docs/inception/plans/` and `aidlc-docs/construction/plans/`
 - Examples: `story-generation-plan.md`, `unit-of-work-plan.md`
 
 ### Artifacts

plugins/cursor-aidlc/README.md

@@ -45,7 +45,7 @@ This works but is less clean than Option 1.
 
 ## Using the Rules
 
-Once installed, the `aidlc/aidlc-orchestrator.mdc` rule is set to
+Once installed, the `.cursor/rules/aidlc-orchestrator.mdc` rule is set to
 `alwaysApply: true`, so Cursor loads it on every interaction. To start a
 workflow, just describe the work:
 

plugins/cursor-aidlc/rules/common/content-validation.mdc

@@ -43,7 +43,7 @@ alwaysApply: false
 ```
 
 ### Implementation Pattern
-```markdown
+````markdown
 ## Workflow Visualization
 
 ### Mermaid Diagram (if syntax valid)
@@ -58,6 +58,7 @@ Phase 1: INCEPTION
 - Stage 2: Requirements Analysis (COMPLETED)
 [continue with text representation]
 ```
+````
 
 ## General Content Validation
 

plugins/cursor-aidlc/rules/common/terminology.mdc

@@ -170,7 +170,7 @@ Examples (these are internal sub-steps within a single stage, not separate stage
 
 ### Plans
 Documents with checkboxes and questions that guide execution.
-- Located in `aidlc-docs/plans/`
+- Located in phase-specific plan directories such as `aidlc-docs/inception/plans/` and `aidlc-docs/construction/plans/`
 - Examples: `story-generation-plan.md`, `unit-of-work-plan.md`
 
 ### Artifacts

scripts/build-plugins.py

@@ -80,7 +80,7 @@ def plugin_readme(version: str) -> str:
 
 **Version**: {version}
 **Source of truth**: `aidlc-rules/` in this repository
-**Generator**: `scripts/build-cc-plugin.py`
+**Generator**: `scripts/build-plugins.py`
 
 > This directory is **generated**. Do not edit files here directly — edit the
 > canonical sources in `aidlc-rules/` and run the generator. CI enforces sync.
@@ -192,7 +192,7 @@ def plugin_readme(version: str) -> str:
 `aidlc-rules/` at the repository root, then regenerate:
 
 ```bash
-python scripts/build-cc-plugin.py
+python scripts/build-plugins.py
 ```
 
 CI (`plugin-sync` job) runs the generator on every PR and fails if the
@@ -1242,7 +1242,7 @@ def cursor_plugin_readme(version: str) -> str:
 
 ## Using the Rules
 
-Once installed, the `aidlc/aidlc-orchestrator.mdc` rule is set to
+Once installed, the `.cursor/rules/aidlc-orchestrator.mdc` rule is set to
 `alwaysApply: true`, so Cursor loads it on every interaction. To start a
 workflow, just describe the work: