fix(coderabbit): review generated outputs

[ANcpLua]

What changed

• Tighten the Pro+ CodeRabbit config after first reviewer feedback.
• Stop excluding generated outputs and lockfiles from CodeRabbit review so generated-file drift checks and path instructions can actually inspect those changes.
• Keep heavy build/output folders excluded (bin, obj, dist, node_modules, coverage, minified bundles, artifacts).
• Split issue-enrichment labels from PR area labels to reduce config drift.

Validation

• Regenerated .coderabbit.yaml from the same schema-backed generator.
• Validated .coderabbit.yaml against the live CodeRabbit v2 schema before pushing.

[coderabbitai]

Warning

Rate limit exceeded

@ANcpLua has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 1 minute and 16 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 0e578081-b1dc-4076-8b0c-7945b6c58865

📥 Commits

Reviewing files that changed from the base of the PR and between 48dd827 and f5b9eb1.

📒 Files selected for processing (1)

• .coderabbit.yaml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dev/coderabbit-proplus-generated-review-20260516160309

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch dev/coderabbit-proplus-generated-review-20260516160309

• 🛠️ architecture hardening
• 🛠️ security pass
• 🛠️ test gap closure
• 🛠️ docs and changelog alignment
• 🛠️ performance and allocation pass

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

@coderabbitai autofix

[coderabbitai]

Note

Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it.

Autofix skipped. No unresolved CodeRabbit review comments with fix instructions found.

[claude]

Claude encountered an error after 2s —— View job

---

I'll analyze this and get back to you.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

The PR successfully updates .coderabbit.yaml to include generated files and lockfiles in reviews and shifts from area-based to type-based issue labels. However, there is a synchronization gap between the labeling_instructions and the auto_planning.labels trigger list; several labels like documentation and dependencies are configured for enrichment but will not trigger automatic planning.

Furthermore, while the removal of exclusion patterns for generated files (e.g., .g.cs, package-lock.json) aligns with the PR's stated goals, it may lead to increased noise and low-value suggestions from AI agents on non-human-editable files. Codacy analysis currently reports the configuration as up to standards, but these logic inconsistencies should be addressed prior to merging.

About this PR

• Enabling reviews for generated files and lockfiles (like package-lock.json and .g.cs) aligns with the PR intent but may significantly increase the volume of non-actionable comments in future pull requests. Monitor the review quality to ensure these files do not drown out human-authored code changes.

Test suggestions

• Verify that generated files (e.g., File.g.cs) are no longer filtered out by path_filters.
• Verify that lockfiles (e.g., package-lock.json) are no longer filtered out by path_filters.
• Verify that build output folders like 'bin/' and 'dist/' remain filtered out by path_filters.
• Verify that issue enrichment successfully applies type-based labels like 'bug' or 'enhancement' based on the new labeling instructions.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify that generated files (e.g., File.g.cs) are no longer filtered out by path_filters.
2. Verify that lockfiles (e.g., package-lock.json) are no longer filtered out by path_filters.
3. Verify that build output folders like 'bin/' and 'dist/' remain filtered out by path_filters.
4. Verify that issue enrichment successfully applies type-based labels like 'bug' or 'enhancement' based on the new labeling instructions.

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}

[codacy-production]

_{🟡 MEDIUM RISK}

Suggestion: The removal of path filters for generated files and lockfiles may cause AI agents to analyze code not intended for manual review, increasing noise in PRs. If you encounter too much noise, consider restoring exclusions like !**/*.g.cs, !**/*.Designer.cs, or !**/package-lock.json.

[codacy-production]

_{🟡 MEDIUM RISK}

Suggestion: The labeling_instructions (lines 591-607) and auto_planning.labels (lines 584-588) are out of sync. Specifically, help-wanted is listed as an auto-planning trigger but lacks instructions for automatic labeling. Conversely, the documentation and dependencies labels have instructions but are not in the auto_planning.labels trigger list, meaning issues in these categories will not be automatically planned. Additionally, the review:slop label for detecting low-quality AI content has been removed; consider restoring it if automated content filtering is required.