--effort persists to config.json; project settings can't set effort (1.88.5) #1118

Bug: cmd -p "Reply OK" --effort max runs at max, but also writes "reflection/beam:free": "max" into ~/.commandcode/config.json reasoningEffort. The next plain cmd -p runs at max too. The CLI reference says --effort sets effort "for the session". Expected: no write to config, the way --model doesn't change the saved model.

Feature: {"effort":"max"} in <project>/.commandcode/settings.json or settings.local.json is ignored (the session reports "effort":"high" in --output-format json). Please support project-scoped effort (and ideally model), so a launcher that can't pass flags (scheduled runs from an orchestrator, for example) can choose effort per project without changing every session on the machine.

Repro: Linux, command-code 1.88.5, default model reflection/beam:free.