fix: handle symlinks when scanning user/project skill directories

[tangdogdaihuman]

Summary

Fix collectSkillsFromRoots to handle symlinked skill directories — the same way collectPluginSkillDirectories already does.

Problem

On Windows (and potentially other platforms), Dirent.isDirectory() returns false for directories that are symbolic links. The user/project skill scanning code only checked isDirectory(), silently skipping all symlinked skills in ~/.claude/skills/. In practice this caused ~14 of 22 user skills to be hidden from the desktop settings UI.

Fix

Changed the guard in collectSkillsFromRoots from:

if (!entry.isDirectory() || ...)

to:

if ((!entry.isDirectory() && !entry.isSymbolicLink()) || ...)

This exactly matches the pattern already used at line 317 in collectPluginSkillDirectories.

Test plan

• On Windows with symlinked skills in ~/.claude/skills/, open Settings > Skills tab — all 22 skills should now appear instead of 8
• Real directories (non-symlinks) continue to work as before
• Symlinks pointing to non-directories are filtered by loadSkillMeta returning null

[github-actions]

PR quality triage

Changed areas: area:server

CLI core policy: No CLI-core policy block detected.

Missing-test policy: No missing-test policy block detected.

Coverage baseline policy: No coverage-baseline policy block detected.

CLI core files:

• none

Coverage policy files:

• none

Expected checks:

• change-policy
• desktop-checks
• server-checks
• desktop-native-checks
• coverage-checks

Test coverage signals:

• No obvious missing-test signal from changed paths.

Risk notes:

• No special risk notes from changed paths.

Hard merge gates still come from GitHub Actions, not AI review.

Dosu handoff: Dosu can be used as the AI reviewer for risk explanation, missing-test prompts, and maintainer Q&A. If it does not comment automatically from the PR template, ask:

@dosubot review this PR for changed-area risk, missing tests, docs impact, desktop startup risk, and CLI core impact.