fix(ci): align llvm cov report contract

[KooshaPari]

The workspace coverage job runs all tests and writes LCOV successfully, then fails because this cargo-llvm-cov version rejects --workspace on the report subcommand. Keep --json, redirect stdout, and remove the unsupported flag.

Source branch retained for provenance.

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[coderabbitai]

Warning

Review limit reached

@KooshaPari, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 58 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 4120b8ae-80b5-4973-8908-d22e85254783

📥 Commits

Reviewing files that changed from the base of the PR and between c826953 and 9224810.

📒 Files selected for processing (1)

• .github/workflows/mutation.yml

📝 Walkthrough

Walkthrough

The GitHub Actions workflows now filter Rust coverage inputs, handle missing coverage records defensively, conditionally run mutation testing for relevant changes, and gate mutation aggregation and reporting on the computed scope.

Changes

CI workflow hardening

Layer / File(s)	Summary
Coverage collection and parsing .github/workflows/coverage.yml	Workspace and critical-crate coverage commands exclude selected files and defensively parse configuration and workspace line percentages.
Mutation testing scope gating .github/workflows/mutation.yml	A scope job detects Rust/Cargo-related changes and gates mutation testing accordingly.
Mutation summary aggregation and gates .github/workflows/mutation.yml	Mutation counts come from text summaries, while aggregation, threshold checks, and artifact uploads run only when mutation testing is required.

Estimated code review effort: 3 (Moderate) | ~25 minutes

Sequence Diagram(s)

sequenceDiagram
  participant GitHubEvent
  participant scope
  participant mutation
  participant summarize
  GitHubEvent->>scope: provide event and changed paths
  scope->>scope: determine whether mutation testing is required
  scope->>mutation: pass required output
  mutation->>summarize: provide per-crate mutation summaries
  summarize->>summarize: aggregate results when required

Loading

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly references the CI llvm-cov report contract change, which matches the main workflow update.
Description check	✅ Passed	The description is related to the coverage workflow changes, especially the cargo-llvm-cov report contract fix.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/coverage-report-cli-contract

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch fix/coverage-report-cli-contract

---

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.}

[github-actions]

No high/critical vulnerabilities introduced by this PR. ✅

[socket-security]

Dependency limit exceeded — report not shown.

This pull request scan exceeded the 10,000-dependency limit applied to this scan, so the results are incomplete and may be inaccurate. To avoid reporting false positives, Socket has not posted a report.

Upgrade your plan to raise the dependency limit and get complete reports, or view the partial scan in the dashboard.

Socket is always free for open source. If this is a non-commercial open source project, contact us to request a free Team account.

[github-actions]

No high/critical vulnerabilities introduced by this PR. ✅

[github-actions]

No high/critical vulnerabilities introduced by this PR. ✅

[github-actions]

No high/critical vulnerabilities introduced by this PR. ✅

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/coverage.yml:
- Around line 168-175: Indent the embedded Python body beginning with `import
json` and the closing `PY` heredoc terminator to the same indentation level as
the surrounding `run: |` block, while preserving the Python logic unchanged so
the workflow remains valid YAML.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: f6ba5301-d72f-4623-806c-f959c38bc3ce

📥 Commits

Reviewing files that changed from the base of the PR and between 86a8045 and c826953.

📒 Files selected for processing (1)

• .github/workflows/coverage.yml

📜 Review details

⏰ Context from checks skipped due to timeout. (3)

• GitHub Check: cargo-mutants (nightly correctness check) (perfharness)
• GitHub Check: Analyze (rust)
• GitHub Check: Mergify Merge Protections

🧰 Additional context used

🪛 actionlint (1.7.12)

.github/workflows/coverage.yml

[error] 168-168: could not parse as YAML: could not find expected ':'

(syntax-check)

🪛 YAMLlint (1.37.1)

.github/workflows/coverage.yml

[error] 169-169: syntax error: could not find expected ':'

(syntax)

🔇 Additional comments (2)

.github/workflows/coverage.yml (2)

60-62: LGTM!

---

74-82: LGTM!

[coderabbitai]

🎯 Functional Correctness | 🔴 Critical | ⚡ Quick win

Indent the embedded Python heredoc to keep the workflow valid YAML.

These lines are outside the run: | block’s indentation, so actionlint/yamllint reject the workflow before it runs. Indent the Python body and PY terminator to the same YAML block level.

Proposed fix

-import json
-import sys
-
-data = json.load(open(f"coverage-{sys.argv[1]}.json")).get("data", [])
-record = next((item for item in data if item.get("name") == "Workspace"), data[0] if data else {})
-percent = record.get("totals", {}).get("lines", {}).get("percent", 0.0)
-print(f"{percent:.2f}")
-PY
+          import json
+          import sys
+
+          data = json.load(open(f"coverage-{sys.argv[1]}.json")).get("data", [])
+          record = next((item for item in data if item.get("name") == "Workspace"), data[0] if data else {})
+          percent = record.get("totals", {}).get("lines", {}).get("percent", 0.0)
+          print(f"{percent:.2f}")
+          PY

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	import json
	import sys
	data = json.load(open(f"coverage-{sys.argv[1]}.json")).get("data", [])
	record = next((item for item in data if item.get("name") == "Workspace"), data[0] if data else {})
	percent = record.get("totals", {}).get("lines", {}).get("percent", 0.0)
	print(f"{percent:.2f}")
	PY
	import json
	import sys
	data = json.load(open(f"coverage-{sys.argv[1]}.json")).get("data", [])
	record = next((item for item in data if item.get("name") == "Workspace"), data[0] if data else {})
	percent = record.get("totals", {}).get("lines", {}).get("percent", 0.0)
	print(f"{percent:.2f}")
	PY

🧰 Tools

🪛 actionlint (1.7.12)

[error] 168-168: could not parse as YAML: could not find expected ':'

(syntax-check)

🪛 YAMLlint (1.37.1)

[error] 169-169: syntax error: could not find expected ':'

(syntax)

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/coverage.yml around lines 168 - 175, Indent the embedded
Python body beginning with `import json` and the closing `PY` heredoc terminator
to the same indentation level as the surrounding `run: |` block, while
preserving the Python logic unchanged so the workflow remains valid YAML.

Source: Linters/SAST tools

[github-actions]

No high/critical vulnerabilities introduced by this PR. ✅

[github-actions]

No high/critical vulnerabilities introduced by this PR. ✅

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud