Release archive
3.2.223

CRYPTO-HISTORY-COMPARABLE-CONTEXT-DIAGNOSTICS (Report QA)

Release v3.2.223 focuses on CRYPTO-HISTORY-COMPARABLE-CONTEXT-DIAGNOSTICS (Report QA).

FixedInternal
CRYPTO-HISTORY-COMPARABLE-CONTEXT-DIAGNOSTICS (Report QA)

Release digest

Fixed

  • CRYPTO-HISTORY-COMPARABLE-CONTEXT-DIAGNOSTICS (Report QA) — Crypto history readiness manifests now separate report-context fields that are merely attached in at least one dated snapshot from fields that are comparable across the configured minimum snapshot count.
  • Added comparable_report_context_fields and missing_comparable_report_context_fields so report review can identify which historical fields still need repeated snapshots before they can support stronger evidence-backed trend or context reasoning.

Internal

  • Added focused history-readiness coverage for partially comparable snapshot context, proving a field can be attached without being comparable across the history window.
  • 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-readiness diagnostic and does not change visible report output, billing, scoring, audit coverage, legal claims, or investment guidance.

Technical notes