Release archive
3.2.242

CRYPTO-SNAPSHOT-NORMALIZED-CONTEXT-PERSISTENCE (Report QA)

Release v3.2.242 focuses on CRYPTO-SNAPSHOT-NORMALIZED-CONTEXT-PERSISTENCE (Report QA).

FixedInternal
CRYPTO-SNAPSHOT-NORMALIZED-CONTEXT-PERSISTENCE (Report QA)

Release digest

Fixed

  • CRYPTO-SNAPSHOT-NORMALIZED-CONTEXT-PERSISTENCE (Report QA) — Daily crypto BigQuery snapshot rows now prefer normalized, merged report-facing context over stale shallow canonical fields before serializing historical security_evidence, contract_addresses, source_links, and admin_controls.
  • Snapshot export still falls back to attached raw report-context fields when normalization leaves a field empty, and preserves raw section_freshness dates when the normalized shell lacks freshness timestamps.

Internal

  • Added focused daily snapshot coverage proving canonical and wrapper evidence are merged into stable history JSON without leaking raw wrapper keys or dropping existing canonical context.
  • 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 snapshot/history persistence contract and does not change visible report claims, billing, scoring, audit coverage, legal claims, or investment guidance.

Technical notes