ci(codecov): expand coverage to hardware, adapters, and ffb flags

[EffortlessSteven]

Summary

Extends the Codecov integration to track execution-surface coverage across four independent flags, each targeting a distinct subsystem with separate claim boundaries.

Coverage Flags

Flag	Scope	Status
rust-core	Portable control-plane crates	Blocking on failures
rust-hardware	HID and device abstraction	Advisory
rust-adapters	Simulator adapter implementations	Advisory
rust-ffb	Force feedback and safety systems	Advisory

Changes

1. Expand workflow crate selection

   • Core flag: flight-core, flight-axis, flight-bus, flight-scheduler, flight-rules, flight-profile, flight-units, flight-session, flight-metrics, and supporting crates
   • Hardware flag: flight-hid, flight-hid-support, flight-device-common, flight-virtual
   • Adapters flag: flight-simconnect, flight-xplane, flight-dcs-export, flight-adapter-common
   • FFB flag: flight-ffb, flight-ffb-moza, flight-ffb-vpforce, flight-tactile

2. Separate coverage runs per flag

   • Each flag generates independent coverage-<flag>.json and lcov-<flag>.info artifacts
   • Separate Codecov upload steps with appropriate failure modes
   • Receipt tracks all flag statuses

3. Document flag semantics

   • Adds docs/ci/coverage-flags.md explaining scope, claim boundaries, and interpretation guidance
   • Clarifies what each flag measures and what it doesn't claim to prove

Claim Boundary

Each flag remains execution-surface evidence only and does not prove:

• Real-time deadline correctness
• Actual hardware/device correctness (requires hardware gate)
• Simulator protocol correctness (requires integration testing)
• Force feedback safety (requires QG-FFB-SAFETY gate)
• Release readiness

CI Economics

• Default PR impact: None (coverage only runs on labeled PRs)
• Branching: Fully independent from policy registration PR
• Failure mode: Only rust-core flag blocks; rust-hardware, rust-adapters, rust-ffb are advisory
• Rollback: Delete expanded crate lists from workflow step, keep single-flag reporting

Validation

• Workflow syntax valid
• Coverage generation per-flag confirmed
• Receipt includes all flag statuses
• Documentation complete
• Advisory flags will not block CI

---

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 57 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: 04831c1a-3fd1-47f2-b65b-2944e428ca46

📥 Commits

Reviewing files that changed from the base of the PR and between 77f6b3e and 057b26b.

📒 Files selected for processing (1)

• docs/ci/coverage-flags.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/expand-codecov-flags-AqxiH

---

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