086599b670
CI / lint (pull_request) Successful in 54s
CI / push-validation (pull_request) Successful in 29s
CI / typecheck (pull_request) Successful in 1m11s
CI / build (pull_request) Successful in 1m4s
CI / helm (pull_request) Successful in 1m7s
CI / quality (pull_request) Successful in 1m33s
CI / security (pull_request) Successful in 1m40s
CI / unit_tests (pull_request) Successful in 6m24s
CI / integration_tests (pull_request) Successful in 11m2s
CI / coverage (pull_request) Successful in 11m50s
CI / docker (pull_request) Successful in 1m44s
CI / status-check (pull_request) Successful in 4s
The module docstring at lines 8-9 claimed the scenario was tagged ``@tdd_expected_fail`` so CI would invert a failing result while the bug existed. Both claims are false: the implementation already holds ``_registry_lock`` around all reads and writes (src/cleveragents/ providers/registry.py:800,817), so the scenario passes normally, and the feature file deliberately does not carry ``@tdd_expected_fail``. Rewrite the module docstring to describe the current behaviour — the lock is present, the scenario passes, the tag is intentionally omitted, and the test now functions as a regression guard against the lock being removed. Update the two inner step docstrings in the same way so "this assertion fires when the bug exists" no longer contradicts the fixed implementation. No runtime behaviour changes. The lint gate passes. ISSUES CLOSED: #10409