CRYPTO-HISTORY-CAMELCASE-SNAPSHOT-ALIASES (PDF Reports)

Release digest

CRYPTO-HISTORY-CAMELCASE-SNAPSHOT-ALIASES (PDF Reports) — Crypto report history normalization now canonicalizes camelCase snapshot fields such as trustScore, priceUsd, dataCompleteness, sectionSources, sectionFreshness, surfaceContract, securityEvidence, contractAddresses, sourceLinks, and adminControls before PDF and history-readiness evaluation.
History readiness checks now count attached report-context fields regardless of whether fixture/client rows arrive in BigQuery JSON, snake_case, or camelCase report-payload shape, while preserving missing-history behavior for projects with no attached snapshots.

Added focused route-normalizer and history-readiness tests proving camelCase report-context aliases become canonical PDF/history fields without rendering None, N/A, or fake zero evidence.
Updated docs/architecture/CRYPTO_REPORTS.md and knowledge-base/docs/crypto/dashboard-ui.md. Public docs decision: document the accepted attached-history payload shape because this affects report data interpretation, while avoiding audit, safety, billing, legal, or investment claims.