{"repo":"NousResearch/hermes-agent","public_id":"134995","display_label":"serve-restart marker cleanup and failure messaging","summary":"These items address how a dashboard respawn error is communicated and how stale serve-restart markers tied to stopped PIDs are properly cleared when a respawn cannot be scheduled.","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":134995,"title":"[Bug]: pending serve-restart marker is keyed on the stopped PID, every hermes invocation warns until a manual restart","url":null,"state":"open"},{"kind":"pr","number":135003,"title":"fix(cli): discharge a serve-restart marker when its respawn is booked failed","url":null,"state":"open","close_reason":{"refs":[{"kind":"pr","value":"#134328","number":134328},{"kind":"pr","value":"#134995","number":134995},{"kind":"pr","value":"#135155","number":135155}],"category":"superseded_by_pr","implication":"superseded"},"merged":false},{"kind":"pr","number":135155,"title":"fix(update): name the remedy when a dashboard respawn fails","url":null,"state":"closed","close_reason":{"refs":[{"kind":"pr","value":"#135003","number":135003}],"category":"superseded_by_pr","implication":"superseded"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}