fix(tui): make the flush test assert its own claim, and stop y/n propagation

Two remaining review points.

The test named "enabling yolo clears a prompt that is already on screen" only
asserted that a reply was sent — never that the prompt left the screen, which is
the behaviour in its name. It now asserts the pending list empties. This works
without emitting `permission.replied` because autoApprove removes the request
optimistically on success.

Adds `stopPropagation()` to the dialog's `y` and `n` branches, matching the
`return` branch. Two reviewers disagreed on whether this is load-bearing: the
dialog blurs the focused renderable on open and refocuses in a later tick, so a
stray character cannot reach the prompt today. It is free consistency that keeps
that true if the ordering ever changes.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01964Prd1Sz5JwWZmNTrFdiU

Author: Haider

packages/tui/src/component/dialog-yolo-confirm.tsx

@@ -56,13 +56,19 @@ export function DialogYoloConfirm(props: { onChoose: (enable: boolean) => void }
       options[selected()].run()
       return
     }
+    // stopPropagation for consistency with the `return` branch above. The dialog blurs
+    // the focused renderable on open and only refocuses in a later tick, so a stray
+    // character cannot reach the prompt today — this keeps it that way if that ordering
+    // ever changes.
     if (evt.name === "y" && !evt.ctrl && !evt.meta) {
       evt.preventDefault()
+      evt.stopPropagation()
       run(true)
       return
     }
     if (evt.name === "n" && !evt.ctrl && !evt.meta) {
       evt.preventDefault()
+      evt.stopPropagation()
       run(false)
     }
   })

packages/tui/test/cli/cmd/tui/yolo-sync.test.tsx

@@ -214,6 +214,10 @@ describe("tui sync: yolo auto-approve", () => {
       await wait(() => pending(sync, ROOT).length === 1)
       sync.yolo.set(ROOT, true)
       await wait(() => replies.length === 1)
+      // Assert the behaviour in the test's name, not just that a reply went out: the
+      // prompt must actually leave the screen. autoApprove removes it optimistically on
+      // success, so this does not depend on the server's permission.replied event.
+      await wait(() => pending(sync, ROOT).length === 0)
     } finally {
       app.renderer.destroy()
       await tmp[Symbol.asyncDispose]()