Cairn
NousResearch/hermes-agent

Kanban 'completed' status handling in dependency checks

Cluster 31717 · dashboard. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

The members concern Kanban task status handling: one reports that approval comments do not resume work and that a 'completed' status does not satisfy dependencies. The other two are fix PRs, one accepting 'completed' as a terminal status in dependency checks and one normalizing legacy 'completed' status.

Open issues1

  • Issue#31717Kanban approval comments do not resume work; completed status does not satisfy dependencies

Open PRs1

  • PR#31765fix(kanban): accept 'completed' as terminal status in dependency checks

1 PR closed without merging

From the close comments: other 1

  • #31767 fix(kanban): normalize legacy completed task status · other → #31717, #31765
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.00 means 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 Lab

At a glance

Subsystem
dashboard
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/31717.json
cluster/31717.md