Release archive
3.2.248

CRYPTO-SECURITY-EVIDENCE-COVERAGE-COUNTS (PDF Reports)

Release v3.2.248 focuses on CRYPTO-SECURITY-EVIDENCE-COVERAGE-COUNTS (PDF Reports).

AddedInternal
CRYPTO-SECURITY-EVIDENCE-COVERAGE-COUNTS (PDF Reports)

Release digest

Added

  • CRYPTO-SECURITY-EVIDENCE-COVERAGE-COUNTS (PDF Reports) — Crypto security evidence normalization now preserves sanitized covered_contract_count and finding_count metadata when source payloads attach covered-contract lists or finding counts.
  • The PDF Security Evidence Details table now includes a Coverage column so reviewers can distinguish attached coverage counts from missing coverage detail without exposing raw contract addresses, raw finding text, or raw evidence URLs.

Internal

  • Extended backend payload-normalizer, PDF view-model, generated-PDF, and regression-pack tests to prove security coverage counts render safely and do not introduce raw addresses, URLs, unsafe audit claims, or investment copy.
  • 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 refines internal report evidence depth and PDF reviewer detail without adding a new public feature, billing behavior, scoring claim, audit coverage claim, legal claim, or investment guidance.

Technical notes