fix(cli): do not repaint the prompt after a keypress quits the session

[nimbly1]

Fixes #32

Ctrl-D at an empty prompt (and the second Ctrl-C of a double Ctrl-C) exits with code 0, but the live input box and the shortcut hint were painted again after the terminal had been cleaned up, so they stayed on screen as if the prompt were still interactive.

Chat.onKey() ends with an unconditional this.refresh(). For a quit keypress, onControl() has already run quit() -> finish() -> Screen.finish(), which clears the composer and footer and restores the cursor. The refresh then calls setHint/setComposer and paints the box again. This follows the starting point in the issue.

The change is one line: if (!this.quitting) this.refresh();, the same guard the other refresh call sites in chat.ts already use. Ctrl-D in a non-empty draft (delete forward) and Ctrl-C while a task runs do not quit, so they still refresh as before.

Tests

Two tests in packages/cli/test/chat.test.ts, using the existing in-process session() harness: Ctrl-D at an empty prompt, and a second Ctrl-C after the first one armed the quit. Each checks the prompt is on screen before the key, that the session exits 0, and that nothing written after the quit began draws the prompt text, the box or the auto-approve hint. Both fail without the change and pass with it.

• npx vitest run on every test file that imports chat.ts (chat.test.ts, dashboard.test.ts, mcp-ui.test.ts, mcp/audit-regressions.test.ts): 7 tests fail identically on an unmodified main and with this change on my Windows machine (the Ctrl-O output test, the signing-in file mode test, and several signal and path tests); 2 more tests pass with the change.
• pnpm typecheck passes.
• I did not add the PTY-backed terminal test from the acceptance criteria, which needs a real terminal, and I did not check the result in a real terminal or on macOS.

Generated with Claude Code