Nothing open on GitHub. Fix merged in #114904 on 18 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #114904. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #114904. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address cases where kanban run rows remain in a 'running' state incorrectly, including dead workers being inconsistently handled, rows missing worker PIDs, and rows not transitioning after a worker exits cleanly.
Open issues0
Open PRs0
Fixes on record
-
#114904 fix(kanban): a dead worker is booked the same way whichever dispatcher process notices it, and a tripped violation budget holds the card (#113611, #113610, salvage #113638)
files:
cli.py,hermes_cli/kanban_db.py,hermes_cli/kanban_db_dispatch.py,hermes_cli/quiet_single_query.py,tests/hermes_cli/test_kanban_worker_exit_trailer.py,website/docs/user-guide/features/kanban.md
1 PR closed without merging
From the close comments: other 1
-
#113632 fix(kanban): reclaim running rows that never recorded a worker PID · other →
#114904,#113632
Closed issues · 1
- Closed#113610[Bug]: kanban run row stays 'running' after a worker exits rc=0 with no terminal transition — classification is inconsistent across runs
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #114904
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 18 Sep 2026