Problem
The Windows terminal path needs more than a package-level install. The TUI helper must read real Windows console input, report resize events, preserve redraw behavior, and shut down cleanly.
Without that parity, Windows users can install Ourocode but still hit fragile interactive behavior in PowerShell, Windows Terminal, or cmd.exe. This complements the broader Windows install work tracked in #39.
Proposed change
Extend the Windows TUI helper to acquire native console handles, translate Windows console input into the same byte/event stream the Elixir TUI expects, and package the Windows launcher alongside the helper.
Acceptance criteria
Related files
rust/ourocode_ipc/src/bin/ourocode_tty.rs
rust/ourocode_ipc/src/bin/ourocode.rs
lib/ourocode/terminal/tty_driver.ex
lib/ourocode/terminal/tui_driver_session.ex
scripts/package-windows.ps1
install.ps1
Problem
The Windows terminal path needs more than a package-level install. The TUI helper must read real Windows console input, report resize events, preserve redraw behavior, and shut down cleanly.
Without that parity, Windows users can install Ourocode but still hit fragile interactive behavior in PowerShell, Windows Terminal, or cmd.exe. This complements the broader Windows install work tracked in #39.
Proposed change
Extend the Windows TUI helper to acquire native console handles, translate Windows console input into the same byte/event stream the Elixir TUI expects, and package the Windows launcher alongside the helper.
Acceptance criteria
ourocode_tty.exeandourocode.exe.Related files
rust/ourocode_ipc/src/bin/ourocode_tty.rsrust/ourocode_ipc/src/bin/ourocode.rslib/ourocode/terminal/tty_driver.exlib/ourocode/terminal/tui_driver_session.exscripts/package-windows.ps1install.ps1