Upgrade Slack fast mode orchestration

[mrubens]

Summary

• handle !fast before normal Slack task routing and keep subsequent thread replies in the same fast conversation
• let fast mode answer directly, launch or manage Roomote agent tasks, and use approved deployment-wide MCP integrations
• keep delegated task questions, progress updates, and closeout messages in the originating Slack thread
• isolate fast sessions and locks by Slack workspace, channel, and thread
• cache MCP tool discovery while rejecting local, custom, credential-only, and unsupported integrations

Why

Slack fast mode behaved like a one-shot routing shortcut. Conversational replies could fall back into task routing, acknowledgements could be forwarded unnecessarily to active tasks, and every turn rediscovered MCP tools. This makes fast mode own the conversation while preserving the existing Roomote task lifecycle for work that genuinely needs execution.

User impact

Users can start a lightweight conversation with !fast, continue naturally in its Slack thread, get direct answers without task-processing reactions, and delegate work only when appropriate. Fast mode can use deployment integrations without receiving filesystem, shell, local transport, or arbitrary network access.

Validation

• 123 focused tests across fast-mode orchestration, deployment MCP authorization, Slack routing, and Slack task launching
• pnpm lint:fast
• pnpm check-types:fast
• pnpm knip
• changed-file ESLint and git diff --check
• mock Slack app-mention and unmentioned thread-continuation scenario, confirming direct replies, no reactions, no task launch, and workspace-scoped session persistence

[roomote-community]

1 issue outstanding. See task

• Restrict fast-mode integrations to read-only or explicitly approved tools.
• Enforce the active-task rule for launch_task decisions.
• Fix the new unmentioned-routing test's default timeout failure.

_{Reviewed 4861530}

[roomote-community]

This exposes every tool returned by a deployment integration to a direct fast-mode turn, including mutation tools. For example, the enabled Notion endpoint advertises notion-create-pages, notion-update-page (including in_trash), and notion-append-blocks; the decision service will execute any discovered name without task delegation or confirmation. Filter this surface to read-only tools (or use an explicit fast-mode allowlist) before adding it to the model prompt.