feat: Windows terminal support

[mikew]

So they key here is start "" /WAIT nvim ..., but getting there is annoying.

We write a .bat file, because the user's shell might be git-bash which would need translating windows paths and cmd-style arguments. We still have to be aware of powershell and cmd, so that's all plumbed through, so powershell users on Linux should also be supported now.

Closes #54

Preview

Screen.Recording.2025-08-19.at.1.28.56.AM.mov

[Copilot]

Pull Request Overview

This PR adds Windows terminal support to the nvrh tool by implementing special handling for Windows shells and creating batch file launchers. The key innovation is using start "" /WAIT nvim ... in batch files to properly handle Windows terminal behavior.

• Refactors command string building to support different shell types (PowerShell, cmd, bat, bash)
• Moves SSH arguments and other configuration from context to local variables for better separation of concerns
• Adds Windows-specific launcher batch file creation and cleanup

Reviewed Changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
src/nvrh_binary_ssh/main.go	Moves SSH arguments from context to client struct
src/nvim_helpers/main.go	Refactors command building with shell-specific support and new batch file handling
src/context/main.go	Removes deprecated fields and adds Windows launcher path
src/client/main.go	Implements Windows detection, batch file creation, and refactors variable scoping
src/bridge_files/lua/types/nvrh.lua	Adds Windows launcher path type definition
src/bridge_files/lua/setup_nvim_launcher.lua	New file for creating batch launcher files
src/bridge_files/lua/init_nvrh.lua	Adds cleanup for Windows launcher files
src/bridge_files/lua/init_bridge.lua	Updates function signature for Windows launcher path
script/test	Minor test script adjustment

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}