Check Slack channel reads after token revocation

Verify Slack bot membership again after revoking app tokens

Revoking all tokens for a Slack app can invalidate the installed bot's effective channel access even when reinstalling yields the same bot user ID and requested scopes. A fresh auth.test success does not establish channel reads. After credential rotation, test conversations.history on representative public and private channels, restore missing memberships, then rerun bounded reconciliation before declaring the collector healthy. Existing database coverage timestamps can remain green from the prior credential, so require a post-rotation read and successful reconcile timestamp. This is a rotation-specific check, not a general claim that every reinstall removes membership.

Applies when: Rotating or revoking a Slack bot credential used by a channel collector. Keywords: Slack bot token revoke reinstall channel membership not_in_channel private history reconcile