VincentandOrcaWin e58c051d16 fix(terminal): trust Pi CSI-u Shift+Enter on Windows (#9703) (#11769) ...

* fix(terminal): trust Pi CSI-u Shift+Enter on Windows (#9703)

Pi enables the Kitty keyboard protocol at startup and decodes CSI-u, but
TUI_AGENT_CONFIG['pi'] never set windowsShiftEnterEncoding, so on Windows
Pi could only get CSI-u via the flaky live-KKP-flag path
(isKittyKeyboardActivePane). After a tool ran a subprocess that emitted a
reset sequence, the KKP flags dropped to 0, Orca sent Esc+CR, and Pi read
it as plain Enter -> submit. It recovered on the next pane refocus.

Set windowsShiftEnterEncoding: 'csi-u' for pi, mirroring the Droid fix
(#7668), so the trusted CSI-u route covers Pi reliably independent of
KKP-flag churn from tool subprocesses.

* fix(terminal): complete Pi Windows CSI-u trust lifecycle

* test(terminal): name foreground retry timing

* test(git): accept bounded SSH remote probes

---------

Co-authored-by: OrcaWin <293788423+OrcaWin@users.noreply.github.com>

2026-08-02 00:58:37 -07:00

..

cli

chore(dead-code): drop ~2k lines of unreachable exports and orphan modules (#12077)

2026-08-02 00:33:57 -07:00

main

fix(terminal): trust Pi CSI-u Shift+Enter on Windows (#9703) (#11769)

2026-08-02 00:58:37 -07:00

preload

fix(quit): stop durable state writes from parking the main thread on quit (#11931)

2026-08-01 19:22:39 -07:00

relay

refactor(relay): collapse the duplicated FrameDecoder into one shared module (#12078)

2026-08-02 00:58:10 -07:00

renderer

fix(terminal): trust Pi CSI-u Shift+Enter on Windows (#9703) (#11769)

2026-08-02 00:58:37 -07:00

shared

fix(terminal): trust Pi CSI-u Shift+Enter on Windows (#9703) (#11769)

2026-08-02 00:58:37 -07:00

types

…