test(core): fix autoMode test fixture on Windows

The fixture's mock isPathWithinWorkspace used path.sep to join the root
prefix, but the hard-coded test paths use forward slashes regardless of
OS. On Windows path.sep is '\\', so prefix matching failed and L5.1
fast-path tests returned false (and the L5.1-gating test then fell into
the classifier branch, hitting an undefined getToolRegistry mock).

Hard-code '/' in the fixture — it controls only intra-file consistency
between mock roots and mock paths, not real workspace behavior.

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

Author: LaZzyMan

packages/core/src/permissions/autoMode.test.ts

@@ -5,7 +5,6 @@
  */
 
 import { describe, it, expect, vi } from 'vitest';
-import * as path from 'node:path';
 import {
   SAFE_TOOL_ALLOWLIST,
   evaluateAutoMode,
@@ -108,10 +107,10 @@ describe('isInSafeToolAllowlist', () => {
 function makeConfig(workspaceRoots: string[]): Config {
   return {
     getWorkspaceContext: () => ({
+      // Test fixture: roots and paths in this file use POSIX-style separators
+      // regardless of OS, so hard-code '/' (not path.sep) for the prefix check.
       isPathWithinWorkspace: (p: string) =>
-        workspaceRoots.some(
-          (root) => p === root || p.startsWith(root + path.sep),
-        ),
+        workspaceRoots.some((root) => p === root || p.startsWith(root + '/')),
     }),
   } as unknown as Config;
 }