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/security/cmfrt-three-permissionset-pattern.bad.al

@@ -0,0 +1,16 @@
+// Only one flat permission set — no composition, no read-only role.
+// Adding a new table means updating this one set and hoping nothing was missed.
+permissionset 2045222 "CMFRT GD Geodynamics"
+{
+    Assignable = true;
+    Caption = 'CMFRT GD Geodynamics';
+    Permissions =
+        table "CMFRT GD POI" = X,
+        tabledata "CMFRT GD POI" = RIMD,
+        table "CMFRT GD Setup" = X,
+        tabledata "CMFRT GD Setup" = RIMD,
+        page "CMFRT GD POI" = X,
+        page "CMFRT GD Setup" = X,
+        codeunit "CMFRT GD IGeodynamics" = X,
+        codeunit "CMFRT GD IGeodynamics Impl" = X;
+}