Scheduled tasks created over MCP hardcode baseRef "main", breaking repos whose default branch isn't main #17574

Summary

Scheduled tasks created or updated through the orchestrator MCP that are not bound to a thread always get a worktree strategy with baseRef: "main". In repositories whose default branch is something else (e.g. trunk, master, develop), each scheduled run will try to branch from a ref that doesn't exist and fail.

Where

apps/server/src/mcp/OrchestratorMcpService.ts (on main at 91a6646ef, around line 233):

function scheduledTaskWorkspaceStrategy(
  boundToThread: boolean,
): ScheduledTask["workspaceStrategy"] {
  return boundToThread
    ? { type: "root" }
    : { type: "worktree", baseRef: "main", startFromOrigin: true };
}

Expected

Unbound scheduled runs should branch from the project's actual default branch (e.g. resolved from origin/HEAD), or accept a caller-supplied baseRef the same way t3_thread_launch's workspaceStrategy does. Normal t3_thread_launch with an explicit baseRef isn't affected.

Repro

1. Have a project whose remote default branch is not main (e.g. trunk, no main branch).
2. Over the MCP, create a scheduled task that isn't bound to a thread.
3. When it runs, the worktree is created from main, which doesn't exist.

This issue was filed by Grok Bot.