{"repo":"NousResearch/hermes-agent","public_id":"51030","display_label":"Token collision detection fix in gateway config","summary":"These items address a bug where same-token credential collision detection fails because the lookup for adapter config tokens is broken. The work involves detecting and fixing this gap in the gateway/multiplexer layer.","subsystem":"gateway","counts":{"members":3,"open_issues":0,"open_issues_distinct":0,"open_prs":0,"closed_issues":1,"merged_prs":1,"attempt_prs":1},"landed_fix":{"status":"merged_to_main","basis":"structural","pr":59321,"merged_at":"2026-07-07T08:25:33+00:00"},"resolution":{"state":"resolved","by":"pr-59321"},"freshness":{"state":"verified","last_verified_at":"2026-07-07T08:25:33+00:00","is_stale":false},"grouping":{"backbone":"STRUCTURAL_SPANNING","link_density":0.6666666666666666},"fix_edges":[{"issue_number":51030,"pr_number":59321,"tier":"verified","basis":"closing_ref","confidence":0.95,"recoverable_from_timeline":true,"pr_merged_at":"2026-07-07T08:25:33+00:00"}],"members":[{"kind":"issue","number":51030,"title":"Multiplexer: same-token collision detection is dead for Telegram — _adapter_credential_fingerprint never finds a token at adapter.config.token","url":null,"state":"closed"},{"kind":"pr","number":51064,"title":"fix(gateway): detect config token credential collisions","url":null,"state":"closed","close_reason":{"refs":[{"kind":"commit","value":"d297568299fbc0481e3edaa9f35d13aa692b20b1","number":0},{"kind":"pr","value":"#59321","number":59321},{"kind":"pr","value":"#51064","number":51064}],"category":"implemented_elsewhere","implication":"superseded"},"merged":false},{"kind":"pr","number":59321,"title":"fix(gateway): detect config-held token credential collisions (#51064 salvage)","url":null,"state":"merged","close_reason":{"category":"merged"},"merged":true,"is_fix_pr":true,"fix_tier":"verified","files_changed":["gateway/run.py","tests/gateway/test_multiplex_adapter_registry.py"]}],"trust":{"default_tier":"verified","includes_suggested":false}}