6eb9c41407
CI / build (pull_request) Successful in 44s
CI / helm (pull_request) Successful in 53s
CI / lint (pull_request) Successful in 59s
CI / quality (pull_request) Successful in 1m0s
CI / push-validation (pull_request) Successful in 44s
CI / typecheck (pull_request) Successful in 1m9s
CI / security (pull_request) Successful in 1m10s
CI / unit_tests (pull_request) Successful in 5m47s
CI / docker (pull_request) Successful in 1m34s
CI / integration_tests (pull_request) Successful in 8m33s
CI / coverage (pull_request) Successful in 9m9s
CI / status-check (pull_request) Successful in 4s
Address reviewer blocking issues on PR #11003: 1. Remove unused `import os` and inner `MagicMock` re-import from the gemini fallback step definitions (ruff F401). 2. Remove `@tdd_expected_fail` from the TDD feature now that the registry fix makes the scenario pass; keep `@tdd_issue` / `@tdd_issue_4750` as permanent regression markers. 3. Rewrite three feature step texts to use the env-var step defs that already exist in `provider_registry_steps.py` instead of duplicating them (drops the `env var` phrasing the original feature used and that had no matching step def). 4. Add `"gemini"` to `FallbackSelector.DEFAULT_FALLBACK_ORDER` after `"google"` so the actor-configured fallback chain mirrors the registry-level fix. 5. Rename three of the new feature/step pairs to avoid ambiguous-step collisions that crashed every behave-parallel worker at module-load time (the root cause of the "8 features errored, 0 scenarios" pattern): - `the result should be ProviderType "GEMINI"` collided with `cli_steps.py:138`'s `@then("the result should be {expected}")`; renamed to `the gemini fallback default should be ProviderType "GEMINI"`. - `the result should be None` had the same collision; renamed to `the clean gemini registry default should be None`. - `@given("I have the ProviderRegistry class")` was duplicated in `provider_registry_steps.py:186`; the duplicate is removed and the existing definition is reused. ISSUES CLOSED: #10906