{"repo":"NousResearch/hermes-agent","public_id":"44294","display_label":"Fix reply_to metadata forwarding in gateway/qqbot","summary":"These changes address how reply_to information is extracted from gateway metadata and forwarded through to adapter parameters, including during background task completion delivery. All three items relate to preserving reply context across the gateway and qqbot layers.","subsystem":"gateway","counts":{"members":3,"open_issues":1,"open_issues_distinct":1,"open_prs":2,"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":44294,"title":"fix(qqbot): bridge reply_to from gateway metadata to adapter parameter","url":null,"state":"open"},{"kind":"pr","number":44307,"title":"fix(qqbot): extract reply_to from gateway metadata before discarding","url":null,"state":"open","close_reason":{"category":"uncategorized","implication":"needs_llm"},"merged":false},{"kind":"pr","number":134416,"title":"fix(gateway): forward event_message_id as reply_to in background task completion delivery","url":null,"state":"open","close_reason":{"category":"silent_close","implication":"active"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}