Windows server: sessions on ConPTY, daemon outside the ssh job

[ralyodio]

Anthony: hqsh must work as a server on every device, Windows included.

• Refactor: the daemon is platform-neutral (daemon.go) behind a console interface: a PTY on Unix (console_unix.go, the moved code), a pseudo console on Windows (console_windows.go). The session lock, socket mode and dead-socket check moved with them.
• Windows sessions: run pwsh, else Windows PowerShell, else cmd.exe, on a ConPTY. HQSH_SHELL overrides the shell on every OS.
• Surviving disconnects: Win32-OpenSSH kills a connection's job on disconnect. The daemon starts with CREATE_BREAKAWAY_FROM_JOB, else via WMI Win32_Process.Create (outside any ssh job), else as a plain detached process.
• hqsh server setup on Windows: reports the start mode, shell and socket dir.
• README: Windows hosts and their requirements (OpenSSH server, hqsh.exe on PATH or in ~/.local/bin).

Tests

• Windows: a cmd.exe session on a real ConPTY. It starts, computes set /a, resizes, survives a disconnect and resumes without a gap, is listed, and returns exit status 7.
• Unit tests for the WMI command line and the environment block.
• The portable protocol test clients moved to helpers_test.go.
• A verbose CI step now shows which service manager each OS actually used.
• The Linux suite is unchanged and passing; go vet passes for linux, darwin and windows.

🤖 Generated with Claude Code