build: correct CodeRabbit schema syntax (#1608)

Co-authored-by: copilot-swe-agent[bot] <[email protected]>
Co-authored-by: alandtse <[email protected]>

Author: Copilot

.coderabbit.yaml

@@ -1,26 +1,27 @@
 # CodeRabbit AI Configuration
 
-instructions: |
-    When reviewing PRs, please provide suggestions for:
-
-    1. **Conventional Commit Titles** (if not following https://www.conventionalcommits.org/ or
-    if the existing title does not describe the code changes):
-       Format: type(scope): description
-       Length: 50 characters limit for title, 72 for body
-       Style: lowercase description, no ending period
-       Examples:
-       - feat(vr): add cross-eye sampling
-       - fix(water): resolve flowmap bug
-       - docs: update shader documentation
+reviews:
+    path_instructions:
+        - path: "**/*"
+          instructions: |
+              When reviewing PRs, please provide suggestions for:
 
-    2. **Issue References** (if PR fixes bugs or implements features):
-       Suggest adding appropriate GitHub keywords:
-       - "Fixes #123" or "Closes #123" for bug fixes
-       - "Implements #123" or "Addresses #123" for features
-       - "Related to #123" for partial implementations
+              1. **Conventional Commit Titles** (if not following https://www.conventionalcommits.org/ or
+              if the existing title does not describe the code changes):
+                 Format: type(scope): description
+                 Length: 50 characters limit for title, 72 for body
+                 Style: lowercase description, no ending period
+                 Examples:
+                 - feat(vr): add cross-eye sampling
+                 - fix(water): resolve flowmap bug
+                 - docs: update shader documentation
 
-    Otherwise, use your standard review approach focusing on code quality.
+              2. **Issue References** (if PR fixes bugs or implements features):
+                 Suggest adding appropriate GitHub keywords:
+                 - "Fixes #123" or "Closes #123" for bug fixes
+                 - "Implements #123" or "Addresses #123" for features
+                 - "Related to #123" for partial implementations
 
-reviews:
+              Otherwise, use your standard review approach focusing on code quality.
     path_filters:
         - "**/*.hlsl"