Kanban blocked status lost on board reads
Cluster 109260 · hermes cli. Data as of
1 open item. Fix merged in #109334 on 13 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 #109334. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #109334. That is separate from the fix event. - Still open
- 0 issues and 1 PR.
A bug where cards set to blocked status are incorrectly promoted back to an unblocked state whenever the board is read, without requiring a dispatcher tick. The members address preserving the blocked/initial-status gate through board reads and dispatcher cycles.
Open issues0
Open PRs1
- PR#109378fix(kanban): preserve blocked state during board reads
Fixes on record
-
#109334 fix(kanban): initial_status=blocked gates survive board reads and dispatcher ticks (#109260, salvage #108170)
files:
hermes_cli/kanban_db.py,tests/hermes_cli/test_kanban_blocked_sticky.py
Closed issues · 1
- Closed#109260[Bug]: kanban `--initial-status blocked` is undone by any board read — `hermes kanban list` promotes the card in ~1 s, no dispatcher tick needed
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
- Subsystem
- hermes cli
- Merged PRs
- #109334
- Closed issues
- 1
- Attempts
- 0 PRs closed without merging
- Fix link checked
- 13 Sep 2026