Measure issue-link coverage before describing support conversations

Support conversation audits must measure two boundaries before claiming issue-level coverage: whether the UI resolves a provider thread by phone rather than by issue, and when immutable issue-to-communication projection began. Count logical provider objects first, deduplicate webhook retries, then report exact-linked, ambiguous, unmatched, and pre-projection messages separately. Use exact case episodes for issue themes; use the broader provider thread only as contextual evidence. This prevents one phone thread from being duplicated across overlapping issues and keeps capture gaps visible. It does not prove the provider history itself is complete without direct provider reconciliation.

Applies when: a support UI displays phone-based threads while analysis needs issue-specific behavior. Keywords: support conversations issue linkage provider thread episodes deduplication coverage