AccountId Preservation and Routing Fixes

This cluster addresses issues related to the preservation and normalization of accountId for consistent messaging and routing across various sessions and gateways.

12 PRs

fix sessions Representative: #14359

#	Title	Author	Created	GitHub
4693	fix: keep main session displayName on outbound sends	ManojINaik	2026-01-30	View
8095	fix(sessions): include accountId in deliveryContext for outbound per-peer DM ...	codeslayer44	2026-02-03	View
8357	fix(gateway): preserve accountId across gateway restarts	alfredo-feat-volky	2026-02-03	View
8507	fix: preserve accountId for multi-account agent-to-agent messaging	djh58	2026-02-04	View
8694	Fix Telegram routing when token override omits accountId	codvik	2026-02-04	View
9437	fix: normalize accountId in binding matching for consistent routing	dbottme	2026-02-05	View
13477	routing: normalize account ID matching for agent bindings	davidahmann	2026-02-10	View
14359	fix: prefer named Telegram account over orphan 'default' in binding resolution rep	itsGustav	2026-02-12	View
14488	Fix Telegram default account listing and CLI cache-write usage mapping	abdulbb	2026-02-12	View
15727	fix(routing): resolve channel default account instead of hardcoded 'default'	FuseWeb	2026-02-13	View
20948	fix: propagate accountId from heartbeat delivery context to agent run	odrobnik	2026-02-19	View
23238	fix(telegram): account named "default" silently breaks inbound polling	anillBhoi	2026-02-22	View