Resume unsent TUI input after reconnecting (#49105)

## Why

Reconnecting paused all recovered input, including queued messages that had never been sent. Those messages can resume automatically once any uncertain submissions are resolved.

## What changed

- Track unsent and unconfirmed messages separately. Reconcile submitted prompts and steers using exact client message IDs from restored history, buffered events, and later receipts.
- Remove confirmed submissions from the recovered queue and resume unsent input after replay. Keep uncertain submissions paused without resending them, and show a notice identifying the message whose delivery could not be confirmed.
- Preserve pauses for unavailable conversations, pending compact/review requests, and existing input recovery failures.
- Simplify reconnect status text and remove blanket disconnect/reconnect transcript notices.

## Testing

Update reconnect integration tests and snapshots for automatic queue resumption. Add coverage for matching and unrelated receipts, missing history, late confirmations across navigation, pending compaction, and preservation of image-failure recovery pauses.

GitOrigin-RevId: d0b9aa43c4019d472985d12bbce8ba9bbfb9253b
This commit is contained in:
Eric Traut
2026-09-29 00:17:56 +00:00
committed by copyberry
parent 7e049b3eaa
commit 136391a23e
20 changed files with 355 additions and 100 deletions
@@ -206,6 +206,7 @@ impl ChatWidget {
.push_back(QueuedUserMessage {
user_message,
action,
delivery: MessageDelivery::Unsent,
pending_pastes,
source,
});
@@ -238,6 +239,7 @@ impl ChatWidget {
|| self.input_queue.suppress_queue_autosend
|| self.input_queue.rate_limit_recovery_pending
|| self.input_queue.recovered_queue
|| self.input_queue.has_unconfirmed_messages()
{
return false;
}