@documentation-robotics/cli 0.1.7 → 0.1.9

package/dist/integrations/claude_code/skills/dr_engineering_guide/SKILL.md

@@ -49,7 +49,7 @@ When ambiguous, ask: "Are you about to start building this, currently building i
 ### Checklist to Work Through
 
 **1. Layer Coverage Check**
-Map the proposed change to the 12-layer model:
+Map the proposed change to the 13-layer model:
 
 - Which layers are touched? (List them explicitly)
 - Which layers are conspicuously absent? (e.g., a new service with no APM or security)
@@ -155,7 +155,7 @@ dr schema node <spec-node-id>
 "Your service should match the ApplicationService spec type, which means: single responsibility, exposes at most one API contract, references exactly one business service."
 
 **5. Suggest Implementation Order**
-Based on the 12-layer model, suggest bottom-up implementation:
+Based on the 13-layer model, suggest bottom-up implementation:
 
 1. Data model / data store first (schema before logic)
 2. Application service next (business logic)

package/dist/integrations/github_copilot/agents/dr-advisor.md

@@ -16,7 +16,7 @@ You are an expert advisor for **Documentation Robotics** end users, specializing
    - Best practices for naming, organization, and structure
 
 2. **Concept Explanation**: Provide clear explanations of:
-   - The 12-layer architecture and what each layer represents
+   - The 13-layer architecture and what each layer represents
    - Cross-layer relationship patterns (A, B, C, D)
    - Intra-layer relationship types (34 semantic predicates)
    - The purpose and benefits of changesets
@@ -96,7 +96,7 @@ You are an expert advisor for **Documentation Robotics** end users, specializing
 
 **Be Precise**: Use correct DR terminology
 
-- 12 layers, not "tiers" or "levels"
+- 13 layers, not "tiers" or "levels"
 - "Relationships" not "links" (post-v0.8.1)
 - Specific entity types (not generic terms)
 - Correct field names and formats
@@ -116,21 +116,22 @@ You are an expert advisor for **Documentation Robotics** end users, specializing
 
 ## Key Knowledge Areas
 
-### The 12-Layer Architecture
+### The 13-Layer Architecture
 
 ```
 01. Motivation     - Goals, principles, requirements, constraints (WHY)
 02. Business       - Capabilities, processes, services, actors (WHAT)
-03. Security       - Roles, policies, threats, controls (WHO/PROTECTION)
-04. Application    - Components, services, interfaces (HOW)
-05. Technology     - Platforms, frameworks, infrastructure (WITH)
-06. API            - OpenAPI 3.0.3 specifications (CONTRACTS)
-07. Data Model     - JSON Schema Draft 7 structures (STRUCTURE)
-08. Data Store      - SQL DDL persistence (STORAGE)
-09. UX             - Three-Tier UI architecture (EXPERIENCE)
-10. Navigation     - Multi-modal routing (FLOW)
-11. APM            - OpenTelemetry observability (MONITORING)
-12. Testing        - ISP coverage model (VERIFICATION)
+03. Product        - Personas, capabilities, features, workflows, milestones (PRODUCT)
+04. Security       - Roles, policies, threats, controls (WHO/PROTECTION)
+05. Application    - Components, services, interfaces (HOW)
+06. Technology     - Platforms, frameworks, infrastructure (WITH)
+07. API            - OpenAPI 3.0.3 specifications (CONTRACTS)
+08. Data Model     - JSON Schema Draft 7 structures (STRUCTURE)
+09. Data Store      - SQL DDL persistence (STORAGE)
+10. UX             - Three-Tier UI architecture (EXPERIENCE)
+11. Navigation     - Multi-modal routing (FLOW)
+12. APM            - OpenTelemetry observability (MONITORING)
+13. Testing        - ISP coverage model (VERIFICATION)
 ```
 
 ### Cross-Layer Relationship Patterns

package/dist/integrations/github_copilot/agents/dr-architect.md

@@ -46,23 +46,24 @@ Unlike specialized agents that do one thing, you understand the **full picture**
 
 ## Knowledge Base: DR Specification v0.8.1
 
-### The 12-Layer Architecture
+### The 13-Layer Architecture
 
-Documentation Robotics models systems across 12 distinct architectural layers:
+Documentation Robotics models systems across 13 distinct architectural layers:
 
 ```
 01. Motivation     - WHY (goals, principles, requirements, constraints)
 02. Business       - WHAT (capabilities, processes, services, actors)
-03. Security       - WHO/PROTECTION (actors, roles, policies, threats)
-04. Application    - HOW (components, services, interfaces, events)
-05. Technology     - WITH (platforms, frameworks, infrastructure)
-06. API            - CONTRACTS (OpenAPI 3.0.3 specs - 26 entity types)
-07. Data Model     - STRUCTURE (JSON Schema Draft 7 - 17 entity types)
-08. Data Store      - PERSISTENCE (SQL DDL - 10 entity types)
-09. UX             - EXPERIENCE (Three-Tier Architecture - 26 entity types)
-10. Navigation     - FLOW (Multi-Modal routing - 10 entity types)
-11. APM            - OBSERVE (OpenTelemetry 1.0+ - 14 entity types)
-12. Testing        - VERIFY (ISP Coverage Model - 17 entity types)
+03. Product        - PRODUCT (personas, capabilities, features, workflows, milestones)
+04. Security       - WHO/PROTECTION (actors, roles, policies, threats)
+05. Application    - HOW (components, services, interfaces, events)
+06. Technology     - WITH (platforms, frameworks, infrastructure)
+07. API            - CONTRACTS (OpenAPI 3.0.3 specs - 26 entity types)
+08. Data Model     - STRUCTURE (JSON Schema Draft 7 - 17 entity types)
+09. Data Store      - PERSISTENCE (SQL DDL - 10 entity types)
+10. UX             - EXPERIENCE (Three-Tier Architecture - 26 entity types)
+11. Navigation     - FLOW (Multi-Modal routing - 10 entity types)
+12. APM            - OBSERVE (OpenTelemetry 1.0+ - 14 entity types)
+13. Testing        - VERIFY (ISP Coverage Model - 17 entity types)
 ```
 
 ### Core Principles
@@ -660,7 +661,7 @@ dr changeset abandon <changeset-id>
 **"What is Documentation Robotics?"**
 
 - Architecture-as-data philosophy
-- 12-layer separation of concerns
+- 13-layer separation of concerns
 - Traceability through cross-layer relationships
 - Standards-based integration
 
@@ -1520,7 +1521,7 @@ Would you like me to:
 ```
 User: How do I model a microservice?
 
-Agent: Great question! Let me explain how microservices map to DR's 12-layer model.
+Agent: Great question! Let me explain how microservices map to DR's 13-layer model.
 
 A microservice typically spans multiple layers:
 

package/dist/integrations/github_copilot/skills/dr_01_motivation_layer/SKILL.md

@@ -27,7 +27,7 @@ version: 0.8.1
 
 ## Layer Overview
 
-The Motivation Layer is the **highest layer** in the 12-layer architecture and provides governance to all other layers. It describes:
+The Motivation Layer is the **highest layer** in the 13-layer architecture and provides governance to all other layers. It describes:
 
 - **WHY** - The reasons and drivers behind architectural decisions
 - **WHO** - Stakeholders with interests in the outcome
@@ -115,7 +115,7 @@ This layer uses **ArchiMate 3.2 Motivation Layer** standard without custom exten
 | **Layer 4 (Application)** | ApplicationService supports Goals, delivers Value, governed by Principles; ApplicationFunction fulfills Requirements              |
 | **Layer 5 (Technology)**  | TechnologyService supports Goals, governed by Principles; Node fulfills Requirements, constrained by Constraints                  |
 | **Layer 6 (API)**         | Operation supports Goals (x-supports-goals), fulfills Requirements, governed by Principles, constrained by Constraints            |
-| **Layer 7-12**            | All layers can reference Principles, Constraints, Requirements, Goals for governance and traceability                             |
+| **Layer 7-13**            | All layers can reference Principles, Constraints, Requirements, Goals for governance and traceability                             |
 
 **Design Pattern:** Lower layers "look up" to the Motivation layer to justify WHY they exist and WHAT value they deliver.
 

package/dist/integrations/github_copilot/skills/dr_03_product_layer/SKILL.md

@@ -0,0 +1,253 @@
+---
+name: LAYER_03_PRODUCT
+description: Expert knowledge for Product Layer modeling in Documentation Robotics
+triggers:
+  [
+    "product",
+    "feature",
+    "persona",
+    "capability",
+    "milestone",
+    "user workflow",
+    "product roadmap",
+    "product planning",
+    "product management"
+  ]
+version: 0.8.4
+---
+
+# Product Layer Skill
+
+**Layer Number:** 03
+**Specification:** Metadata Model Spec v0.8.4
+**Purpose:** Defines product personas, capabilities, features, user workflows, and milestones that represent what the product does and for whom.
+
+---
+
+## Layer Overview
+
+The Product Layer captures the **product management dimension** of architecture:
+
+- **WHO** - Personas and target user archetypes
+- **WHAT** - Capabilities and features the product delivers
+- **HOW** - User workflows describing how users accomplish goals
+- **WHEN** - Milestones representing delivery roadmap
+- **WHY** - Linkage to business goals and requirements
+
+This layer uses a **custom specification** designed for product planning, prioritization, and user-centric modeling — distinct from Business layer (organization-internal processes) and UX layer (UI/interface design).
+
+**Key Innovation:** Bridges strategic intent (Motivation layer) and organizational structure (Business layer) with externally-facing product value planning and delivery.
+
+---
+
+## Entity Types
+
+> **CLI Introspection:** Run `dr schema types product` for the authoritative, always-current list of node types.
+> Run `dr schema node <type-id>` for full attribute details on any type.
+
+| Entity Type      | Description                                                | Key Attributes                                                                                        |
+| ---------------- | ---------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
+| **Persona**      | User archetype with shared goals, behaviors, pain points   | category (primary, secondary, served, negative), proficiency (novice, intermediate, advanced, expert) |
+| **Capability**   | Product ability independent of implementation              | status (proposed, planned, developing, delivered, deprecated), properties                             |
+| **Feature**      | User-visible unit of functionality delivering capabilities | priority (critical, high, medium, low, informational), status, size (xs, s, m, l, xl)                 |
+| **UserWorkflow** | Sequence of user-facing steps to accomplish a goal         | complexity (simple, moderate, complex), properties                                                    |
+| **Milestone**    | Time-bound delivery target grouping features/capabilities  | status (proposed, planned, active, completed, cancelled)                                              |
+
+---
+
+## Intra-Layer Relationships
+
+The Product layer models product structure and planning via these core relationships:
+
+| Source                 | Predicate       | Destination          | Cardinality  | Rationale                                      |
+| ---------------------- | --------------- | -------------------- | ------------ | ---------------------------------------------- |
+| `product.capability`   | `aggregates`    | `product.capability` | many-to-many | Capability decomposition into sub-capabilities |
+| `product.feature`      | `realizes`      | `product.capability` | many-to-many | Feature delivers a capability                  |
+| `product.feature`      | `serves`        | `product.persona`    | many-to-many | Feature targets a persona                      |
+| `product.feature`      | `scheduled-for` | `product.milestone`  | many-to-many | Feature assigned to delivery milestone         |
+| `product.capability`   | `scheduled-for` | `product.milestone`  | many-to-many | Capability assigned to milestone               |
+| `product.userworkflow` | `serves`        | `product.persona`    | many-to-many | Workflow designed for a persona                |
+| `product.userworkflow` | `composes`      | `product.feature`    | many-to-many | Workflow composed of features                  |
+| `product.milestone`    | `precedes`      | `product.milestone`  | many-to-many | Milestone sequencing                           |
+| `product.feature`      | `depends-on`    | `product.feature`    | many-to-many | Feature dependency                             |
+
+---
+
+## Cross-Layer References
+
+### Outgoing References (Product → Motivation)
+
+Product layer references Motivation layer to justify product decisions with strategic goals:
+
+| Predicate        | Source       | Target      | Rationale                                    |
+| ---------------- | ------------ | ----------- | -------------------------------------------- |
+| `realizes`       | Persona      | Stakeholder | Persona concretizes stakeholder archetypes   |
+| `satisfies`      | Feature      | Requirement | Feature satisfies business/user requirements |
+| `supports`       | Capability   | Goal        | Capability supports strategic goals          |
+| `delivers`       | UserWorkflow | Outcome     | Workflow delivers business outcomes          |
+| `delivers-value` | Feature      | Value       | Feature delivers business value              |
+| `fulfills`       | Capability   | Requirement | Capability fulfills requirements             |
+
+### Outgoing References (Product → Business)
+
+Product layer references Business layer to align with organizational services and roles:
+
+| Predicate    | Source       | Target           | Rationale                               |
+| ------------ | ------------ | ---------------- | --------------------------------------- |
+| `realizes`   | Feature      | BusinessService  | Feature realizes a business service     |
+| `aggregates` | UserWorkflow | BusinessProcess  | Workflow aggregates business processes  |
+| `realizes`   | Capability   | BusinessFunction | Capability realizes a business function |
+| `serves`     | Persona      | BusinessRole     | Persona is served by a business role    |
+
+### Incoming References (Lower Layers → Product)
+
+Higher layers (Security through Testing) reference Product layer for feature-level concerns:
+
+- Application → Feature: Application components implement features
+- UX → Feature: UI views render features
+- Testing → Feature: Test cases validate features
+- API → Feature: API operations expose features
+
+---
+
+## Persona Definition
+
+A Persona is a **user archetype** representing a class of users with shared goals, behaviors, and pain points.
+
+**Distinction from Stakeholder (Motivation layer):**
+
+- **Stakeholder** - Organizational relationship (internal/external/regulatory/customer)
+- **Persona** - Behavioral archetype with usage patterns and proficiency levels
+
+**Categories:**
+
+- **Primary** - Core user the product is designed for
+- **Secondary** - Important but not primary user
+- **Served** - User who benefits indirectly
+- **Negative** - User archetype the product explicitly doesn't serve
+
+**Proficiency Levels:**
+
+- **Novice** - First-time users, minimal technical background
+- **Intermediate** - Recurring users with some experience
+- **Advanced** - Power users with domain expertise
+- **Expert** - Specialists who push product limits
+
+---
+
+## Capability Definition
+
+A Capability is an **ability the product possesses**, independent of how it's implemented.
+
+**Distinction from BusinessFunction (Business layer):**
+
+- **BusinessFunction** - Internal organizational grouping of behavior
+- **Capability** - Externally-facing product ability
+
+**Lifecycle Statuses:**
+
+- **Proposed** - Idea under evaluation
+- **Planned** - Scheduled for development
+- **Developing** - Currently being built
+- **Delivered** - Implemented and released
+- **Deprecated** - No longer supported
+
+---
+
+## Feature Definition
+
+A Feature is a **user-visible unit of functionality** that delivers one or more capabilities and is the primary unit of product planning.
+
+**Distinction from Requirement (Motivation layer):**
+
+- **Requirement** - What system _must_ do (functional/non-functional/regulatory)
+- **Feature** - Planned unit of value with prioritization, sizing, and lifecycle
+
+**Priority Levels:**
+
+- **Critical** - Product cannot function without it
+- **High** - Core functionality users expect
+- **Medium** - Valuable enhancement
+- **Low** - Nice-to-have optimization
+- **Informational** - Documentation or informational
+
+**Sizing Estimates:**
+
+- **XS** - < 1 day of effort
+- **S** - 1–3 days
+- **M** - 1–2 weeks
+- **L** - 2–4 weeks
+- **XL** - > 4 weeks
+
+---
+
+## User Workflow Definition
+
+A UserWorkflow is a **sequence of user-facing steps** through the product to accomplish a goal.
+
+**Complexity Assessment:**
+
+- **Simple** - Linear flow, 2–3 steps, minimal decision points
+- **Moderate** - Multiple branches, 5–10 steps, some conditional logic
+- **Complex** - Many decision points, 10+ steps, cross-system integration
+
+---
+
+## Milestone Definition
+
+A Milestone is a **time-bound delivery target** grouping features or capabilities.
+
+**Lifecycle Statuses:**
+
+- **Proposed** - Candidate milestone under evaluation
+- **Planned** - Scheduled for planning and estimation
+- **Active** - Development underway
+- **Completed** - Released to users
+- **Cancelled** - Postponed or deprioritized
+
+---
+
+## Best Practices
+
+1. **Start with Personas, End with Workflows** - Understand users first, model journeys last
+2. **Features Deliver Capabilities** - Every feature should map to at least one capability
+3. **Capabilities Support Goals** - Link capabilities to motivation layer goals for justification
+4. **Milestones Sequence Logically** - Plan dependencies and prerequisites
+5. **Workflows are User-Centric** - Name them from the user's perspective
+6. **Prioritization Reflects Business Value** - Higher priority features deliver more strategic value
+7. **Link to Business Layer** - Map features to business services to show value realization
+
+---
+
+## Quick Reference
+
+**Add Commands:**
+
+```bash
+dr add product persona <name>
+dr add product capability <name>
+dr add product feature <name>
+dr add product user-workflow <name>
+dr add product milestone <name>
+```
+
+**Relationship Commands:**
+
+```bash
+dr relationship add <source> <destination> --predicate <predicate>
+```
+
+**Available Predicates:**
+
+- `aggregates` - Capability decomposes into sub-capability
+- `realizes` - Feature/Capability realizes capability/service/function
+- `serves` - Feature/Workflow/Persona serves persona/role
+- `scheduled-for` - Feature/Capability scheduled for milestone
+- `composes` - Workflow composed of features
+- `depends-on` - Feature depends on feature
+- `precedes` - Milestone precedes milestone
+- `satisfies` - Feature satisfies requirement
+- `supports` - Capability supports goal
+- `delivers` - Workflow delivers outcome
+- `delivers-value` - Feature delivers value
+- `fulfills` - Capability fulfills requirement

package/dist/reports/model-report-orchestrator.js

@@ -16,7 +16,7 @@ class ModelReportOrchestrator {
   }
   /**
    * Regenerate reports for a specific set of affected layers.
-   * On first invocation or when reports don't exist, regenerates all 12 reports.
+   * On first invocation or when reports don't exist, regenerates all 13 reports.
    * Invalid layer names in the affected set are skipped with a warning.
    */
   async regenerate(affectedLayers) {
@@ -31,7 +31,7 @@ class ModelReportOrchestrator {
     }
   }
   /**
-   * Regenerate all 12 layer reports.
+   * Regenerate all 13 layer reports.
    * Lets mkdir errors propagate so callers can handle them with proper telemetry.
    */
   async regenerateAll() {
@@ -54,7 +54,7 @@ class ModelReportOrchestrator {
     return affected;
   }
   /**
-   * Check if all 12 report files exist and are initialized.
+   * Check if all 13 report files exist and are initialized.
    * Returns false only if files don't exist (ENOENT); propagates other errors like EACCES, EMFILE, EIO.
    */
   async isInitialized() {

package/dist/reports/model-report-orchestrator.js.map

@@ -1,7 +1,7 @@
 {
   "version": 3,
   "sources": ["../../src/reports/model-report-orchestrator.ts"],
-  "sourcesContent": ["/**\n * Model Report Orchestrator\n *\n * Coordinates report generation across all 12 architecture layers.\n * Determines which reports need regeneration and manages the report directory.\n */\n\nimport type { Model } from '../core/model.js';\nimport { ModelReportDataCollector } from './model-report-data.js';\nimport { ModelLayerReportGenerator } from './model-layer-report-generator.js';\nimport { CANONICAL_LAYER_NAMES, type CanonicalLayerName, getLayerOrder, isValidLayerName } from '../core/layers.js';\nimport { getErrorMessage } from '../utils/errors.js';\nimport * as fs from 'fs/promises';\nimport * as path from 'path';\n\nexport class ModelReportOrchestrator {\n  private collector: ModelReportDataCollector;\n  private generator: ModelLayerReportGenerator;\n\n  constructor(private model: Model, private rootPath: string) {\n    this.collector = new ModelReportDataCollector();\n    const modelVersion = model.manifest.version || 'unknown';\n    const generatedAt = new Date().toISOString();\n    this.generator = new ModelLayerReportGenerator(modelVersion, generatedAt);\n  }\n\n  /**\n   * Regenerate reports for a specific set of affected layers.\n   * On first invocation or when reports don't exist, regenerates all 12 reports.\n   * Invalid layer names in the affected set are skipped with a warning.\n   */\n  async regenerate(affectedLayers: Set<string>): Promise<void> {\n    if (!(await this.isInitialized())) {\n      return this.regenerateAll();\n    }\n\n    for (const layerName of affectedLayers) {\n      // Type predicate narrows layerName to CanonicalLayerName automatically\n      if (!isValidLayerName(layerName)) {\n        console.warn(`Skipping invalid layer name: ${layerName}`);\n        continue;\n      }\n      await this.generateLayerReport(layerName);\n    }\n  }\n\n  /**\n   * Regenerate all 12 layer reports.\n   * Lets mkdir errors propagate so callers can handle them with proper telemetry.\n   */\n  async regenerateAll(): Promise<void> {\n    // Ensure report directory exists\n    const reportDir = this.getReportDir();\n    await fs.mkdir(reportDir, { recursive: true });\n\n    // Generate all 12 layer reports\n    for (const layerName of CANONICAL_LAYER_NAMES) {\n      await this.generateLayerReport(layerName);\n    }\n  }\n\n  /**\n   * Compute the set of layers affected by a change to a primary layer.\n   * Returns the primary layer plus any layers that have cross-layer relationships with it.\n   * Throws if the primary layer is not a recognized canonical layer name.\n   */\n  computeAffectedLayers(primaryLayer: CanonicalLayerName): Set<CanonicalLayerName> {\n    // Defense-in-depth: validate despite type signature (guards against as casts from callers)\n    if (!isValidLayerName(primaryLayer)) {\n      throw new Error(\n        `Invalid primary layer name: '${primaryLayer}' is not a recognized canonical layer. ` +\n        `Valid layers are: ${CANONICAL_LAYER_NAMES.join(', ')}`\n      );\n    }\n\n    const affected = new Set<CanonicalLayerName>([primaryLayer]);\n\n    for (const rel of this.model.relationships.getAll()) {\n      // Outbound: this layer references another layer\n      if (rel.layer === primaryLayer && rel.targetLayer) {\n        // Validate layer name before casting (defensive: guards against user-editable YAML with invalid layer names)\n        if (isValidLayerName(rel.targetLayer)) {\n          affected.add(rel.targetLayer);\n        }\n      }\n      // Inbound: another layer references this layer\n      if (rel.targetLayer === primaryLayer) {\n        // Validate layer name before casting (defensive: guards against user-editable YAML with invalid layer names)\n        if (isValidLayerName(rel.layer)) {\n          affected.add(rel.layer);\n        }\n      }\n    }\n\n    return affected;\n  }\n\n  /**\n   * Check if all 12 report files exist and are initialized.\n   * Returns false only if files don't exist (ENOENT); propagates other errors like EACCES, EMFILE, EIO.\n   */\n  private async isInitialized(): Promise<boolean> {\n    for (const layerName of CANONICAL_LAYER_NAMES) {\n      try {\n        await fs.access(this.getReportFilePath(layerName));\n      } catch (error: unknown) {\n        const err = error as NodeJS.ErrnoException;\n        // Only ENOENT (file not found) should return false; other errors propagate\n        if (err.code === 'ENOENT') {\n          return false;\n        }\n        // Re-throw permission errors, I/O errors, etc.\n        throw error;\n      }\n    }\n    return true;\n  }\n\n  /**\n   * Get the reports directory path.\n   */\n  private getReportDir(): string {\n    return path.join(this.rootPath, 'documentation-robotics', 'reports');\n  }\n\n  /**\n   * Get the full file path for a layer report.\n   */\n  private getReportFilePath(layerName: CanonicalLayerName): string {\n    const layerNumber = getLayerOrder(layerName);\n    const paddedNumber = String(layerNumber).padStart(2, '0');\n    const filename = `${paddedNumber}-${layerName}-layer-report.md`;\n    return path.join(this.getReportDir(), filename);\n  }\n\n  /**\n   * Generate and write a single layer report.\n   * Separates concerns to distinguish programming bugs from I/O errors.\n   * Lets generation and write errors propagate so callers can handle them with proper telemetry.\n   */\n  private async generateLayerReport(layerName: CanonicalLayerName): Promise<void> {\n    let data;\n    let markdown;\n\n    try {\n      // Collect layer data (may throw if programming bug or model is corrupted)\n      data = this.collector.collectLayerData(this.model, layerName);\n\n      // Generate markdown report (may throw if programming bug)\n      markdown = this.generator.generate(data);\n    } catch (error) {\n      throw new Error(\n        `Failed to generate report content for layer: ${layerName} (programming error or corrupted model) - ${getErrorMessage(error)}`\n      );\n    }\n\n    // Write to file (may throw for I/O errors like ENOSPC, EACCES, EIO)\n    // Let write errors propagate so callers can handle them with proper telemetry\n    const filePath = this.getReportFilePath(layerName);\n    await fs.writeFile(filePath, markdown, 'utf-8');\n  }\n}\n"],
+  "sourcesContent": ["/**\n * Model Report Orchestrator\n *\n * Coordinates report generation across all 13 architecture layers.\n * Determines which reports need regeneration and manages the report directory.\n */\n\nimport type { Model } from '../core/model.js';\nimport { ModelReportDataCollector } from './model-report-data.js';\nimport { ModelLayerReportGenerator } from './model-layer-report-generator.js';\nimport { CANONICAL_LAYER_NAMES, type CanonicalLayerName, getLayerOrder, isValidLayerName } from '../core/layers.js';\nimport { getErrorMessage } from '../utils/errors.js';\nimport * as fs from 'fs/promises';\nimport * as path from 'path';\n\nexport class ModelReportOrchestrator {\n  private collector: ModelReportDataCollector;\n  private generator: ModelLayerReportGenerator;\n\n  constructor(private model: Model, private rootPath: string) {\n    this.collector = new ModelReportDataCollector();\n    const modelVersion = model.manifest.version || 'unknown';\n    const generatedAt = new Date().toISOString();\n    this.generator = new ModelLayerReportGenerator(modelVersion, generatedAt);\n  }\n\n  /**\n   * Regenerate reports for a specific set of affected layers.\n   * On first invocation or when reports don't exist, regenerates all 13 reports.\n   * Invalid layer names in the affected set are skipped with a warning.\n   */\n  async regenerate(affectedLayers: Set<string>): Promise<void> {\n    if (!(await this.isInitialized())) {\n      return this.regenerateAll();\n    }\n\n    for (const layerName of affectedLayers) {\n      // Type predicate narrows layerName to CanonicalLayerName automatically\n      if (!isValidLayerName(layerName)) {\n        console.warn(`Skipping invalid layer name: ${layerName}`);\n        continue;\n      }\n      await this.generateLayerReport(layerName);\n    }\n  }\n\n  /**\n   * Regenerate all 13 layer reports.\n   * Lets mkdir errors propagate so callers can handle them with proper telemetry.\n   */\n  async regenerateAll(): Promise<void> {\n    // Ensure report directory exists\n    const reportDir = this.getReportDir();\n    await fs.mkdir(reportDir, { recursive: true });\n\n    // Generate all 13 layer reports\n    for (const layerName of CANONICAL_LAYER_NAMES) {\n      await this.generateLayerReport(layerName);\n    }\n  }\n\n  /**\n   * Compute the set of layers affected by a change to a primary layer.\n   * Returns the primary layer plus any layers that have cross-layer relationships with it.\n   * Throws if the primary layer is not a recognized canonical layer name.\n   */\n  computeAffectedLayers(primaryLayer: CanonicalLayerName): Set<CanonicalLayerName> {\n    // Defense-in-depth: validate despite type signature (guards against as casts from callers)\n    if (!isValidLayerName(primaryLayer)) {\n      throw new Error(\n        `Invalid primary layer name: '${primaryLayer}' is not a recognized canonical layer. ` +\n        `Valid layers are: ${CANONICAL_LAYER_NAMES.join(', ')}`\n      );\n    }\n\n    const affected = new Set<CanonicalLayerName>([primaryLayer]);\n\n    for (const rel of this.model.relationships.getAll()) {\n      // Outbound: this layer references another layer\n      if (rel.layer === primaryLayer && rel.targetLayer) {\n        // Validate layer name before casting (defensive: guards against user-editable YAML with invalid layer names)\n        if (isValidLayerName(rel.targetLayer)) {\n          affected.add(rel.targetLayer);\n        }\n      }\n      // Inbound: another layer references this layer\n      if (rel.targetLayer === primaryLayer) {\n        // Validate layer name before casting (defensive: guards against user-editable YAML with invalid layer names)\n        if (isValidLayerName(rel.layer)) {\n          affected.add(rel.layer);\n        }\n      }\n    }\n\n    return affected;\n  }\n\n  /**\n   * Check if all 13 report files exist and are initialized.\n   * Returns false only if files don't exist (ENOENT); propagates other errors like EACCES, EMFILE, EIO.\n   */\n  private async isInitialized(): Promise<boolean> {\n    for (const layerName of CANONICAL_LAYER_NAMES) {\n      try {\n        await fs.access(this.getReportFilePath(layerName));\n      } catch (error: unknown) {\n        const err = error as NodeJS.ErrnoException;\n        // Only ENOENT (file not found) should return false; other errors propagate\n        if (err.code === 'ENOENT') {\n          return false;\n        }\n        // Re-throw permission errors, I/O errors, etc.\n        throw error;\n      }\n    }\n    return true;\n  }\n\n  /**\n   * Get the reports directory path.\n   */\n  private getReportDir(): string {\n    return path.join(this.rootPath, 'documentation-robotics', 'reports');\n  }\n\n  /**\n   * Get the full file path for a layer report.\n   */\n  private getReportFilePath(layerName: CanonicalLayerName): string {\n    const layerNumber = getLayerOrder(layerName);\n    const paddedNumber = String(layerNumber).padStart(2, '0');\n    const filename = `${paddedNumber}-${layerName}-layer-report.md`;\n    return path.join(this.getReportDir(), filename);\n  }\n\n  /**\n   * Generate and write a single layer report.\n   * Separates concerns to distinguish programming bugs from I/O errors.\n   * Lets generation and write errors propagate so callers can handle them with proper telemetry.\n   */\n  private async generateLayerReport(layerName: CanonicalLayerName): Promise<void> {\n    let data;\n    let markdown;\n\n    try {\n      // Collect layer data (may throw if programming bug or model is corrupted)\n      data = this.collector.collectLayerData(this.model, layerName);\n\n      // Generate markdown report (may throw if programming bug)\n      markdown = this.generator.generate(data);\n    } catch (error) {\n      throw new Error(\n        `Failed to generate report content for layer: ${layerName} (programming error or corrupted model) - ${getErrorMessage(error)}`\n      );\n    }\n\n    // Write to file (may throw for I/O errors like ENOSPC, EACCES, EIO)\n    // Let write errors propagate so callers can handle them with proper telemetry\n    const filePath = this.getReportFilePath(layerName);\n    await fs.writeFile(filePath, markdown, 'utf-8');\n  }\n}\n"],
   "mappings": "AAQA,SAAS,gCAAgC;AACzC,SAAS,iCAAiC;AAC1C,SAAS,uBAAgD,eAAe,wBAAwB;AAChG,SAAS,uBAAuB;AAChC,YAAY,QAAQ;AACpB,YAAY,UAAU;AAEhB,MAAO,wBAAuB;EAId;EAAsB;EAHlC;EACA;EAER,YAAoB,OAAsB,UAAgB;AAAtC,SAAA,QAAA,OAAsB,KAAA,WAAA,UACxC,KAAK,YAAY,IAAI,yBAAwB;AAC7C,UAAM,eAAe,MAAM,SAAS,WAAW,WACzC,eAAc,oBAAI,KAAI,GAAG,YAAW;AAC1C,SAAK,YAAY,IAAI,0BAA0B,cAAc,WAAW;EAC1E;;;;;;EAOA,MAAM,WAAW,gBAA2B;AAC1C,QAAI,CAAE,MAAM,KAAK,cAAa;AAC5B,aAAO,KAAK,cAAa;AAG3B,eAAW,aAAa,gBAAgB;AAEtC,UAAI,CAAC,iBAAiB,SAAS,GAAG;AAChC,gBAAQ,KAAK,gCAAgC,SAAS,EAAE;AACxD;MACF;AACA,YAAM,KAAK,oBAAoB,SAAS;IAC1C;EACF;;;;;EAMA,MAAM,gBAAa;AAEjB,UAAM,YAAY,KAAK,aAAY;AACnC,UAAM,GAAG,MAAM,WAAW,EAAE,WAAW,GAAI,CAAE;AAG7C,eAAW,aAAa;AACtB,YAAM,KAAK,oBAAoB,SAAS;EAE5C;;;;;;EAOA,sBAAsB,cAAgC;AAEpD,QAAI,CAAC,iBAAiB,YAAY;AAChC,YAAM,IAAI,MACR,gCAAgC,YAAY,4DACvB,sBAAsB,KAAK,IAAI,CAAC,EAAE;AAI3D,UAAM,WAAW,oBAAI,IAAwB,CAAC,YAAY,CAAC;AAE3D,eAAW,OAAO,KAAK,MAAM,cAAc,OAAM;AAE/C,MAAI,IAAI,UAAU,gBAAgB,IAAI,eAEhC,iBAAiB,IAAI,WAAW,KAClC,SAAS,IAAI,IAAI,WAAW,GAI5B,IAAI,gBAAgB,gBAElB,iBAAiB,IAAI,KAAK,KAC5B,SAAS,IAAI,IAAI,KAAK;AAK5B,WAAO;EACT;;;;;EAMQ,MAAM,gBAAa;AACzB,eAAW,aAAa;AACtB,UAAI;AACF,cAAM,GAAG,OAAO,KAAK,kBAAkB,SAAS,CAAC;MACnD,SAAS,OAAgB;AAGvB,YAFY,MAEJ,SAAS;AACf,iBAAO;AAGT,cAAM;MACR;AAEF,WAAO;EACT;;;;EAKQ,eAAY;AAClB,WAAO,KAAK,KAAK,KAAK,UAAU,0BAA0B,SAAS;EACrE;;;;EAKQ,kBAAkB,WAA6B;AACrD,UAAM,cAAc,cAAc,SAAS,GAErC,WAAW,GADI,OAAO,WAAW,EAAE,SAAS,GAAG,GAAG,CACxB,IAAI,SAAS;AAC7C,WAAO,KAAK,KAAK,KAAK,aAAY,GAAI,QAAQ;EAChD;;;;;;EAOQ,MAAM,oBAAoB,WAA6B;AAC7D,QAAI,MACA;AAEJ,QAAI;AAEF,aAAO,KAAK,UAAU,iBAAiB,KAAK,OAAO,SAAS,GAG5D,WAAW,KAAK,UAAU,SAAS,IAAI;IACzC,SAAS,OAAO;AACd,YAAM,IAAI,MACR,gDAAgD,SAAS,6CAA6C,gBAAgB,KAAK,CAAC,EAAE;IAElI;AAIA,UAAM,WAAW,KAAK,kBAAkB,SAAS;AACjD,UAAM,GAAG,UAAU,UAAU,UAAU,OAAO;EAChD;;",
   "names": []
 }

package/dist/schemas/bundled/analyzers/cbm.json

@@ -1,7 +1,7 @@
 {
   "name": "cbm",
-  "version": "0.8.4",
-  "source_version": "0.8.4",
+  "version": "0.9.0",
+  "source_version": "0.9.0",
   "analyzer": {
     "name": "cbm",
     "display_name": "codebase-memory-mcp",

package/dist/schemas/bundled/analyzers/manifest.json

@@ -1,9 +1,9 @@
 {
-  "specVersion": "0.8.4",
+  "specVersion": "0.9.0",
   "analyzers": [
     {
       "name": "cbm",
-      "version": "0.8.4"
+      "version": "0.9.0"
     }
   ]
 }

package/dist/schemas/bundled/api.json

@@ -1,10 +1,10 @@
 {
-  "specVersion": "0.8.4",
+  "specVersion": "0.9.0",
   "layer": {
     "id": "api",
-    "number": 6,
+    "number": 7,
     "name": "API Layer",
-    "description": "Layer 6: API Layer",
+    "description": "Layer 7: API Layer",
     "inspired_by": {
       "standard": "OpenAPI 3.0",
       "version": "3.0",

package/dist/schemas/bundled/apm.json

@@ -1,10 +1,10 @@
 {
-  "specVersion": "0.8.4",
+  "specVersion": "0.9.0",
   "layer": {
     "id": "apm",
-    "number": 11,
+    "number": 12,
     "name": "APM Observability Layer",
-    "description": "Layer 11: APM Observability Layer",
+    "description": "Layer 12: APM Observability Layer",
     "inspired_by": {
       "standard": "OpenTelemetry",
       "version": "1.0",

package/dist/schemas/bundled/application.json

@@ -1,10 +1,10 @@
 {
-  "specVersion": "0.8.4",
+  "specVersion": "0.9.0",
   "layer": {
     "id": "application",
-    "number": 4,
+    "number": 5,
     "name": "Application Layer",
-    "description": "Layer 4: Application Layer",
+    "description": "Layer 5: Application Layer",
     "inspired_by": {
       "standard": "ArchiMate 3.2",
       "version": "3.2",

package/dist/schemas/bundled/base.json

@@ -1,5 +1,5 @@
 {
-  "specVersion": "0.8.4",
+  "specVersion": "0.9.0",
   "schemas": {
     "spec-node": {
       "$schema": "http://json-schema.org/draft-07/schema#",
@@ -596,6 +596,7 @@
         "optimizes",
         "owns",
         "performs",
+        "precedes",
         "protects",
         "provides",
         "realizes",
@@ -606,6 +607,7 @@
         "requires",
         "resolves-with",
         "satisfies",
+        "scheduled-for",
         "serves",
         "specializes",
         "supports",
@@ -1617,6 +1619,32 @@
         "symmetry": false,
         "reflexivity": false
       }
+    },
+    "scheduled-for": {
+      "predicate": "scheduled-for",
+      "inverse": "schedules",
+      "category": "structural",
+      "description": "Element is assigned to a time-bound delivery target",
+      "archimate_alignment": null,
+      "semantics": {
+        "directionality": "bidirectional",
+        "transitivity": false,
+        "symmetry": false,
+        "reflexivity": false
+      }
+    },
+    "precedes": {
+      "predicate": "precedes",
+      "inverse": "follows",
+      "category": "behavioral",
+      "description": "Element comes before another in a temporal sequence",
+      "archimate_alignment": null,
+      "semantics": {
+        "directionality": "bidirectional",
+        "transitivity": true,
+        "symmetry": false,
+        "reflexivity": false
+      }
     }
   }
 }

package/dist/schemas/bundled/business.json

@@ -1,5 +1,5 @@
 {
-  "specVersion": "0.8.4",
+  "specVersion": "0.9.0",
   "layer": {
     "id": "business",
     "number": 2,

package/dist/schemas/bundled/data-model.json

@@ -1,10 +1,10 @@
 {
-  "specVersion": "0.8.4",
+  "specVersion": "0.9.0",
   "layer": {
     "id": "data-model",
-    "number": 7,
+    "number": 8,
     "name": "Data Model Layer",
-    "description": "Layer 7: Data Model Layer",
+    "description": "Layer 8: Data Model Layer",
     "inspired_by": {
       "standard": "JSON Schema Draft 7",
       "version": "Draft 7",

package/dist/schemas/bundled/data-store.json

@@ -1,10 +1,10 @@
 {
-  "specVersion": "0.8.4",
+  "specVersion": "0.9.0",
   "layer": {
     "id": "data-store",
-    "number": 8,
+    "number": 9,
     "name": "Data Store Layer",
-    "description": "Layer 8: Data Store Layer",
+    "description": "Layer 9: Data Store Layer",
     "inspired_by": {
       "standard": "ISO/IEC 9075 (SQL) + Paradigm Extensions",
       "version": "2024",