Keep a Local Setting Out of the Team Contract
Your machine's editor path should not become every colleague's setup problem. Separate shared project behavior from preferences that belong to one checkout.
When Claude Code proposes a settings change, ask which configuration scope owns it and why. A team-wide validation command and a personal display preference have different audiences. Inspect the resulting diff before committing anything.
Try the shared configuration in a fresh disposable checkout with no personal settings copied across. If it fails because it assumes your home directory or a locally stored secret, the shared contract is incomplete. Document required setup through a memorable project command. Keep credentials in their existing secret store rather than turning a convenient local fix into a tracked configuration file.
