Services named most often in incident records (counts under review)

Under review: while the block-verdict review is on, this route answers HTTP 200 with every verdict field set to unknown or null (some coverage fields may remain), a top-level review object (status under_review, verdict unknown, reason, source, and dataAsOf: the data date, or null when the source reports none or could not be read) and X-Voidly-Verdict-Review: under_review, with Cache-Control no-store. A held answer is not an outage and not a finding either way; see https://voidly.ai/data-quality#block-verdict-review. While held, services, service_count and total_incidents_with_services are null; citable incidents with evidence remain at /data/incidents. Synthetic empty-list example. Frequency over curated incidents does not establish service blocking prevalence.