feat(routing): add KiloClaw as a named routing mode

[kilo-code-bot]

Summary

• Added kiloclaw as an explicit routing mode in both FRONTIER_MODE_TO_MODEL and BALANCED_MODE_TO_MODEL in describeRouting
• For Frontier: routes to Claude Opus with reasoning enabled and high verbosity (same config as plan)
• For Balanced: routes to Kimi with reasoning enabled (same config as plan)
• Updated applyResolvedAutoModel to pass 'kiloclaw' directly as the mode instead of mapping it to 'plan', so KiloClaw now appears in the routing description

Verification

• Reviewed the diff manually; the change is additive and consistent with existing mode configurations
• Typecheck could not be run due to missing tsgo binary in the environment

Visual Changes

N/A

Reviewer Notes

Previously, featureHeader === 'kiloclaw' was mapped to 'plan' before lookup, so KiloClaw was silently sharing plan's routing without appearing in describeRouting. Now it has its own named entry, making the routing description accurate and allowing independent tuning in future.

[kilo-code-bot]

Code Review Summary

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	0
WARNING	1
SUGGESTION	0

Issue Details (click to expand)

WARNING

File	Line	Issue
src/lib/kilo-auto-model.ts	266	Passing mixed-case KiloClaw still bypasses the resolver lookup because x-kilocode-mode is not lowercased upstream, so KiloClaw requests fall back to the default code model

Other Observations (not in diff)

N/A

Fix these issues in Kilo Cloud

Files Reviewed (2 files)

• src/lib/kilo-auto-model.ts - 1 issue
• src/tests/openrouter-models-sorting.approved.json - 0 issues

[chrarnoldus]

so it shows up in the description