Problem

Four test cases create a dangling symlink with fs.symlinkSync() (to exercise statSync catch branches) without guarding for platforms where symlink creation isn't permitted. On Windows without Developer Mode / admin rights, fs.symlinkSync throws EPERM, so these tests fail and npm test is red on Windows:

Reproduction (Windows 11, Node 24, non-admin)

$ node tests/ci/validators.test.js
  ✗ skips unreadable skill directory entries without error (broken symlink)
    Error: EPERM: operation not permitted, symlink 'C:\nonexistent\target\path' -> '...\broken-skill'
  Results: Passed: 164, Failed: 1

Same EPERM failure in the session-manager (×2) and utils rounds.

Fix

Wrap each symlinkSync in try/catch and skip cleanly on failure, mirroring the convention already used in this repo — see tests/ci/validators.test.js Round 57 and tests/hooks/config-protection.test.js:

try {
  fs.symlinkSync('/nonexistent/...', linkPath);
} catch {
  // Skip on systems that don't support symlinks (e.g. Windows without
  // Developer Mode / admin rights, where symlinkSync throws EPERM).
  console.log('    (skipped — symlinks not supported)');
  /* clean up temp dirs */ return;
}

On Linux/macOS and admin Windows the symlink still succeeds and the tests run exactly as before; only the unsupported-symlink path now skips instead of failing. Test-only change — no runtime/source behavior is affected.

Verification

After the change, on the same Windows machine:

tests/ci/validators.test.js        Results: Passed: 165, Failed: 0   (was 164/1)
tests/lib/session-manager.test.js  Results: Passed: 169, Failed: 0   (was 167/2)
tests/lib/utils.test.js            Failed: 0                         (was 1)

The guarded tests print (skipped — symlinks not supported). npx eslint on the three files and scripts/ci/check-unicode-safety.js both pass.

Notes / out of scope

• tests/scripts/trae-install.test.js also uses symlinkSync, but that file is already skipped wholesale on Windows ("Trae shell scripts are Unix-only"), so it does not fail — intentionally left untouched.
• Separately observed on Windows (not addressed here, possible follow-ups): a timeout-enforcement test in tests/integration/hooks.test.js and a slow tests/lib/agent-compress.test.js.

🤖 Generated with Claude Code

Summary by cubic

Guarded dangling-symlink tests so the suite passes on Windows where symlink creation needs admin/Developer Mode. When fs.symlinkSync throws EPERM/EACCES, tests skip and clean up; other errors rethrow to avoid masking real failures.

• Bug Fixes
  • Wrapped fs.symlinkSync in try/catch in tests/ci/validators.test.js, tests/lib/session-manager.test.js (×2), and tests/lib/utils.test.js; on EPERM/EACCES log skip, clean up, and return; otherwise rethrow.
  • No source/runtime changes; behavior unchanged on systems where symlinks work.

^{Written for commit 0dc9692. Summary will update on new commits.}

Summary by CodeRabbit

• Tests
  • Improved test resilience on systems where creating symlinks is restricted. Tests that attempt to create broken symlinks now catch unsupported errors, log a skip, clean up temporary test artifacts, and return early instead of failing. When symlink creation succeeds, original assertions still run—improving cross-platform reliability of the test suite.