CRYPTO-CONTRACT-REGISTRY-SOURCE-ALIAS-NORMALIZATION (Report QA)

Release digest

CRYPTO-CONTRACT-REGISTRY-SOURCE-ALIAS-NORMALIZATION (Report QA) — Crypto project payload normalization now accepts contract registry, verified-deployment, and source-repository packet aliases such as contractRegistry, contract_registry, verifiedDeployments, verified_deployments, sourceRepositories, and source_repositories.
These aliases normalize into reviewer-safe contract_addresses and source_links rows while keeping raw contract addresses, repository URLs, explorer URLs, and raw source field names out of PDF view-model rows.

Added focused normalizer and report view-model tests for contract registry, verified deployment, and source repository aliases.
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 normalization contract and does not change visible PDF output, billing, scoring, audit coverage, legal claims, or investment guidance.