bc-code-intelligence-mcp 1.6.0 → 1.6.1

package/dist/tools/workflow_list/schema.js

@@ -5,17 +5,17 @@
  */
 export const workflowListTool = {
     name: 'workflow_list',
-    description: `List all available BC Code Intelligence workflows.
-
-Use this tool to discover structured workflows that can guide the user through complex processes like code reviews, debugging, or app development.
-
-Returns a list of available workflows with:
-- workflow_type: The ID to pass to workflow_start
-- name: Human-readable workflow name
-- description: What the workflow helps with
-- specialist: The recommended specialist for this workflow
-- phases: The phases/steps in the workflow
-
+    description: `List all available BC Code Intelligence workflows.
+
+Use this tool to discover structured workflows that can guide the user through complex processes like code reviews, debugging, or app development.
+
+Returns a list of available workflows with:
+- workflow_type: The ID to pass to workflow_start
+- name: Human-readable workflow name
+- description: What the workflow helps with
+- specialist: The recommended specialist for this workflow
+- phases: The phases/steps in the workflow
+
 Call this early in conversations to see if a workflow matches the user's intent.`,
     inputSchema: {
         type: 'object',

package/dist/tools/workflow_next/schema.js

@@ -5,14 +5,14 @@
  */
 export const workflowNextTool = {
     name: 'workflow_next',
-    description: `Get the next action to perform in a workflow session.
-
-Call this when you're ready for the next task. The engine returns:
-- Current progress (phase, files completed, percent)
-- Current file's checklist status
-- Next action with explicit instructions
-- Tool call suggestions for the action
-
+    description: `Get the next action to perform in a workflow session.
+
+Call this when you're ready for the next task. The engine returns:
+- Current progress (phase, files completed, percent)
+- Current file's checklist status
+- Next action with explicit instructions
+- Tool call suggestions for the action
+
 The agent MUST follow the next_action instructions exactly.`,
     inputSchema: {
         type: 'object',

package/dist/tools/workflow_progress/schema.js

@@ -5,11 +5,11 @@
  */
 export const workflowProgressTool = {
     name: 'workflow_progress',
-    description: `Report progress on current workflow action and get the next action.
-
-Call this after completing each action (analyzing a file, applying a topic, converting an instance).
-Include any findings, proposed changes, and topics to add to the checklist.
-
+    description: `Report progress on current workflow action and get the next action.
+
+Call this after completing each action (analyzing a file, applying a topic, converting an instance).
+Include any findings, proposed changes, and topics to add to the checklist.
+
 The engine updates session state and returns the next action to perform.`,
     inputSchema: {
         type: 'object',

package/dist/tools/workflow_start/schema.js

@@ -5,20 +5,20 @@
  */
 export const workflowStartTool = {
     name: 'workflow_start',
-    description: `Start a workflow session - a stateful checklist management system that drives agents through systematic, file-by-file processing.
-
-Workflows provide:
-- File inventory with per-file checklists
-- Dynamic checklist expansion based on analysis
-- Pattern scanning for migrations (e.g., Error→ErrorInfo)
-- Batch operations for large-scale changes
-- Progress tracking and session persistence
-
-The workflow drives the agent with explicit next-action instructions.
-
-Example usage:
-- Start a code review: workflow_type="code-review"
-- Start an error migration: workflow_type="error-to-errorinfo-migration"
+    description: `Start a workflow session - a stateful checklist management system that drives agents through systematic, file-by-file processing.
+
+Workflows provide:
+- File inventory with per-file checklists
+- Dynamic checklist expansion based on analysis
+- Pattern scanning for migrations (e.g., Error→ErrorInfo)
+- Batch operations for large-scale changes
+- Progress tracking and session persistence
+
+The workflow drives the agent with explicit next-action instructions.
+
+Example usage:
+- Start a code review: workflow_type="code-review"
+- Start an error migration: workflow_type="error-to-errorinfo-migration"
 - Start a BC upgrade: workflow_type="bc-version-upgrade" with source_version and target_version`,
     inputSchema: {
         type: 'object',

package/dist/tools/workflow_status/schema.js

@@ -5,14 +5,14 @@
  */
 export const workflowStatusTool = {
     name: 'workflow_status',
-    description: `Get current workflow v2 session status without advancing.
-
-Returns:
-- Overall progress (phase, percent complete)
-- Summary of findings by severity
-- Summary of proposed changes
-- Optionally: status of all files
-
+    description: `Get current workflow v2 session status without advancing.
+
+Returns:
+- Overall progress (phase, percent complete)
+- Summary of findings by severity
+- Summary of proposed changes
+- Optionally: status of all files
+
 Use this to check on workflow progress or recover context after interruption.`,
     inputSchema: {
         type: 'object',

package/embedded-knowledge/.github/ISSUE_TEMPLATE/bug-report.md

@@ -1,24 +1,24 @@
----
-name: Content Bug Report
-about: Report incorrect or outdated BC knowledge
-title: '[BUG] '
-labels: ['bug', 'content-error']
-assignees: ''
----
-
-## Content Bug Report
-
-### Affected Content
-Which file(s) or topic(s) contain the error?
-
-### Bug Description
-What information is incorrect or outdated?
-
-### Expected Content
-What should the correct information be?
-
-### BC Version Context
-Which BC versions are affected by this error?
-
-### Evidence
+---
+name: Content Bug Report
+about: Report incorrect or outdated BC knowledge
+title: '[BUG] '
+labels: ['bug', 'content-error']
+assignees: ''
+---
+
+## Content Bug Report
+
+### Affected Content
+Which file(s) or topic(s) contain the error?
+
+### Bug Description
+What information is incorrect or outdated?
+
+### Expected Content
+What should the correct information be?
+
+### BC Version Context
+Which BC versions are affected by this error?
+
+### Evidence
 Any links, documentation, or testing that supports the correction?

package/embedded-knowledge/.github/ISSUE_TEMPLATE/content-improvement.md

@@ -1,24 +1,24 @@
----
-name: Content Improvement
-about: Suggest improvements to existing knowledge content
-title: '[IMPROVEMENT] '
-labels: ['enhancement', 'content-improvement']
-assignees: ''
----
-
-## Content Improvement Suggestion
-
-### Target Content
-Which file(s) or topic(s) need improvement?
-
-### Issue Description
-What is incorrect, unclear, or missing?
-
-### Proposed Changes
-What specific improvements do you suggest?
-
-### BC Version Impact
-Do the changes affect BC version compatibility?
-
-### Additional Context
+---
+name: Content Improvement
+about: Suggest improvements to existing knowledge content
+title: '[IMPROVEMENT] '
+labels: ['enhancement', 'content-improvement']
+assignees: ''
+---
+
+## Content Improvement Suggestion
+
+### Target Content
+Which file(s) or topic(s) need improvement?
+
+### Issue Description
+What is incorrect, unclear, or missing?
+
+### Proposed Changes
+What specific improvements do you suggest?
+
+### BC Version Impact
+Do the changes affect BC version compatibility?
+
+### Additional Context
 Any additional context, links, or examples that would help?

package/embedded-knowledge/.github/ISSUE_TEMPLATE/knowledge-request.md

@@ -1,30 +1,30 @@
----
-name: Knowledge Topic Request
-about: Request new BC knowledge topic or enhancement to existing topic
-title: '[KNOWLEDGE] '
-labels: ['enhancement', 'knowledge-request']
-assignees: ''
----
-
-## Knowledge Topic Request
-
-### BC Domain
-Which BC domain does this relate to? (performance, api-design, security, etc.)
-
-### Topic Description
-What specific BC concept or pattern should be documented?
-
-### BC Version Context
-Which BC versions does this apply to?
-
-### Use Case
-What scenario or problem would this knowledge help solve?
-
-### Existing Resources
-Are there any existing resources, documentation, or examples for this topic?
-
-### Priority
-- [ ] Critical (blocking development)
-- [ ] High (significant impact)
-- [ ] Medium (helpful enhancement)
+---
+name: Knowledge Topic Request
+about: Request new BC knowledge topic or enhancement to existing topic
+title: '[KNOWLEDGE] '
+labels: ['enhancement', 'knowledge-request']
+assignees: ''
+---
+
+## Knowledge Topic Request
+
+### BC Domain
+Which BC domain does this relate to? (performance, api-design, security, etc.)
+
+### Topic Description
+What specific BC concept or pattern should be documented?
+
+### BC Version Context
+Which BC versions does this apply to?
+
+### Use Case
+What scenario or problem would this knowledge help solve?
+
+### Existing Resources
+Are there any existing resources, documentation, or examples for this topic?
+
+### Priority
+- [ ] Critical (blocking development)
+- [ ] High (significant impact)
+- [ ] Medium (helpful enhancement)
 - [ ] Low (nice to have)

package/embedded-knowledge/AGENTS.md

@@ -1,178 +1,178 @@
-# AGENTS.md - Repository Context for AI Assistants
-
-## Repository Purpose
-This is the **knowledge content repository** for the BC Code Intelligence (bc-code-intel) system.
-
-## What This Repo Contains
-- **BC Domain Knowledge**: 87+ atomic topics across 24 domains (performance, API design, security, etc.)
-- **Methodology Frameworks**: Step-by-step AI workflow guidance for systematic optimization
-- **Specialists Definitions**: 14 AI persona configurations with domain expertise and behavioral constraints
-- **Strategic Prompts**: High-level prompts for common BC development scenarios
-- **Pure Markdown Content**: No code whatsoever - only knowledge content with YAML frontmatter
-
-## What This Repo Does NOT Contain
-- TypeScript/JavaScript code (that's in bc-code-intelligence-mcp repository)
-- MCP server implementation or protocol handling
-- Build processes, dependencies, or package.json files
-- Compiled or generated content
-
-## Repository Structure
-```
-domains/                    # BC knowledge organized by domain
-├── performance/           # Performance optimization patterns
-├── api-design/           # REST/OData API best practices
-├── data-architecture/    # Table design and relationships
-├── security/             # Authentication and authorization
-└── [20 other domains]/
-
-methodologies/            # AI workflow frameworks
-├── phases/              # Systematic analysis phases
-└── workflows/           # Complete optimization workflows
-
-specialists/             # AI persona definitions
-├── alex-architect.md        # Strategic Planning & Architecture
-├── casey-copilot.md         # AI-Enhanced Development Coach
-├── dean-debug.md            # Performance & Troubleshooting
-├── eva-errors.md            # Error Handling & Exception Management
-├── jordan-bridge.md         # Systems Connection & Event-Driven Design
-├── logan-legacy.md          # Legacy Code & Version Migration
-├── maya-mentor.md           # Learning & Skill Development
-├── morgan-market.md         # AppSource & ISV Business Expert
-├── quinn-tester.md          # Quality Validation & Test Design
-├── roger-reviewer.md        # Code Quality & Review Standards
-├── sam-coder.md             # Efficient Implementation Expert
-├── seth-security.md         # Security & Permission Management
-├── taylor-docs.md           # Documentation & Knowledge Management
-└── uma-ux.md                # User Experience & Interface Design
-
-prompts/                # Strategic prompts
-├── analyze-performance.md
-├── review-architecture.md
-└── [other prompts]/
-```
-
-## Content Standards
-- **Atomic Topics**: One focused concept per markdown file
-- **YAML Frontmatter**: Rich metadata for AI consumption including:
-  - BC version compatibility (`bc_versions: "14+"`)
-  - Difficulty level, tags, domain classification
-  - Cross-references to related topics
-- **Version Awareness**: All content specifies BC version compatibility
-- **Consistent Structure**: Follow established patterns for headings, examples, cross-references
-
-## AI Assistant Guidelines When Working With This Repo
-1. **Content Focus**: Maintain accuracy of BC technical information
-2. **Structure Integrity**: Preserve YAML frontmatter completeness and consistency
-3. **Version Compatibility**: Always specify BC version ranges for patterns/features
-4. **Cross-References**: Maintain accurate links between related topics
-5. **Atomic Principle**: Keep each file focused on one specific concept
-6. **NO CODE**: This repository contains NO executable code - knowledge only
-7. **Link Integrity**: Ensure internal topic references remain valid
-
-## GitHub Copilot Coding Agent Guidelines
-
-### Content Creation Patterns
-When creating new knowledge topics, ALWAYS use this YAML frontmatter template:
-```yaml
----
-title: "Descriptive Topic Title"
-domain: "performance|api-design|security|etc"
-bc_versions: "14+|18+|19+|specific-range"
-difficulty: "beginner|intermediate|advanced"
-tags: ["tag1", "tag2", "tag3"]
-related_topics:
-  - "path/to/related/topic.md"
-  - "another/related/topic.md"
-applies_to:
-  - "AL Language"
-  - "Business Central Server"
-  - "Web Client"
-last_updated: "2025-01-01"
----
-```
-
-### File Naming Conventions
-- Use kebab-case for all filenames: `api-pagination-patterns.md`
-- Include domain prefix when needed: `performance-caching-strategies.md`
-- Keep names descriptive but concise (max 50 characters)
-- Avoid abbreviations unless universally understood
-
-### Content Structure Requirements
-1. **H1 Title**: Must match YAML frontmatter title exactly
-2. **Overview Section**: 2-3 sentence summary of the concept
-3. **Implementation Details**: Step-by-step guidance with BC code examples
-4. **Best Practices**: Bulleted list of key recommendations
-5. **Common Pitfalls**: What to avoid with explanations
-6. **Version Notes**: BC version-specific considerations
-7. **See Also**: Cross-references to related topics
-
-### Cross-Reference Validation
-- Use relative paths: `../performance/caching-strategies.md`
-- Verify target files exist before creating references
-- Update both directions when creating new relationships
-- Use descriptive link text: `[API Pagination Patterns](../api-design/pagination-patterns.md)`
-
-### Domain Organization Rules
-```
-domains/
-├── performance/          # Speed, memory, resource optimization
-├── api-design/          # REST, OData, integration patterns
-├── security/            # Authentication, authorization, data protection
-├── data-architecture/   # Table design, relationships, normalization
-├── error-handling/      # Exception management, validation
-├── testing/            # Unit, integration, performance testing
-└── [other domains]/    # Maintain alphabetical order
-```
-
-### Validation Checklist
-Before committing new content, verify:
-- [ ] YAML frontmatter is complete and valid
-- [ ] BC version compatibility is specified
-- [ ] Cross-references use relative paths and exist
-- [ ] Content is atomic (one focused concept)
-- [ ] No executable code is included
-- [ ] Examples use realistic BC scenarios
-- [ ] Tags are consistent with existing taxonomy
-
-### Common Anti-Patterns to Avoid
-- ❌ **Code Repositories**: Never include .cs, .al, .js, or executable files
-- ❌ **Generic Examples**: Avoid "MyTable" - use realistic BC entities
-- ❌ **Version Ambiguity**: Never omit BC version compatibility
-- ❌ **Broken Cross-References**: Always validate links before committing
-- ❌ **Topic Drift**: Keep each file focused on ONE concept
-- ❌ **Outdated Information**: Update last_updated when making changes
-
-## Common Tasks
-- Adding new BC knowledge topics with proper frontmatter and validation
-- Updating existing topics for new BC versions with migration notes
-- Creating bidirectional cross-references between related topics
-- Validating YAML frontmatter structure and consistency
-- Organizing content within domain hierarchies and maintaining taxonomy
-- Performing content audits for accuracy and BC version compatibility
-
-## GitHub Copilot Integration Workflows
-
-### New Topic Creation Workflow
-1. **Domain Classification**: Determine primary domain from existing taxonomy
-2. **Version Research**: Identify minimum BC version and any version-specific notes
-3. **Template Application**: Use YAML frontmatter template with all required fields
-4. **Content Development**: Follow structure requirements for consistency
-5. **Cross-Reference Integration**: Add to related topics and update existing references
-6. **Validation**: Run through validation checklist before committing
-
-### Content Update Workflow
-1. **Impact Assessment**: Identify which BC versions are affected
-2. **Cross-Reference Review**: Check if related topics need updates
-3. **Version Compatibility**: Update bc_versions field if needed
-4. **Last Updated**: Always update timestamp when making changes
-5. **Validation**: Ensure all links and references remain valid
-
-### Quality Assurance Patterns
-- **Atomic Content Principle**: Each file covers exactly one BC concept
-- **Consistent Terminology**: Use official Microsoft BC terminology
-- **Practical Examples**: Include realistic Business Central scenarios
-- **Version Awareness**: Every pattern specifies BC version compatibility
-- **Link Validation**: Cross-references must be bidirectional and accurate
-
-## Integration
+# AGENTS.md - Repository Context for AI Assistants
+
+## Repository Purpose
+This is the **knowledge content repository** for the BC Code Intelligence (bc-code-intel) system.
+
+## What This Repo Contains
+- **BC Domain Knowledge**: 87+ atomic topics across 24 domains (performance, API design, security, etc.)
+- **Methodology Frameworks**: Step-by-step AI workflow guidance for systematic optimization
+- **Specialists Definitions**: 14 AI persona configurations with domain expertise and behavioral constraints
+- **Strategic Prompts**: High-level prompts for common BC development scenarios
+- **Pure Markdown Content**: No code whatsoever - only knowledge content with YAML frontmatter
+
+## What This Repo Does NOT Contain
+- TypeScript/JavaScript code (that's in bc-code-intelligence-mcp repository)
+- MCP server implementation or protocol handling
+- Build processes, dependencies, or package.json files
+- Compiled or generated content
+
+## Repository Structure
+```
+domains/                    # BC knowledge organized by domain
+├── performance/           # Performance optimization patterns
+├── api-design/           # REST/OData API best practices
+├── data-architecture/    # Table design and relationships
+├── security/             # Authentication and authorization
+└── [20 other domains]/
+
+methodologies/            # AI workflow frameworks
+├── phases/              # Systematic analysis phases
+└── workflows/           # Complete optimization workflows
+
+specialists/             # AI persona definitions
+├── alex-architect.md        # Strategic Planning & Architecture
+├── casey-copilot.md         # AI-Enhanced Development Coach
+├── dean-debug.md            # Performance & Troubleshooting
+├── eva-errors.md            # Error Handling & Exception Management
+├── jordan-bridge.md         # Systems Connection & Event-Driven Design
+├── logan-legacy.md          # Legacy Code & Version Migration
+├── maya-mentor.md           # Learning & Skill Development
+├── morgan-market.md         # AppSource & ISV Business Expert
+├── quinn-tester.md          # Quality Validation & Test Design
+├── roger-reviewer.md        # Code Quality & Review Standards
+├── sam-coder.md             # Efficient Implementation Expert
+├── seth-security.md         # Security & Permission Management
+├── taylor-docs.md           # Documentation & Knowledge Management
+└── uma-ux.md                # User Experience & Interface Design
+
+prompts/                # Strategic prompts
+├── analyze-performance.md
+├── review-architecture.md
+└── [other prompts]/
+```
+
+## Content Standards
+- **Atomic Topics**: One focused concept per markdown file
+- **YAML Frontmatter**: Rich metadata for AI consumption including:
+  - BC version compatibility (`bc_versions: "14+"`)
+  - Difficulty level, tags, domain classification
+  - Cross-references to related topics
+- **Version Awareness**: All content specifies BC version compatibility
+- **Consistent Structure**: Follow established patterns for headings, examples, cross-references
+
+## AI Assistant Guidelines When Working With This Repo
+1. **Content Focus**: Maintain accuracy of BC technical information
+2. **Structure Integrity**: Preserve YAML frontmatter completeness and consistency
+3. **Version Compatibility**: Always specify BC version ranges for patterns/features
+4. **Cross-References**: Maintain accurate links between related topics
+5. **Atomic Principle**: Keep each file focused on one specific concept
+6. **NO CODE**: This repository contains NO executable code - knowledge only
+7. **Link Integrity**: Ensure internal topic references remain valid
+
+## GitHub Copilot Coding Agent Guidelines
+
+### Content Creation Patterns
+When creating new knowledge topics, ALWAYS use this YAML frontmatter template:
+```yaml
+---
+title: "Descriptive Topic Title"
+domain: "performance|api-design|security|etc"
+bc_versions: "14+|18+|19+|specific-range"
+difficulty: "beginner|intermediate|advanced"
+tags: ["tag1", "tag2", "tag3"]
+related_topics:
+  - "path/to/related/topic.md"
+  - "another/related/topic.md"
+applies_to:
+  - "AL Language"
+  - "Business Central Server"
+  - "Web Client"
+last_updated: "2025-01-01"
+---
+```
+
+### File Naming Conventions
+- Use kebab-case for all filenames: `api-pagination-patterns.md`
+- Include domain prefix when needed: `performance-caching-strategies.md`
+- Keep names descriptive but concise (max 50 characters)
+- Avoid abbreviations unless universally understood
+
+### Content Structure Requirements
+1. **H1 Title**: Must match YAML frontmatter title exactly
+2. **Overview Section**: 2-3 sentence summary of the concept
+3. **Implementation Details**: Step-by-step guidance with BC code examples
+4. **Best Practices**: Bulleted list of key recommendations
+5. **Common Pitfalls**: What to avoid with explanations
+6. **Version Notes**: BC version-specific considerations
+7. **See Also**: Cross-references to related topics
+
+### Cross-Reference Validation
+- Use relative paths: `../performance/caching-strategies.md`
+- Verify target files exist before creating references
+- Update both directions when creating new relationships
+- Use descriptive link text: `[API Pagination Patterns](../api-design/pagination-patterns.md)`
+
+### Domain Organization Rules
+```
+domains/
+├── performance/          # Speed, memory, resource optimization
+├── api-design/          # REST, OData, integration patterns
+├── security/            # Authentication, authorization, data protection
+├── data-architecture/   # Table design, relationships, normalization
+├── error-handling/      # Exception management, validation
+├── testing/            # Unit, integration, performance testing
+└── [other domains]/    # Maintain alphabetical order
+```
+
+### Validation Checklist
+Before committing new content, verify:
+- [ ] YAML frontmatter is complete and valid
+- [ ] BC version compatibility is specified
+- [ ] Cross-references use relative paths and exist
+- [ ] Content is atomic (one focused concept)
+- [ ] No executable code is included
+- [ ] Examples use realistic BC scenarios
+- [ ] Tags are consistent with existing taxonomy
+
+### Common Anti-Patterns to Avoid
+- ❌ **Code Repositories**: Never include .cs, .al, .js, or executable files
+- ❌ **Generic Examples**: Avoid "MyTable" - use realistic BC entities
+- ❌ **Version Ambiguity**: Never omit BC version compatibility
+- ❌ **Broken Cross-References**: Always validate links before committing
+- ❌ **Topic Drift**: Keep each file focused on ONE concept
+- ❌ **Outdated Information**: Update last_updated when making changes
+
+## Common Tasks
+- Adding new BC knowledge topics with proper frontmatter and validation
+- Updating existing topics for new BC versions with migration notes
+- Creating bidirectional cross-references between related topics
+- Validating YAML frontmatter structure and consistency
+- Organizing content within domain hierarchies and maintaining taxonomy
+- Performing content audits for accuracy and BC version compatibility
+
+## GitHub Copilot Integration Workflows
+
+### New Topic Creation Workflow
+1. **Domain Classification**: Determine primary domain from existing taxonomy
+2. **Version Research**: Identify minimum BC version and any version-specific notes
+3. **Template Application**: Use YAML frontmatter template with all required fields
+4. **Content Development**: Follow structure requirements for consistency
+5. **Cross-Reference Integration**: Add to related topics and update existing references
+6. **Validation**: Run through validation checklist before committing
+
+### Content Update Workflow
+1. **Impact Assessment**: Identify which BC versions are affected
+2. **Cross-Reference Review**: Check if related topics need updates
+3. **Version Compatibility**: Update bc_versions field if needed
+4. **Last Updated**: Always update timestamp when making changes
+5. **Validation**: Ensure all links and references remain valid
+
+### Quality Assurance Patterns
+- **Atomic Content Principle**: Each file covers exactly one BC concept
+- **Consistent Terminology**: Use official Microsoft BC terminology
+- **Practical Examples**: Include realistic Business Central scenarios
+- **Version Awareness**: Every pattern specifies BC version compatibility
+- **Link Validation**: Cross-references must be bidirectional and accurate
+
+## Integration
 This repository is consumed by the MCP server via git submodule as the embedded knowledge layer (Layer 0).