Symlinks inside a command-produced plugin directory are now checked before being installed.
What's wrong with this entry?
When a plugin install produces a directory whose top-level entries are symlinks, each entry is now run through the same untrusted-link check already used elsewhere, so a link pointing at a network location or through an untrusted link is refused instead of being linked into the install.
- The refusal message names the path and the reason.
- Unconditional.
points at a network location or through a link that cannot be trusted; refusing to link it
Strings lifted out of the shipped bundle, so the claim above can be checked against them.