feat(mobile): force efficient model as the dev default - #5018
Conversation
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Executive SummaryIncrementally re-reviewed the follow-up commits that promote the dev-only Files Reviewed (3 files)
Previous Review Summary (commit e0c26cf)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit e0c26cf)Status: No Issues Found | Recommendation: Merge Executive SummaryReviewed the dev-only Files Reviewed (3 files)
Reviewed by kimi-k3 · Input: 119.9K · Output: 5.7K · Cached: 182.3K Review guidance: REVIEW.md from base branch |
Move the kilo-auto/efficient dev default above the server, local, and organization overrides. Release builds keep the previous priority.
Summary
kilo-auto/efficientfor a new mobile session.Why
Development sessions need one stable efficient model. A stale preference from an earlier
session must not change the dev default. Release builds must not change at all.
How
pickAutoSelectedModel.kilo-auto/efficientfirst when__DEV__is true and the catalog holds the model.lastSelected, then the local persisted preference, then the organization default, thenthe first catalog entry.
Verification
pnpm testfromapps/mobile— passed, 330 files and 3041 tests.pnpm typecheckfromapps/mobile— passed.pnpm lintfromapps/mobile— passed.E2E
Bot E2E verification uses an iOS development build and checks the fresh new-session picker.
Visual Changes
N/A — this change alters the selected model, not the picker layout.