Release archive
3.2.244

CRYPTO-REPORT-GAP-PARTIAL-EVIDENCE-CLASSIFICATION (Report QA)

Release v3.2.244 focuses on CRYPTO-REPORT-GAP-PARTIAL-EVIDENCE-CLASSIFICATION (Report QA).

FixedInternal
CRYPTO-REPORT-GAP-PARTIAL-EVIDENCE-CLASSIFICATION (Report QA)

Release digest

Fixed

  • CRYPTO-REPORT-GAP-PARTIAL-EVIDENCE-CLASSIFICATION (Report QA) — The crypto report data-gap analyzer now classifies attached-but-incomplete security evidence as partial_payload_evidence instead of fully missing payload evidence.
  • Security gaps that only say evidence is not attached in Vartovii data remain missing_payload_evidence, preserving the distinction between no attached proof and shallow attached proof.

Internal

  • Added focused analyzer coverage for security provenance copy that contains an attached source label but lacks audit scope, provider, freshness, or remediation details.
  • 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 changes internal report-gap classification for planning and does not change downloadable PDF sections, billing, scoring, audit coverage, legal claims, or investment guidance.

Technical notes