fix(global-settings): ignore the model and effort keys Claude Code writes in settings.json (v2.7.1)

[WilcoLouwerse]

Problem

Since v2.7.0, check-settings-version.sh compares the installed ~/.claude/settings.json with the canonical copy at session start and skips only the model key. Under relock option (B), Claude Code writes more than model into that file. Its main extra write is the effort level, which /effort and the effort picker save per model as modelSettings.<model>.effortLevel. Every effort change therefore raised FILES OUT OF SYNC (top-level keys: modelSettings). Following the repair then overwrote the file and threw the user's choice away.

Change

The comparison now leaves out every top-level key that the client itself writes for a model or effort choice:

Key	Written by
model	the VSCode model picker and /model
modelSettings	/effort and the effort picker, per model
effortLevel	the same choice when it cannot be keyed by model
fastMode	/fast
advisorModel	/advisor
switchModelsOnFlag	the VSCode toggle that switches model when a safeguard flags a message

The list comes from the Claude Code 2.1.286 extension and CLI: the settings schema descriptions, the webview's writable-settings allowlist and the CLI's userSettings writes. Hooks, permissions and every other key still count as drift.

• VERSION 2.7.0 → 2.7.1, because an installed hook script changed.
• README.md and docs/claude/global-claude-settings.md now name the skipped keys.

Tests

• tests/test-check-settings-version.sh: 81 passed, 0 failed. New cases:
  • 7b: all six keys set → up to date.
  • 7c: modelSettings next to a permissions change → only permissions is reported.
• Negative control: run against the v2.7.0 script, exactly the three new assertions fail.

🤖 Generated with Claude Code