fix(loop-scheduler): reset agentBusy when drainPending detects idle context

The agentBusy flag could get stuck if an agent_start event fired but no
matching agent_end followed (e.g. crash or forced shutdown).  The
scheduler would then show 'pending' forever even though the agent was
completely idle.

Now drainPendingJobs() and drainPendingWatchJobs() ask the ExtensionContext's
isIdle() as a ground-truth fallback whenever agentBusy is true.  If the
context reports idle, we reset agentBusy = false and proceed to dispatch
pending jobs instead of bailing out.

0 files changed, 0 insertions, 0 deletions