Kanban dependency block routing edge cases

NousResearch/hermes-agent · cluster 129486 · cron

Data as of

3 open items. Fix attempted, not merged.

The short answer

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

These issues and fixes address edge cases in how dependency classifications are routed or promoted in the kanban system, specifically for cards that are already blocked, running in-place, or parked.

Open issues1

  • Issue#129486kanban block --kind dependency on an already-blocked card leaves a sticky, never-promoted dependency block

Open PRs2

  • PR#129495fix(kanban): route dependency classification for parked cards
  • PR#129503fix(kanban): route an in-place dependency classification like the running path
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
cron
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.