fix: resume saved user messages after execution recovery (#13270)

Preserve verified native process-stop evidence and retry saved user messages through normal continuation admission after recovery cleanup. Show the current wait reason and serialize delivery so a saved message starts one fresh turn.

Validated with 410 focused tests, typecheck, build, token gates, all PR CI checks, and Greptile 5/5.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
DottaandPaperclip authored and GitHub committed 2026-09-11 17:12:55 -05:00
1 parent 250deab910
commit 51b0e01ead
17 files changed
+471 -95

No files matched your search

@@ -78,6 +78,15 @@ describe("TaskChatQueuedMessages", () => {
return props;
}
it("shows the saved message's wait reason and removes it when admission succeeds", () => {
const message = "Waiting for the previous environment to stop. Your message will start automatically.";
render({ queue: { ...queue, executionWait: { reason: "remote_cleanup", message } } });
expect(container.querySelector('[role="status"]')?.textContent).toContain(message);
expect(container.textContent).toContain("First queued message");
render();
expect(container.textContent).not.toContain(message);
});
it("renders each queued message once as a compact one-line row", () => {
render();
const pane = container.querySelector(
@@ -365,6 +365,11 @@ export function TaskChatQueuedMessages({
data-testid="task-chat-queued-messages"
aria-label="Queued messages"
>
{queue.executionWait && (
<div role="status" aria-live="polite" className="px-3 py-1.5 text-xs text-muted-foreground">
{queue.executionWait.message}
</div>
)}
<DndContext
sensors={sensors}
collisionDetection={closestCenter}