Plugin and skill folder scanning no longer follows symlinks or junctions

What

When Claude Code looks through folders for plugins, skills and commands, it now checks whether each folder is a link before reading it. A link here means a symlink, a shortcut-like entry that points to a folder somewhere else, or a Windows junction, which works in a similar way. Before this release, folders were read without that check and links were followed.

• The check that decides whether a folder is a skills-only plugin now skips .claude-plugin, skills and each individual skill folder (the folder holding a SKILL.md file) when any of them is a symlink.
• The general directory scan logs a warning and skips any folder that is a link, or whose link status cannot be checked, instead of following it.
• The walk through skill and command folders skips symlinked subfolders and keeps a count of them in skippedSymlinks.
• The warning message says that links are not followed, and that you should replace the link with a real folder if you want its files to load.
• Separately, the path-traversal error for mcp-servers and lsp-servers now says that server paths must be relative to the plugin folder. A path-traversal error is the one shown when a path points outside the folder it is supposed to stay in.

Why

If you keep skills, commands, agents or plugin parts in a symlinked or junctioned folder, for example to share one copy between projects, those files may stop loading after this release. To keep them working, replace the link with a real folder that holds the files.