CRYPTO-HISTORY-SNAPSHOT-DATE-ALIAS-NORMALIZATION (Report QA)

Release digest

CRYPTO-HISTORY-SNAPSHOT-DATE-ALIAS-NORMALIZATION (Report QA) — Crypto report history normalization now accepts supported snapshot timestamp aliases such as snapshotDate, date, observed_at, captured_at, collected_at, created_at, and updated_at before PDF trend and delta logic evaluates attached historical context.
PDF view-model trend, delta, and historical-context quality rows now count only dated snapshots as attached report history, so undated rows cannot create fake Trust Score movement, market movement, or current-vs-previous evidence deltas.

Added focused PDF view-model, route-normalizer, and history-readiness tests covering supported timestamp aliases and undated-history fallback behavior.
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 normalization contract and does not change visible report claims, billing, scoring, audit coverage, legal claims, or investment guidance.