Release digest
Fixed
- CRYPTO-SECURITY-ASSESSMENT-EVIDENCE-ALIASES (Report Logic) — Crypto
project normalization now recognizes security-assessment and finding-count
payload shapes such as
security_assessments,security.assessments,assessment_title,vendor,assessor,findings,issue_count,resolved_findings,unresolved_findings,reviewed_at,assessed_at,report_link,remediation_state, andfix_status.
Internal
- Added focused coverage proving assessment/finding payloads normalize into
reviewer-safe
security_evidencerows with label, provider, safe finding-count scope, date, remediation, and URL context while keeping raw finding text out of PDF-facing view-model rows. - Updated
docs/architecture/CRYPTO_REPORTS.mdanddocs/reports/audits/2026-06-01_CRYPTO_REPORT_DATA_GAP_ANALYSIS.mdbecause this expands the internal security-evidence normalization contract. Public docs decision: no public documentation change is required because this only expands accepted attached evidence shapes and does not change downloadable PDF behavior, billing, audit coverage, safety language, legal claims, or investment guidance.