Repository navigation
Questions raised during a Telegram turn are now answered in Telegram.
The host allows one user-questions provider process-wide and the Web bridge claims it first in a web profile, so a question asked from a Telegram session was answered in the browser while the bot appeared to stop mid-turn.
The channel now installs a router over the incumbent provider: sessions bound to a chat get inline keyboards, every other session reaches the browser exactly as before. Set routeQuestions: false to restore the old behaviour.
This shares a slot the host models as exclusive, so it fails safe at every step — it verifies the field is writable and the incumbent recognisable before touching anything, hands the incumbent every session it cannot resolve, passes that provider's rejections through untouched, and restores it on disposal. A future DSH that makes the field private costs the feature, not the boot.
Also adds the first tests for the inline-keyboard flow itself: 133 tests total.