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/events/cmfrt-onbefore-onafter-all-globals.bad.al

@@ -0,0 +1,15 @@
+// No integration events — dependent extensions cannot intercept or react
+// to the operation without using an AL override, which is a breaking pattern.
+codeunit 2045700 "CMFRT BA Item Price Impl"
+{
+    procedure CMFRTBAUpdateItemPrice(ItemNo: Code[20]; UnitPrice: Decimal)
+    var
+        Item: Record Item;
+    begin
+        Item.SetLoadFields("Unit Price");
+        if Item.Get(ItemNo) then begin
+            Item.Validate("Unit Price", UnitPrice);
+            Item.Modify();
+        end;
+    end;
+}