[BUG] Cloud routines (remote_trigger) never load MCP connector tools — all connectors enabledInChat:false on 2.1.199 (regression of #35899)

Summary

In a cloud routine (scheduled / remote-triggered CCR session), attached MCP connectors are never injected as tools. ListConnectors reports every connector as connected: true but enabledInChat: false, and ToolSearch for slack/mcp returns zero mcp__* tools. This is the same failure mode fixed for scheduled tasks in #35899 (v2.1.101), now recurring at the remote_trigger entrypoint on a current build.

Environment

• Claude Code 2.1.199 (claude --version), Node 22, Ubuntu 24.04
• CLAUDE_CODE_ENTRYPOINT=remote_trigger
• CLAUDE_CODE_REMOTE_ENVIRONMENT_TYPE=cloud_default
• Model: claude-sonnet-4-6; routine created and fired via the routines API, and re-tested via the web UI.

Steps to reproduce

1. Create a routine with one or more claude.ai connectors attached (they also auto-attach from the environment default).
2. Fire it (Run now or on schedule).
3. From the routine prompt, run ListConnectors and ToolSearch for slack and mcp.

Actual behavior

• ListConnectors: all connectors connected: true, every one enabledInChat: false.
• ToolSearch 'slack' → no deferred tools. ToolSearch 'mcp' → only SearchMcpRegistry / ListConnectors / SuggestConnectors / WebFetch; zero mcp__* connector tools.
• The subagent-dispatch workaround from #35899 / #43397 does not work: a spawned subagent sees the same zero mcp__* tools. Neither the top-level session nor the subagent receives any connector tools.
• Toggling a connector on in the routine's Connectors tab in the web UI does not help — after explicitly enabling it there and re-running, ListConnectors still reports enabledInChat: false and no tools load.

Expected behavior

Connectors attached to a routine should have their tools loaded into the autonomous session (per the routines docs, all connected connectors are included by default), without requiring an interactive message to warm the session.

Impact

Any unattended routine that depends on a connector (e.g. Slack, Gmail, Google Drive) is non-functional — the agent sees no connector tools and cannot act. The previously documented subagent workaround no longer mitigates it, and there is no per-session mechanism to set enabledInChat: true in a routine.

Related (same class, other entrypoints)

• #35899 — fixed in v2.1.101; this appears to be a regression at the routine entrypoint.
• #43397 — closed as duplicate of #35899.
• Currently open at other entrypoints: #73081 (VS Code extension), #72914 (CLI), #67432 (desktop spawn_task).