Widens #137037 from Mattermost to the whole class (#137027):
- Runtime notices never reach a bot peer: every busy-path reply (ack, redirect,
drain), lifecycle/status and credits notices, tool progress, interim and thinking
bubbles, the long-running heartbeat, the auto-reset notice, and the runtime failure
copy ("not processed", retry hints, generic failure apology) on a failed or empty
turn. The model's own reply is still delivered.
- Chain rules in gateway.bot_loop_guard (config.yaml): a human message starts a chain,
each bot message after it is one hop, max_hops (default 4) caps them, a bot repeating
the same text in one chain is dropped, and with bot_replies_expect_reply false (the
default) a bot answering the reply this bot just gave it starts no turn. A bot
message also counts as not expecting a reply, so a silence marker ends it quietly.
- Bot authorship everywhere it is knowable: a generic per-adapter bot_users opt-in
(config.yaml platform extra) for platforms whose events carry no bot flag,
Mattermost props.from_bot, QQ guild author.bot.
- Bot Mode message_agent: agent/bot_chain.py owns a per-session hop count carried in
the delivery's author envelope (runtime-written, parse_turn_author keeps it), refuses
sends past the same max_hops and identical repeated asks, sends a reply to the bot
that messaged this turn notify-only (expects_reply false, no wake), and refuses a
message back to a bot whose reply said it needs no answer. tools/bot_mode_dm.py gets
only the gate call and the wake flag (LANE dm owns that file; same wake names as #144789).