5abe2e1880
Addresses the review on #92315: - Windows behavior made explicit: AF_UNIX event-loop support doesn't exist there, so the witness is permanently absent, the payload records loop_tick_socket=False, and stale-file probes classify UNKNOWN, never WEDGED — deliberate fail-safe (graceful drain remains the backstop). WSL2, the #90502 incident environment, is Linux and arms normally. - New test asserts the default tick_timeout/tick_strikes/tick_gap_s math stays inside the documented probe budget so retuning can't silently blow past the 10s subprocess query tier.