bc-code-intelligence-mcp 1.5.9 → 1.6.0

package/embedded-knowledge/domains/eva-errors/fielderror-method-syntax.md

@@ -1,11 +1,21 @@
----
+---
 title: "FieldError Method Syntax and Behavior"
 domain: "eva-errors"
 difficulty: "intermediate"
 bc_versions: "14+"
 tags: ["fielderror", "validation", "error-messages", "posting"]
 samples: "samples/fielderror-syntax.md"
----
+
+relevance_signals:
+  constructs: ["FieldError", "FieldNo", "TestField"]
+  keywords: ["FieldError", "validation error", "field-specific error", "posting codeunit", "error message generation"]
+  anti_pattern_indicators: ["redundant condition checking", "generic error for field-specific issue"]
+  positive_pattern_indicators: ["FieldError with custom message", "lowercase message", "field number constant"]
+
+applicable_object_types: ["codeunit", "table", "page"]
+
+relevance_threshold: 0.5
+---
 # FieldError Method Syntax and Behavior
 
 ## Overview

package/embedded-knowledge/domains/eva-errors/testfield-error-handling.md

@@ -1,4 +1,4 @@
----
+---
 title: "TestField Error Handling and Custom Messages"
 domain: "eva-errors"
 difficulty: "intermediate"
@@ -6,7 +6,17 @@ bc_versions: "14+"
 tags: ["error-handling", "validation", "user-experience", "custom-messages"]
 prerequisites: ["testfield-basic-syntax", "error-handling-fundamentals"]
 samples: "samples/testfield-error-handling.md"
----
+
+relevance_signals:
+  constructs: ["TestField", "TryFunction", "Error", "GetLastErrorText"]
+  keywords: ["TestField", "error handling", "custom message", "validation", "try function", "batch processing", "error aggregation"]
+  anti_pattern_indicators: ["suppressing legitimate errors", "ignoring validation failures"]
+  positive_pattern_indicators: ["TryFunction wrapper", "custom validation", "aggregated errors", "progressive validation"]
+
+applicable_object_types: ["codeunit", "table", "page"]
+
+relevance_threshold: 0.5
+---
 # TestField Error Handling and Custom Messages
 
 ## Overview

package/embedded-knowledge/domains/eva-errors/try-function-usage.md

@@ -8,6 +8,16 @@ samples: "samples/try-function-usage.md"
 related_topics:
   - "codeunit-run-pattern.md"
   - "testfield-error-handling.md"
+
+relevance_signals:
+  constructs: ["TryFunction", "GetLastErrorText", "ClearLastError", "HttpClient", "HttpResponseMessage"]
+  keywords: ["try function", "error handling", "external system", "HTTP call", "validation without termination", "read-only operation"]
+  anti_pattern_indicators: ["database write inside try", "INSERT inside try", "MODIFY inside try", "DELETE inside try", "suppressing errors"]
+  positive_pattern_indicators: ["external service wrapper", "error detection", "graceful failure", "web service call"]
+
+applicable_object_types: ["codeunit"]
+
+relevance_threshold: 0.6
 ---
 # Try Function Usage Guidelines
 

package/embedded-knowledge/domains/jordan-bridge/al-event-subscriber-architecture.md

@@ -14,6 +14,16 @@ implementation_steps: ["design-subscriber-structure", "implement-loose-coupling"
 validation_criteria: ["maintained-loose-coupling", "acceptable-performance-impact"]
 technical_areas: ["al-code", "integration"]
 samples: "samples/al-event-subscriber-architecture.md"
+
+relevance_signals:
+  constructs: ["EventSubscriber", "IntegrationEvent", "BusinessEvent", "Subscriber", "OnBefore", "OnAfter"]
+  keywords: ["event subscriber", "loose coupling", "event-driven", "integration", "extensibility", "publisher", "event handler"]
+  anti_pattern_indicators: ["tight coupling", "direct data access", "circular dependency", "subscriber failure"]
+  positive_pattern_indicators: ["single responsibility", "error isolation", "background session", "event contract"]
+
+applicable_object_types: ["codeunit"]
+
+relevance_threshold: 0.5
 ---
 
 # AL Event Subscriber Architecture

package/embedded-knowledge/domains/jordan-bridge/automatic-registration.md

@@ -1,11 +1,21 @@
----
+---
 title: "API Page Automatic Web Service Registration"
 domain: "jordan-bridge"
 difficulty: "intermediate"
 bc_versions: "14+"
 tags: ["web-services", "automatic-registration", "deployment"]
 samples: "samples/automatic-registration.md"
----
+
+relevance_signals:
+  constructs: ["APIPage", "APIPublisher", "APIGroup", "APIVersion", "EntityName", "EntitySetName", "ODataKeyFields"]
+  keywords: ["web service", "automatic registration", "OData", "API endpoint", "service metadata", "deployment"]
+  anti_pattern_indicators: []
+  positive_pattern_indicators: ["API page", "web service registration", "OData endpoint", "service discovery"]
+
+applicable_object_types: ["page"]
+
+relevance_threshold: 0.4
+---
 # API Page Automatic Web Service Registration
 
 ## Overview

package/embedded-knowledge/domains/jordan-bridge/business-process-template-patterns.md

@@ -7,6 +7,16 @@ tags: ["business-process", "workflow-templates", "process-automation", "business
 prerequisites: ["template-method-pattern-al", "business-process-design", "workflow-patterns"]
 samples: "samples/business-process-templates.md"
 related_topics: ["template-method-pattern-al", "workflow-automation-patterns"]
+
+relevance_signals:
+  constructs: ["Interface", "Codeunit", "Enum", "Record"]
+  keywords: ["business process", "workflow template", "state management", "approval workflow", "document processing", "process automation"]
+  anti_pattern_indicators: ["over-generalization", "configuration complexity", "state corruption"]
+  positive_pattern_indicators: ["process flow", "state machine", "business rule", "template pattern", "workflow step"]
+
+applicable_object_types: ["codeunit", "table", "enum"]
+
+relevance_threshold: 0.5
 ---
 
 # Business Process Template Patterns

package/embedded-knowledge/domains/jordan-bridge/error-response-patterns.md

@@ -1,11 +1,21 @@
----
+---
 title: "Business Central API Error Response Patterns"
 domain: "jordan-bridge"
 difficulty: "intermediate"
 bc_versions: "14+"
 tags: ["error-handling", "http-status", "api-responses"]
 samples: "samples/api-error-responses.md"
----
+
+relevance_signals:
+  constructs: ["HttpClient", "HttpResponseMessage", "HttpStatusCode", "JsonObject", "JsonToken", "Error"]
+  keywords: ["error response", "HTTP status", "OData error", "400 Bad Request", "401 Unauthorized", "403 Forbidden", "404 Not Found", "409 Conflict", "500 Internal Server Error", "retry logic"]
+  anti_pattern_indicators: []
+  positive_pattern_indicators: ["error handling", "status code", "retry-after", "error recovery", "graceful degradation"]
+
+applicable_object_types: ["codeunit", "page"]
+
+relevance_threshold: 0.5
+---
 # Business Central API Error Response Patterns
 
 ## Overview

package/embedded-knowledge/domains/jordan-bridge/etag-implementation.md

@@ -1,11 +1,21 @@
----
+---
 title: "ETag Implementation for Optimistic Concurrency"
 domain: "jordan-bridge"
 difficulty: "advanced"
 bc_versions: "14+"
 tags: ["etag", "concurrency", "conflict-resolution"]
 samples: "samples/etag-implementation.md"
----
+
+relevance_signals:
+  constructs: ["SystemRowVersion", "SystemId", "If-Match", "If-None-Match", "HttpHeaders"]
+  keywords: ["ETag", "optimistic concurrency", "If-Match", "If-None-Match", "conflict detection", "concurrent modification", "version control"]
+  anti_pattern_indicators: ["lost update", "data corruption", "concurrent access without etag"]
+  positive_pattern_indicators: ["ETag validation", "concurrency control", "conflict resolution", "conditional operation"]
+
+applicable_object_types: ["page", "codeunit"]
+
+relevance_threshold: 0.5
+---
 # ETag Implementation for Optimistic Concurrency
 
 ## Overview

package/embedded-knowledge/domains/jordan-bridge/field-control-selection.md

@@ -1,11 +1,21 @@
----
+---
 title: "API Page Field Control Selection Strategy"
 domain: "jordan-bridge"
 difficulty: "intermediate"
 bc_versions: "14+"
 tags: ["field-control", "api-design", "data-exposure"]
 samples: "samples/api-field-control.md"
----
+
+relevance_signals:
+  constructs: ["field", "SystemId", "SystemCreatedAt", "SystemModifiedAt", "Editable", "FieldClass"]
+  keywords: ["field selection", "API field", "data exposure", "field control", "read-only", "editable field", "calculated field", "sensitive data"]
+  anti_pattern_indicators: ["exposing sensitive data", "PII exposure", "unnecessary field exposure"]
+  positive_pattern_indicators: ["field visibility", "security consideration", "performance optimization", "selective field loading"]
+
+applicable_object_types: ["page"]
+
+relevance_threshold: 0.4
+---
 # API Page Field Control Selection Strategy
 
 ## Overview

package/embedded-knowledge/domains/jordan-bridge/task-scheduler-pattern-implementation.md

@@ -7,6 +7,16 @@ tags: ["task-scheduler", "job-processing", "async-patterns", "workflow-managemen
 prerequisites: ["task-scheduler-basics", "queue-processing", "error-handling"]
 samples: "samples/task-scheduler-pattern.md"
 related_topics: ["command-queue-pattern-al", "event-bridge-pattern-al"]
+
+relevance_signals:
+  constructs: ["TaskScheduler", "CreateTask", "JobQueue", "Codeunit.Run", "StartSession", "Sleep"]
+  keywords: ["task scheduler", "job queue", "background processing", "async task", "scheduled job", "retry policy", "batch processing"]
+  anti_pattern_indicators: ["resource exhaustion", "infinite retry", "state corruption", "silent failure"]
+  positive_pattern_indicators: ["idempotent task", "exponential backoff", "dead letter queue", "task monitoring"]
+
+applicable_object_types: ["codeunit", "table"]
+
+relevance_threshold: 0.5
 ---
 
 # Task Scheduler Pattern Implementation

package/embedded-knowledge/domains/jordan-bridge/url-structure-naming-patterns.md

@@ -1,11 +1,21 @@
----
+---
 title: "API Page URL Structure and Entity Naming Patterns"
 domain: "jordan-bridge"
 difficulty: "beginner"
 bc_versions: "14+"
 tags: ["api-endpoints", "url-structure", "naming-conventions"]
 samples: "samples/api-url-naming.md"
----
+
+relevance_signals:
+  constructs: ["APIPublisher", "APIGroup", "APIVersion", "EntityName", "EntitySetName"]
+  keywords: ["URL structure", "entity naming", "API endpoint", "OData URL", "RESTful", "plural noun", "naming convention"]
+  anti_pattern_indicators: ["inconsistent pluralization", "generic names", "technical names instead of business names"]
+  positive_pattern_indicators: ["domain-driven naming", "consistent convention", "plural entity name", "hyphen separation"]
+
+applicable_object_types: ["page"]
+
+relevance_threshold: 0.3
+---
 # API Page URL Structure and Entity Naming Patterns
 
 ## Overview

package/embedded-knowledge/domains/maya-mentor/case-multiple-conditions-ranges.md

@@ -1,4 +1,4 @@
----
+---
 title: "Case Statement Multiple Conditions and Ranges"
 domain: "maya-mentor"
 subdomain: "maya-mentor"
@@ -9,7 +9,17 @@ tags: ["case", "ranges", "multiple-values", "advanced-patterns", "conditional-lo
 prerequisites: ["case-statement-syntax", "data-types", "operators"]
 related_topics: ["case-statement-syntax", "case-performance", "numeric-operations"]
 samples: "samples/case-statement-multiple-conditions.md"
----
+
+relevance_signals:
+  constructs: ["case", "of", "else", "end"]
+  keywords: ["case statement", "range", "multiple values", "dotdot", "conditional logic", "branching", "pattern matching"]
+  anti_pattern_indicators: []
+  positive_pattern_indicators: ["case multiple values", "case range", "comma-separated values", "dotdot operator"]
+
+applicable_object_types: ["codeunit", "page", "table", "report", "query"]
+
+relevance_threshold: 0.4
+---
 # Case Statement Multiple Conditions and Ranges
 
 ## Overview

package/embedded-knowledge/domains/maya-mentor/case-statement-syntax-structure.md

@@ -1,4 +1,4 @@
----
+---
 title: "AL Case Statement Syntax and Structure"
 domain: "maya-mentor"
 subdomain: "maya-mentor"
@@ -9,7 +9,17 @@ tags: ["case", "switch", "control-flow", "syntax", "branching"]
 prerequisites: ["if-statements", "variable-types", "basic-syntax"]
 related_topics: ["case-multiple-conditions", "case-performance", "case-error-handling"]
 samples: "samples/case-statement-syntax-structure.md"
----
+
+relevance_signals:
+  constructs: ["case", "of", "else", "end", "begin"]
+  keywords: ["case statement", "switch", "control flow", "branching", "syntax", "enum", "option"]
+  anti_pattern_indicators: []
+  positive_pattern_indicators: ["case statement", "case syntax", "case of", "switch pattern"]
+
+applicable_object_types: ["codeunit", "page", "table", "report", "query"]
+
+relevance_threshold: 0.4
+---
 # AL Case Statement Syntax and Structure
 
 ## Overview

package/embedded-knowledge/domains/maya-mentor/fielderror-syntax-usage.md

@@ -1,4 +1,4 @@
----
+---
 title: "FieldError Syntax and Usage"
 domain: "maya-mentor"
 difficulty: "beginner"
@@ -7,7 +7,17 @@ tags: ["fielderror", "error-handling", "validation", "record-methods", "user-fee
 prerequisites: ["record-basics", "field-access"]
 samples: "samples/fielderror-syntax-usage.md"
 related_topics: ["testfield-method", "error-method", "field-validation", "record-validation"]
----
+
+relevance_signals:
+  constructs: ["FieldError", "Error", "OnValidate"]
+  keywords: ["field error", "validation", "error handling", "user feedback", "field validation", "runtime error"]
+  anti_pattern_indicators: []
+  positive_pattern_indicators: ["FieldError", "field error message", "field validation error", "record.FieldError"]
+
+applicable_object_types: ["table", "codeunit", "page"]
+
+relevance_threshold: 0.4
+---
 # FieldError Syntax and Usage
 
 ## Overview

package/embedded-knowledge/domains/maya-mentor/fielderror-vs-testfield.md

@@ -1,4 +1,4 @@
----
+---
 title: "FieldError vs TestField Decision Guide"
 domain: "maya-mentor"  
 difficulty: "intermediate"
@@ -6,7 +6,17 @@ bc_versions: "14+"
 tags: ["fielderror", "testfield", "validation", "error-handling", "method-comparison", "decision-making", "field-validation"]
 prerequisites: ["fielderror-syntax-usage", "testfield-basic-syntax"]
 related_topics: ["validation-patterns", "error-handling-strategies", "field-validation"]
----
+
+relevance_signals:
+  constructs: ["FieldError", "TestField", "Error", "OnValidate"]
+  keywords: ["fielderror", "testfield", "validation", "comparison", "decision", "method choice", "error handling"]
+  anti_pattern_indicators: []
+  positive_pattern_indicators: ["FieldError vs TestField", "when to use FieldError", "when to use TestField", "validation method choice"]
+
+applicable_object_types: ["table", "codeunit", "page"]
+
+relevance_threshold: 0.4
+---
 # FieldError vs TestField Decision Guide
 
 ## Overview

package/embedded-knowledge/domains/maya-mentor/testfield-basic-syntax.md

@@ -1,4 +1,4 @@
----
+---
 title: "TestField Basic Syntax and Usage"
 domain: "maya-mentor"
 difficulty: "beginner"
@@ -6,7 +6,17 @@ bc_versions: "14+"
 tags: ["validation", "fields", "error-handling", "data-integrity"]
 prerequisites: ["record-variables", "field-access"]
 samples: "samples/testfield-basic-syntax.md"
----
+
+relevance_signals:
+  constructs: ["TestField", "Error", "OnValidate"]
+  keywords: ["testfield", "validation", "mandatory field", "required field", "field check", "data integrity"]
+  anti_pattern_indicators: []
+  positive_pattern_indicators: ["TestField", "field validation", "mandatory check", "required field validation"]
+
+applicable_object_types: ["table", "codeunit", "page"]
+
+relevance_threshold: 0.4
+---
 # TestField Basic Syntax and Usage
 
 ## Overview

package/embedded-knowledge/domains/morgan-market/partner-readiness-analysis.md

@@ -10,6 +10,16 @@ related_topics:
   - "../alex-architect/api-interface-design-patterns.md"
   - "../dean-debug/telemetry-fundamentals.md"
   - "../seth-security/access-modifier-strategy.md"
+
+relevance_signals:
+  constructs: ["IntegrationEvent", "BusinessEvent", "InternalEvent", "Access", "ObsoleteState", "ObsoleteReason", "LogMessage", "Session"]
+  keywords: ["AppSource", "partner readiness", "extensibility", "telemetry", "access modifiers", "events", "ISV", "PTE", "public API", "versioning", "upgrade codeunit", "migration"]
+  anti_pattern_indicators: ["insufficient events", "undocumented events", "everything public", "no deprecation", "missing telemetry", "verbose logging"]
+  positive_pattern_indicators: ["event architecture", "proper telemetry", "access modifier strategy", "interface architecture", "documentation", "versioning strategy"]
+
+applicable_object_types: ["codeunit", "table", "page", "interface", "permissionset"]
+
+relevance_threshold: 0.5
 ---
 # Partner Readiness Analysis for AppSource Apps
 

package/embedded-knowledge/domains/parker-pragmatic/proposal-workflows/creating-effective-proposals.md

@@ -11,6 +11,16 @@ applies_to:
   - "AI-Assisted Development"
   - "Collaborative Workflows"
 last_updated: "2025-11-01"
+
+relevance_signals:
+  constructs: ["SetCurrentKey", "SetRange", "FindFirst", "FindSet", "Error"]
+  keywords: ["AI proposal", "proposal-based", "trust building", "verification", "specialist review", "temporary folder", "reviewable", "transparency", "confidence level"]
+  anti_pattern_indicators: ["direct changes", "over-confident", "no cleanup plan", "incomplete code", "vague proposal"]
+  positive_pattern_indicators: ["complete working example", "clear reasoning", "honest limitations", "specialist review", "cleanup instructions", "confidence rating"]
+
+applicable_object_types: ["codeunit", "table", "page", "report", "query"]
+
+relevance_threshold: 0.3
 ---
 
 # Creating Effective AI Proposals

package/embedded-knowledge/domains/parker-pragmatic/trust-building/working-with-ai-skeptics.md

@@ -11,6 +11,16 @@ applies_to:
   - "AI-Assisted Development"
   - "Team Collaboration"
 last_updated: "2025-11-01"
+
+relevance_signals:
+  constructs: ["SetCurrentKey", "SetRange", "FindFirst"]
+  keywords: ["AI skepticism", "trust building", "transparency", "verification", "proposal", "control", "collaboration", "confidence level", "specialist validation", "learning"]
+  anti_pattern_indicators: ["rush trust building", "hide limitations", "dismiss skepticism", "autonomous changes", "over-promise"]
+  positive_pattern_indicators: ["explain reasoning", "provide evidence", "invite validation", "acknowledge uncertainty", "gradual trust", "proposal-based"]
+
+applicable_object_types: ["codeunit", "table", "page", "report", "query"]
+
+relevance_threshold: 0.3
 ---
 
 # Working with AI-Skeptical Developers

package/embedded-knowledge/domains/quinn-tester/fielderror-validation-patterns.md

@@ -1,4 +1,4 @@
----
+---
 title: "FieldError in Validation Patterns"
 domain: "quinn-tester"
 difficulty: "intermediate"
@@ -7,7 +7,17 @@ tags: ["fielderror", "validation", "business-rules", "onvalidate", "posting-code
 prerequisites: ["fielderror-syntax-usage", "field-triggers", "validation-fundamentals"]
 related_topics: ["business-rule-validation", "posting-procedures", "data-integrity-patterns"]
 samples: "samples/fielderror-validation-patterns.md"
----
+
+relevance_signals:
+  constructs: ["FieldError", "OnValidate", "Error", "TestField"]
+  keywords: ["validation", "business rules", "data integrity", "posting", "error handling", "field validation"]
+  anti_pattern_indicators: ["validation fails", "data integrity violation", "invalid field value"]
+  positive_pattern_indicators: ["FieldError pattern", "validation procedure", "business rule enforcement"]
+
+applicable_object_types: ["table", "codeunit", "page"]
+
+relevance_threshold: 0.5
+---
 # FieldError in Validation Patterns
 
 ## Overview

package/embedded-knowledge/domains/quinn-tester/isolation-testing-patterns.md

@@ -9,6 +9,16 @@ related_topics:
   - "../alex-architect/testability-design-patterns.md"
   - "../roger-reviewer/testability-code-smells.md"
 source: "Adapted from Vjeko.com: Testing in isolation (Dec 2023)"
+
+relevance_signals:
+  constructs: ["Interface", "Codeunit", "procedure"]
+  keywords: ["test double", "mock", "stub", "spy", "dummy", "isolation", "dependency injection", "unit testing", "test"]
+  anti_pattern_indicators: ["flaky test", "slow test", "database dependency in test"]
+  positive_pattern_indicators: ["test isolation", "mock implementation", "test double", "dependency injection"]
+
+applicable_object_types: ["codeunit"]
+
+relevance_threshold: 0.5
 ---
 # Isolation Testing Patterns with Test Doubles
 

package/embedded-knowledge/domains/quinn-tester/rule-execution.md

@@ -1,11 +1,21 @@
----
+---
 title: "API Page Validation Rule Execution"
 domain: "quinn-tester"
 difficulty: "intermediate"
 bc_versions: "14+"
 tags: ["validation", "business-rules", "data-integrity"]
 samples: "samples/rule-execution.md"
----
+
+relevance_signals:
+  constructs: ["OnValidate", "Error", "FieldError", "TestField"]
+  keywords: ["API", "OData", "validation", "business rules", "data integrity", "HTTP", "batch processing"]
+  anti_pattern_indicators: ["validation bypass", "API error", "validation performance issue"]
+  positive_pattern_indicators: ["API validation", "rule execution", "OData validation", "field validation"]
+
+applicable_object_types: ["page", "table", "codeunit"]
+
+relevance_threshold: 0.5
+---
 # API Page Validation Rule Execution
 
 ## Overview

package/embedded-knowledge/domains/quinn-tester/table-safety-validation-patterns.md

@@ -1,4 +1,4 @@
----
+---
 title: "Table Safety Validation Patterns for Error Prevention"
 domain: "quinn-tester"
 difficulty: "intermediate"
@@ -6,7 +6,17 @@ bc_versions: "14+"
 tags: ["error-prevention", "table-safety", "validation", "defensive-programming", "data-protection"]
 prerequisites: ["error-handling", "al-tables"]
 samples: "samples/table-safety-validation-patterns.md"
----
+
+relevance_signals:
+  constructs: ["IsTemporary", "Error", "TestField", "FieldError"]
+  keywords: ["defensive programming", "error prevention", "validation", "precondition", "data protection", "fail-fast"]
+  anti_pattern_indicators: ["validation bypass", "generic error handling", "late validation", "skip safety check"]
+  positive_pattern_indicators: ["safety validation", "precondition check", "defensive programming", "error prevention"]
+
+applicable_object_types: ["table", "codeunit"]
+
+relevance_threshold: 0.5
+---
 # Table Safety Validation Patterns for Error Prevention
 
 ## Overview

package/embedded-knowledge/domains/quinn-tester/temporary-table-operation-validation.md

@@ -1,4 +1,4 @@
----
+---
 title: "Temporary Table Operation Validation Patterns"
 domain: "quinn-tester"
 difficulty: "intermediate"
@@ -6,7 +6,17 @@ bc_versions: "14+"
 tags: ["validation", "temporary-tables", "data-integrity", "operation-safety", "preconditions"]
 prerequisites: ["al-tables", "validation-patterns"]
 samples: "samples/temporary-table-operation-validation.md"
----
+
+relevance_signals:
+  constructs: ["IsTemporary", "Error", "FieldError", "TestField"]
+  keywords: ["temporary table", "validation", "precondition", "operation safety", "data integrity", "table characteristics"]
+  anti_pattern_indicators: ["incomplete validation", "late validation", "silent failure", "missing precondition check"]
+  positive_pattern_indicators: ["temporary table validation", "operation validation", "precondition check", "table type check"]
+
+applicable_object_types: ["table", "codeunit"]
+
+relevance_threshold: 0.5
+---
 # Temporary Table Operation Validation Patterns
 
 ## Overview

package/embedded-knowledge/domains/roger-reviewer/al-begin-end-block-structure.md

@@ -14,6 +14,16 @@ improvement_suggestion: "Use proper begin/end block structure for maintainable A
 implementation_steps: ["understand-block-types", "apply-nesting-rules", "maintain-indentation"]
 validation_criteria: ["proper-block-nesting", "consistent-indentation", "clear-trigger-structure"]
 technical_areas: ["al-code", "syntax"]
+
+relevance_signals:
+  constructs: ["begin", "end", "trigger", "procedure", "if", "then", "else", "case", "while", "for", "try", "catch"]
+  keywords: ["block structure", "nesting", "indentation", "scope", "trigger", "procedure body", "control structure"]
+  anti_pattern_indicators: ["mismatched begin/end", "inconsistent indentation", "excessive nesting", "empty blocks"]
+  positive_pattern_indicators: ["proper block nesting", "consistent indentation", "clear trigger structure"]
+
+applicable_object_types: ["codeunit", "page", "table", "report", "query", "xmlport", "pageextension", "tableextension"]
+
+relevance_threshold: 0.4
 ---
 
 # AL Begin/End Block Structure Conventions

package/embedded-knowledge/domains/roger-reviewer/al-binary-operator-spacing.md

@@ -14,6 +14,16 @@ improvement_suggestion: "Use consistent spacing around binary operators to impro
 implementation_steps: ["standardize-operator-spacing", "apply-consistent-patterns", "validate-readability"]
 validation_criteria: ["consistent-operator-spacing", "improved-expression-clarity"]
 technical_areas: ["al-code"]
+
+relevance_signals:
+  constructs: ["+", "-", "*", "/", "mod", "=", "<>", "<", ">", "<=", ">=", "and", "or", "not", ":="]
+  keywords: ["operator spacing", "expression", "binary operator", "arithmetic", "comparison", "logical", "assignment"]
+  anti_pattern_indicators: ["no spacing around operators", "inconsistent spacing", "cramped expressions"]
+  positive_pattern_indicators: ["single space before and after", "consistent operator spacing", "clear operator separation"]
+
+applicable_object_types: ["codeunit", "page", "table", "report", "query", "xmlport", "pageextension", "tableextension"]
+
+relevance_threshold: 0.4
 ---
 
 # AL Binary Operator Spacing

package/embedded-knowledge/domains/roger-reviewer/al-blank-line-organization.md

@@ -14,6 +14,16 @@ improvement_suggestion: "Use strategic blank lines to organize AL code into logi
 implementation_steps: ["identify-logical-sections", "insert-separating-blank-lines", "validate-consistency"]
 validation_criteria: ["logical-grouping-clear", "consistent-spacing-applied"]
 technical_areas: ["al-code"]
+
+relevance_signals:
+  constructs: ["var", "begin", "end", "procedure", "trigger"]
+  keywords: ["blank line", "white space", "code organization", "logical grouping", "visual separation"]
+  anti_pattern_indicators: ["excessive blank lines", "no blank lines", "random spacing", "inconsistent patterns"]
+  positive_pattern_indicators: ["logical section separation", "consistent spacing", "clear functional boundaries"]
+
+applicable_object_types: ["codeunit", "page", "table", "report", "query", "xmlport", "pageextension", "tableextension"]
+
+relevance_threshold: 0.4
 ---
 
 # AL Blank Line Organization

package/embedded-knowledge/domains/roger-reviewer/al-case-action-formatting.md

@@ -14,6 +14,16 @@ improvement_suggestion: "Format case statement actions with consistent indentati
 implementation_steps: ["standardize-case-indentation", "align-action-blocks", "validate-readability"]
 validation_criteria: ["consistent-indentation", "clear-action-separation"]
 technical_areas: ["al-code"]
+
+relevance_signals:
+  constructs: ["case", "of", "else", "end"]
+  keywords: ["case statement", "case action", "case branch", "decision structure", "control flow"]
+  anti_pattern_indicators: ["inconsistent case label alignment", "poor action block indentation", "unclear action boundaries"]
+  positive_pattern_indicators: ["consistent indentation", "clear action separation", "aligned case labels"]
+
+applicable_object_types: ["codeunit", "page", "table", "report", "query", "xmlport", "pageextension", "tableextension"]
+
+relevance_threshold: 0.4
 ---
 
 # AL Case Action Formatting