Release archive
3.2.183

CRYPTO-HISTORY-SNAPSHOT-NORMALIZATION (Report Logic)

Release v3.2.183 focuses on CRYPTO-HISTORY-SNAPSHOT-NORMALIZATION (Report Logic).

FixedInternal
CRYPTO-HISTORY-SNAPSHOT-NORMALIZATION (Report Logic)

Release digest

Fixed

  • CRYPTO-HISTORY-SNAPSHOT-NORMALIZATION (Report Logic) — Crypto report history rows now preserve the project slug, serialize date/Decimal values, expose legacy BigQuery score columns as previous score_breakdown context, and derive conservative data_completeness metadata from positive attached snapshot values only. This makes historical delta sections more useful when prior snapshots exist without counting zero-valued legacy metrics as attached coverage evidence.

Internal

  • Added report-route coverage for normalized BigQuery history rows and focused coverage proving zero-valued legacy snapshot metrics do not become attached evidence.
  • Updated docs/architecture/CRYPTO_REPORTS.md and knowledge-base/docs/crypto/dashboard-ui.md because this changes historical snapshot behavior in downloadable crypto PDFs. Public-docs decision: user-facing crypto docs now explain that historical coverage metadata is derived only from attached positive snapshot values and does not invent movement from missing or zero legacy metrics.

Technical notes