fix(tui): suppress verbose CLI logging on Windows alt-screen to prevent TUI leak

[aboimpinto]

Summary

This is the missing second commit from PR #1776. The maintainer merged the first commit (stop RUST_LOG from leaking tracing messages) but closed PR #1776 without merging this follow-up fix.

Problem

On Windows, stderr cannot be redirected to the log file (no dup2). When --verbose or DEEPSEEK_LOG_LEVEL=debug is set, eprintln! calls from crate::logging still leak into the TUI alt-screen buffer, corrupting the display � even after the RUST_LOG fix was merged.

Fix

Call crate::logging::set_verbose(false) at two points:

1. run_tui() � right after EnterAlternateScreen, so verbose logging is suppressed for the entire TUI session on Windows.
2. resume_terminal() � right after re-entering alt-screen during terminal recovery, so the suppression holds across suspend/resume cycles.

Changes

• crates/tui/src/tui/ui.rs: +9 lines � set_verbose(false) calls in run_tui and resume_terminal, gated by #[cfg(windows)].

Related

• Issue: Windows: RUST_LOG leaks tracing into TUI alt-screen #1774 (original bug report)
• PR fix: stop RUST_LOG from leaking tracing messages into TUI alt-screen on Windows #1776 (original PR � only first commit was merged)
• Closes [URGENT] Windows: CLI verbose logging still leaks into TUI alt-screen after PR #1776 (second commit was not merged) #1909 (tracking issue for this missing fix)

Urgent: this is a regression on Windows for users who run with verbose/debug logging.

[gemini-code-assist]

Code Review

This pull request introduces Windows-specific logic to suppress verbose logging when entering or resuming the TUI's alternate screen, aiming to prevent log output from corrupting the interface. Feedback indicates that this approach is currently permanent on Windows, unlike the scoped redirection used on Unix, and suggests restoring the verbosity state during cleanup. Additionally, the reviewer noted that this fix only addresses internal logging and recommended exploring WinAPI-based stderr redirection to handle third-party output and panics more effectively.

[aboimpinto]

Addressed the code review feedback:

[aboimpinto]

Rebased onto current main (v0.8.44). Only 1 commit needed — the test commit was already upstream.

[Hmbown]

Stewardship note: #1909 is now the canonical tracking issue for this Windows verbose-log leak, and the thinner duplicate #1904 was closed in favor of it. Keeping the issue open while this PR has a Windows failure; the next useful step is to inspect that failing check before deciding whether to merge, harvest, or revise.

[aboimpinto]

Fixed the composer_history flaky test (timeout 5s → 30s). The memory_guidance_matches_constitutional_tier_order failure is pre-existing on main (prompts.rs is unchanged by this PR).

[Hmbown]

Thanks @aboimpinto. I checked this while triaging v0.8.45 PRs. The current PR diff only contains Cargo.toml/Cargo.lock version/dependency churn and does not include the described alt-screen verbose logging change, so I’m not merging it as-is. I’m keeping #1909 open because the underlying Windows logging issue still needs an actual code fix or a restored patch.