CRYPTO-REPORT-EVIDENCE-READINESS-HARDENING (Report Logic) & CRYPTO-HISTORY-READINESS-INFRA-SKIP (Report Logic)

Release digest

CRYPTO-REPORT-EVIDENCE-READINESS-HARDENING (Report Logic) — Crypto project normalization now recognizes singular audit payload objects such as audit, audit_report, security.audit, and security.audit_report, including fields like report_title, audit_firm, audited_by, audit_scope, findings_summary, and report_published_at.
CRYPTO-HISTORY-READINESS-INFRA-SKIP (Report Logic) — The crypto history readiness checker now reports skipped instead of failed when the BigQuery client or query path is unavailable, keeping local QA distinct from real thin-history findings.

Added focused coverage proving singular audit objects normalize into reviewer-safe security_evidence rows with label, provider, scope, date, and report URL context while keeping the PDF/report contract legally bounded.
Added focused coverage proving history readiness skips are explicit and do not become false report-data failures when BigQuery infrastructure is unavailable.
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 because this expands the report-facing security-evidence normalization contract and hardens the internal history-readiness gate. Public-docs decision: user-facing crypto docs now mention singular audit objects as accepted evidence shapes without claiming audit completion, vulnerability clearance, verified safety, legal assurance, or investment suitability. No public docs change is required for the history-readiness skip behavior because it is internal QA tooling only.