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/breaking-changes/cmfrt-add-parameter-via-overload.good.al

@@ -0,0 +1,15 @@
+codeunit 2045700 "CMFRT TST Calculator"
+{
+    // Original signature — kept unchanged and marked obsolete once callers migrate.
+    [Obsolete('Use CMFRTTSTCalculateSumWithRounding instead.', 'Task-23859')]
+    procedure CMFRTTSTCalculateSum(NumberOne: Decimal; NumberTwo: Decimal): Decimal
+    begin
+        exit(CMFRTTSTCalculateSumWithRounding(NumberOne, NumberTwo, 2));
+    end;
+
+    // New overload with extra parameter — callers can adopt at their own pace.
+    procedure CMFRTTSTCalculateSumWithRounding(NumberOne: Decimal; NumberTwo: Decimal; Decimals: Integer): Decimal
+    begin
+        exit(Round(NumberOne + NumberTwo, Power(10, -Decimals)));
+    end;
+}