Description

When a scheduled prompt (via /every or /after) fires, it appears to kill the existing prompt queue. If there are N items queued up and a scheduled prompt triggers, the agent processes the scheduled prompt but does not pop the next item from the queue afterward. The queue remains stalled until the schedule time comes up again (which could be hours or days away).

Steps to Reproduce

1. Start an interactive Copilot CLI session with experimental mode enabled
2. Queue up multiple tasks (e.g., submit 5+ prompts or use the inbox/queue)
3. While the agent is processing items from the queue, trigger a scheduled prompt (/every or /after)
4. After the scheduled prompt completes, observe that the agent does not pop the next item from the queue

Expected Behavior

After a scheduled prompt completes, the agent should resume processing the existing queue (pop the next item).

Actual Behavior

The agent stops after completing the scheduled prompt. The queue is effectively frozen until the next scheduled time (which could be hours or days away).

Additional Context

This might be intentional (to allow the scheduled prompt to run mid-task), but the current behavior stalls the queue for an extended period.