[newhoggy]

Closes #133

Adds Coverage (GitHub Actions integration 15368) to the main ruleset's required checks. CONTRIBUTING now lists seven checks and explains that Coverage satisfies the merge queue requirement as a skipped job; workflow comments match. Thresholds, permissions, fork handling, and executable workflow configuration stay as configured in #131.

The implementation plan records the prerequisites:

• The main push published coverage-baseline; PR #132's Coverage job downloaded it and skipped recomputation. Its comment shows deltas without a recomputed note.
• All three initial Coverage executions succeeded (99 s, 58 s, 37 s versus 15 minutes). No flakes or release-induced failures observed in this small sample; version: latest remains a future source of risk. ci: also dogfood the pull request's own patchcov build #134 owns testing the PR-built binary.
• actions: read remains: the action uses the artifact download API, whose installation-token permissions require Actions read. A token without this permission was not experimentally tested.
• The existing merge_group job is skipped, as intended.

Verification

Ran from this feature worktree, with every Cargo command explicitly targeting its Cargo.toml, before commit and after fetching/rebasing onto current main:

• actionlint .github/workflows/ci.yml, git diff --check, JSON/workflow/docs consistency assertions: passed; seven unique required checks, all pinned to Actions.
• cargo fmt --check: passed.
• cargo test --locked --all-targets: 540 passed.
• cargo test --locked --doc: 1 passed.
• cargo clippy --locked --all-targets -- -D warnings: passed. The first attempt reported a missing generated .rmeta; immediate retry and the full repeated suites passed.
• cargo run --locked -- lint-markers: passed.
• cargo +1.88.0 test --locked --all-targets: 540 passed.
• cargo +1.88.0 test --locked --doc: 1 passed.
• RUSTDOCFLAGS='-D warnings' cargo doc --locked --no-deps --document-private-items: passed.

All seven checks in this PR's GitHub CI run passed, including Linux/macOS/Windows tests. Coverage downloaded the existing main baseline and skipped recomputation; its comment reports 99.4% overall coverage, zero delta, and no new executable lines.

Review and live configuration

Reviewed the committed three-file diff against origin/main...HEAD and its surrounding workflow/ruleset/docs: no actionable findings, no fixes or skipped findings. No departure from the plan or unrelated follow-ups.

This PR's Coverage run passed in 35 seconds. Applied the Coverage requirement to active ruleset 24650034. Fresh ruleset and effective main rules readbacks confirm all seven required checks are pinned to GitHub Actions; an exact payload comparison confirms every other live setting was preserved.

A post-change merge queue/release smoke test is not verified: it requires a merge, which this issue-to-pr run does not perform.

[github-actions]

Coverage

Total: 99.4% ⚪ 0 pp vs main

Comparing 9f564e3..0337281 (merge-base → PR head)

No per-file coverage changes vs main.

Touched files absent from every coverage report (3)

• .github/rulesets/main.json
• .github/workflows/ci.yml
• CONTRIBUTING.md

These files may contain no executable code or may have been omitted from the coverage run.

Patch coverage

No new executable lines added by this diff.

_{📦 Full per-file coverage summary · run summary}