docs(kilo-auto-model): clarify plan model usage for KiloClaw

[kilo-code-bot]

Summary

• Added inline comments to src/lib/kilo-auto-model.ts clarifying how KiloClaw requests are routed to the "plan" workflow mode model, ensuring they always get the highest-reasoning model in each tier (Claude Opus for frontier, Kimi for balanced).
• Disambiguated the "plan" key in mode-to-model maps: it refers to a Kilo Code workflow mode (high-level reasoning/planning), not a billing/subscription plan.
• Explained the difference between KiloClaw routing (forced to "plan" mode) and Kilo Code extension routing (uses the client-sent mode like code, architect, ask, etc.).

Verification

• Verified only comment additions via git diff — no logic changes
• Confirmed file parses correctly (no syntax errors introduced)

Visual Changes

N/A

Reviewer Notes

The word "plan" is overloaded in this codebase: it means a workflow mode in the mode-to-model routing maps, and a billing plan in the KiloClaw billing system. The added comments make this distinction explicit to prevent future confusion.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (1 files)

• src/lib/kilo-auto-model.ts

---

_{Reviewed by gpt-5.4-20260305 · 116,511 tokens}