question dismissal, A2: the silent write + the dismissal pause (owner design 2026-10-03)

- {type:"dismiss"} input event: parse + pure appends with the answer-event
  orphan discipline (dangling-call 400, kind match, answer must be dismissed)
- POST /api/chats/[id]/dismiss: the no-turn composition — write-ahead append,
  409 while a turn runs, emits record-changed (new bus word; idle views sync)
- needsContinuation: an all-dismissed trailing batch demands nothing;
  endsInDismissal = the derived pause predicate (tail-based, no latch)
- wake pipeline: while the record ends in a dismissal the pump holds every
  delivery in the steer queue — the user's next send is the wake (until the
  text-turn steer claim lands, settlement re-pump delivers right after it)
- session-core.dismissQuestion: optimistic skipped card + silent POST;
  chat.tsx confirmAbort question-mode swaps submitAnswer for it; ESC-abort
  popup everywhere (AbortTurnDialog) with popup-Esc claimed via state gate
- parallel question calls dismiss call-by-call (results bind by id)

components/abort-turn-dialog.tsx

@@ -17,8 +17,10 @@ import { createPortal } from "react-dom";
  *
  * What "abort" means is mode-dependent: from a running turn it kills
  * the turn (partial stays); from a pending question there is no turn to
- * kill — abort IS dismissal (QuestionAnswerData.dismissed), and the
- * teacher acknowledges the skip in its next turn like any answer.
+ * kill — abort IS dismissal (A2, 2026-10-03): the silent route writes
+ * the skipped toolResult and wakes NOTHING; the session pauses until
+ * the user's next plain message, which carries the dismissal to the
+ * model in its context.
  */
 
 /** What Esc is aborting — drives copy and the confirm action. */