fix(coderabbit): tighten review path guidance

[ANcpLua]

What changed

• Split JSON into JSON-specific CodeRabbit guidance instead of applying TypeScript runtime guidance to *.json files.
• Narrow OpenTelemetry/TypeSpec model guidance to semantic-convention/model directories and TypeSpec files instead of all YAML.
• Make the CI release-safety pre-merge check more deterministic.
• Use knowledge_base.mcp.usage: auto so MCP context is consumed when provisioned without falsely requiring it everywhere.

Validation

• Regenerated .coderabbit.yaml from the schema-backed generator.
• Validated .coderabbit.yaml against the live CodeRabbit v2 schema.
• Checked generated path entries for remaining brace globs and broad YAML/JSON misrouting 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 2 minutes and 55 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: 878bc382-a730-4245-9528-3bddfeac5d3d

📥 Commits

Reviewing files that changed from the base of the PR and between 78347f4 and a32f9b7.

📒 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-final-20260516161330

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch dev/coderabbit-proplus-final-20260516161330

• 🛠️ 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 pull request is currently inconsistent with its own description. While the changes to the 'CI Release Safety' instructions and the MCP usage setting are correctly implemented and meet Codacy quality standards, two primary objectives are missing from the code: the separation of JSON-specific guidance and the narrowing of OpenTelemetry/TypeSpec model guidance. These missing implementation details constitute a significant gap in the acceptance criteria.

About this PR

• Scope Misalignment: The PR description mentions splitting JSON guidance and narrowing OpenTelemetry/TypeSpec model guidance to specific directories, but these changes are absent from the .coderabbit.yaml file. The validation section also claims path routing was checked, but no path filters were modified.

Test suggestions

• Verify the 'CI Release Safety' instruction set includes specific pass/fail logic for workflow and secret exposure.
• Verify MCP usage is set to 'auto' to allow conditional context provisioning.
• Verify specific guidance for *.json files is separate from TypeScript runtime guidance.
• Verify OpenTelemetry/TypeSpec guidance is scoped to specific directories and excludes general YAML.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify specific guidance for *.json files is separate from TypeScript runtime guidance.
2. Verify OpenTelemetry/TypeSpec guidance is scoped to specific directories and excludes general YAML.

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