CRYPTO-HISTORY-READINESS-JSON-CONTEXT (Report QA)

Release digest

CRYPTO-HISTORY-READINESS-JSON-CONTEXT (Report QA) — Crypto history readiness now normalizes raw BigQuery report-context JSON fields such as data_completeness_json, section_sources_json, section_freshness_json, surface_contract_json, security_evidence_json, contract_addresses_json, source_links_json, and admin_controls_json before evaluating trend, delta, and report-history completeness.
Snapshot readiness checks no longer undercount attached report context when a client or fixture returns raw BigQuery rows instead of the parsed history shape used by the API route.

Added focused history-readiness coverage proving raw BigQuery JSON fields produce full report-history readiness without leaking *_json, None, or N/A markers into the manifest.
Updated docs/architecture/CRYPTO_REPORTS.md and docs/reports/audits/2026-06-01_CRYPTO_REPORT_DATA_GAP_ANALYSIS.md. Public docs decision: no public documentation update is required because this is an internal report-history QA contract and does not change visible report claims, billing, scoring, audit coverage, legal claims, or investment guidance.