abcd's lab snapshot (internal/core/lab/mint.go) and launch parity check (internal/core/launch/parity.go) run `git checkout` through gitutil's isolated environment, which drops the person's global git config, so in a repository whose Git LFS filter is set up by a normal global `git lfs install` their snapshot trees hold LFS pointer text instead of the real files. Same cause as iss-2610111729375108 (fixed for lane worktrees by gitutil.WorkingTreeCommand); noticed by that fix's sweep on 2026-10-11, not reproduced for these two callers.

Frontmatter

.abcd/work/issues/open/iss-2610112042253783-lab-and-parity-checkouts-get-lfs.md
open on GitHub ↗ · commit history ↗

mentions1

• iss-2610111729375108abcd's lane worktrees and restarts in a repository that uses Git LFS hold LFS pointer text instead of the real files. Lane creation (`git worktree add`, internal/core/implement/loop/lane.go) and a restart's `reset --hard` (restart.go) run through gitutil's isolated environment, which sets GIT_CONFIG_GLOBAL=/dev/null (internal/gitutil/repo.go), so the filter that a normal, global `git lfs install` defines is never seen and nothing is smudged. Reproduced 2026-10-11 with git-lfs 3.7.1: in a repository whose image is tracked by LFS, the person's own `git worktree add` writes the image's bytes, while the same command with GIT_CONFIG_GLOBAL=/dev/null writes `version https://git-lfs.github…` pointer text. The implementer then builds and tests against placeholders. This is abcd changing how a repository works, which the security scope rule (principle abcd-fixes-what-it-adds) forbids.