least-cost-routing

# Least-cost routing (route_request) `route_request` (sync) and `route_request_async` (async) pick the **cheapest eligible `(provider, model)`** candidate that meets your constraints, then dispatch it through the normal provider path. They are **dormant by default**: registered only when `[least_cost].enabled = true` in `~/.llm-cli-gateway/config.toml` and Personal Agent Config Kit is disabled. If the tools are absent, routing is off or Kit is active; use a specific provider tool only when that tool is valid for the active boundary. ## Never use this for a mandatory exhaustive review Least-cost routing is for a model-agnostic, cost-constrained task. It is not a review-completion mechanism. Do not use `route_request`, `route_request_async`, `select:"cheapest"`, `select:"cheapest_per_tier"`, `maxCostUsd`, a budget waiver, or output/token caps to restrict a required cross-provider review. A complete review must use the local stdio gateway MCP surface and its explicit required reviewer roster until every reviewer returns an evidence-backed unconditional approval. If a reviewer cannot run, repair/retry it or report the review incomplete/blocked; do not replace it with the cheapest candidate. When the user explicitly authorizes full provider permissions and native MCP access for that mandatory review, use `multi-llm-review`'s full-access protocol: build and launch the current target checkout's `node dist/index.js --transport=stdio` server, not a global gateway; reapply each pro...