squad link / squad init --remote should auto-add .squad/config.json to .gitignore #202

Problem

.squad/config.json is written by squad link and squad init --remote to store the teamRoot path for remote squad mode. The teamRoot field is an absolute path to the developer's local machine — it is inherently machine-local and must never be committed.

Currently, .squad/config.json is not added to .gitignore by any of these commands, so running git add .squad/ accidentally includes it. This is how a file containing /home/username/code/squad ended up in a PR branch.

Expected behavior

squad link and squad init --remote should automatically append .squad/config.json to the user's .gitignore (creating it if it doesn't exist), the same way tools like dotenv or npm init manage their own ignore entries.

Notes

• Similar pattern: squad init already handles .squad/orchestration-log/ and .squad/log/ in .gitignore
• The fix is in packages/squad-cli/src/cli/commands/link.ts and packages/squad-cli/src/cli/commands/init-remote.ts
• Detected during PR review for issue squad init installs generic CI/CD workflows without opt-in #201