/effort always reports 'max' regardless of effort set via /model

Bug

/effort always reports max (Maximum capability with deepest reasoning (Opus 4.6 only)) regardless of what effort level was set via /model.

Steps to reproduce

1. /effort → reports max
2. /model → select Opus 4.6 with medium effort
3. /effort → still reports max
4. /model → select Opus 4.6 with low effort
5. /effort → still reports max
6. /model → select Sonnet 4.6 with medium effort
7. /effort → still reports max

Expected behavior

/effort reflects the effort level currently active (as set by /model).

Actual behavior

/effort always returns max — the two commands are out of sync.

Version

1.2.1.76

Notes

Related to the recently shipped fix for "Fixed --effort CLI flag being reset by unrelated settings writes on startup" — the fix may have introduced or exposed a read-side issue where /effort reads from a different source than /model writes to.