CRYPTO-SECURITY-DATA-ROOM-EVIDENCE-NORMALIZATION (Report QA)

Release digest

CRYPTO-SECURITY-DATA-ROOM-EVIDENCE-NORMALIZATION (Report QA) — Crypto project payload normalization now accepts security data-room and readiness packet aliases such as securityDataRoom, security_data_room, securityPacket, securityDocuments, readiness.securityEvidence, and nested security.documents.
These aliases normalize into reviewer-safe security_evidence rows when label, provider, scope, date, or remediation context is attached, without rendering raw evidence URLs or raw alias names in PDF view-model rows.

Added focused normalizer and PDF view-model tests proving security data-room packets clear false Security evidence depth gaps only when reviewable context is attached.
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 evidence-normalization contract and does not change visible report claims, billing, scoring, audit coverage, legal claims, or investment guidance.