ci(codecov): add quiet Codecov config

[EffortlessSteven]

Summary

Adds step 2 of the diffguard Codecov rollout: codecov.yml with advisory statuses and disabled comments for quiet operation.

CI economics

• Default PR LEM impact: None; configuration file only.
• Workflow touched: None; this is a configuration file for the Codecov service.
• Branch protection impact: None; all statuses are informational (threshold applied but do not block).
• Failure mode caught: None directly; this is configuration that enables the coverage workflow from PR 1 to report.
• Cheaper signal considered: Configuration is static YAML; no cheaper signal available.
• Rollback path: Delete codecov.yml and coverage.yml workflow will still generate and upload artifacts; Codecov service defaults apply.

Claim boundary

Codecov coverage is Rust execution-surface evidence only. It does not prove:

• diff parser correctness
• rule evaluation correctness
• inline suppression correctness
• renderer completeness (SARIF, JUnit, Checkstyle, GitLab, etc.)
• LSP diagnostic correctness
• false-positive baseline or trend correctness
• mutation adequacy
• fuzz robustness
• release readiness

Those are separate proof lanes (test, golden, conformance, fuzz, mutation).

Configuration highlights

• Project coverage: Auto target with 5% threshold (informational)
• Patch coverage: 70% target with 20% threshold (informational)
• Comments: Disabled (no commit comments from Codecov)
• Annotations: Disabled (no GitHub check annotations)
• Precision: 2 decimal places, round down
• Flags: rust-core to track Rust execution surface
• Ignores: Benchmarks, examples, and target directories

Validation

• codecov.yml is valid YAML
• all status sections are informational (will not block)
• comments and annotations are both disabled (quiet operation)
• precision, range, and rounding are reasonable defaults
• flag matches the workflow (rust-core)

---

Generated by Claude Code

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[coderabbitai]

Warning

Rate limit exceeded

@EffortlessSteven has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 48 minutes and 33 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: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: edf485a7-e688-4d77-aa8b-53367819501f

📥 Commits

Reviewing files that changed from the base of the PR and between 3e1d9e1 and 718a2b6.

📒 Files selected for processing (1)

• codecov.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/codecov-config

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.