base red: cmux-tui builds for Windows again (cmux-automations unix-only)
Summary
build-windows / build x86_64-pc-windows-gnu fails for every PR whose change routes it on. It runs cargo build -p cmux-tui --target x86_64-pc-windows-gnu, and that fails with could not compile cmux-automations (lib) due to 35 previous errors. The errors are std::os::unix, std::os::fd, and libc::localtime_r / gmtime_r / timegm / kill / pid_t (seen on #28678 and #28759, for example job 124460652801).
cmux-tui uses cmux-automations only from cli/automation.rs. That module is already #[cfg(unix)], as is its run_if_requested call in cli.rs. Only the dependency was declared for every target. This PR moves it to [target.'cfg(unix)'.dependencies], so a Windows build no longer compiles the crate. Nothing changes on macOS or Linux, and Cargo.lock is unchanged.
Base push runs don't run build-windows, so this red never shows on base. next-autoland then counts it as each PR's own red, which holds back otherwise-ready PRs.
Testing
Red: base, as build-windows on #28678 and #28759 at their heads (35 errors in crates\cmux-automations). Green: this PR's own build-windows job.
Observed / Not run
Observed: the Windows errors in those jobs' logs, all in cmux-automations, and that cmux-tui reaches the crate only through cfg(unix) code (git grep cmux_automations).
Not run: a local Windows cross-build (this VM has no mingw toolchain); this PR's CI build-windows job runs it.
Changelog
none
Agent session: agent session
š¤ Generated with Claude Code
![View with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/view-with-codesmith-dark-v3-3x.png)
![Autofix with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/autofix-with-codesmith-dark-3x.png)
Need help on this PR? Tag @codesmith-bot with what you need.
Summary by cubic
Fixes the Windows build of cmux-tui by making cmux-automations a unix-only dependency.
cmux-automations uses std::os::unix and libc unix calls, so compiling it for x86_64-pc-windows-gnu failed with 35 errors. cmux-tui only reaches the crate from cli/automation.rs, which is already #[cfg(unix)]. Moving the dependency to [target.'cfg(unix)'.dependencies] means Windows builds skip the crate entirely. macOS and Linux builds are unchanged, and Cargo.lock is untouched.