bc-code-intelligence-mcp 1.5.8 → 1.6.0

package/embedded-knowledge/codelens-mappings.yaml

@@ -0,0 +1,111 @@
+# CodeLens Pattern-to-Specialist Mappings
+# These patterns are matched against AL code to suggest relevant specialists
+
+mappings:
+  # Error handling -> Eva
+  - pattern: "\\bError\\s*\\("
+    specialist: eva-errors
+    label: "Ask Eva about ErrorInfo"
+
+  - pattern: "\\bMessage\\s*\\("
+    specialist: eva-errors
+    label: "Review messaging with Eva"
+
+  - pattern: "\\bFieldError\\s*\\("
+    specialist: eva-errors
+    label: "FieldError guidance from Eva"
+
+  - pattern: "\\bTestField\\s*\\("
+    specialist: eva-errors
+    label: "TestField patterns with Eva"
+
+  # Events and integration -> Jordan
+  - pattern: "OnBefore|OnAfter|\\[EventSubscriber"
+    specialist: jordan-bridge
+    label: "Review with Jordan"
+
+  - pattern: "HttpClient|WebServiceActionContext"
+    specialist: jordan-bridge
+    label: "Integration review with Jordan"
+
+  - pattern: "\\[IntegrationEvent"
+    specialist: jordan-bridge
+    label: "Event design with Jordan"
+
+  # Security -> Seth
+  - pattern: "TableData|RIMD|Permissions"
+    specialist: seth-security
+    label: "Security review with Seth"
+
+  - pattern: "\\[Scope\\s*\\("
+    specialist: seth-security
+    label: "Scope review with Seth"
+
+  - pattern: "\\[InherentPermissions"
+    specialist: seth-security
+    label: "InherentPermissions with Seth"
+
+  - pattern: "\\[InherentEntitlements"
+    specialist: seth-security
+    label: "Entitlements review with Seth"
+
+  # Testing -> Quinn
+  - pattern: "\\[Test\\]"
+    specialist: quinn-tester
+    label: "Ask Quinn about testing"
+
+  - pattern: "\\[TestPermissions"
+    specialist: quinn-tester
+    label: "Test permissions with Quinn"
+
+  - pattern: "\\[HandlerFunctions"
+    specialist: quinn-tester
+    label: "Handler functions with Quinn"
+
+  - pattern: "LibraryAssert|Assert\\."
+    specialist: quinn-tester
+    label: "Assertions with Quinn"
+
+  # Performance -> Dean
+  - pattern: "FindSet|FindFirst|ModifyAll"
+    specialist: dean-debug
+    label: "Performance review with Dean"
+
+  - pattern: "SetLoadFields|SetAutoCalcFields"
+    specialist: dean-debug
+    label: "SIFT/performance with Dean"
+
+  - pattern: "CalcFields|CalcSums"
+    specialist: dean-debug
+    label: "CalcFields optimization with Dean"
+
+  - pattern: "LogMessage|Session\\.LogMessage"
+    specialist: dean-debug
+    label: "Telemetry with Dean"
+
+  # Documentation -> Taylor
+  - pattern: "/// <summary>"
+    specialist: taylor-docs
+    label: "Documentation with Taylor"
+
+  - pattern: "/// <param"
+    specialist: taylor-docs
+    label: "Parameter docs with Taylor"
+
+  # Architecture -> Alex
+  - pattern: "codeunit \\d+|table \\d+"
+    specialist: alex-architect
+    label: "Architecture with Alex"
+
+  - pattern: "\\[Obsolete"
+    specialist: alex-architect
+    label: "Deprecation strategy with Alex"
+
+  - pattern: "interface "
+    specialist: alex-architect
+    label: "Interface design with Alex"
+
+  # Code quality -> Roger
+  - pattern: "procedure .+\\("
+    specialist: roger-reviewer
+    label: "Code review with Roger"

package/embedded-knowledge/domains/alex-architect/api-delegate-operation-pattern.md

@@ -7,6 +7,16 @@ tags: ["api-delegates", "operation-delegation", "api-patterns", "extensibility"]
 prerequisites: ["api-basics", "interface-implementation", "event-handling"]
 samples: "samples/api-delegate-operation.md"
 related_topics: ["api-interface-design-patterns", "event-bridge-pattern-al"]
+
+relevance_signals:
+  constructs: []
+  keywords: ["delegate", "delegation", "operation handler", "handler registration", "delegate registry", "chain of responsibility", "context", "fallback", "extensibility", "API contract"]
+  anti_pattern_indicators: ["over-delegation", "tight coupling between delegates", "too many delegation points"]
+  positive_pattern_indicators: ["delegate contract", "handler interface", "delegate registration", "operation delegation", "delegate caching"]
+
+applicable_object_types: ["codeunit", "interface"]
+
+relevance_threshold: 0.4
 ---
 
 # API Delegate Operation Pattern

package/embedded-knowledge/domains/alex-architect/api-fieldset-registration-pattern.md

@@ -7,6 +7,16 @@ tags: ["api-fieldsets", "field-registration", "api-extensibility", "metadata-dri
 prerequisites: ["api-basics", "fieldset-concepts", "registration-patterns"]
 samples: "samples/api-fieldset-registration.md"
 related_topics: ["api-interface-design-patterns", "api-delegate-operation-pattern"]
+
+relevance_signals:
+  constructs: []
+  keywords: ["fieldset", "field registration", "field metadata", "dynamic fields", "field selection", "API extensibility", "permission-aware", "field discovery", "field transformation"]
+  anti_pattern_indicators: ["over-registration", "inconsistent field metadata", "too many fields"]
+  positive_pattern_indicators: ["field registry", "module-based registration", "field metadata management", "conditional field registration", "hierarchical fields"]
+
+applicable_object_types: ["codeunit", "page", "table"]
+
+relevance_threshold: 0.4
 ---
 
 # API Fieldset Registration Pattern

package/embedded-knowledge/domains/alex-architect/api-interface-design-patterns.md

@@ -7,6 +7,16 @@ tags: ["api-interfaces", "contract-design", "api-patterns", "interface-segregati
 prerequisites: ["interface-basics", "api-fundamentals", "contract-design"]
 samples: "samples/api-interface-design.md"
 related_topics: ["api-delegate-operation-pattern", "api-fieldset-registration-pattern"]
+
+relevance_signals:
+  constructs: ["interface"]
+  keywords: ["interface design", "API contract", "interface segregation", "command-query separation", "fluent interface", "builder pattern", "versioning", "deprecation", "backward compatibility"]
+  anti_pattern_indicators: ["interface bloat", "breaking changes", "monolithic interface", "large interface"]
+  positive_pattern_indicators: ["focused interface", "contract stability", "interface composition", "consumer-centric design", "additive evolution"]
+
+applicable_object_types: ["codeunit", "interface", "page"]
+
+relevance_threshold: 0.4
 ---
 
 # API Interface Design Patterns

package/embedded-knowledge/domains/alex-architect/api-page-development-patterns.md

@@ -14,6 +14,16 @@ improvement_suggestion: "Use API pages for structured external system integratio
 implementation_steps: ["design-api-structure", "implement-field-exposure", "optimize-performance"]
 validation_criteria: ["odata-compliance", "security-integration", "performance-optimization"]
 technical_areas: ["al-code", "integration"]
+
+relevance_signals:
+  constructs: ["PageType = API", "EntityName", "EntitySetName", "ODataKeyFields"]
+  keywords: ["API page", "OData", "external integration", "business entity", "field exposure", "API contract", "JSON serialization", "REST endpoint"]
+  anti_pattern_indicators: ["direct table exposure", "internal field leakage", "incomplete entity", "breaking contract changes", "over-normalization"]
+  positive_pattern_indicators: ["business entity focus", "contract stability", "field exposure strategy", "API versioning", "selective field loading"]
+
+applicable_object_types: ["page"]
+
+relevance_threshold: 0.5
 ---
 
 # AL API Page Development Patterns

package/embedded-knowledge/domains/alex-architect/complex-facade-patterns.md

@@ -7,6 +7,16 @@ tags: ["complex-facade", "enterprise-patterns", "multi-layer-facade", "facade-co
 prerequisites: ["facade-pattern-al-implementation", "enterprise-architecture", "advanced-al"]
 samples: "samples/complex-facade-patterns.md"
 related_topics: ["facade-pattern-al-implementation", "enterprise-integration-patterns"]
+
+relevance_signals:
+  constructs: []
+  keywords: ["facade", "multi-layer facade", "facade composition", "enterprise architecture", "cross-system coordination", "transaction spanning", "workflow orchestration", "circuit breaker", "API gateway", "microservice coordination"]
+  anti_pattern_indicators: ["over-engineering", "tight coupling between facades", "performance overhead", "monitoring gaps"]
+  positive_pattern_indicators: ["facade hierarchy", "composite facade", "domain-specific facade", "event-driven facade", "caching-enabled facade", "policy-driven facade"]
+
+applicable_object_types: ["codeunit", "interface"]
+
+relevance_threshold: 0.4
 ---
 
 # Complex Facade Patterns

package/embedded-knowledge/domains/alex-architect/delegating-to-github-copilot-agents.md

@@ -13,6 +13,16 @@ applies_to:
   - "Issue Management"
   - "AI-Assisted Development"
 last_updated: "2025-10-26"
+
+relevance_signals:
+  constructs: []
+  keywords: ["GitHub Copilot", "Copilot Agent", "issue creation", "task delegation", "AI workflow", "object ID", "naming conventions", "acceptance criteria", "context management"]
+  anti_pattern_indicators: ["vague requirements", "missing object IDs", "no naming standards", "ignoring layer context"]
+  positive_pattern_indicators: ["object identity specification", "naming conventions documentation", "BC architecture context", "data model definition", "API requirements", "test requirements", "acceptance criteria"]
+
+applicable_object_types: ["table", "page", "codeunit", "report", "query", "tableextension", "pageextension", "enum", "permissionset"]
+
+relevance_threshold: 0.3
 ---
 
 # Delegating Coding Tasks to GitHub Copilot Agents

package/embedded-knowledge/domains/alex-architect/facade-pattern-al-implementation.md

@@ -7,6 +7,16 @@ tags: ["facade-pattern", "structural-patterns", "api-simplification", "complexit
 prerequisites: ["object-orientation-al", "interface-basics", "module-design"]
 samples: "samples/facade-pattern-al.md"
 related_topics: ["complex-facade-patterns", "adapter-pattern-al"]
+
+relevance_signals:
+  constructs: []
+  keywords: ["facade", "facade pattern", "unified interface", "complexity encapsulation", "API simplification", "business process facade", "data access facade", "integration facade", "service layer"]
+  anti_pattern_indicators: ["over-simplification", "facade bloat", "too many responsibilities"]
+  positive_pattern_indicators: ["unified interface", "complexity hiding", "codeunit facade", "business facade method", "clean API", "simplified interface"]
+
+applicable_object_types: ["codeunit", "interface"]
+
+relevance_threshold: 0.4
 ---
 
 # Facade Pattern AL Implementation

package/embedded-knowledge/domains/alex-architect/facade-pattern-external-api.md

@@ -14,6 +14,16 @@ improvement_suggestion: "Use facade pattern to simplify external API integration
 implementation_steps: ["create-facade-codeunit", "abstract-api-calls", "centralize-error-handling"]
 validation_criteria: ["single-entry-point", "hidden-complexity", "clean-interfaces"]
 technical_areas: ["al-code", "integration"]
+
+relevance_signals:
+  constructs: ["HttpClient", "HttpRequestMessage", "HttpResponseMessage", "JsonObject", "JsonToken"]
+  keywords: ["external API", "API integration", "facade pattern", "HTTP client", "authentication", "OAuth", "JWT", "retry logic", "circuit breaker", "rate limiting", "API gateway"]
+  anti_pattern_indicators: ["direct API calls scattered", "shared HTTP client without abstraction", "exposed technical details", "mixed responsibilities"]
+  positive_pattern_indicators: ["single gateway", "business-focused methods", "centralized error handling", "retry logic", "graceful degradation", "configuration driven"]
+
+applicable_object_types: ["codeunit"]
+
+relevance_threshold: 0.5
 ---
 
 # AL Facade Pattern for External API Integration

package/embedded-knowledge/domains/alex-architect/object-id-ninja-integration.md

@@ -13,6 +13,16 @@ applies_to:
   - "AppSource Development"
 last_updated: "2025-10-27"
 conditional_mcp: "al-objid-mcp-server"
+
+relevance_signals:
+  constructs: []
+  keywords: ["object ID", "ID collision", "ID management", "Object ID Ninja", "MCP", "ID reservation", "ID range", "app.json", "idRanges", "publisher range", "AppSource"]
+  anti_pattern_indicators: ["ID conflicts", "duplicate object ID", "manual ID tracking", "ID collision"]
+  positive_pattern_indicators: ["ID range configuration", "ID reservation", "collision prevention", "team coordination", "Object ID Ninja"]
+
+applicable_object_types: ["table", "page", "codeunit", "report", "query", "xmlport", "enum", "permissionset", "tableextension", "pageextension"]
+
+relevance_threshold: 0.5
 ---
 
 # AL Object ID Ninja MCP Integration

package/embedded-knowledge/domains/alex-architect/recommend-object-id-ninja.md

@@ -7,6 +7,16 @@ tags: ["object-ids", "architecture", "tooling", "recommendations", "collaboratio
 conditional_mcp_missing: "al-objid-mcp-server"
 estimated_time: "5 minutes"
 last_updated: "2025-10-27"
+
+relevance_signals:
+  constructs: []
+  keywords: ["object ID", "ID collision", "ID management", "manual ID tracking", "ID range", "AppSource", "publisher range", "team coordination", "merge conflict"]
+  anti_pattern_indicators: ["ID conflicts", "duplicate object ID", "race condition", "merge conflicts from IDs", "manual tracking"]
+  positive_pattern_indicators: ["ID range allocation", "pre-commit checklist", "ID registry", "range documentation"]
+
+applicable_object_types: ["table", "page", "codeunit", "report", "query", "xmlport", "enum", "permissionset", "tableextension", "pageextension"]
+
+relevance_threshold: 0.5
 ---
 
 # Manual Object ID Management and Collision Prevention

package/embedded-knowledge/domains/alex-architect/subscriber-codeunit-size-optimization.md

@@ -1,4 +1,4 @@
----
+---
 title: "Subscriber Codeunit Size and Organization"
 domain: "alex-architect"
 difficulty: "intermediate"
@@ -6,7 +6,17 @@ bc_versions: "14+"
 tags: ["codeunit-design", "organization", "maintainability", "performance"]
 prerequisites: ["codeunit-basics", "event-subscriber-patterns"]
 samples: "samples/subscriber-organization.md"
----
+
+relevance_signals:
+  constructs: ["EventSubscriber", "SingleInstance"]
+  keywords: ["subscriber codeunit", "codeunit size", "event subscriber", "functional cohesion", "domain organization", "subscriber architecture", "compilation overhead", "merge conflict"]
+  anti_pattern_indicators: ["monolithic subscriber codeunit", "oversized codeunit", "too many subscribers in one codeunit", "excessive fragmentation"]
+  positive_pattern_indicators: ["domain-based organization", "layer-based organization", "functional cohesion", "subscriber grouping", "size threshold", "refactoring trigger"]
+
+applicable_object_types: ["codeunit"]
+
+relevance_threshold: 0.5
+---
 # Subscriber Codeunit Size and Organization
 
 ## Overview

package/embedded-knowledge/domains/alex-architect/systemid-integration.md

@@ -1,11 +1,21 @@
----
+---
 title: "SystemId Integration in API Pages"
 domain: "alex-architect"
 difficulty: "intermediate"
 bc_versions: "14+"
 tags: ["systemid", "data-modeling", "entity-relationships"]
 samples: "samples/systemid-integration.md"
----
+
+relevance_signals:
+  constructs: ["SystemId", "GUID", "ODataKeyFields"]
+  keywords: ["SystemId", "GUID", "unique identifier", "API page", "OData", "external integration", "data synchronization", "entity relationship", "foreign key", "concurrency control", "ETag"]
+  anti_pattern_indicators: []
+  positive_pattern_indicators: ["SystemId as key", "stable identifier", "external reference", "SystemId integration", "GUID-based relationship"]
+
+applicable_object_types: ["table", "page", "tableextension", "pageextension"]
+
+relevance_threshold: 0.4
+---
 # SystemId Integration in API Pages
 
 ## Overview

package/embedded-knowledge/domains/alex-architect/testability-design-patterns.md

@@ -10,6 +10,16 @@ related_topics:
   - "../roger-reviewer/testability-code-smells.md"
   - "api-interface-design-patterns.md"
 source: "Adapted from Vjeko.com: Testing in isolation (Dec 2023)"
+
+relevance_signals:
+  constructs: ["interface", "implements"]
+  keywords: ["testability", "dependency injection", "interface abstraction", "decoupling", "isolation testing", "test double", "mock", "tight coupling", "dependency", "substitution"]
+  anti_pattern_indicators: ["tight coupling", "direct dependency", "setup switch", "configuration-driven branching", "cannot test in isolation"]
+  positive_pattern_indicators: ["interface abstraction", "dependency injection", "backward compatible overload", "test double", "decoupled design", "injectable dependency"]
+
+applicable_object_types: ["codeunit", "interface"]
+
+relevance_threshold: 0.5
 ---
 # Designing Code for Testability in Isolation
 

package/embedded-knowledge/domains/casey-copilot/long-running-session-instructions.md

@@ -9,6 +9,16 @@ related_topics:
   - "project-context-files.md"
   - "incremental-development-patterns.md"
 source: "Adapted from Anthropic Engineering: Effective harnesses for long-running agents (Nov 2025)"
+
+relevance_signals:
+  constructs: ["Codeunit.Run", "Try", "Commit"]
+  keywords: ["AI agent", "long-running session", "context window", "incremental progress", "handoff", "PROGRESS.md", "feature list", "clean state", "verification", "testing requirements"]
+  anti_pattern_indicators: ["one-shot overreach", "premature victory", "vague goals", "no state management", "unlimited scope"]
+  positive_pattern_indicators: ["environment orientation", "feature lists", "incremental progress", "clean state requirements", "progress tracking", "bounded scope"]
+
+applicable_object_types: ["codeunit", "table", "page", "report", "query", "xmlport"]
+
+relevance_threshold: 0.3
 ---
 # Effective Instructions for Long-Running AI Sessions
 

package/embedded-knowledge/domains/chris-config/configuration-file-discovery.md

@@ -11,6 +11,16 @@ related_topics:
 applies_to:
   - "BC Code Intelligence MCP Server"
 last_updated: "2025-10-30"
+
+relevance_signals:
+  constructs: []
+  keywords: ["config", "configuration", "bc-code-intel-config", "workspace", "layers", "priority", "merge", "user config", "project config", "environment variable"]
+  anti_pattern_indicators: []
+  positive_pattern_indicators: ["configuration file", "config.json", "config.yaml", "set_workspace_info", "layer priority"]
+
+applicable_object_types: []
+
+relevance_threshold: 0.4
 ---
 
 # Configuration File Discovery

package/embedded-knowledge/domains/chris-config/configuration-file-formats.md

@@ -11,6 +11,16 @@ related_topics:
 applies_to:
   - "BC Code Intelligence MCP Server"
 last_updated: "2025-10-29"
+
+relevance_signals:
+  constructs: []
+  keywords: ["json", "yaml", "config", "configuration", "knowledge_layers", "git", "authentication", "az_cli", "pat", "token"]
+  anti_pattern_indicators: []
+  positive_pattern_indicators: ["config file", "configuration format", "bc-code-intel-config", "layer configuration", "authentication setup"]
+
+applicable_object_types: []
+
+relevance_threshold: 0.4
 ---
 
 # Configuration File Formats and Creation

package/embedded-knowledge/domains/chris-config/content-types-structure.md

@@ -12,6 +12,16 @@ applies_to:
   - "BC Code Intelligence MCP Server"
   - "Knowledge Layer Architecture"
 last_updated: "2025-10-27"
+
+relevance_signals:
+  constructs: []
+  keywords: ["topics", "specialists", "methodologies", "frontmatter", "yaml", "domains", "content types", "knowledge layer", "markdown"]
+  anti_pattern_indicators: []
+  positive_pattern_indicators: ["content structure", "yaml frontmatter", "specialist definition", "topic format", "knowledge content"]
+
+applicable_object_types: []
+
+relevance_threshold: 0.4
 ---
 
 # Content Types Structure

package/embedded-knowledge/domains/chris-config/knowledge-content-creation.md

@@ -7,6 +7,16 @@ tags: ["knowledge-creation", "content-authoring", "yaml-frontmatter", "markdown"
 related_topics: ["multi-team-layer-configuration", "content-quality-standards"]
 applies_to: ["Knowledge Base", "Team Documentation", "Project Customization"]
 last_updated: "2025-01-01"
+
+relevance_signals:
+  constructs: []
+  keywords: ["knowledge", "content", "frontmatter", "yaml", "override", "domain", "tags", "bc_versions", "difficulty", "markdown"]
+  anti_pattern_indicators: []
+  positive_pattern_indicators: ["create knowledge", "write content", "custom topic", "override embedded", "knowledge authoring"]
+
+applicable_object_types: []
+
+relevance_threshold: 0.4
 ---
 
 # Creating Custom BC Knowledge Content

package/embedded-knowledge/domains/chris-config/layer-system-fundamentals.md

@@ -12,6 +12,16 @@ applies_to:
   - "BC Code Intelligence MCP Server"
   - "Knowledge Layer Architecture"
 last_updated: "2025-10-27"
+
+relevance_signals:
+  constructs: []
+  keywords: ["layer", "priority", "embedded", "git layer", "project layer", "override", "knowledge architecture", "four-layer", "layer resolution"]
+  anti_pattern_indicators: []
+  positive_pattern_indicators: ["layer system", "knowledge layer", "layer priority", "layer override", "embedded knowledge"]
+
+applicable_object_types: []
+
+relevance_threshold: 0.4
 ---
 
 # Layer System Fundamentals

package/embedded-knowledge/domains/chris-config/multi-team-layer-configuration.md

@@ -7,6 +7,16 @@ tags: ["configuration", "enterprise", "layers", "git-repositories", "team-collab
 related_topics: ["knowledge-overrides", "layer-system-architecture"]
 applies_to: ["MCP Server", "VS Code Integration", "Team Environments"]
 last_updated: "2025-01-01"
+
+relevance_signals:
+  constructs: []
+  keywords: ["multi-team", "organization", "enterprise", "git repository", "layer priority", "team collaboration", "company standards", "authentication"]
+  anti_pattern_indicators: []
+  positive_pattern_indicators: ["team layer", "company layer", "organization setup", "shared knowledge", "multi-team configuration"]
+
+applicable_object_types: []
+
+relevance_threshold: 0.4
 ---
 
 # Multi-Team Layer Configuration for Organizations

package/embedded-knowledge/domains/chris-config/workspace-detection-solutions.md

@@ -12,6 +12,16 @@ applies_to:
   - "BC Code Intelligence MCP Server"
   - "VS Code MCP Extension"
 last_updated: "2025-10-27"
+
+relevance_signals:
+  constructs: []
+  keywords: ["workspace", "set_workspace_root", "get_workspace_root", "process.cwd", "VS Code", "project layer", "lazy initialization"]
+  anti_pattern_indicators: ["project config not found", "project layer not loading", "workspace not detected"]
+  positive_pattern_indicators: ["set workspace", "workspace detection", "workspace root", "project configuration"]
+
+applicable_object_types: []
+
+relevance_threshold: 0.5
 ---
 
 # Workspace Detection Solutions

package/embedded-knowledge/domains/dean-debug/bc-telemetry-buddy-integration.md

@@ -13,6 +13,16 @@ applies_to:
   - "Production Monitoring"
 last_updated: "2025-10-27"
 conditional_mcp: "bc-telemetry-buddy"
+
+relevance_signals:
+  constructs: ["Session.LogMessage", "bctb_query_telemetry", "bctb_get_event_catalog", "bctb_get_recommendations"]
+  keywords: ["telemetry", "Application Insights", "KQL", "performance monitoring", "MCP", "telemetry buddy", "production issues", "query execution"]
+  anti_pattern_indicators: []
+  positive_pattern_indicators: ["data-driven analysis", "telemetry data", "performance metrics", "KQL query"]
+
+applicable_object_types: ["codeunit"]
+
+relevance_threshold: 0.4
 ---
 
 # BC Telemetry Buddy MCP Integration

package/embedded-knowledge/domains/dean-debug/bc24-no-series-conversion-guide.md

@@ -7,6 +7,16 @@ tags: ["bc24-migration", "no-series-conversion", "legacy-modernization", "breaki
 prerequisites: ["no-series-implementation-patterns", "no-series-module-patterns-bc24", "business-foundation-architecture"]
 samples: "samples/bc24-no-series-conversion.md"
 related_topics: ["no-series-module-patterns-bc24", "no-series-validation-module-bc24", "no-series-implementation-patterns"]
+
+relevance_signals:
+  constructs: ["NoSeriesManagement", "NoSeriesMgt", "InitSeries", "GetNextNo", "PeekNextNo", "TestManual", "SelectSeries", "LookupRelatedNoSeries", "NoSeries", "NoSeriesBatch"]
+  keywords: ["BC24", "No. Series", "number generation", "migration", "conversion", "obsolete", "Business Foundation", "Codeunit 396", "Codeunit 310"]
+  anti_pattern_indicators: ["NoSeriesMgt.InitSeries", "NoSeriesMgt.GetNextNo", "Codeunit NoSeriesManagement"]
+  positive_pattern_indicators: ["NoSeries.GetNextNo", "NoSeries.PeekNextNo", "NoSeries.TestManual"]
+
+applicable_object_types: ["codeunit", "table", "page"]
+
+relevance_threshold: 0.6
 ---
 
 # BC24 No. Series Conversion Guide

package/embedded-knowledge/domains/dean-debug/case-statement-performance-best-practices.md

@@ -1,4 +1,4 @@
----
+---
 title: "Case Statement Performance and Best Practices"
 domain: "dean-debug"
 difficulty: "intermediate"
@@ -6,7 +6,17 @@ bc_versions: "14+"
 tags: ["case", "performance", "optimization", "control-flow"]
 prerequisites: ["case-statement-syntax", "performance-fundamentals"]
 samples: "samples/case-performance-optimization.md"
----
+
+relevance_signals:
+  constructs: ["case", "of", "else"]
+  keywords: ["case statement", "control flow", "branch", "jump table", "branch prediction", "performance optimization"]
+  anti_pattern_indicators: ["nested case", "complex case expression", "resource-heavy branch"]
+  positive_pattern_indicators: ["branch frequency ordering", "early exit", "simple expression"]
+
+applicable_object_types: ["codeunit", "page", "report", "table"]
+
+relevance_threshold: 0.4
+---
 # Case Statement Performance and Best Practices
 
 ## Overview

package/embedded-knowledge/domains/dean-debug/compound-statements-debugging.md

@@ -1,4 +1,4 @@
----
+---
 title: "AL Compound Statements for Enhanced Debugging"
 domain: "dean-debug"
 difficulty: "intermediate"
@@ -6,7 +6,17 @@ bc_versions: "14+"
 tags: ["debugging", "compound-statements", "breakpoints", "code-analysis"]
 prerequisites: ["compound-statement-readability", "al-debugging-basics"]
 samples: "samples/compound-statements-debugging.md"
----
+
+relevance_signals:
+  constructs: ["begin", "end"]
+  keywords: ["debugging", "breakpoint", "compound statement", "execution flow", "variable scope", "step-through", "tracing"]
+  anti_pattern_indicators: []
+  positive_pattern_indicators: ["structured code", "explicit boundaries", "logical blocks"]
+
+applicable_object_types: ["codeunit", "page", "report", "table"]
+
+relevance_threshold: 0.3
+---
 # AL Compound Statements for Enhanced Debugging
 
 ## Overview

package/embedded-knowledge/domains/dean-debug/custom-dimensions-best-practices.md

@@ -1,4 +1,4 @@
----
+---
 title: "Custom Dimensions Best Practices"
 domain: "dean-debug"
 difficulty: "intermediate"
@@ -6,7 +6,17 @@ bc_versions: "14+"
 tags: ["telemetry", "dimensions", "analytics", "monitoring"]
 prerequisites: ["bc-session-logmessage-methods"]
 samples: "samples/custom-dimensions.md"
----
+
+relevance_signals:
+  constructs: ["Session.LogMessage", "Dictionary"]
+  keywords: ["custom dimensions", "telemetry", "Application Insights", "cardinality", "dimension naming", "analytics", "monitoring"]
+  anti_pattern_indicators: ["high-cardinality dimension", "dynamic dimension name", "sensitive data in telemetry"]
+  positive_pattern_indicators: ["consistent naming", "business context", "correlation identifier"]
+
+applicable_object_types: ["codeunit"]
+
+relevance_threshold: 0.4
+---
 # Custom Dimensions Best Practices
 
 ## Overview

package/embedded-knowledge/domains/dean-debug/custom-telemetry-implementation.md

@@ -14,6 +14,16 @@ improvement_suggestion: "Implement custom telemetry for actionable monitoring an
 implementation_steps: ["design-telemetry-schema", "implement-session-logmessage", "validate-privacy-compliance"]
 validation_criteria: ["privacy-compliant", "actionable-data", "performance-neutral"]
 technical_areas: ["al-code", "monitoring"]
+
+relevance_signals:
+  constructs: ["Session.LogMessage", "DataClassification", "TelemetryScope", "Dictionary"]
+  keywords: ["telemetry", "custom telemetry", "Application Insights", "diagnostics", "monitoring", "privacy", "observability"]
+  anti_pattern_indicators: ["logging PII", "telemetry flooding", "functional telemetry dependency"]
+  positive_pattern_indicators: ["Session.LogMessage", "DataClassification::SystemMetadata", "TelemetryScope::ExtensionPublisher"]
+
+applicable_object_types: ["codeunit"]
+
+relevance_threshold: 0.5
 ---
 
 # Custom Telemetry Implementation in AL