A queued message whose send failed says why, and one cut off goes again

[fxck]

On a Mate (Milo), a turn ended and the follow-up queued under it was never sent.

The cause. A queued message lives in the tab and goes out when the turn ends. If that send failed at that moment (the account check timing out, the link dropping, a refusal), the message was put back held. A held message:

• never went out again on its own;
• blocked everything queued behind it;
• looked exactly like a waiting one: only the clock's tooltip changed, and the reason showed in the top banner, or nowhere if the send was cut off.

Now:

• A send that was cut off goes back in the queue unheld and is retried automatically, at most 3 times. Each retry carries the first attempt's message and command ids, so a command the server already accepted is deduped by its command receipts (OrchestrationEngine.ts) and can never start a second turn.
• A refused send is held with its reason, shown on its bubble in place of the clock. ↑ becomes Retry, which mints fresh ids. The top banner no longer repeats the reason.
• Messages behind a held one say "Waits for the message above".
• While a question or approval is open, the next message says "Waits for your answer above", and its ↑ is disabled with that tooltip rather than doing nothing.

Tests:

• queuedMessageStore tables cover a held reason, the never-due rule, Retry clearing the hold and the ids kept across a requeue.
• queuedSendOutcome covers 9 cases, and queuedSendAttemptIds 3.
• A harness at /design-queued.html shows the bubble's states.

🤖 Generated with Claude Code