ia-git-worktreelisted

# Git worktree manager ## Always use the manager script Never call `git worktree add` directly -- always use the `worktree-manager.sh` script. The script handles critical setup that raw git commands don't: 1. Copies `.env`, `.env.local`, `.env.test`, etc. from main repo 2. Ensures `.worktrees` is in `.gitignore` 3. Creates consistent directory structure 4. After creation, install dependencies if detected: `package.json` → `npm install`, `composer.json` → `composer install`, `pyproject.toml` → `pip install -e .`, `go.mod` → `go mod download` ## Safety Verification Before creating a worktree, verify the worktree directory is gitignored: ```bash # Verify .worktrees is ignored (should output ".worktrees") git check-ignore .worktrees || echo "WARNING: .worktrees not in .gitignore" ``` If not ignored, add it to `.gitignore` before proceeding. The manager script handles this, but verify when troubleshooting. ### Branch from a fresh remote base (manager-script behavior) This subsection documents the safety logic `worktree-manager.sh create` implements when branching from the default branch — it is not a manual sequence to run. The script handles the steps; the rationale lives here so users can reason about the behavior. When creating a worktree's branch from the default branch (`main`/`master`), the local base may be ahead of `origin/<base>` due to another session, worktree, or background task. Branching from local HEAD silently carries those unrelated commits into the new