[Docs] Clarify automation output destinations

[roomote-community]

Created by Roomote. Follow up by mentioning @roomote, in the web UI, or in Discord.

What changed

• Updated the Automations guide to describe Automation output as a shared Slack or Discord Manager Channel.
• Clarified that fallback selection runs only when Slack is disconnected and either no destination is saved or the saved destination is Slack, then documented the Teams, Telegram, and Discord order.

Why this change was made

The public guide still described Automation output as Slack-only after Discord became a supported Manager Channel destination.

Impact

Operators now see the current destination choices and understand that disconnecting Slack can reroute reports from a saved Slack destination.

Screenshots

The rendered guide limits fallback selection to no saved destination or a saved Slack destination, then shows the Teams, Telegram, and Discord order.

[roomote-community]

No code issues found. See task

• apps/docs/automations.mdx:167 The fallback is not limited to an unset Manager Channel: resolveAutomationRuntimeDestination discards a saved Slack destination once Slack disconnects, then falls through to Teams, Telegram, or Discord. Document the condition in terms of no usable non-Slack destination so operators understand that disconnecting Slack still reroutes reports.
• apps/docs/automations.mdx:168 The new condition promised a primary-conversation fallback whenever no usable non-Slack destination resolved, but a saved Teams destination without a resolvable serviceUrl returns null immediately in resolveAutomationRuntimeDestination and never reaches that fallback. The wording now correctly limits fallback selection to no saved destination or a saved Slack destination after Slack disconnects.

_{Reviewed da618a2}

[roomote-community]

Fixed in da618a2. The guide now limits fallback selection to the two branches that actually fall through: no saved destination, or a saved Slack destination when Slack is disconnected. It no longer implies that an unusable saved Teams destination falls through. Docs validation passed, and the PR description contains refreshed visual proof.