fix(ui): dismiss skipped confirmations when sending a message

Co-Authored-By: Paperclip <noreply@paperclip.ing>

doc/DEVELOPING.md

@@ -576,6 +576,10 @@ behavior for review cards. Its dismissal save and decisions are simulated;
 server persistence and permission boundaries have separate regression tests.
 The demo uses real thread/form components with fixture response callbacks.
 The Agent Chat stories share the same component fixture.
+The **Send instead of confirming** and **Reopen skipped confirmation** stories
+exercise sending a separate message while a completion review is open, then
+opening that unchanged request from the feed. These use the production thread
+with simulated message saves and decision callbacks.
 
 Use **Composer → New task** to review task creation through the production
 `TaskChatComposer`. The editor, file menu, work modes, assignee/model picker,

doc/SPEC-implementation.md

@@ -1975,6 +1975,12 @@ Dismissal never creates an answer, decision, execution, or continuation wake.
 Raw runtime requests retain browser-local dismissal; reopening restores the
 original request and draft. A failed save leaves the request open with an error.
 
+Sending a separate message closes the current composer request immediately,
+before the send finishes. After a successful send, earlier requests stay in the
+feed and can be reopened manually; a newer request can still open normally.
+If sending fails, restore the previous form unless the person has opened a
+different request. This presentation change does not answer or approve a request.
+
 A saved ordinary question becomes historical after a newer human task message
 or explicit human dismissal. It remains answerable after completion without
 reopening work or waking the agent. Dismissed ordinary requests, including native