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/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;
+}