chore: exclude git worktrees from tooling

[erickzhao]

Summary

Enables using git worktrees in this repo without breaking things in the root repository. Worktrees created under .claude/worktrees/ are full nested checkouts, and several CI tools recursed into them.

I built a fake worktree under .claude/worktrees/ and ran each CI tool against it to determine which actually descend in (rather than inferring from glob rules). Three tools needed exclusions:

Tool	Problem
vitest	include: ['**/spec/**/*.spec.ts'] matched specs inside the worktree → every spec runs twice, with potential fixture-path collisions
oxlint	.claude not in ignorePatterns → lints duplicate source
oxfmt	.claude not in ignorePatterns → format-checks duplicate source

Each now excludes **/.claude/**.

Already safe (verified, no change needed)

markdownlint-cli2 + lint-roller (their **/*.md globs don't descend into dot-directories), knip (scoped to package.json workspaces), build tooling (getPackageInfo only reads packages/), the CI artifact upload (packages/*/*/dist/*), and git status (git auto-excludes registered worktrees).

Notes

• A bare .claude entry does not work for oxlint/oxfmt — unlike node_modules, a hidden directory needs an explicit glob (**/.claude/**). Verified the glob form works.
• Nothing under .claude is tracked in git, so excluding it wholesale is safe.
• Scope: covers worktrees under .claude/worktrees/. Worktrees placed elsewhere in the tree would need their own exclusions.

Test plan

• Built a probe worktree under .claude/worktrees/ and confirmed vitest/oxlint/oxfmt each picked up the duplicate files before the fix
• Confirmed all three exclude the probe after the fix
• Confirmed a normal run (no worktree present) is unaffected (oxlint still lints all 255 files)
• Configs remain valid JSON

🤖 Generated with Claude Code