Avoid core.excludesfile for worktree-local ignores due to p10k gitstatus mismatch

Background

In a linked Git worktree, p10k/powerlevel10k can show an untracked marker such as ?1 even when git status reports a clean working tree.

Observed case:

• Worktree: ~/projects/issue-recorder-wt-change-domain
• Git CLI: git status / git status --porcelain --untracked-files=all reports clean
• p10k VCS segment: shows ?1
• The ignored path was ignored via worktree-local core.excludesfile:
  • .git/worktrees/<worktree>/config.worktree
  • core.excludesfile = .../.git/worktrees/<worktree>/info/exclude

When disabling the configured excludes file, Git also reports the same untracked path, which confirms p10k/gitstatus is effectively not honoring this core.excludesfile setup.

Related upstream issue

• https://github.com/romkatv/gitstatus/issues/299

This appears related to gitstatus/gitstatusd not fully respecting core.excludesfile.

Decision / guidance

Avoid relying on core.excludesfile for worktree-local ignore rules when p10k/gitstatus prompt accuracy matters.

Prefer one of:

1. repo .gitignore when the ignore rule is shareable;
2. common repo exclude at .git/info/exclude when local-only but shared across worktrees is acceptable;
3. accepting/turning off p10k untracked display if worktree-local excludes are required.

Notes

At the time of investigation, local p10k was using gitstatusd v1.5.4; no confirmed upstream fix was found.

The issue names worktree-local .git/worktrees//config.worktree and info/exclude paths, plus .git/info/exclude, but no repository documentation file or test. First inspect the existing documentation and ignore-file guidance. Done means recording the p10k/gitstatus limitation and the listed alternatives without implying an upstream fix.