Deferred from PR #35 review (round 3): the release binary is GUI-subsystem (windows_subsystem = "windows"), so while agents capturing piped stdout work fine (pipe handles are inherited) and AttachConsole(ATTACH_PARENT_PROCESS) covers most interactive cases, an interactive pickgauge usage in cmd/PowerShell has imperfect ergonomics: the prompt can return before output and exit codes aren't reliably observable in all invocation styles.
Expected: a small console-subsystem helper/shim (or subsystem switch at link time for a second binary target) so Windows terminal users get synchronous, exit-code-correct behavior.
Risk: low — Linux/macOS unaffected; Windows agents using piped subprocess invocation (the documented pattern in docs/usage-json.md) work today.
Deferred from PR #35 review (round 3): the release binary is GUI-subsystem (
windows_subsystem = "windows"), so while agents capturing piped stdout work fine (pipe handles are inherited) andAttachConsole(ATTACH_PARENT_PROCESS)covers most interactive cases, an interactivepickgauge usagein cmd/PowerShell has imperfect ergonomics: the prompt can return before output and exit codes aren't reliably observable in all invocation styles.Expected: a small console-subsystem helper/shim (or subsystem switch at link time for a second binary target) so Windows terminal users get synchronous, exit-code-correct behavior.
Risk: low — Linux/macOS unaffected; Windows agents using piped subprocess invocation (the documented pattern in docs/usage-json.md) work today.