[Refactor] Consolidate Fast tools on Roomote MCP

[roomote-roomote]

​Opened on behalf of @daniel-lxs. Follow up by mentioning @roomote-roomote or in the web UI.

What changed

Removed Fast-native manage_tasks, get_chat_message_context, and get_chat_channel_messages. Fast now routes task inspection and chat-context requests through integration_call to the actor-authorized Roomote MCP catalog introduced in #1604.

Native tools with Fast-specific orchestration or visibility semantics remain unchanged: task launch/message/cancel, chat replies/reactions, event retry/ignore, and integration_call. Fast injects its Slack or Discord conversation provider into Roomote MCP chat lookups and defaults omitted channels to the active conversation target. Slack uses the current channel, while Discord uses the current thread when present. Slack channel history still defaults to the previous 24 hours when oldest is omitted.

Fast also accepts the shared all-repositories target for delegated launches. Discord treats that sentinel as the existing deployment-wide workspace target instead of attempting to resolve it as a configured environment.

Why this change was made

Fast previously maintained parallel native contracts for capabilities now exposed by the Roomote MCP. Consolidating them avoids duplicated schemas, authorization paths, and tests while preserving the scoped current-conversation behavior of the removed chat adapters.

Impact

Fast retains task inspection and chat-context capabilities through the Roomote MCP, using the same actor-resolved catalog as delegated tasks. Chat lookups without an explicit channel continue to target the active Slack channel or Discord thread, while explicit channel references and message links remain supported. Explicit all-repositories launches work consistently from Slack and Discord. The native surface is smaller and has one source of truth for shared deployment operations.

Related PRs

• #1613: Expose deployment MCP tools directly in Fast

[roomote-community]

No code issues found. See task

• Chat lookups through integration_call no longer receive the Fast conversation provider, so raw channel IDs fail. (packages/cloud-agents/src/server/fast-agent/fast-agent-service.ts:913)
• Fast chat lookups no longer default to the current conversation channel, so calls without an explicit channel fail. (packages/cloud-agents/src/server/fast-agent/fast-agent-service.ts:938)
• Advertising the all-repositories target breaks Fast launches from Discord because the sentinel is resolved as a concrete environment. (apps/api/src/handlers/discord/fast-agent.ts:141)

_{Reviewed 0b3fbe0}

[roomote-roomote]

Fixed in 0b3fbe0f: Discord Fast launches now treat __all_repositories__ as the deployment-wide workspace target instead of resolving it as a concrete environment. Added a focused adapter regression test; related Fast launch tests, affected package typechecks, and the full pre-push gate pass.