Add CMFRT naming conventions, object ID ranges, and patterns documentation

- Introduced guidelines for using the "CMFRT" prefix in object names, fields, and procedures to avoid naming collisions and ensure clarity.
- Established rules for object ID ranges to prevent conflicts with other extensions and maintain historical integrity.
- Documented best practices and anti-patterns for various coding patterns, including case statements, interface injection, label usage, and validation methods.
- Implemented a standards review skill to evaluate AL source changes against CMFRT company standards, ensuring compliance with naming, permissions, and architectural patterns.

custom/knowledge/patterns/cmfrt-case-requires-else.good.al

@@ -0,0 +1,18 @@
+codeunit 2045760 "CMFRT GD Status Processor"
+{
+    procedure CMFRTGDProcessByStatus(Status: Enum "CMFRT GD POI Status")
+    begin
+        case Status of
+            Status::Active:
+                CMFRTGDActivatePOI();
+            Status::Inactive:
+                CMFRTGDDeactivatePOI();
+            Status::Pending:
+                CMFRTGDQueuePOIForReview();
+            else
+                // New enum values added in the future are caught here
+                // instead of silently doing nothing.
+                Error('Unhandled POI status: %1', Status);
+        end;
+    end;
+}