TUI 对话中进程崩溃，输入内容泄漏到 PowerShell 终端

[xiaowuguiya888]

环境：Windows 10/11, Windows Terminal, codewhale v0.8.44
复现步骤：

1. 在 PowerShell 中运行 codewhale
2. 正常进行多轮对话
3. 某次 AI 回复完成后，输入框的焦点丢失
4. 输入的任何内容不再进入 TUI，而是被 PowerShell 当成 cmdlet 执行
5. 报错：The term '...' is not recognized as a name of a cmdlet...

[xiaowuguiya888]

[Hmbown]

感谢报告和截图。这个症状看起来属于 Windows alt-screen / 终端恢复 / 日志泄漏这一组问题，我先不关闭，等真实版本复测后再判断。

当前 v0.8.48 候选里有两个相关修复在处理：

• fix(tui): init runtime log before alt-screen, add Windows stderr redirect (#1909) #2259：更早初始化 TUI runtime log，并在 Windows 下把 stderr 重定向到日志文件，避免日志/崩溃输出打穿 alt-screen。
• fix(tui): suppress verbose logs while alt-screen is active #2262：在 TUI 持有 alt-screen 时临时抑制 verbose CLI 日志，并在退出/暂停/恢复/紧急恢复路径恢复原状态。

等这些修复合并并进入 v0.8.48 后，麻烦再用 Windows Terminal + PowerShell 复测一次。如果仍然复现，请追加 Windows Terminal 版本、PowerShell 版本，以及已脱敏的最后几行 TUI/runtime 日志；不要贴 API key、路径中敏感信息或完整对话内容。

[Hmbown]

Thanks again for this Windows/PowerShell crash report. Since v0.8.48 is now published, could you please retest with the current release when you have a chance?\n\nA couple of related fixes landed in this release line: #2259 suppresses noisy alt-screen logging on Windows, and #2295 tightens the Windows runtime logging path so terminal output should not leak back into PowerShell during TUI execution. I am not closing this yet because the original report was about a crash plus input/output leakage, and I would rather have fresh Windows Terminal + PowerShell evidence before calling it fixed.\n\nIf it still reproduces, the most useful details would be: Windows Terminal/PowerShell versions, the exact CodeWhale version from codewhale --version, whether it happens after a specific tool call, and any ~/.codewhale/logs/ TUI log from that run.