fix(buzz): subscribe to newly joined channels

[bricelb]

What changed

• Extract the channel UUID from relay-signed Buzz kind:44100 membership events.
• Subscribe the WebSocket transport to a newly joined community channel immediately.
• Keep an explicit BUZZ_CHANNELS list authoritative; automatic discovery only applies when that list is empty.
• Start the new subscription at the membership timestamp so prior channel history is not replayed.

Root cause

_handle_membership_event() called _discover_dms() and subscribed anything it added. That helper intentionally excludes real community channels to avoid misclassifying them as mention-free DMs, so a channel joined after gateway startup never entered _channel_state. The gateway only saw it after a restart rebuilt the initial channel list.

User impact

With automatic Buzz channel discovery enabled, adding the Hermes identity to a public, private, or ephemeral channel now makes the running gateway listen immediately. Users no longer need to restart the gateway after each channel addition.

Validation

• scripts/run_tests.sh tests/gateway/test_buzz_adapter.py tests/gateway/test_buzz_websocket.py -q (30 passed)
• .venv/bin/ruff check plugins/platforms/buzz/adapter.py tests/gateway/test_buzz_websocket.py
• git diff --check

[alt-glitch]

This was generated by AI during triage.

Related to #74823 and #76156. This is the narrow event-driven join-subscription repair; #74823 expands startup discovery and #76156 adds broader membership reconciliation and addressing behavior. The overlap is real, but the scopes are not identical; please choose or consolidate the intended membership policy.

[teknium1]

Thanks for the narrow Buzz delivery repair. The current-main premise is verified: plugins/platforms/buzz/adapter.py:801-813 only subscribes conversations added by _discover_dms(), while _discover_dms() excludes real community channels at plugins/platforms/buzz/adapter.py:958 through _may_reclassify_as_dm() (plugins/platforms/buzz/adapter.py:1063-1076).

Commit 1f1dae22a9c3139af3ea9b4e198ff78f7ffff4de addresses that exact gap by extracting the membership event's h channel tag, respecting the explicit channel list, and issuing a subscription with the membership boundary as the high-water mark. Its scope remains limited to the Buzz plugin and its WebSocket tests.

Automated hermes-sweeper review.

[bricelb]

The intended scope of #76823 is deliberately narrow: preserve the existing startup discovery and addressing policies, and only repair live subscription when an automatic-mode agent receives a channel membership-add event. It does not attempt removal reconciliation, polling fallback, or addressing-policy changes. If maintainers prefer #74823’s broader startup membership policy, I’m happy for this PR to be considered superseded once that path lands. Brice -- "Ideas are everything. Charge accordingly." Josh Bryer

…

Le 2 août 2026 à 16:29, Siddharth Balyan ***@***.***> a écrit : alt-glitch left a comment (NousResearch/hermes-agent#76823) <#76823 (comment)> This was generated by AI during triage. Related to #74823 <#74823> and #76156 <#76156>. This is the narrow event-driven join-subscription repair; #74823 <#74823> expands startup discovery and #76156 <#76156> adds broader membership reconciliation and addressing behavior. The overlap is real, but the scopes are not identical; please choose or consolidate the intended membership policy. — Reply to this email directly, view it on GitHub <#76823?email_source=notifications&email_token=ABZC2MSJ3NAXTPHDIAN6IA35H5F3NA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJVHA2TGMJUGA2KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5158531404>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABZC2MXNUHW3ZRCTYCENK335H5F3NAVCNFSNUABGKJSXA33TNF2G64TZHMYTAMRUGU2TIMRWG45US43TOVSTWNJQGQZDQMBRGI4DTILWAI>. You are receiving this because you authored the thread.