# NousResearch/hermes-agent · Kanban stale failure error and respawn guard handling

## Open now

- 1 issue, 1 PR open on GitHub.
- #121281: kanban: a manual \`blocked\` → \`ready\` promote keeps the stale \`last_failure_error\`, and \`blocker_auth\` parks the card forever
- PR #121292: fix(kanban): clear stale failure error on manual promote

These members concern kanban cards where a manual blocked-to-ready promote retains a stale last_failure_error, and where blocker_auth is described as parking the card. Two items propose changes: clearing the stale error on promote and basing the respawn guard on run outcomes rather than error text.

## TL;DR

- 3 member(s): 1 open issue(s), 0 closed issue(s), 1 open PR(s), 0 merged PR(s), 1 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Open related issues

- #121281: kanban: a manual \`blocked\` → \`ready\` promote keeps the stale \`last_failure_error\`, and \`blocker_auth\` parks the card forever

## Prior & competing PRs

- **#121292: fix(kanban): clear stale failure error on manual promote**. open
  - maintainer direction: category `stale_abandoned`; implication `active`; refs `a510d6c64a61582688133b5f54c8191e190a1f49`
  - files: `hermes_cli/kanban_db.py`, `tests/hermes_cli/test_kanban_db.py`
- **#142737: fix(kanban): respawn guard decides from run outcomes, never from error prose**. closed without merge
  - maintainer direction: category `stale_abandoned`; implication `active`

## Fix status

- No merged fix on record.
- Subsystem: `cron`