test: cover RadarReports' empty-corpus arms in the e2e variant build

[hivecommons-hive]

Test Improvement

src/components/RadarReports/index.js branches on two document-level fields of
data/radar-reports.json:

• line 6 — if (!data.generatedAt) return null;, so SyncStatus renders no
  provenance line;
• line 24 — const radarReports = data.radarReports || [];, the fallback that
  supplies the list the page maps over.

Neither is reachable against the checked-in corpus, which always carries a
generatedAt and six reports. Both are ordinary shapes: the file is
regenerated daily from cncf.io by npm run collect:radar-reports via
.github/workflows/refresh-radar-reports.yml, so a collector run that fetches
nothing produces exactly them.

Two new files, no edits to existing ones:

• tests/e2e/fixtures/data-variants/radar-reports.json — clears both fields in
  the variant build. Clearing them in the ordinary coverage build would trade
  the provenance line and all six rendered reports for these arms rather than
  add a case, which is the same reason AwardsTimeline's provenance paragraph
  lives in the variant build.
• tests/e2e/radar-reports-variant.spec.js — pairs /resources/radar-reports
  with /e2e-coverage-variant/resources/radar-reports, asserting the
  provenance line and all six <li> on the first and neither on the second.
  Asserting the real route too is what makes the pair evidence that the arms
  switched, rather than that one page happens to look a certain way.

What this does not do

It does not move lines 6 and 24 out of the e2e report's uncovered list, and
the PR does not claim to. The browser demonstrably takes both arms — the
variant chunk keeps the branches (function i(){if(!o.ro)return null;...} and
let e=o.Gb||[], compiled against {"ro":null,...,"Gb":null}) and the
assertions only pass if it did — but getRegionCoverage in
tests/tools/e2e-coverage-report.mjs keys a region on its exact original
coordinates, and the two builds map back to different ones: the real build
records 6:25:6:37 count 0 and 24:40:24:46 count 0, while the variant
records 7:2:21:1 count 0 and 21:0:29:26 count 1 and emits no key matching
either zero region. That residue is #1066 / #1079; once the union folds the two
builds' coordinates, these arms fold with no change here. The spec preamble
records the observed keys so the next reader does not have to re-derive them.

Verification

Run locally at 8afaa67:

• npm run test — 1941 passed, 0 failed.
• npm run build:e2e:coverage then npm run test:e2e:coverage with a
  Playwright chromium run — 300 passed, 0 failed, including both new cases.
• npm run report:e2e:coverage -- --check-source 100 --check-source-regions 80 --require-source-files — exit 0; src files 87.79% regions, well above the
  CI floor of 80, so .github/workflows/ci.yml needs no change.

Files claimed

tests/e2e/fixtures/data-variants/radar-reports.json (new) and
tests/e2e/radar-reports-variant.spec.js (new). Disjoint from every open
hold-gated PR: it does not touch tests/e2e-data-fixtures.test.mjs (#1034,
#1078), tests/e2e/data-variants.spec.js (#1034),
tests/tools/e2e-coverage-report.mjs (#1040, #1070),
tests/e2e/fixtures/data-variants/metrics.json (#1093), or any member
directory, case studies, or svg-active-content file. The cases lists in
tests/e2e-data-fixtures.test.mjs are hardcoded rather than exhaustive, so a
new variant overlay needs no edit there — the same reason #1093's metrics.json
variant needed none.

Related Issue

Refs #1097 — the first completion box (the overlay and the spec) is what this
lands; the second (lines 6 and 24 leaving the uncovered-region list) stays open
and is gated on the region-union work in #1066 / #1079, which lives in
tests/tools/e2e-coverage-report.mjs and is occupied by #1040 and #1070.

---

Filed by quality agent (hold-gated mode). Human review required.

— hive: agent=quality backend=copilot model=claude-opus-5 copilot=1.0.88

[hivecommons-hive]

Important

Held for human review by the hive's ACMM level gate.

This PR was opened by the "quality" agent while Hive policy required a human checkpoint for that agent. Non-outreach agents are held at ACMM L3–L5; the outreach agent is always held because it publishes project-facing communication.

Hive will keep the hold label until a human removes it. Operators can make a deliberate one-off release during an ACMM level change with release_level_holds=true, but level changes never release this hold automatically.