fix(ui): simplify Capability and Fuse advanced routing options

[tin-berri]

TLDR

Problem this solves:

• Forecast forms expose three unwanted routing overrides

How it solves it:

• Remove those controls and explicitly disable them on Save

User Flow

Before: Capability and Fuse expose overrides beyond their forecast policy

1. Open /models-and-endpoints/, select Auto-Routers, then edit a Capability or Fuse router
2. Expand Advanced routing options
3. Context Window Escalation and Escalation Keywords appear; Capability also exposes Adaptive Routing

After: both forecast forms use the requested smaller set of options

1. Open /models-and-endpoints/, select Auto-Routers, then edit a Capability or Fuse router
2. Expand Advanced routing options
3. Those three controls are absent; Save explicitly disables them, including previously enabled values

Changes

• Filter the three sections from the shared Capability/Fuse create and edit form
• Save adaptive: false, enable_context_window_escalation: false, and escalation_keywords: []
• Remove the corresponding tuning fields while preserving other stored settings
• Keep Complexity controls and the existing stalled-task and response-format behavior

Relevant issues

• Simplify Capability and Fuse advanced options after feat(ui): configure capability and Fuse v2 classifiers #41315
• Prevent backend defaults or old saved values from activating hidden overrides

Affected release

Linear ticket

Pre-Submission checklist

• Meaningful regression tests: eight failures against the old implementation
• 372 focused tests pass; 249 rerun after test lint cleanup
• Production TypeScript and make check pass without budget changes
• Scope is limited to these dashboard options and their serialization
• Required CI passes on 9d640b86ed; CodeQL reports zero findings across all three languages
• Greptile confidence 5/5 on 9d640b86ed
• Bugbot reports no new issues on 9d640b86ed; Veria reports no security issues

Screenshots / Proof of Fix

Real localhost dashboard, proxy, and isolated Postgres database

Before (174c1ac4ed)

After (9d640b86ed)

Seeded enabled overrides for both classifier types, saved each through the dashboard, and confirmed disabled flags, an empty escalation list, and removed tuning fields via /model/info. Solver assignments, profiles, judge settings, and model overrides were preserved. Cancel kept the seeded configuration unchanged

Stored configuration verification

Type

UI improvement

Caveats (if any)

• Existing Capability/Fuse configurations adopt the disabled settings when saved in the dashboard; API/YAML runtime support remains available

Final Attestation

• Tests cover create/edit serialization, stored overrides, mode switching, and retained Complexity controls

[greptile-apps]

Greptile Summary

This PR simplifies Capability and Fuse router configuration by hiding unsupported advanced routing controls and explicitly disabling their persisted values during create and edit saves.

• Filters Adaptive Routing, Context Window Escalation, and Escalation Keywords from forecast forms.
• Serializes disabled values and removes associated tuning fields for forecast classifiers.
• Preserves unrelated stored router configuration and retains the full controls for non-forecast classifiers.
• Adds focused create, edit, integration, and serialization regression coverage.

Confidence Score: 5/5

The PR appears safe to merge, with the requested create/edit disabling behavior and unrelated-setting preservation covered by the implementation and focused tests.

No actionable new findings remain; there were no changes after the previous review SHA, no prior Greptile findings were supplied for re-checking, and the full PR diff consistently limits the behavior change to forecast classifiers.

Important Files Changed

Filename	Overview
ui/litellm-dashboard/src/components/add_model/ComplexityRouterConfig.tsx	Hides the three removed advanced sections only for Capability and Fuse forecast classifiers.
ui/litellm-dashboard/src/components/add_model/build_complexity_router_config.ts	Explicitly disables hidden forecast overrides on create while retaining existing non-forecast serialization behavior.
ui/litellm-dashboard/src/components/edit_auto_router/edit_auto_router_modal.tsx	Treats forecast escalation keywords as managed during edits so they are cleared without dropping unrelated stored settings.
ui/litellm-dashboard/src/components/add_model/ForecastClassifierConfig.integration.test.tsx	Updates integration coverage to verify that forecast submissions disable adaptive routing.
ui/litellm-dashboard/src/components/add_model/add_auto_router_tab.test.tsx	Verifies hidden forecast controls, retained advanced sections, and explicit disabled create values.
ui/litellm-dashboard/src/components/add_model/build_complexity_router_config.test.ts	Covers disabled forecast overrides, removed tuning fields, and unchanged heuristic serialization.
ui/litellm-dashboard/src/components/edit_auto_router/build_updated_complexity_router_config.test.ts	Verifies edit saves clear hidden forecast overrides while preserving unrelated and future backend settings.
ui/litellm-dashboard/src/components/add_model/forecast_classifier_config.test.ts	Updates forecast configuration expectations to require disabled adaptive routing.

_{Reviews (2): Last reviewed commit: "fix(ui): simplify Capability and Fuse ro..." | Re-trigger Greptile}

[tin-berri]

@greptileai Please review this dashboard follow-up, including explicit disabled values on create/edit saves and preservation of unrelated router settings

[tin-berri]

bugbot run

Please review the current commit for regressions in classifier controls, saved configuration, and retained Complexity behavior

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 9d640b8. Configure here.}