Repository navigation
refactor(auto-routing): remove auto-decider candidate sync - #7541
Conversation
Code Review SummaryStatus: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (23 files)
Notes: the previously flagged Fix these issues in Kilo Cloud Previous Review Summaries (2 snapshots, latest commit b034571)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit b034571)Status: 1 Issue Found | Recommendation: Address before merge Executive SummaryThe migration-drop warning is resolved by removing Overview
Issue Details (click to expand)WARNING
Files Reviewed (3 files)
Fix these issues in Kilo Cloud Previous review (commit 27b2b3a)Status: 2 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (26 files)
Reviewed by deepseek-v4.1-flash · Input: 176.1K · Output: 21.9K · Cached: 1.5M Review guidance: REVIEW.md from base branch |
8331b42 to
4c5c6ad
Compare
bot: Remove the auto-decider sync. The decider candidates for the efficient and frontier routers now come only from the models an admin picks. This PR is stacked on #7519.
Change
autoDeciderModels, exclusion and min/max cost config, with its admin UI.deciderModelsis the admin list.0017dropsconfig_auto_decider_models,config_auto_decider_exclusionsand the auto-decider cost columns.terminal-bench.tsstays, because the OpenRouter model sync still uses it.Effect after deploy
platform_requestedat the next reconcile, and the next publish ranks only configured pairs.Verification
auto-routing303,auto-routing-benchmark520 tests pass. Web admin, model-stats and client Jest pass 1132 tests. Typecheck passes, and type-aware lint is clean.0017. The rows survive.