ci: add trusted coverage report validation
Merged
RE
2mo ago+666+666+012345678901234567890123456789-69-69-01234567890123456789
Problem
The coverage check currently trusts a merged artifact produced by pull request workflow code and cannot prove that every CI partition contributed data. It also publishes only line coverage, so linked/shared source and branch data are not represented by canonical repository identities.
Solution
- Preserve the complete 60-partition test matrix and require an exact reviewed artifact set.
- Add per-artifact receipts which bind every report to the same tested merge commit.
- Move validation and merging into the trusted
workflow_runreporter, then verify the recorded merge commit contains the triggering pull request head. - Validate canonical source paths, source-file existence, and reported line bounds against the exact tested tree.
- Publish de-duplicated physical line coverage and conservative canonical branch coverage.
- Keep the coverage conclusion successful during calibration while surfacing all validation failures as reporting-job failures.
Rollout
This independently mergeable slice establishes trustworthy inputs and report-only canonical metrics. Follow-up work can add same-matrix main-versus-PR baselines, measure normal variance, and enable regression conclusions without introducing an unstable 90% gate.
Advances #10867