What problem does it solve? Cross-platform Rust crates with platform-gated code can silently break in their shared modules, and a Windows host has no visibility into whether the macOS tray crate still compiles cleanly from its side. This Skill runs a daily build probe that turns a Windows compile of the macos-tray crate into a health signal for the shared codebase. ## Core Features & Use Cases - Daily cross-platform build probe: Syncs the windows-next branch and runs cargo build -p tillandsias-macos-tray --release, where exit 0 confirms the cfg-gating is intact and a non-zero exit signals a regression in shared modules. - Structured findings ledger: Appends timestamped sections to plan/issues/probe-macos-tray-on-windows-findings-YYYY-MM-DD.md with cargo exit code, first error line, classification, and shared-crate impact. - Conditional cross-host escalation: Files a coordination note in plan/issues/tray-convergence-coordination.md only when an unexpected shared-crate error appears, then commits and pushes to windows-next. - Use Case: A Windows host on a 24-hour loop detects that tillandsias-host-shell no longer compiles, classifies it as a regression, and escalates so the macOS host sees the breakage before its next integration cycle. ## Quick Start Run the daily probe to build the macos-tray crate from this Windows checkout and file the findings under plan/issues.
