fix(providers): enforce per-plan budget in FallbackSelector.select() #10747

Merged

HAL9000 merged 1 commits from fix/issue-10485-fallback-selector-budget-limits into master

2026-06-06 13:43:58 +00:00

Author	SHA1	Message	Date
HAL9000	1b12af2765	fix(providers): enforce per-plan budget in FallbackSelector.select() CI / lint (pull_request) Successful in 40s Details CI / helm (pull_request) Successful in 35s Details CI / build (pull_request) Successful in 56s Details CI / quality (pull_request) Successful in 1m29s Details CI / typecheck (pull_request) Successful in 1m36s Details CI / security (pull_request) Successful in 1m35s Details CI / push-validation (pull_request) Successful in 26s Details CI / unit_tests (pull_request) Successful in 6m2s Details CI / docker (pull_request) Successful in 1m44s Details CI / integration_tests (pull_request) Successful in 9m56s Details CI / coverage (pull_request) Successful in 12m16s Details CI / status-check (pull_request) Successful in 17s Details Imported CostMetadata into fallback_selector.py to access per-plan budget data. Extended FallbackSelector.__init__ with cost_metadata: CostMetadata \| None = None and stored it in self._cost_metadata. Implemented per-plan budget check in FallbackSelector.select() immediately after the daily budget validation to enforce per-plan limits during selection. Added two new TDD scenarios to features/cost_controls.feature to exercise per-plan budget behavior, tagged @tdd_issue @tdd_issue_10471. Added new test steps at features/steps/tdd_fallback_plan_budget_steps.py to support the new scenarios. ISSUES CLOSED: #10485	2026-06-06 09:24:27 -04:00