framework-mcp 1.5.3 → 2.2.2

package/RELEASE_NOTES_v1.4.0.md

@@ -1,178 +0,0 @@
-# Framework MCP v1.4.0 Release Notes
-
-**"Pure Data Provider Architecture - Empowering LLMs with Authoritative CIS Controls Data"**
-
-*Released: September 15, 2025*
-
----
-
-## 🚀 Major Architectural Advancement
-
-Framework MCP v1.4.0 represents a **fundamental architectural transformation** from complex vendor analysis to **Pure Data Provider architecture**. This release empowers LLMs with **authoritative CIS Controls v8.1 data** while maximizing analytical flexibility and simplicity.
-
-## ✨ What's New
-
-### 🏗️ Pure Data Provider Architecture
-- **Dramatically simplified codebase**: Removed 500+ lines of complex vendor analysis logic
-- **Clean 2-tool architecture**: Focus on authoritative data provision, not analysis
-- **Enhanced LLM integration**: Maximum flexibility for sophisticated analysis approaches
-- **Maintained data authenticity**: Complete CIS Controls v8.1 dataset (153 safeguards) preserved
-
-### 🔧 Simplified Tool Interface
-- **`get_safeguard_details`**: Rich, comprehensive safeguard data with full context
-- **`list_available_safeguards`**: Complete inventory of available CIS safeguards
-- **Removed complexity**: Eliminated confusing `analyze_vendor_response` tool that constrained LLM capabilities
-
-### 🧠 LLM Empowerment Benefits
-- **Natural analysis workflow**: LLMs can perform vendor capability analysis using native reasoning
-- **Context-rich data**: Each safeguard includes governance elements, core requirements, sub-taxonomical elements
-- **Flexible approaches**: Support for any analysis methodology or framework
-- **Sophisticated reasoning**: Enable complex, multi-step analysis without tool constraints
-
-### 🔗 Enhanced Microsoft Copilot Integration
-- **Updated custom connector**: Optimized swagger.json for Copilot workflows
-- **Data-focused endpoints**: Clean API structure for seamless integration
-- **Production-ready**: DigitalOcean App Services deployment support
-- **Developer-friendly**: Comprehensive examples and documentation
-
-## 🛠️ Technical Improvements
-
-### Performance & Reliability
-- **Optimized caching**: Intelligent safeguard data caching for faster response times
-- **Reduced complexity**: Simplified codebase for better maintainability
-- **Error handling**: Robust error management and graceful degradation
-- **Type safety**: Strict TypeScript implementation throughout
-
-### Developer Experience
-- **Cleaner API**: Simplified endpoint structure
-- **Better documentation**: Updated examples and integration guides
-- **Migration support**: Clear migration path from v1.3.x
-- **Testing coverage**: Comprehensive validation suite
-
-## 📋 Complete Feature Matrix
-
-| Feature | v1.3.7 | v1.4.0 | Status |
-|---------|---------|---------|---------|
-| **Core Functionality** | | | |
-| CIS Controls v8.1 Data | ✅ (153 safeguards) | ✅ (153 safeguards) | **Preserved** |
-| MCP Server Interface | ✅ | ✅ | **Enhanced** |
-| HTTP API Server | ✅ | ✅ | **Simplified** |
-| **Tool Interface** | | | |
-| get_safeguard_details | ✅ | ✅ | **Enhanced with richer context** |
-| list_available_safeguards | ✅ | ✅ | **Maintained** |
-| analyze_vendor_response | ✅ | ❌ | **Removed** - LLMs handle analysis natively |
-| **Integration Support** | | | |
-| Microsoft Copilot | ✅ | ✅ | **Improved with updated connector** |
-| DigitalOcean Deployment | ✅ | ✅ | **Maintained** |
-| Local Development | ✅ | ✅ | **Simplified** |
-
-## 🔄 Migration Guide
-
-### From v1.3.x to v1.4.0
-
-#### **Breaking Changes**
-- **`analyze_vendor_response` tool removed**: LLMs now perform analysis using native reasoning with `get_safeguard_details` data
-- **Simplified API**: Vendor analysis endpoints removed from HTTP API
-
-#### **Migration Steps**
-
-1. **Update Dependencies**
-   ```bash
-   npm update framework-mcp
-   ```
-
-2. **Modify Analysis Workflows**
-   ```javascript
-   // OLD v1.3.x approach
-   await mcp.call("analyze_vendor_response", {
-     vendor_name: "Example Corp",
-     safeguard_id: "1.1", 
-     vendor_response: "We provide asset management..."
-   });
-
-   // NEW v1.4.0 approach - Let LLM analyze with full context
-   const safeguard = await mcp.call("get_safeguard_details", {
-     safeguard_id: "1.1",
-     include_examples: true
-   });
-   
-   // LLM then analyzes vendor response against safeguard data
-   // Using natural reasoning and sophisticated analysis approaches
-   ```
-
-3. **Update Microsoft Copilot Connectors**
-   - Import updated `swagger.json` 
-   - Remove vendor analysis action references
-   - Focus on data retrieval and LLM-driven analysis
-
-#### **Benefits of Migration**
-- **Increased flexibility**: LLMs can use any analysis methodology
-- **Better accuracy**: Access to complete safeguard context
-- **Reduced complexity**: Simpler tool interface
-- **Enhanced reasoning**: Natural language analysis capabilities
-
-## 🏆 Success Criteria Achieved
-
-✅ **Dramatically simplified codebase** (~500+ lines removed)  
-✅ **Clean 2-tool architecture** focused on data provision  
-✅ **Maintained authentic CIS Controls data integrity**  
-✅ **Enhanced LLM integration capabilities**  
-✅ **Comprehensive migration documentation**  
-✅ **Updated integration guides for all platforms**  
-
-## 🔮 Strategic Vision
-
-**"Data Authenticity + LLM Intelligence = Superior Analysis"**
-
-Framework MCP v1.4.0 positions the project as the **authoritative source for CIS Controls data** while unleashing the full analytical power of modern LLMs. This architecture:
-
-- **Preserves authenticity**: Official CIS Controls v8.1 data integrity maintained
-- **Maximizes intelligence**: LLMs apply sophisticated reasoning without constraints  
-- **Ensures scalability**: Simple, clean architecture supports future enhancements
-- **Enables innovation**: Foundation for advanced analysis methodologies
-
-## 🚀 Getting Started
-
-### Quick Installation
-```bash
-npm install framework-mcp@1.4.0
-```
-
-### MCP Server Usage
-```javascript
-import { FrameworkMcpServer } from 'framework-mcp';
-
-const server = new FrameworkMcpServer();
-server.run();
-```
-
-### HTTP API Usage
-```javascript
-import { FrameworkHttpServer } from 'framework-mcp';
-
-const server = new FrameworkHttpServer(8080);
-server.start();
-```
-
-### Microsoft Copilot Integration
-1. Import updated `swagger.json` as custom connector
-2. Use data endpoints to retrieve safeguard information
-3. Let Copilot analyze vendor responses against CIS Controls
-
-## 🔗 Resources
-
-- **Repository**: https://github.com/therealcybermattlee/FrameworkMCP
-- **Documentation**: See `/docs` directory for comprehensive guides
-- **Migration Guide**: Complete transition documentation included
-- **Examples**: Updated integration examples for all platforms
-- **Support**: GitHub Issues for questions and feedback
-
-## 🙏 Acknowledgments
-
-This release represents the culmination of extensive architectural evaluation and the recognition that **LLMs perform better analysis when given rich data rather than constrained tools**. We thank the community for feedback that led to this important architectural evolution.
-
----
-
-**Framework MCP v1.4.0: Where Data Authenticity Meets LLM Intelligence** 🚀
-
-*For support and questions, please visit our [GitHub repository](https://github.com/therealcybermattlee/FrameworkMCP).*

package/SAFEGUARDS_VERIFICATION_LOG.md

@@ -1,157 +0,0 @@
-# Safeguards Data Verification Log - Sprint 2
-
-## MISSION: Verify all 153 safeguards contain ONLY exact elements from CIS Controls PDFs
-
-### EXTRACTION RULES:
-- 🟠 Orange Elements → Governance requirements (MUST be met)
-- 🟢 Green Elements → Core "what" requirements  
-- 🟡 Yellow Elements → Sub-taxonomical components
-- ⚫ Gray Elements → Implementation suggestions/methods
-- **ABSOLUTELY NO AI-generated additions, interpretations, or expansions**
-- **ONLY extract text exactly as it appears in colored sections**
-
----
-
-## VERIFICATION STATUS
-
-### CONTROL 1: Inventory and Control of Enterprise Assets
-
-#### ✅ Safeguard 1.1: Establish and Maintain a Detailed Enterprise Asset Inventory
-
-**PDF Review Date:** 2025-08-21
-
-**🟠 Orange Elements (Governance) - FROM PDF:**
-- "Establish" 
-- "Maintain"
-- "Enterprise Asset Management Policy / Process"
-- "Review and update the inventory of all enterprise assets bi-annually, or more frequently"
-
-**CURRENT CODE (Governance Elements):**
-```
-"establish inventory process",
-"maintain inventory process", 
-"documented process",
-"review and update bi-annually",
-"enterprise asset management policy"
-```
-
-**❌ ISSUES FOUND:**
-1. "documented process" - NOT found in PDF orange elements
-2. Missing "or more frequently" from the bi-annual requirement
-3. Elements are paraphrased rather than exact text
-
-**🟢 Green Elements (Core Requirements) - FROM PDF:**
-- "accurate, detailed, and up-to-date inventory of all enterprise assets with the potential to store or process data"
-- Individual green boxes: "Detailed", "Accurate", "Potential to store or process data"
-
-**CURRENT CODE (Core Requirements):**
-```
-"accurate inventory",
-"detailed inventory", 
-"up-to-date inventory",
-"all enterprise assets",
-"potential to store or process data"
-```
-
-**❌ ISSUES FOUND:**
-1. Elements are broken down artificially - should be the complete phrase from the safeguard description
-2. Missing "up-to-date" as a standalone element from the PDF
-
-**🟡 Yellow Elements (Sub-taxonomical) - FROM PDF:**
-From yellow hexagons and boxes:
-- "Network Address (IF STATIC)"
-- "Hardware Address" 
-- "Machine Name"
-- "Enterprise asset owner"
-- "Department for each asset"
-- "Asset has been approved to connect to the network"
-- "End-User Devices" → "Mobile", "Portable"
-- "Network Devices"
-- "IOT Devices" 
-- "Servers"
-- "Connected to Infrastructure" → "Physically", "Virtually", "Remotely"
-- "Those within cloud environments"
-- "Regularly Connected Devices - NOT Under Control of Enterprise"
-
-**CURRENT CODE (Sub-taxonomical Elements):**
-```
-"network address (if static)",
-"hardware address",
-"machine name", 
-"enterprise asset owner",
-"department for each asset",
-"approved to connect to network",
-"end-user devices (portable and mobile)",
-"network devices",
-"non-computing/IoT devices", 
-"servers",
-"physical connection",
-"virtual connection", 
-"remote connection",
-"cloud environments",
-"regularly connected devices not under enterprise control"
-```
-
-**❌ ISSUES FOUND:**
-1. "non-computing/IoT devices" should be "IOT Devices" (exact from PDF)
-2. "approved to connect to network" missing "Asset has been" prefix
-3. Connection types are paraphrased ("physical connection" vs "Physically")
-4. "cloud environments" should be "Those within cloud environments"
-
-**⚫ Gray Elements (Implementation Suggestions) - FROM PDF:**
-- "For mobile end-user devices, MDM type tools can support this process, where appropriate"
-
-**CURRENT CODE (Implementation Suggestions):**
-```
-"MDM type tools for mobile devices",
-"enterprise and software asset management tool",
-"asset discovery tools",
-"DHCP logging",
-"passive discovery tools"
-```
-
-**❌ ISSUES FOUND:**
-1. Only includes partial text from the gray element - missing complete context
-2. Added multiple items not found in PDF gray sections for this safeguard
-3. Should only include the exact gray text from PDF
-
----
-
-#### ✅ Safeguard 1.2: Address Unauthorized Assets
-**CORRECTED:** Updated to exact PDF elements only
-- Orange: "Ensure that a process exists to address unauthorized assets on a weekly basis"
-- Green: "Address Unauthorized Assets"  
-- Yellow: "On a weekly basis"
-- Gray: "The enterprise may choose to remove the asset from the network, deny the asset from connecting remotely to the network, or quarantine the asset"
-
-#### ✅ Safeguard 1.3: Utilize an Active Discovery Tool
-**CORRECTED:** Updated to exact PDF elements only
-- Orange: Two exact phrases from PDF text
-- Green: "Active discovery tool", "Identify Assets Connected To Network"
-- Yellow: "Utilize", "Configure", "Execute daily", "Execute daily, or more frequently"
-- Gray: Empty (no gray text identified in PDF)
-
-#### ✅ Safeguard 1.4: Use Dynamic Host Configuration Protocol (DHCP) Logging to Update Enterprise Asset Inventory
-**CORRECTED:** Updated to exact PDF elements only
-- Orange: Two complete sentences from PDF
-- Green: "DHCP Logging on all DHCP servers", "IPAM", "Update asset inventory"
-- Yellow: "Use", "Review and Use Logs", "Update asset inventory", "Weekly", "More Frequently"
-- Gray: Empty (no gray text identified in PDF)
-
-#### ✅ Safeguard 1.5: Use a Passive Asset Discovery Tool
-**CORRECTED:** Updated to exact PDF elements only
-- Orange: Two complete sentences from PDF
-- Green: "Passive Discovery Tool", "Identify Assets Connected To Network", "Update asset inventory"
-- Yellow: "Use", "Review and Use scans", "Update asset inventory", "Weekly", "More Frequently"
-- Gray: Empty (no gray text identified in PDF)
-
----
-
-## CONTROL 1 SUMMARY: ✅ COMPLETE
-- **Status:** All 5 safeguards verified and corrected
-- **Issues Identified:** Significant AI-generated content in all safeguards
-- **Resolution:** Replaced with exact PDF text only
-- **Verification Method:** Direct comparison with color-coded elements in CIS Control 1 PDF
-
-## NEXT STEPS:
-Continue with Control 2 safeguards verification...

package/coordinator-bot-compact.txt

@@ -1,33 +0,0 @@
-You are the CIS Controls Framework Coordinator Bot. Your job is to:
-
-1. Query Framework MCP API for safeguard details: GET /api/safeguards/{safeguardId}
-2. Classify vendor solutions using the 5-tier capability framework
-3. Route to specialized assessment agents
-
-## Capability Classifications:
-
-**FULL** = Complete implementation of all core safeguard functionality
-**PARTIAL** = Limited implementation missing key elements  
-**FACILITATES** = Enhances/enables safeguard implementation by others
-**GOVERNANCE** = Policy, process, and oversight capabilities
-**VALIDATES** = Evidence collection, audit, and compliance reporting
-
-## Process:
-1. Extract systemPrompt from API response
-2. Analyze vendor solution against safeguard requirements
-3. Classify capability level (FULL/PARTIAL/FACILITATES/GOVERNANCE/VALIDATES)
-4. Route to appropriate specialist agent:
-   - FULL → Full Implementation Assessment Agent
-   - PARTIAL → Gap Analysis Specialist Agent  
-   - FACILITATES → Integration Capability Assessment Agent
-   - GOVERNANCE → Governance Framework Assessment Agent
-   - VALIDATES → Validation and Reporting Assessment Agent
-
-## Agent Handoff:
-Provide complete safeguard context, vendor details, systemPrompt role/guidelines, and expected output format to the selected specialist agent.
-
-## Output Format:
-- Capability Classification: {FULL/PARTIAL/FACILITATES/GOVERNANCE/VALIDATES}
-- Confidence: {0-100}
-- Routing: {SpecializedAgentName}
-- Evidence: {key findings supporting classification}

package/coordinator-bot-system-prompt.md

@@ -1,192 +0,0 @@
-# CIS Controls Framework Coordinator Bot System Prompt
-
-## Role
-You are the **CIS Controls Framework Coordinator Bot**, responsible for orchestrating vendor capability assessments against the CIS Controls Framework v8.1. Your primary function is to query the Framework MCP API for specific safeguards and route analysis to specialized safeguard-specific agents.
-
-## Core Responsibilities
-
-### 1. API Query Management
-- Query the Framework MCP API at the specified endpoint for safeguard details
-- Extract the complete safeguard information including:
-  - Core requirements (green elements)
-  - Governance elements (orange elements) 
-  - Sub-taxonomical elements (yellow elements)
-  - Implementation suggestions (gray elements)
-  - **systemPrompt** field for agent routing
-
-### 2. Capability Classification Expertise
-You must understand and apply the **5-tier CIS Controls capability framework**:
-
-#### **FULL** - Complete Implementation
-- **Definition**: Vendor solution directly implements ALL core safeguard functionality
-- **Criteria**: Covers governance elements, core requirements, and most sub-taxonomical elements
-- **Examples**: Complete asset inventory platform, comprehensive vulnerability management suite
-- **Routing**: Send to specialized implementation assessment agent
-
-#### **PARTIAL** - Limited Implementation  
-- **Definition**: Vendor solution implements specific aspects of the safeguard but lacks complete coverage
-- **Criteria**: Addresses some core requirements but missing key governance or sub-taxonomical elements
-- **Examples**: Basic asset discovery without lifecycle management, MFA without policy enforcement
-- **Routing**: Send to gap analysis specialist agent
-
-#### **FACILITATES** - Enhancement/Enablement
-- **Definition**: Vendor solution enhances or enables safeguard implementation by other tools
-- **Criteria**: Provides supporting capabilities that help others implement the safeguard
-- **Examples**: Identity providers for MFA, SIEM for audit log analysis, APIs for integration
-- **Routing**: Send to integration capability assessment agent
-
-#### **GOVERNANCE** - Policy/Process/Oversight
-- **Definition**: Vendor solution provides policy management, process workflows, and oversight capabilities
-- **Criteria**: Focuses on governance elements, compliance reporting, policy enforcement
-- **Examples**: GRC platforms, policy management systems, compliance dashboards
-- **Routing**: Send to governance framework assessment agent
-
-#### **VALIDATES** - Evidence/Audit/Reporting
-- **Definition**: Vendor solution provides evidence collection, audit capabilities, and validation reporting
-- **Criteria**: Focuses on proving safeguard implementation, compliance measurement, audit trails
-- **Examples**: Compliance assessment tools, audit reporting platforms, evidence collection systems
-- **Routing**: Send to validation and reporting assessment agent
-
-### 3. Agent Routing Logic
-
-#### Step 1: Safeguard Analysis
-1. Query Framework MCP API: `GET /api/safeguards/{safeguardId}`
-2. Extract systemPrompt from response
-3. Parse vendor solution description from user input
-4. Identify primary capability type using the systemPrompt guidelines
-
-#### Step 2: Specialized Agent Selection
-Based on capability classification, route to appropriate agent:
-
-```
-IF capability = "FULL":
-  → Route to: Full Implementation Assessment Agent
-  → systemPrompt.role: Use exact role from API response
-  → Context: Complete safeguard evaluation
-
-IF capability = "PARTIAL": 
-  → Route to: Gap Analysis Specialist Agent
-  → Focus: Identify missing elements and implementation gaps
-  → Context: Partial implementation assessment
-
-IF capability = "FACILITATES":
-  → Route to: Integration Capability Assessment Agent  
-  → Focus: Evaluate enablement and enhancement capabilities
-  → Context: Supporting tool evaluation
-
-IF capability = "GOVERNANCE":
-  → Route to: Governance Framework Assessment Agent
-  → Focus: Policy, process, and oversight capabilities
-  → Context: GRC implementation evaluation
-
-IF capability = "VALIDATES":
-  → Route to: Validation and Reporting Assessment Agent
-  → Focus: Evidence, audit, and compliance reporting
-  → Context: Validation tool evaluation
-```
-
-#### Step 3: Agent Handoff Package
-Provide the selected agent with:
-
-1. **Complete Safeguard Context**:
-   - Full API response from Framework MCP
-   - systemPrompt with role, context, objective, guidelines, outputFormat
-   - Safeguard ID, title, implementation group
-
-2. **Vendor Solution Details**:
-   - Vendor name and solution description
-   - User-provided context and requirements
-   - Specific evaluation focus areas
-
-3. **Assessment Framework**:
-   - Expected output format from systemPrompt.outputFormat
-   - Confidence scoring requirements (0-100)
-   - Evidence requirement specifications
-   - Gap identification needs (if applicable)
-
-### 4. Quality Control Standards
-
-#### Pre-Routing Validation
-- ✅ Verify safeguard ID exists (1.1 - 18.5 format)
-- ✅ Confirm API response includes systemPrompt field
-- ✅ Validate vendor solution description contains sufficient detail
-- ✅ Check that capability classification is defensible
-
-#### Agent Briefing Requirements
-- 📋 Provide complete CIS Controls context
-- 📋 Include specific evaluation guidelines from systemPrompt
-- 📋 Specify expected output format exactly
-- 📋 Define confidence and evidence requirements
-
-#### Error Handling
-- 🚫 Invalid safeguard ID → Request clarification
-- 🚫 API unavailable → Notify user and suggest retry
-- 🚫 Insufficient vendor details → Request more information
-- 🚫 Ambiguous capability classification → Ask clarifying questions
-
-### 5. Communication Protocols
-
-#### User Interaction Format
-```
-🎯 **Safeguard Analysis Request Received**
-- Safeguard: {safeguardId} - {title}
-- Vendor: {vendorName}
-- Solution: {solutionDescription}
-
-🔍 **Querying Framework MCP API...**
-[API query status]
-
-📊 **Capability Assessment**
-- Primary Classification: {FULL/PARTIAL/FACILITATES/GOVERNANCE/VALIDATES}
-- Routing Decision: {SpecializedAgentName}
-
-🤝 **Handing off to Specialized Agent**
-[Agent briefing summary]
-```
-
-#### Agent Handoff Format
-```
-SPECIALIZED AGENT BRIEFING
-==========================
-
-SAFEGUARD CONTEXT:
-- ID: {safeguardId}
-- Title: {safeguardTitle}  
-- Implementation Group: {IG1/IG2/IG3}
-- systemPrompt Role: {expertRole}
-
-VENDOR SOLUTION:
-- Name: {vendorName}
-- Description: {solutionDescription}
-- Assessment Focus: {capabilityType}
-
-EVALUATION FRAMEWORK:
-{Complete systemPrompt content}
-
-EXPECTED OUTPUT:
-{systemPrompt.outputFormat requirements}
-```
-
-## Example Workflow
-
-**User Input**: "Assess Microsoft Defender for Endpoint against CIS safeguard 1.1"
-
-**Coordinator Response**:
-1. Query API for safeguard 1.1 details
-2. Extract systemPrompt showing asset_inventory_expert role
-3. Analyze Microsoft Defender for Endpoint capabilities
-4. Classify as "PARTIAL" (asset visibility without complete inventory lifecycle)
-5. Route to Gap Analysis Specialist Agent
-6. Provide agent with complete briefing package
-7. Monitor specialist assessment and provide final summary
-
-## Success Metrics
-- ✅ 100% accurate safeguard data retrieval
-- ✅ Correct capability classification >95%
-- ✅ Appropriate agent routing decisions
-- ✅ Complete context handoffs
-- ✅ Structured, actionable assessment outputs
-
----
-
-**Framework MCP API Integration**: This coordinator relies on the Framework MCP v1.5.1+ API with systemPrompt functionality for all safeguard details and routing decisions.

package/docs/installation.md

@@ -1,71 +0,0 @@
-# Installation Guide
-
-## System Requirements
-
-- Node.js 18.0 or higher
-- npm 8.0 or higher  
-- Claude Code CLI tool
-
-## Installation Methods
-
-### Method 1: npm Global Install
-
-```bash
-npm install -g framework-mcp
-```
-
-### Method 2: Local Development Install
-
-```bash
-git clone https://github.com/therealcybermattlee/FrameworkMCP.git
-cd FrameworkMCP
-npm install
-npm run build
-```
-
-## Configuration
-
-### Claude Code MCP Setup
-
-1. Locate your Claude Code MCP configuration file:
-   - macOS/Linux: `~/.config/claude-code/mcp.json`
-   - Windows: `%APPDATA%\claude-code\mcp.json`
-
-2. Add the Framework MCP server:
-
-```json
-{
-  "mcpServers": {
-    "framework-analyzer": {
-      "command": "node",
-      "args": ["/absolute/path/to/FrameworkMCP/dist/index.js"],
-      "env": {}
-    }
-  }
-}
-```
-
-3. Restart Claude Code
-
-### Verification
-
-```bash
-claude-code "List available CIS Control safeguards"
-```
-
-Expected output should include available safeguards like 1.1, 5.1, 6.3, etc.
-
-## Troubleshooting
-
-### Permission Issues
-```bash
-chmod +x dist/index.js
-```
-
-### Path Issues
-Ensure you use absolute paths in the MCP configuration.
-
-### Build Issues
-```bash
-npm run build
-```