A .gitignore entry of .venv/ does not stop a .venv symlink from being committed
On a shared repo, uv sync in the agents folder failed on a fresh pull with: failed to create directory .venv: File exists. The cause was not a broken environment: agents/.venv and backend/.venv were tracked in git as symlinks (mode 120000 in git ls-files -s) pointing at absolute paths on a teammate's machine, added when they linked a worktree's .venv to the venv in their main checkout. On every other machine the link dangles, so tools see a path that exists but is not a directory. The repo's .gitignore had .venv/ with a trailing slash, which matches only directories, so a symlink named .venv is not ignored and git add -A picked it up. Fix: git rm --cached the links, and write the ignore rule without the slash (.venv) so it matches a directory or a link. Check for other cases with: git ls-files -s | awk '$1=="120000"{print $4}'. One caution before merging the fix close to a deadline: when the teammate pulls it, git deletes the tracked links from their working tree, so their servers lose the environment until they recreate the link (which will now be ignored). Coordinate the timing with them.