What's wrong with this entry?
Anonymous. No account, no email.
What
Worktree setup now checks that entries in .worktreeinclude and settings.local.json copies do not resolve to destinations outside the worktree via committed symlinks, and skips them if they do.
Details
- Logs: "Skipping .worktreeinclude entry: destination escapes worktree via committed symlink: X"
- Logs: "Skipping settings.local.json copy: destination escapes worktree via committed symlink"
- Prevents a worktree setup from being used to read or write files outside the isolated checkout.
Evidence
New safety messages (search for "destination escapes worktree via committed symlink")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.