kimi -r startup session picker does not support repeated Ctrl-C/Ctrl-D exit

[MicroGery]

What version of Kimi Code is running?

0.10.1

Which open platform/subscription were you using?

Kimi Code

Which model were you using?

Kimi-k2.6

What platform is your computer?

Windows

What issue are you seeing?

When starting Kimi Code with kimi -r in a directory where the startup session picker is shown, the picker does not behave like the normal TUI exit flow.
In the normal TUI, pressing Ctrl-C or Ctrl-D once shows an exit confirmation hint, and pressing the same shortcut again exits. In the startup session picker, Ctrl-C and Ctrl-D were not handled consistently, so users could only dismiss the picker with Escape.
This is especially noticeable when running kimi -r without a session id to browse existing sessions. The picker should support the same repeated Ctrl-C / Ctrl-D exit behavior as the main TUI

What steps can reproduce the bug?

1. Start Kimi Code with the resume picker:

   kimi -r
   

2. When the startup session picker is shown, press Ctrl-C.

3. Observe that the picker does not use the normal double-tap exit flow.

4. Repeat with Ctrl-D.

Optional edge case:

1. Start kimi -r in a directory where the startup picker has at least one session.
2. Press Ctrl-C or Ctrl-D once in the picker.
3. Before the confirmation timeout expires, select a session.
4. Press the same shortcut once in the resumed session.

What is the expected behavior?

The startup session picker should behave consistently with the normal Kimi Code TUI exit flow:

• Pressing Ctrl-C once should show the standard “press again to exit” confirmation hint.
• Pressing Ctrl-C again within the confirmation window should exit Kimi Code.
• Pressing Ctrl-D once should show the standard “press again to exit” confirmation hint.
• Pressing Ctrl-D again within the confirmation window should exit Kimi Code.

If the user leaves the picker by selecting a session, any pending exit confirmation from the picker should be cleared so it does not affect the resumed session.

Additional information

No response