Let bots take in messages sent while they reply

A reply read the session once at the start, so a message sent while it
ran was never seen, and the follow-up reply queued for it then finished
silently: the message was saved before the reply, so the thread ended
with the bot. Those messages went unanswered.

The text loop now reads new user messages after every round of tools and
before an answer goes out, and the bot decides from what each one means
whether it changes the work (folded in, or the unsent answer redrafted)
or is a separate request, which it acknowledges at once with the new
send_message tool and does after the current work. Messages sent that
way are marked interim, so the thinking row stays up while the bot
works. A reply job records the newest user message it read, and a queued
reply only stays silent when a finished reply already read everything.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

src/data/app-data.ts

@@ -402,6 +402,12 @@ export const AppData = {
      * reads it through `grabReplyMaxToolSteps`.
      */
     BotReplyMaxToolSteps: 20,
+    /**
+     * Messages a chat reply may send while it works (`send_message`):
+     * acknowledging something the user wrote meanwhile, a heads-up. Its
+     * answer still comes at the end.
+     */
+    BotReplyInterimMessagesMax: 3,
     /**
      * The most steps a saved run limit may ask for, for a task run or a
      * chat reply. A typo in the settings page can't turn one run into an