NousResearch/hermes-agent

Kanban: recover done tasks from protocol-violation blocks

Cluster 60802 · cron. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
5items grouped
Known?
Yes. 5 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 3 PRs 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.

Multiple fixes and iterations addressing recovery of completed tasks that become stuck in protocol-violation blocks, using task_runs history. Also includes related headless worker and re-queue respawn improvements.

Open issues1

  • Issue#60802fix(kanban): recover done tasks from protocol-violation blocks via task_runs history

Open PRs1

  • PR#60825fix(kanban): restore done tasks after protocol violations

3 PRs closed without merging

From the close comments: duplicate 2 · superseded by another PR 1

  • #60833 fix(kanban): recover done tasks from protocol-violation blocks via task_runs history · superseded by another PR → #60843, #60802
  • #60843 fix(kanban): recover done tasks from protocol-violation blocks via task_runs history (#60802) · duplicate → #60833, #60825
  • #60949 fix(kanban): recover done tasks from protocol-violation blocks via task_runs history · duplicate → #60843, #60893
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.40: 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
3 PRs closed without merging

For your agent

The same facts, typed.