Fix missed smooth_target_alpha in smoke test, update stale docstring

Remove smooth_target_alpha from CT002 constructor in
smoke_efficiency_saturation.py (missed during refactor).
Update test_balancer_probe_lockup.py docstring to remove reference
to deleted test_smoother.py.

https://claude.ai/code/session_01LrkYqzhz4EMqBAKG4YAdUR

Author: claude

tests/smoke_efficiency_saturation.py

@@ -109,13 +109,13 @@ def __init__(
             ct_mac=ct_mac,
             active_control=True,
             fair_distribution=True,
-            smooth_target_alpha=0.9,
             deadband=5,
             min_efficient_power=min_efficient_power,
             efficiency_rotation_interval=scaled_rotation,
             efficiency_saturation_threshold=efficiency_saturation_threshold,
             saturation_decay_factor=saturation_decay_factor,
             consumer_ttl=120 / time_scale,
+            reset_fn=None,
             **ct_kwargs,
         )
 

tests/test_balancer_probe_lockup.py

@@ -9,15 +9,11 @@
 (visible in the log for ~1.5 hours until manual restart).  The grid
 drifts ~97 W uncompensated for the entire window.
 
-The root cause is exercised here at two levels:
-
-1. A *unit-level* repro that drives :class:`LoadBalancer.compute_target`
-   with the exact report sequence from the log (two phase-B consumers,
-   scripted power outputs and meter readings) and asserts the active
-   battery receives a reasonable target after the handoff.
-
-2. A *smoother-level* repro in ``test_smoother.py`` covering the
-   ``sample_id`` dedup that fires even when ``raw_total`` has changed.
+The root cause is exercised here via a *unit-level* repro that drives
+:class:`LoadBalancer.compute_target` with the exact report sequence from
+the log (two phase-B consumers, scripted power outputs and meter
+readings) and asserts the active battery receives a reasonable target
+after the handoff.
 """
 
 from __future__ import annotations