bc-code-intelligence-mcp 1.5.7 → 1.5.8

package/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2024 Business Central Knowledge Base
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+MIT License
+
+Copyright (c) 2024 Business Central Knowledge Base
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.

package/README.md

@@ -1,165 +1,165 @@
-# BC Code Intelligence MCP Server
-
-[![Install with NPX in VS Code](https://img.shields.io/badge/Install%20with%20NPX-VS%20Code-blue?style=for-the-badge&logo=visual-studio-code)](https://vscode.dev/redirect/mcp/install?name=bc-code-intel&config=%7B%22type%22%3A%22stdio%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22bc-code-intelligence-mcp%22%5D%7D)
-[![Installation Guide](https://img.shields.io/badge/Installation%20Guide-All%20Platforms-green?style=for-the-badge&logo=github)](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Installation-Guide)
-
-**Get instant help from AI Business Central experts** right in your favorite AI tool. No more searching docs - just ask and get expert guidance tailored to your specific BC development challenges.
-
----
-
-## 🚀 Quick Start
-
-1. **Click the blue "Install with NPX" button above** (VS Code users)
-2. **Switch to Agent Mode** in VS Code's Copilot Chat
-3. **Just ask!** - Start with any prompt below
-
-> **Other platforms?** See the [Installation Guide](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Installation-Guide) for Claude Desktop, Cursor, and more.
-
----
-
-## 🤝 New to AI-Assisted Development? Start with Parker
-
-If you're not sure how to work with AI tools, or you're skeptical about letting AI touch your code—**that's exactly why Parker exists**.
-
-Parker is a grizzled veteran who helps you work WITH AI safely:
-- Creates **reviewable proposals** instead of making direct changes
-- **Explains AI reasoning** so you understand what's happening and why
-- **Coordinates other specialists** to validate suggestions before you commit
-- Builds trust **gradually** through transparency and verification
-
-**Just say:**
-- "Parker, I'm new to AI development tools. Help me understand how this works."
-- "Parker, I don't trust AI to write my code. What's a safe way to start?"
-- "Parker, review what the AI just suggested before I accept it."
-
-Once you're comfortable, you can work directly with any specialist—but Parker's always there when you want that extra layer of verification and explanation.
-
----
-
-## 💬 Just Ask - Example Prompts
-
-The BC Code Intelligence specialists are ready to help. Just type naturally - here are some examples:
-
-### 🔍 Debugging & Performance (Dean)
-- "Dean, help me debug this error: 'The record in table Customer already exists'"
-- "I'm seeing slow performance when posting sales orders. Can Dean take a look?"
-- "Ask Dean why my FlowField is always showing zero"
-
-### 🏛️ Legacy Code & Upgrades (Logan)
-- "Logan, I need to upgrade my extension from BC v24 to v27"
-- "I inherited this old extension - can Logan help me understand what it does?"
-- "Help me modernize this C/AL-style code to proper AL patterns"
-
-### 🏗️ Architecture & Design (Alex)
-- "Alex, review my extension's architecture before I submit to AppSource"
-- "I need to design an integration with an external warehouse system"
-- "What's the best way to structure a multi-company solution?"
-
-### 💻 Coding & Implementation (Sam)
-- "Sam, help me write a function to calculate weighted average cost"
-- "I need to create a FactBox that shows related sales history"
-- "Show me the best way to implement a posting routine"
-
-### 🧪 Testing & Quality (Quinn)
-- "Quinn, help me create test coverage for my posting codeunit"
-- "What test scenarios should I include for this validation?"
-- "Review my test codeunit for completeness"
-
-### 📝 Code Review (Roger)
-- "Roger, review this codeunit for best practices"
-- "Check if my code follows BC naming conventions"
-- "Are there any code smells in my Customer Card extension?"
-
-### 🔒 Security (Seth)
-- "Seth, review my permission sets for security issues"
-- "How should I handle user permissions for this sensitive data?"
-- "Check if my API is exposing too much information"
-
-### 🌉 Integration & Events (Jordan)
-- "Jordan, help me design an event-driven integration"
-- "What's the best way to subscribe to posting events?"
-- "How do I create a clean API for external systems?"
-
-### ⚠️ Error Handling (Eva)
-- "Eva, help me implement proper error handling for this process"
-- "What's the best way to validate user input before posting?"
-- "Review my Try/Catch implementation"
-
-### 🎨 User Experience (Uma)
-- "Uma, help me improve my page layout for better usability"
-- "Can we switch from simple Error calls in this app to ErrorInfo with suggested actions?"
-- "Review my action menu structure"
-
-### 🏪 AppSource & ISV (Morgan)
-- "Morgan, help me prepare my app for AppSource submission"
-- "What are the common AppSource validation failures?"
-- "Review my app's technical baseline for AppSource"
-
-### 👩‍🏫 Learning & Mentoring (Maya)
-- "Maya, explain how dimensions work in BC"
-- "I'm new to AL - help me understand events and subscribers"
-- "Walk me through how posting routines work"
-
-### 📚 Documentation (Taylor)
-- "Taylor, help me document this complex codeunit"
-- "Generate XML documentation for my public procedures"
-- "Review my app's README for completeness"
-
-### 🤖 AI-Assisted Development (Casey)
-- "Casey, help me use AI tools effectively in my BC development"
-- "Based on this current project, what are some good instructions to help future agents understand working with this app immediately?"
-
----
-
-## 👥 Meet Your BC Specialist Team
-
-| Specialist | Expertise | Best For |
-|------------|-----------|----------|
-| **🤝 Parker** | AI Trust & Transparency | New to AI tools, safe collaboration, verification-first |
-| **🏗️ Alex** | Architecture & Design | Solution design, extension structure, integration patterns |
-| **💻 Sam** | Expert Coder | Writing AL code, implementation patterns, coding questions |
-| **🔍 Dean** | Debugging & Performance | Errors, slow queries, troubleshooting |
-| **⚠️ Eva** | Error Handling | Validation, Try/Catch, error messages |
-| **🧪 Quinn** | Testing | Test codeunits, test scenarios, code coverage |
-| **📝 Roger** | Code Review | Best practices, naming conventions, code quality |
-| **🔒 Seth** | Security | Permissions, data protection, API security |
-| **🌉 Jordan** | Integration | APIs, events, external connections |
-| **🏛️ Logan** | Legacy & Upgrades | Version migrations, old code, modernization |
-| **🎨 Uma** | User Experience | Page design, usability, UI patterns |
-| **🏪 Morgan** | AppSource & ISV | Publishing, validation, business concerns |
-| **👩‍🏫 Maya** | Mentoring | Learning concepts, explanations, training |
-| **📚 Taylor** | Documentation | Code docs, READMEs, knowledge sharing |
-| **🤖 Casey** | AI Development | Using AI tools, prompt engineering |
-| **⚙️ Chris** | MCP Configuiration | Company/Project MCP knowledge layer help|
-
----
-
-## 📚 Learn More
-
-| Topic | Link |
-|-------|------|
-| **Full Installation Options** | [Installation Guide](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Installation-Guide) |
-| **Common Scenarios** | [Usage Patterns](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Common-Scenarios) |
-| **All MCP Tools** | [Tools Reference](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/MCP-Tools-Reference) |
-| **Company Standards** | [Enterprise Configuration](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Enterprise-Configuration) |
-| **Structured Workflows** | [Methodology Framework](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Methodology-Framework) |
-| **Troubleshooting** | [Common Issues](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Troubleshooting) |
-
----
-
-## 💡 Tips
-
-- **Just use first names** - "Ask Dean" works just as well as "Ask Dean Debug"
-- **Be specific** - Include error messages, code snippets, or version numbers when relevant
-- **Specialists collaborate** - They'll hand off to each other when needed
-- **Context carries over** - Continue conversations naturally
-
----
-
-## 🤝 Contributing
-
-See the [Contributing Guide](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Contributing-Guide) for how to contribute to this project.
-
-## 📄 License
-
-MIT License - see [LICENSE](LICENSE) for details.
+# BC Code Intelligence MCP Server
+
+[![Install with NPX in VS Code](https://img.shields.io/badge/Install%20with%20NPX-VS%20Code-blue?style=for-the-badge&logo=visual-studio-code)](https://vscode.dev/redirect/mcp/install?name=bc-code-intel&config=%7B%22type%22%3A%22stdio%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22bc-code-intelligence-mcp%22%5D%7D)
+[![Installation Guide](https://img.shields.io/badge/Installation%20Guide-All%20Platforms-green?style=for-the-badge&logo=github)](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Installation-Guide)
+
+**Get instant help from AI Business Central experts** right in your favorite AI tool. No more searching docs - just ask and get expert guidance tailored to your specific BC development challenges.
+
+---
+
+## 🚀 Quick Start
+
+1. **Click the blue "Install with NPX" button above** (VS Code users)
+2. **Switch to Agent Mode** in VS Code's Copilot Chat
+3. **Just ask!** - Start with any prompt below
+
+> **Other platforms?** See the [Installation Guide](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Installation-Guide) for Claude Desktop, Cursor, and more.
+
+---
+
+## 🤝 New to AI-Assisted Development? Start with Parker
+
+If you're not sure how to work with AI tools, or you're skeptical about letting AI touch your code—**that's exactly why Parker exists**.
+
+Parker is a grizzled veteran who helps you work WITH AI safely:
+- Creates **reviewable proposals** instead of making direct changes
+- **Explains AI reasoning** so you understand what's happening and why
+- **Coordinates other specialists** to validate suggestions before you commit
+- Builds trust **gradually** through transparency and verification
+
+**Just say:**
+- "Parker, I'm new to AI development tools. Help me understand how this works."
+- "Parker, I don't trust AI to write my code. What's a safe way to start?"
+- "Parker, review what the AI just suggested before I accept it."
+
+Once you're comfortable, you can work directly with any specialist—but Parker's always there when you want that extra layer of verification and explanation.
+
+---
+
+## 💬 Just Ask - Example Prompts
+
+The BC Code Intelligence specialists are ready to help. Just type naturally - here are some examples:
+
+### 🔍 Debugging & Performance (Dean)
+- "Dean, help me debug this error: 'The record in table Customer already exists'"
+- "I'm seeing slow performance when posting sales orders. Can Dean take a look?"
+- "Ask Dean why my FlowField is always showing zero"
+
+### 🏛️ Legacy Code & Upgrades (Logan)
+- "Logan, I need to upgrade my extension from BC v24 to v27"
+- "I inherited this old extension - can Logan help me understand what it does?"
+- "Help me modernize this C/AL-style code to proper AL patterns"
+
+### 🏗️ Architecture & Design (Alex)
+- "Alex, review my extension's architecture before I submit to AppSource"
+- "I need to design an integration with an external warehouse system"
+- "What's the best way to structure a multi-company solution?"
+
+### 💻 Coding & Implementation (Sam)
+- "Sam, help me write a function to calculate weighted average cost"
+- "I need to create a FactBox that shows related sales history"
+- "Show me the best way to implement a posting routine"
+
+### 🧪 Testing & Quality (Quinn)
+- "Quinn, help me create test coverage for my posting codeunit"
+- "What test scenarios should I include for this validation?"
+- "Review my test codeunit for completeness"
+
+### 📝 Code Review (Roger)
+- "Roger, review this codeunit for best practices"
+- "Check if my code follows BC naming conventions"
+- "Are there any code smells in my Customer Card extension?"
+
+### 🔒 Security (Seth)
+- "Seth, review my permission sets for security issues"
+- "How should I handle user permissions for this sensitive data?"
+- "Check if my API is exposing too much information"
+
+### 🌉 Integration & Events (Jordan)
+- "Jordan, help me design an event-driven integration"
+- "What's the best way to subscribe to posting events?"
+- "How do I create a clean API for external systems?"
+
+### ⚠️ Error Handling (Eva)
+- "Eva, help me implement proper error handling for this process"
+- "What's the best way to validate user input before posting?"
+- "Review my Try/Catch implementation"
+
+### 🎨 User Experience (Uma)
+- "Uma, help me improve my page layout for better usability"
+- "Can we switch from simple Error calls in this app to ErrorInfo with suggested actions?"
+- "Review my action menu structure"
+
+### 🏪 AppSource & ISV (Morgan)
+- "Morgan, help me prepare my app for AppSource submission"
+- "What are the common AppSource validation failures?"
+- "Review my app's technical baseline for AppSource"
+
+### 👩‍🏫 Learning & Mentoring (Maya)
+- "Maya, explain how dimensions work in BC"
+- "I'm new to AL - help me understand events and subscribers"
+- "Walk me through how posting routines work"
+
+### 📚 Documentation (Taylor)
+- "Taylor, help me document this complex codeunit"
+- "Generate XML documentation for my public procedures"
+- "Review my app's README for completeness"
+
+### 🤖 AI-Assisted Development (Casey)
+- "Casey, help me use AI tools effectively in my BC development"
+- "Based on this current project, what are some good instructions to help future agents understand working with this app immediately?"
+
+---
+
+## 👥 Meet Your BC Specialist Team
+
+| Specialist | Expertise | Best For |
+|------------|-----------|----------|
+| **🤝 Parker** | AI Trust & Transparency | New to AI tools, safe collaboration, verification-first |
+| **🏗️ Alex** | Architecture & Design | Solution design, extension structure, integration patterns |
+| **💻 Sam** | Expert Coder | Writing AL code, implementation patterns, coding questions |
+| **🔍 Dean** | Debugging & Performance | Errors, slow queries, troubleshooting |
+| **⚠️ Eva** | Error Handling | Validation, Try/Catch, error messages |
+| **🧪 Quinn** | Testing | Test codeunits, test scenarios, code coverage |
+| **📝 Roger** | Code Review | Best practices, naming conventions, code quality |
+| **🔒 Seth** | Security | Permissions, data protection, API security |
+| **🌉 Jordan** | Integration | APIs, events, external connections |
+| **🏛️ Logan** | Legacy & Upgrades | Version migrations, old code, modernization |
+| **🎨 Uma** | User Experience | Page design, usability, UI patterns |
+| **🏪 Morgan** | AppSource & ISV | Publishing, validation, business concerns |
+| **👩‍🏫 Maya** | Mentoring | Learning concepts, explanations, training |
+| **📚 Taylor** | Documentation | Code docs, READMEs, knowledge sharing |
+| **🤖 Casey** | AI Development | Using AI tools, prompt engineering |
+| **⚙️ Chris** | MCP Configuiration | Company/Project MCP knowledge layer help|
+
+---
+
+## 📚 Learn More
+
+| Topic | Link |
+|-------|------|
+| **Full Installation Options** | [Installation Guide](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Installation-Guide) |
+| **Common Scenarios** | [Usage Patterns](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Common-Scenarios) |
+| **All MCP Tools** | [Tools Reference](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/MCP-Tools-Reference) |
+| **Company Standards** | [Enterprise Configuration](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Enterprise-Configuration) |
+| **Structured Workflows** | [Methodology Framework](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Methodology-Framework) |
+| **Troubleshooting** | [Common Issues](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Troubleshooting) |
+
+---
+
+## 💡 Tips
+
+- **Just use first names** - "Ask Dean" works just as well as "Ask Dean Debug"
+- **Be specific** - Include error messages, code snippets, or version numbers when relevant
+- **Specialists collaborate** - They'll hand off to each other when needed
+- **Context carries over** - Continue conversations naturally
+
+---
+
+## 🤝 Contributing
+
+See the [Contributing Guide](https://github.com/JeremyVyska/bc-code-intelligence-mcp/wiki/Contributing-Guide) for how to contribute to this project.
+
+## 📄 License
+
+MIT License - see [LICENSE](LICENSE) for details.

package/dist/layers/embedded-layer.js

@@ -37,20 +37,20 @@ export class EmbeddedKnowledgeLayer extends BaseKnowledgeLayer {
             console.error(`Initializing ${this.name} layer from ${this.embeddedPath}...`);
             // Early validation: Check if embedded knowledge directory exists and has content
             if (!existsSync(this.embeddedPath)) {
-                throw new Error(`
-🚨 BC Code Intelligence MCP Server Setup Issue
-
-PROBLEM: Embedded knowledge directory not found
-PATH: ${this.embeddedPath}
-
-LIKELY CAUSE: The git submodule 'embedded-knowledge' was not initialized when this package was built/installed.
-
-SOLUTIONS:
-📦 For NPM users: Update to the latest version with: npm update bc-code-intelligence-mcp
-🔧 For developers: Run: git submodule init && git submodule update  
-🏢 For package maintainers: Ensure submodules are initialized before npm publish
-
-The embedded-knowledge directory should contain BC expertise (domains/ or topics/, specialists/, methodologies/) required for the MCP server to function.
+                throw new Error(`
+🚨 BC Code Intelligence MCP Server Setup Issue
+
+PROBLEM: Embedded knowledge directory not found
+PATH: ${this.embeddedPath}
+
+LIKELY CAUSE: The git submodule 'embedded-knowledge' was not initialized when this package was built/installed.
+
+SOLUTIONS:
+📦 For NPM users: Update to the latest version with: npm update bc-code-intelligence-mcp
+🔧 For developers: Run: git submodule init && git submodule update  
+🏢 For package maintainers: Ensure submodules are initialized before npm publish
+
+The embedded-knowledge directory should contain BC expertise (domains/ or topics/, specialists/, methodologies/) required for the MCP server to function.
         `.trim());
             }
             // Check if directory has the expected structure (domains/ or topics/ are both valid)
@@ -66,21 +66,21 @@ The embedded-knowledge directory should contain BC expertise (domains/ or topics
             if (!hasMethodologies)
                 missingDirs.push('methodologies');
             if (missingDirs.length > 0) {
-                throw new Error(`
-🚨 BC Code Intelligence MCP Server Setup Issue
-
-PROBLEM: Incomplete embedded knowledge structure
-PATH: ${this.embeddedPath}
-MISSING: ${missingDirs.join(', ')}
-
-LIKELY CAUSE: The embedded-knowledge submodule is present but incomplete or corrupted.
-
-SOLUTIONS:
-📦 For NPM users: Update to the latest version with: npm update bc-code-intelligence-mcp
-🔧 For developers: Run: git submodule update --remote --force
-🏢 For package maintainers: Verify submodule content before npm publish
-
-Expected structure: (domains/ or topics/), specialists/, methodologies/ directories with BC expertise content.
+                throw new Error(`
+🚨 BC Code Intelligence MCP Server Setup Issue
+
+PROBLEM: Incomplete embedded knowledge structure
+PATH: ${this.embeddedPath}
+MISSING: ${missingDirs.join(', ')}
+
+LIKELY CAUSE: The embedded-knowledge submodule is present but incomplete or corrupted.
+
+SOLUTIONS:
+📦 For NPM users: Update to the latest version with: npm update bc-code-intelligence-mcp
+🔧 For developers: Run: git submodule update --remote --force
+🏢 For package maintainers: Verify submodule content before npm publish
+
+Expected structure: (domains/ or topics/), specialists/, methodologies/ directories with BC expertise content.
         `.trim());
             }
             // Load topics, specialists, and indexes in parallel

package/dist/layers/project-layer.js

@@ -247,39 +247,39 @@ export class ProjectKnowledgeLayer extends BaseKnowledgeLayer {
      * Create a sample project override structure
      */
     static generateSampleStructure() {
-        return `
-bckb-overrides/
-├── domains/
-│   ├── performance/
-│   │   └── al-performance-optimization.md    # Override embedded topic
-│   └── custom-domain/
-│       └── company-specific-pattern.md       # New company-specific topic
-├── indexes/
-│   └── company-standards.json                # Company-specific standards
-└── README.md                                 # Documentation for overrides
-
-Example override topic (bckb-overrides/domains/performance/al-performance-optimization.md):
----
-title: "AL Performance Optimization - Company Standards"
-domain: "performance"
-difficulty: "intermediate"
-bc_versions: "14+"
-tags: ["performance", "sift", "company-standard"]
-related_topics: ["database-optimization", "query-patterns"]
----
-
-# AL Performance Optimization - Company Standards
-
-This topic overrides the standard performance optimization guidance with
-company-specific requirements and standards.
-
-## Company Requirements
-
-- All queries must use SetLoadFields
-- SIFT optimization is mandatory for all reporting
-- Performance testing required for all table operations
-
-[Company-specific content here...]
+        return `
+bckb-overrides/
+├── domains/
+│   ├── performance/
+│   │   └── al-performance-optimization.md    # Override embedded topic
+│   └── custom-domain/
+│       └── company-specific-pattern.md       # New company-specific topic
+├── indexes/
+│   └── company-standards.json                # Company-specific standards
+└── README.md                                 # Documentation for overrides
+
+Example override topic (bckb-overrides/domains/performance/al-performance-optimization.md):
+---
+title: "AL Performance Optimization - Company Standards"
+domain: "performance"
+difficulty: "intermediate"
+bc_versions: "14+"
+tags: ["performance", "sift", "company-standard"]
+related_topics: ["database-optimization", "query-patterns"]
+---
+
+# AL Performance Optimization - Company Standards
+
+This topic overrides the standard performance optimization guidance with
+company-specific requirements and standards.
+
+## Company Requirements
+
+- All queries must use SetLoadFields
+- SIFT optimization is mandatory for all reporting
+- Performance testing required for all table operations
+
+[Company-specific content here...]
 `.trim();
     }
 }

package/dist/services/knowledge-service.d.ts

@@ -25,7 +25,7 @@ export declare class KnowledgeService {
     /**
      * Get a specific topic by ID with layer resolution
      */
-    getTopic(topicId: string, includeSamples?: boolean): Promise<AtomicTopic | null>;
+    getTopic(topicId: string, includeSamples?: boolean, contextDomain?: string): Promise<AtomicTopic | null>;
     /**
      * Get topic relationships and learning paths from layers
      */

package/dist/services/knowledge-service.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"knowledge-service.d.ts","sourceRoot":"","sources":["../../src/services/knowledge-service.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,WAAW,EACX,iBAAiB,EACjB,iBAAiB,EACjB,UAAU,EAGX,MAAM,0BAA0B,CAAC;AAClC,OAAO,EAAE,wBAAwB,EAAE,MAAM,4CAA4C,CAAC;AAEtF,OAAO,EAAE,oBAAoB,EAAE,MAAM,wBAAwB,CAAC;AAI9D;;;;;;GAMG;AACH,qBAAa,gBAAgB;IAIf,OAAO,CAAC,MAAM;IAH1B,OAAO,CAAC,YAAY,CAA2B;IAC/C,OAAO,CAAC,WAAW,CAAS;gBAER,MAAM,EAAE,UAAU,EAAE,YAAY,CAAC,EAAE,wBAAwB;IAgB/E;;OAEG;IACG,UAAU,IAAI,OAAO,CAAC,IAAI,CAAC;IAoCjC,OAAO,CAAC,aAAa;IAsBrB;;OAEG;IACG,YAAY,CAAC,MAAM,EAAE,iBAAiB,GAAG,OAAO,CAAC,iBAAiB,EAAE,CAAC;IAU3E;;OAEG;IACG,QAAQ,CAAC,OAAO,EAAE,MAAM,EAAE,cAAc,UAAQ,GAAG,OAAO,CAAC,WAAW,GAAG,IAAI,CAAC;IAkBpF;;OAEG;IACG,qBAAqB,CAAC,OAAO,EAAE,MAAM;IAsB3C;;OAEG;IACH,OAAO,CAAC,oBAAoB;IAa5B;;OAEG;YACW,mBAAmB;IA6BjC;;OAEG;IACG,gBAAgB,CAAC,IAAI,EAAE,MAAM,GAAG,OAAO,CAAC,WAAW,EAAE,CAAC;IAkB5D;;OAEG;IACH,aAAa;;;;;;;;;;IAyBb;;OAEG;IACG,wBAAwB,CAAC,YAAY,EAAE,MAAM,EAAE,KAAK,CAAC,EAAE,MAAM,EAAE,KAAK,SAAK,GAAG,OAAO,CAAC,iBAAiB,EAAE,CAAC;IAmB9G;;;OAGG;IA+BH;;OAEG;IACH;;OAEG;IACG,iBAAiB,IAAI,OAAO,CAAC,oBAAoB,EAAE,CAAC;IAS1D;;OAEG;IACG,aAAa,CAAC,QAAQ,EAAE,MAAM,EAAE,mBAAmB,CAAC,EAAE,MAAM,GAAG,OAAO,CAAC,GAAG,CAAC;IASjF;;OAEG;IACG,sBAAsB,CAAC,KAAK,EAAE,MAAM,GAAG,OAAO,CAAC,GAAG,EAAE,CAAC;IAW3D;;;OAGG;IAOH;;OAEG;IACH,OAAO,CAAC,2BAA2B;CAqCpC"}
+{"version":3,"file":"knowledge-service.d.ts","sourceRoot":"","sources":["../../src/services/knowledge-service.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,WAAW,EACX,iBAAiB,EACjB,iBAAiB,EACjB,UAAU,EAGX,MAAM,0BAA0B,CAAC;AAClC,OAAO,EAAE,wBAAwB,EAAE,MAAM,4CAA4C,CAAC;AAEtF,OAAO,EAAE,oBAAoB,EAAE,MAAM,wBAAwB,CAAC;AAI9D;;;;;;GAMG;AACH,qBAAa,gBAAgB;IAIf,OAAO,CAAC,MAAM;IAH1B,OAAO,CAAC,YAAY,CAA2B;IAC/C,OAAO,CAAC,WAAW,CAAS;gBAER,MAAM,EAAE,UAAU,EAAE,YAAY,CAAC,EAAE,wBAAwB;IAgB/E;;OAEG;IACG,UAAU,IAAI,OAAO,CAAC,IAAI,CAAC;IAoCjC,OAAO,CAAC,aAAa;IAsBrB;;OAEG;IACG,YAAY,CAAC,MAAM,EAAE,iBAAiB,GAAG,OAAO,CAAC,iBAAiB,EAAE,CAAC;IAU3E;;OAEG;IACG,QAAQ,CAAC,OAAO,EAAE,MAAM,EAAE,cAAc,UAAQ,EAAE,aAAa,CAAC,EAAE,MAAM,GAAG,OAAO,CAAC,WAAW,GAAG,IAAI,CAAC;IA4F5G;;OAEG;IACG,qBAAqB,CAAC,OAAO,EAAE,MAAM;IAsB3C;;OAEG;IACH,OAAO,CAAC,oBAAoB;IAa5B;;OAEG;YACW,mBAAmB;IA6BjC;;OAEG;IACG,gBAAgB,CAAC,IAAI,EAAE,MAAM,GAAG,OAAO,CAAC,WAAW,EAAE,CAAC;IAkB5D;;OAEG;IACH,aAAa;;;;;;;;;;IAyBb;;OAEG;IACG,wBAAwB,CAAC,YAAY,EAAE,MAAM,EAAE,KAAK,CAAC,EAAE,MAAM,EAAE,KAAK,SAAK,GAAG,OAAO,CAAC,iBAAiB,EAAE,CAAC;IAmB9G;;;OAGG;IA+BH;;OAEG;IACH;;OAEG;IACG,iBAAiB,IAAI,OAAO,CAAC,oBAAoB,EAAE,CAAC;IAS1D;;OAEG;IACG,aAAa,CAAC,QAAQ,EAAE,MAAM,EAAE,mBAAmB,CAAC,EAAE,MAAM,GAAG,OAAO,CAAC,GAAG,CAAC;IASjF;;OAEG;IACG,sBAAsB,CAAC,KAAK,EAAE,MAAM,GAAG,OAAO,CAAC,GAAG,EAAE,CAAC;IAW3D;;;OAGG;IAOH;;OAEG;IACH,OAAO,CAAC,2BAA2B;CAqCpC"}

package/dist/services/knowledge-service.js

@@ -93,14 +93,82 @@ export class KnowledgeService {
     /**
      * Get a specific topic by ID with layer resolution
      */
-    async getTopic(topicId, includeSamples = false) {
+    async getTopic(topicId, includeSamples = false, contextDomain) {
         if (!this.initialized) {
             await this.initialize();
         }
         // Resolve topic through layer system
         const resolution = await this.layerService.resolveTopic(topicId);
-        if (!resolution)
-            return null;
+        if (!resolution) {
+            // If exact match fails, suggest similar topics
+            const suggestions = await this.layerService.findPartialTopicMatches(topicId);
+            if (suggestions.length > 0) {
+                const error = {
+                    error: 'Topic not found',
+                    message: `Topic ID '${topicId}' not found. Did you mean one of these?`,
+                    suggestions: suggestions.map(s => ({
+                        topic_id: s.id,
+                        title: s.title,
+                        domain: s.domain
+                    }))
+                };
+                // Return error object disguised as a topic for better UX
+                return error;
+            }
+            // No partial matches found - try to extract domain from topic_id and show domain topics
+            const domainMatch = topicId.match(/^([^/]+)\//);
+            if (domainMatch) {
+                const domain = domainMatch[1];
+                const domainTopics = await this.layerService.getTopicsByDomain(domain);
+                if (domainTopics.length > 0) {
+                    return {
+                        error: 'Topic not found',
+                        message: `Topic ID '${topicId}' not found in domain '${domain}'. Available topics in this domain:`,
+                        available_topics: domainTopics.map(t => ({
+                            topic_id: t.id,
+                            title: t.title
+                        }))
+                    };
+                }
+            }
+            // If we have context domain (from active specialist), show topics from that domain
+            if (contextDomain) {
+                const domainTopics = await this.layerService.getTopicsByDomain(contextDomain);
+                if (domainTopics.length > 0) {
+                    return {
+                        error: 'Topic not found',
+                        message: `Topic ID '${topicId}' not found. Available topics in '${contextDomain}' domain:`,
+                        available_topics: domainTopics.map(t => ({
+                            topic_id: t.id,
+                            title: t.title
+                        })),
+                        hint: `You are currently working with the '${contextDomain}' specialist. Use full topic IDs like '${contextDomain}/topic-name'`
+                    };
+                }
+            }
+            // Last resort: show topics grouped by domain for easy navigation
+            const allTopicIds = this.layerService.getAllTopicIds();
+            const topicsByDomain = {};
+            for (const id of allTopicIds) {
+                const domain = id.split('/')[0];
+                if (!topicsByDomain[domain])
+                    topicsByDomain[domain] = [];
+                topicsByDomain[domain].push(id);
+            }
+            // Show max 3 topics per domain, max 10 domains
+            const domainSample = {};
+            const domains = Object.keys(topicsByDomain).slice(0, 10);
+            for (const domain of domains) {
+                domainSample[domain] = topicsByDomain[domain].slice(0, 3);
+            }
+            return {
+                error: 'Topic not found',
+                message: `Topic ID '${topicId}' not found. Available topics by domain (showing ${domains.length} domains):`,
+                topics_by_domain: domainSample,
+                total_topics: allTopicIds.length,
+                hint: 'Topic IDs follow the format: domain/topic-name. Use the domain that matches your current specialist.'
+            };
+        }
         // Return copy to prevent mutation
         const result = { ...resolution.topic };
         if (!includeSamples) {