refactor(policies): rename least_load to kv_pressure_weight

[slin1237]

No description provided.

[coderabbitai]

📝 Walkthrough

Walkthrough

The PR renames the LeastLoadPolicy weight parameter from lambda to kv_pressure_weight across configuration, validation, implementation, instantiation, and Python binding layers, maintaining the same default value and scoring behavior throughout the stack.

Changes

LeastLoad Configuration Parameter Rename

Layer / File(s)	Summary
Configuration schema and validation model_gateway/src/config/types.rs, model_gateway/src/config/validation.rs	PolicyConfig::LeastLoad enum field renamed from lambda to kv_pressure_weight; serde default function renamed from default_least_load_lambda() to default_least_load_kv_pressure_weight() preserving the 1.5 default; validation logic checks the new field with the same finite/non-negative constraints.
Core policy implementation and public API model_gateway/src/policies/least_load.rs	LeastLoadPolicy struct field renamed to kv_pressure_weight; new exported constant DEFAULT_KV_PRESSURE_WEIGHT replaces DEFAULT_LAMBDA; public constructor with_kv_pressure_weight() replaces with_lambda(); score formula updated to use the renamed field.
Policy instantiation in factory and CLI model_gateway/src/policies/factory.rs, model_gateway/src/main.rs	PolicyFactory::create_from_config and CliArgs::parse_policy updated to construct LeastLoadPolicy with kv_pressure_weight parameter.
Python bindings exposure bindings/python/src/lib.rs	Router::to_router_config policy conversion updated to set kv_pressure_weight instead of lambda for PolicyType::LeastLoad.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• lightseekorg/smg#1629: Implements the initial least_load policy with lambda parameter; this PR builds on that foundation by renaming the configuration weight parameter to kv_pressure_weight across all usage sites.

Suggested labels

python-bindings, tests, model-gateway

Suggested reviewers

• CatherineSue
• key4ng
• gongwei-130

Poem

🐰 A weight renamed across the stack so wide,
From lambda's grasp to kv_pressure's stride,
Config and validation, factory and bind,
All dancing in sync with semantic redesign—
Same score, new name, configuration refined! 🌟

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 37.50% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly summarizes the main change: renaming the least_load policy's lambda parameter to kv_pressure_weight, which is the central refactor across all modified files.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch refactor/least-load-kv-pressure-weight

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request renames the lambda parameter to kv_pressure_weight across the codebase, including configuration, validation, and policy implementations, to improve clarity. However, renaming this configuration field directly breaks backward compatibility for existing deployments. It is recommended to add a Serde alias to ensure a smooth upgrade path.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c5b35134bb

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[claude]

Clean, well-executed rename. All references updated consistently across config types, validation, factory, CLI args, Python bindings, and tests. No behavior change, default preserved at 1.5. One minor nit posted about adding a serde alias for the old field name — low risk since the feature only landed today.

Summary: 0 🔴 Important · 1 🟡 Nit · 0 🟣 Pre-existing