{"repo":"NousResearch/hermes-agent","public_id":"121596","display_label":"launchd port-holder orphan handling during updates","summary":"These items concern a recurring conflict during updates where launchd-managed port-holder processes are incorrectly identified or left unsupervised, causing an orphaned process to re-acquire the port and hold it without a token for an extended period. The work focuses on attribution logic and keeping the port holder under launchd supervision across kickstart cycles.","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":121596,"title":"[Bug]: update kill/respawn fight on launchd-served fixed port (same-home variant): orphan re-orphaned every update, token-less impostor holds port for minutes","url":null,"state":"open"},{"kind":"pr","number":121784,"title":"fix(update): attribute launchd orphans by backend shape, not launcher spelling","url":null,"state":"closed","close_reason":{"category":"superseded_by_pr","implication":"superseded"},"merged":false},{"kind":"pr","number":127277,"title":"fix(update): keep a launchd-owned port holder supervised through kickstart -k","url":null,"state":"open","close_reason":{"category":"uncategorized","implication":"needs_llm"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}