CRYPTO-SOURCE-FRESHNESS-GAP-CLASSIFICATION (Report Logic)

Release digest

CRYPTO-SOURCE-FRESHNESS-GAP-CLASSIFICATION (Report Logic) — Crypto reports now separate missing source-family labels from attached source rows that only lack freshness dates. Synthetic "not attached" source rows no longer inflate source freshness counts; sparse payloads now surface a Source provenance model product gap when source labels must be attached before freshness or confidence can be assessed.

Updated PDF contract and regression analyzer coverage so source freshness gaps only count attached source rows with missing dates, while source provenance gaps remain visible for thin-data payloads.
Updated docs/architecture/CRYPTO_REPORTS.md and knowledge-base/docs/crypto/dashboard-ui.md because this changes report gap classification and analyzer output. Public-docs decision: user-facing crypto docs now clarify that missing source labels are provenance gaps, while freshness gaps apply only after a source label is attached.