{"repo":"NousResearch/hermes-agent","public_id":"132473","display_label":"Kanban card completion misclassifying branch-rules 403 as auth blocker","summary":"These items concern the kanban PR-URL completion flow, where a 403 from the branch-rules endpoint is reportedly read as an infrastructure issue and then matched as an auth blocker, leaving a card parked. The two fix-titled items describe changing the respawn guard to rely on run outcomes rather than error text, and treating a branch-rules refusal as having no rules.","subsystem":"hermes_cli","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":132473,"title":"kanban: PR-URL completion contract parks a card forever when the branch-rules endpoint 403s (read as infra, then matched as blocker_auth)","url":null,"state":"open"},{"kind":"pr","number":132479,"title":"fix(kanban): treat a branch-rules refusal as no rules, not an auth blocker","url":null,"state":"open","close_reason":{"category":"silent_close","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}}