The Windows guard's platform argument defaults to linux and no caller overrides it, so it never throws.
What
New errors were added saying that lifecycle hooks and orchestrator mode need a Linux or macOS host, because hooks are POSIX executables spawned directly. In this build the check cannot trigger: both call sites pass only the feature name, and the platform argument defaults to linux, so the guard always returns without throwing.
Details
- One message reads
--hooks-dir is not supported on Windows. - Whether it ever fires depends on a caller passing a real platform value, which nothing in this build does.
Evidence
--hooks-dir is not supported on Windows
Strings lifted out of the shipped bundle, so the claim above can be checked against them.