test(e2e): gate ipc_client_test + vite_build_cache on unix-only

On Windows CI these ignored tests crash their child processes with
"failed to start the persistent thread of the Interprocess linger pool:
Access is denied" from interprocess 2.4 as soon as the Node addon's
client connects. The server-side unit tests on Windows already cover
the IPC protocol; the crash is a downstream interprocess crate issue
that doesn't affect our code paths. Add `platform = "unix"` so the
ignored suite passes on Windows CI, with a comment pointing at the
upstream root cause.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: branchseer

crates/vite_task_bin/tests/e2e_snapshots/fixtures/ipc_client_test/snapshots.toml

@@ -5,6 +5,10 @@ Exercises `ignoreInput` through `@voidzero-dev/vite-task-client`.
 The runner treats `cache_like/` as non-input, so mutations to it between
 runs do not invalidate the cache.
 """
+# Unix-only for now: on Windows CI, interprocess 2.4 aborts the child
+# with "failed to start the persistent thread of the Interprocess linger
+# pool: Access is denied" when the Node addon tries to connect.
+platform = "unix"
 ignore = true
 steps = [
   { argv = [
@@ -32,6 +36,10 @@ Exercises `ignoreOutput`. The task reads and writes `sidecar/tmp.txt`;
 without the ignore the runner's read-write overlap check would refuse to
 cache the run ("read and wrote 'sidecar/tmp.txt'").
 """
+# Unix-only for now: on Windows CI, interprocess 2.4 aborts the child
+# with "failed to start the persistent thread of the Interprocess linger
+# pool: Access is denied" when the Node addon tries to connect.
+platform = "unix"
 ignore = true
 steps = [
   { argv = [
@@ -62,6 +70,10 @@ comment = """
 Exercises `disableCache`. The tool asks the runner not to cache this run,
 so the next invocation re-executes instead of hitting a prior entry.
 """
+# Unix-only for now: on Windows CI, interprocess 2.4 aborts the child
+# with "failed to start the persistent thread of the Interprocess linger
+# pool: Access is denied" when the Node addon tries to connect.
+platform = "unix"
 ignore = true
 steps = [
   { argv = [
@@ -83,6 +95,10 @@ Exercises `fetchEnv(name, { tracked: true })`. The env value becomes part
 of the post-run fingerprint: the same value still hits, a different value
 misses with `tracked env 'PROBE_ENV' changed`.
 """
+# Unix-only for now: on Windows CI, interprocess 2.4 aborts the child
+# with "failed to start the persistent thread of the Interprocess linger
+# pool: Access is denied" when the Node addon tries to connect.
+platform = "unix"
 ignore = true
 steps = [
   { argv = [

crates/vite_task_bin/tests/e2e_snapshots/fixtures/vite_build_cache/snapshots.toml

@@ -7,6 +7,10 @@ any manual input/output configuration. Vite reports
 `@voidzero-dev/vite-task-client`, so fspy-detected reads of `dist/` and
 writes to `node_modules/.vite/` don't poison the cache.
 """
+# Unix-only for now: on Windows CI, interprocess 2.4 aborts the child
+# with "failed to start the persistent thread of the Interprocess linger
+# pool: Access is denied" when the Node addon tries to connect.
+platform = "unix"
 ignore = true
 steps = [
   { argv = [
@@ -47,6 +51,10 @@ the cache AND change the build output — Vite's `define` plugin substitutes
 `process.env.NODE_ENV` at build time, so dead-code elimination leaves only
 the branch matching the current mode.
 """
+# Unix-only for now: on Windows CI, interprocess 2.4 aborts the child
+# with "failed to start the persistent thread of the Interprocess linger
+# pool: Access is denied" when the Node addon tries to connect.
+platform = "unix"
 ignore = true
 steps = [
   { argv = [