Worktrees omit gitignored .claude folder, preventing CLAUDE settings/plugins from roaming

Does this issue occur when all extensions are disabled?: Yes

- VS Code Version:
- OS Version:

Steps to Reproduce:

1. In the repository, have a .claude folder that's gitignored and contains CLAUDE.md, skills, and a claude.settings.json file with enabled plugins.
2. Create a new git worktree for the repository (e.g. `git worktree add ../vscode-worktree `).
3. Open or inspect the newly created worktree.
4. Observe that the .claude folder and its contents are not present in the worktree and the CLAUDE plugins/settings do not roam to the worktree.

Expected behavior:

- Customizations stored in the gitignored .claude folder (CLAUDE.md, skills, claude.settings.json) should be available in worktrees or there should be documentation/behavior that explains why they don't roam.

Actual behavior:

- The .claude folder is absent from newly created worktrees, so CLAUDE settings and enabled plugins configured in the gitignored folder do not appear in worktrees. This leads to fewer customizations in worktrees compared to non-worktree checkouts and caused confusion.

Notes:

- The folder is intentionally gitignored, so this may be expected behavior, but it would be helpful to clarify whether worktrees should copy or otherwise surface gitignored workspace-specific config like .claude, or document recommended approaches to make these settings available across worktrees.

[View original Slack conversation](https://vscodeteam.slack.com/archives/C0AJZ5319PZ/p1783976413239649?thread_ts=1783976413.239649&cid=C0AJZ5319PZ)