v0.8.1

Fix: Missing user token scopes for channel resolver

The channel resolver queries all conversation types (public_channel, private_channel, im, mpim) but the user token manifest only had channels:read. This caused missing_scope errors during channel name resolution, triggering the bot-fallback unnecessarily.

Changes

• Added groups:read, im:read, mpim:read to user token scopes in app manifest
• Updated slackbuzz doctor to probe all conversation types (matching the resolver's actual query)

After upgrading

If you created your Slack app before v0.8.1, re-install with updated scopes:

slackbuzz app create    # Creates app with all required scopes
slackbuzz auth login    # Paste the new tokens
slackbuzz doctor        # Verify everything passes