CRYPTO-EVIDENCE-CAMELCASE-ALIASES (Report Logic)

Release digest

CRYPTO-EVIDENCE-CAMELCASE-ALIASES (Report Logic) — Crypto project normalization now accepts camelCase contract/source and security-evidence payloads such as deployedContracts, sourceVerification, contractAddress, verifiedSourceUrl, securityEvidence, auditReports, reportTitle, auditFirm, coveredContracts, and remediationStatus.
Downloadable report view models can use those normalized rows to reduce false Contract/source canonicalization and Security evidence depth gaps when attached evidence arrives from explorer, forensics, or API-style payloads.

Added normalizer and PDF view-model regression coverage proving camelCase contract/source and security-evidence aliases normalize into reviewer-safe fields without rendering raw contract addresses, raw source URLs, or raw camelCase field names in report-facing rows.
Updated docs/architecture/CRYPTO_REPORTS.md, docs/reports/audits/2026-06-01_CRYPTO_REPORT_DATA_GAP_ANALYSIS.md, and knowledge-base/docs/crypto/dashboard-ui.md to document camelCase contract/source and security-evidence alias support. Public docs decision: public crypto docs were updated because visible downloadable PDF attached-state semantics changed; no safety, audit-completion, legal, billing, or investment claims were added.