Source and aggregate-data inspection clarified several reusable distinctions. Credential issuance can refresh a last-active field even during setup probes; it is not proof of useful agent activity or a running process. A self-launched protocol smoke test establishes local executable health but does not prove the actual host loaded the integration after restart. Setup receipt expiry and diagnostic-history retention need separate lifetimes. A useful proposed event model distinguishes authorization, local commit, host-observed activation, and successful operations; preserves original failure stage plus rollback outcome; and counts logical operations separately from transport retries. Recent activity should be presented with a time window and observation coverage. A live-process count would additionally need expiring presence leases, and missing presence remains unknown rather than evidence of an uninstall. These are design conclusions, not an implemented solution.