CCR scheduled triggers: claude.ai MCP connectors not available in remote session

Description

When a scheduled CCR trigger has mcp_connections configured with claude.ai OAuth connectors (Atlassian, Slack, Gmail), the MCP tools are not available in the remote session's tool registry. The agent cannot find them via ToolSearch and reports them as not connected.

What's Wrong?

The tools don't appear in the deferred tool registry. The remote agent reports:

"The required MCP tools (mcp__claude_ai_Atlassian, mcp__claude_ai_Slack, mcp__claude_ai_Gmail) are not available in this environment — they don't appear in the deferred tool registry."

What Should Happen?

MCP tools from connectors configured in mcp_connections should be available in the remote CCR session's deferred tool registry, allowing the agent to call them via ToolSearch and use them normally.

Steps to Reproduce

1. Create a scheduled trigger at claude.ai/code/scheduled with claude.ai MCP connectors attached (e.g., Atlassian, Slack, Gmail)
2. Run the trigger via the run API or wait for it to fire on schedule
3. In the remote CCR session, the agent attempts to use MCP tools (e.g., mcp__claude_ai_Atlassian__searchJiraIssuesUsingJql)
4. The tools are not found — they don't appear in the deferred tool registry via ToolSearch

Additional Context

• Trigger ID: trig_01SuHNpZRr2LST3wBfnLvgHy
• Connectors configured: Atlassian, Slack, Gmail (all visible in trigger UI at claude.ai/code/scheduled)
• Regression: The trigger worked correctly on 2026-03-31 and started failing on 2026-04-01
• Environment: Default CCR environment
• Claude Code Version: 2.1.89 (Claude Code)
• OS: macOS