This could happen because there was a pause between creating the worktree and adding it to the list of tracked local worktrees, and so we might end up adding the same worktree twice when calling `create_local_worktree` in rapid succession.
This could happen because there was a pause between creating the worktree and adding it to the list of tracked local worktrees, and so we might end up adding the same worktree twice when calling `create_local_worktree` in rapid succession.