{"repo":"NousResearch/hermes-agent","public_id":"126190","display_label":"Kanban respawn guard and stale rate-limit error text","summary":"These items all concern the Kanban respawn guard and stale rate-limit text left in last_failure_error, which one bug report links to a task staying in ready after dependency promotion. The two fix-titled items appear to address this by using run outcomes instead of error prose and by clearing stale text when recompute_ready promotes a card.","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":126190,"title":"[Bug]: Kanban task stuck in ready forever: stale rate-limit text in last_failure_error trips respawn guard blocker_auth after dependency promotion","url":null,"state":"open"},{"kind":"pr","number":126212,"title":"fix(kanban): clear stale rate-limit text when recompute_ready promotes a card","url":null,"state":"open","close_reason":{"refs":[{"kind":"commit","value":"c92379513d","number":0}],"category":"implemented_elsewhere","implication":"superseded"},"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}}