chore: Validate and fix CodeRabbit configuration against latest schema

[ashleyshaw]

Issue Description

CodeRabbit is reporting unrecognized properties in .coderabbit.yml:

• auto_labels
• auto_assign
• auto_review

These properties are not recognized by the current CodeRabbit schema v2 and should be removed or updated.

Validation Plan

1. Fetch Latest Schema: Validate against CodeRabbit v2 schema
2. Current Configuration Review: Audit .coderabbit.yml for:
   • Valid property keys per schema v2
   • Deprecated or invalid settings
   • Unused configuration sections
3. Fix Invalid Properties: Remove or update any unrecognized properties
4. Optimize for Governance Repo: Ensure settings align with the special nature of .github repo

Current Configuration Summary

• Profile: chill (reduce noise, high-signal reviews)
• Path Filters: Excludes build/, node_modules/, logs/, docs/drafts/, schema/, coverage/
• Path Instructions: 10 specialized review rules for different file types
• Features: Auto-reply enabled, high-level summary, review status

Recommendations

1. ✅ Schema language server directive already present at top
2. Review all property keys against latest v2 schema
3. Ensure chat.auto_reply and other settings are valid
4. Update path_instructions to use latest CodeRabbit conventions
5. Consider adding annotations for better PR integration

Acceptance Criteria

• Configuration validated against CodeRabbit v2 schema
• All unrecognized properties removed or documented
• Configuration merged and validated on live PR
• No CodeRabbit configuration warnings on next PR
• Update PR templates if needed to work with optimized CodeRabbit settings

References

• CodeRabbit Configuration Docs: https://docs.coderabbit.ai/guides/configure-coderabbit
• Schema Validator: https://docs.coderabbit.ai/configuration/yaml-validator
• Related PR: feat: Awesome GitHub website Phase 1 implementation #777 (migration guide references fix)

Type

chore

Related

• feat: Awesome GitHub website Phase 1 implementation #777 (previous governance fix)

Definition of Ready (DoR)

• Task/goal described and scoped
• Confirms it does not fit the Code Refactor or Maintenance templates
• Acceptance criteria listed
• Estimate added (if applicable)

Definition of Done (DoD)

• Affected files, labels, or settings updated and documented
• PR uses correct branch prefix (chore/)
• Approved by at least one maintainer

[linear-code]

LS-926