docs(lsp): replace "git worktree" with "git repository" in LSP docs

The word "worktree" (a git subcommand feature for parallel checkouts)
was used interchangeably with "repository" in the LSP docs, causing
confusion. LSP only requires a git-initialized directory, not an actual
worktree.

Fixes two instances: section "When LSP runs" and the troubleshooting
"Editing a file outside any git repo" heading.
This commit is contained in:
freqyfreqy 2026-05-13 23:05:13 -07:00 committed by Teknium
parent 796c8a2d63
commit 8de26e280e

View file

@ -21,7 +21,7 @@ install, no separate daemon to manage.
## When LSP runs ## When LSP runs
LSP is gated on **git workspace detection**. When the agent's working LSP is gated on **git workspace detection**. When the agent's working
directory (or the file being edited) is inside a git worktree, LSP directory (or the file being edited) is inside a git repository, LSP
runs against that workspace. When neither is in a git repo, LSP runs against that workspace. When neither is in a git repo, LSP
stays dormant — useful for messaging gateways where the cwd is the stays dormant — useful for messaging gateways where the cwd is the
user's home directory and there's no project to diagnose. user's home directory and there's no project to diagnose.
@ -249,5 +249,6 @@ the next edit re-spawns.
**Editing a file outside any git repo** **Editing a file outside any git repo**
By design, LSP only runs inside git worktrees. Run `git init` in the By design, LSP only runs inside a git repository. If the project isn't
project, or accept the in-process syntax-only fallback. yet initialized, run `git init` to enable LSP diagnostics. Otherwise the
in-process syntax-only fallback applies.