Scheduled sessions fail when no repos are defined

[quay-devel]

Bug

Scheduled sessions fail with WorkflowReconciled: UpdateFailed when no repositories are defined in the session spec. Regular (non-scheduled) sessions can be created and run without repos, so scheduled sessions should support this too.

Reproduction

1. Create a scheduled session with a workflow but no repos:
   • Workflow: quay/ai-helpers.git → workflows/notification-router
   • Model: claude-sonnet-4-6
   • Schedule: */10 9-17 * * 1-5
   • No repos defined
2. Wait for the schedule to trigger a session
3. Session creates but workflow reconciliation fails

Observed behavior

Session notif-router-1778095302 was created at 2026-05-06T19:21:42Z by the scheduler. Two conditions show the problem:

ReposReconciled:
  status: "True"
  reason: "NoRepos"
  message: "No repositories defined"

WorkflowReconciled:
  status: "False"
  reason: "UpdateFailed"
  message: "Failed to notify runner: Post \"http://session-notif-router-1778095302.quay.svc.cluster.local:8001/workflow\": dial tcp: lookup session-notif-router-1778095302.quay.svc.cluster.local on 172.30.0.10:53: no such host"

The DNS lookup for the runner pod failed, suggesting the pod either didn't start or wasn't ready when the workflow notification was sent.

Expected behavior

Scheduled sessions with no repos should behave the same as manually created sessions with no repos — the agent starts, the workflow loads, and the agent can use MCP tools / gh CLI with the ambient GITHUB_TOKEN.

Context

• Scheduled session name: notif-router-1778095302
• Schedule label: ambient-code.io/scheduled-session-name: schedule-44db4fbf-2627-4016-ad2f-35ba4abbe6c0
• Workflow: quay/ai-helpers.git, branch main, path workflows/notification-router
• The workflow only needs gh CLI and ACP MCP tools — no repo checkout required