Feature flag (tengu_grey_step2) silently overrides explicit effortLevel setting

Bug

The Growthbook feature flag tengu_grey_step2 (cached in .claude.json) silently overrides the user's explicit "effortLevel": "max" setting in settings.json, resetting effort to auto/medium.

Steps to reproduce

1. Set "effortLevel": "max" in ~/.claude/settings.json
2. Observe that tengu_grey_step2 in .claude.json has "enabled": true with messaging about recommending medium effort for Opus
3. UI shows effort as "auto" despite the explicit user setting

Expected behavior

An explicit user setting in settings.json should take precedence over a server-pushed feature flag. A/B tests should not silently override user preferences - especially ones the user deliberately configured.

Workaround

Manually set tengu_grey_step2.enabled to false in .claude.json. However, this may be overwritten on the next Growthbook sync.

Environment

• Windows 11 Enterprise
• Claude Code (VS Code extension)
• Model: opus[1m]