fix(zulip): @all-bots fallback default was user_id=1 — never valid in SyslogGH realm

Dynamic resolution (ADR-006) overrides this on connect, but when the
/api/v1/users call fails the adapter fell back to 1, silently dropping
every @all-bots mention. The realm's all-bots user is 20 (verified
2026-09-25: 'Resolved @all-bots user_id=20 from all-bots@chat.sysloggh.net';
CONTRACT_VERIFICATION_2026-06-29 fixed the Pi config to 20 for the same
reason). Align the Hermes-side fallback with the verified realm value.
This commit is contained in:
Mumuni
2026-09-25 15:31:28 +00:00
parent f0f82d904b
commit fb752be8c9
+5 -1
View File
@@ -64,7 +64,11 @@ logger = logging.getLogger(__name__)
# Constants # Constants
DEFAULT_STREAM = "agent-hub" DEFAULT_STREAM = "agent-hub"
DEFAULT_ALL_BOTS_USER_ID = 1 # SyslogGH realm: the @all-bots user has user_id=20 (verified via
# /api/v1/users and CONTRACT_VERIFICATION_2026-06-29). Dynamic resolution
# on connect overrides this; this value is the fallback when that fails —
# user_id=1 was never valid in this realm and silently dropped @all-bots.
DEFAULT_ALL_BOTS_USER_ID = 20
DEFAULT_POLL_INTERVAL = 3.0 DEFAULT_POLL_INTERVAL = 3.0
MAX_ZULIP_MESSAGE = 10000 MAX_ZULIP_MESSAGE = 10000
TRUNCATION_NOTICE = "\n\n[...truncated at Zulip limit]" TRUNCATION_NOTICE = "\n\n[...truncated at Zulip limit]"