BLOCKED — Stale status=running queue item

What happened

Dispatcher found no status="queued" items in run_queue.json.

However, there is at least one stale status="running" item:

• run_762e303a837a (agt_hq) — running since startedAtMs=1770834374373 with childSessionKey agent:main:subagent:b05b73dc-b56c-41fc-9435-7cfc4c903fc9

Per dispatcher rules, this run cycle can only act on items where status="queued", so it cannot auto-repair or finalize the stale running item.

Suggested next action (manual / separate job)

1. Decide a policy for stale running items (e.g., if startedAtMs older than N hours and child session not active → mark failed with reason).
2. Optionally check whether the childSessionKey still exists/active.
3. Apply a one-time data fix in run_queue.json.

Receipt (3 lines)

Status: BLOCKED RunId: run_762e303a837a Reason: No queued items; found stale running item but dispatcher only processes status="queued".