Release archive
3.2.212

CRYPTO-HISTORY-READINESS-NEXT-ACTION (Report Logic)

Release v3.2.212 focuses on CRYPTO-HISTORY-READINESS-NEXT-ACTION (Report Logic).

FixedInternal
CRYPTO-HISTORY-READINESS-NEXT-ACTION (Report Logic)

Release digest

Fixed

  • CRYPTO-HISTORY-READINESS-NEXT-ACTION (Report Logic) — The crypto history readiness checker now writes readiness_level and next_action into its JSON manifest for every checked slug.
  • History readiness output now distinguishes trend-and-delta-ready, delta-only, not-ready, and infrastructure-unavailable states so report-derived planning can decide whether to wait for snapshots, attach comparable fields, or repair BigQuery access.

Internal

  • Updated history-readiness regression coverage for passed, failed, and skipped manifests, including local BigQuery-unavailable output.
  • Updated docs/architecture/CRYPTO_REPORTS.md and docs/reports/audits/2026-06-01_CRYPTO_REPORT_DATA_GAP_ANALYSIS.md to document the new history-readiness manifest fields. Public docs decision: no public documentation change is required because this is internal QA/planning metadata and does not change downloadable PDF behavior, billing, audit coverage, safety language, legal claims, or investment guidance.

Technical notes