Engagement audits must separate fresh action from inherited state

Reusable audit method: when correlating support with user engagement, inherited or copied submissions and prefilled draft-state markers must not count as fresh user actions. Report explicit views, fresh submissions/attempts, inbound messages, and connected-call proxies separately, then construct disjoint unions. An answered outbound call may contain a user reply, so call direction alone is insufficient; provider answered status is not proof of human speech. Keep ambiguous identity/linkage and missing ingestion visible instead of labelling unmatched cases inactive. Report logged support separately from communication evidence and causal necessity. Observed 2026-09-05 during a read-only theft/Shield driver-engagement audit; provenance is code-path inspection plus aggregate-method validation, with all private counts and identifiers omitted.