CRYPTO-SNAPSHOT-REPORT-CONTEXT-NORMALIZATION (History Storage)

Release digest

CRYPTO-SNAPSHOT-REPORT-CONTEXT-NORMALIZATION (History Storage) — Daily BigQuery crypto snapshot rows now normalize project payloads before serializing report-context JSON, preserving alias and camelCase security, contract/source, and admin-control evidence as canonical history fields.
Explicit canonical report-context fields already attached to the project payload remain authoritative, so snapshot normalization does not overwrite current data_completeness, section_sources, section_freshness, surface_contract, security_evidence, contract_addresses, source_links, or admin_controls values.

Added BigQuery snapshot contract coverage proving alias/camelCase evidence is serialized into canonical report-history JSON without preserving raw camelCase field names.
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 history-storage improvement and does not change visible report copy, billing, scoring, audit coverage, legal claims, or investment guidance.