Release archive
3.2.222

CRYPTO-REPORT-DATA-ACQUISITION-PLAN (Report Planning)

Release v3.2.222 focuses on CRYPTO-REPORT-DATA-ACQUISITION-PLAN (Report Planning).

FixedInternal
CRYPTO-REPORT-DATA-ACQUISITION-PLAN (Report Planning)

Release digest

Fixed

  • CRYPTO-REPORT-DATA-ACQUISITION-PLAN (Report Planning) — The crypto report data-gap analyzer now emits a flattened top-level data_acquisition_plan and a per-case data_acquisition_plan so PDF review can directly identify which data harvester, normalizer, or history-storage slice should close each report-derived gap.
  • Data acquisition plan rows include stable case task ids, priority, product logic layer, gap type, current gap copy, next attachment, minimum fields, accepted payload shapes, verification command, done-state, and a legal-safe boundary.

Internal

  • Extended the crypto PDF regression-pack analyzer contract test to prove ready cases produce no acquisition tasks while thin-data and tokenless cases produce actionable, typed acquisition tasks.
  • 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 planning contract and does not change visible report output, billing, scoring, audit coverage, legal claims, or investment guidance.

Technical notes