[Chore] Clarify CodeRabbit approval checks

.coderabbit.yaml

@@ -55,7 +55,10 @@ reviews:
               or upstream repositories. Report only concrete, actionable conflicts or failure modes, citing
               the relevant repository location or external source. Prioritize correctness, security, data loss,
               lifecycle, and test gaps. Do not report generic best practices, unsupported concerns, speculative
-              style comments, or unrelated refactors. Search for existing helpers before suggesting abstractions.
+              style comments, or unrelated refactors. When changed code introduces a local implementation of a
+              cross-cutting concern, check whether it bypasses or duplicates an established repository abstraction
+              or nearby convention. Report only a concrete inconsistency with behavioral or maintenance impact,
+              and allow intentional deviations.
 
         - path: "**/*.{ts,tsx,js,jsx,mts,mjs,cts,cjs}"
           instructions: >-
@@ -153,10 +156,10 @@ reviews:
         description:
             mode: warning
         issue_assessment:
-            mode: warning
+            mode: error
         custom_checks:
             - name: Regression evidence
-              mode: warning
+              mode: error
               instructions: >-
                   Fail only when a concrete changed behavior lacks focused coverage at the lowest valid
                   test layer, tests merely mirror implementation, an affected error/negative/unset branch