Add CMFRT coding standards documentation and examples

- Introduced guidelines for "one codeunit one global function" architecture to enforce single responsibility in AL code.
- Added best practices and anti-patterns for adding parameters via overloads to maintain backward compatibility.
- Documented the importance of never deleting members in AL and always marking them as obsolete.
- Established the requirement for OnBefore and OnAfter integration events for global procedures to enhance extensibility.
- Defined naming conventions for CMFRT objects, including prefixes and object ID ranges to avoid conflicts.
- Implemented patterns for case statements to ensure all cases are handled, including the necessity of an else clause.
- Introduced the interface injection pattern to allow pluggable operations in table-level code.
- Recommended using Confirm Management for user confirmations to improve testability.
- Established a three-permission set pattern for security to ensure proper access control.
- Created a review skill for CMFRT AL standards to automate compliance checks against established guidelines.

custom/knowledge/architecture/cmfrt-calls-from-base-table-only.bad.al

@@ -0,0 +1,14 @@
+// Subscriber calls the implementation codeunit DIRECTLY — bypasses the base
+// table's entry point and all OnBefore/OnAfter integration events.
+codeunit 2045720 "CMFRT BA Sales Subscribers"
+{
+    [EventSubscriber(ObjectType::Codeunit, Codeunit::"Sales-Post", 'OnAfterPostSalesDoc', '', false, false)]
+    local procedure CMFRTBAOnAfterPostSalesDoc(var SalesHeader: Record "Sales Header")
+    var
+        SyncImpl: Codeunit "CMFRT BA SyncPostedDoc Impl";
+    begin
+        // Direct call to implementation codeunit — OnBefore/OnAfter events on the
+        // base table never fire, dependent extensions cannot intercept this operation.
+        SyncImpl.CMFRTBASyncPostedSalesDoc(SalesHeader."No.");
+    end;
+}