{"repo":"NousResearch/hermes-agent","public_id":"121281","display_label":"Kanban stale failure error and respawn guard handling","summary":"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.","subsystem":"cron","counts":{"members":3,"open_issues":1,"open_issues_distinct":1,"open_prs":1,"closed_issues":0,"merged_prs":0,"attempt_prs":2},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_SPANNING","link_density":0.6666666666666666},"fix_edges":[],"members":[{"kind":"issue","number":121281,"title":"kanban: a manual `blocked` → `ready` promote keeps the stale `last_failure_error`, and `blocker_auth` parks the card forever","url":null,"state":"open"},{"kind":"pr","number":121292,"title":"fix(kanban): clear stale failure error on manual promote","url":null,"state":"open","close_reason":{"refs":[{"kind":"commit","value":"a510d6c64a61582688133b5f54c8191e190a1f49","number":0}],"category":"stale_abandoned","implication":"active"},"merged":false},{"kind":"pr","number":142737,"title":"fix(kanban): respawn guard decides from run outcomes, never from error prose","url":null,"state":"closed","close_reason":{"category":"stale_abandoned","implication":"active"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}