Move dt/sim_warp_factor from config.json to CLI flags

Both are run-mode knobs (how fast to drive this particular process),
not config.json material (a plant/hardware description that stays the
same regardless of how a run happens to be invoked) - --dt and
--sim-warp-factor, defaulting to 1.0 each (real time, 1-simulated-
second ticks) unless a dev/test run asks for a faster warp explicitly.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019qvu5giu7gvRCyEWzf2Vpx

README.md

@@ -114,7 +114,7 @@ callbacks, e.g.:
   real, unmodeled kettle, has no model to feed)
 
 Each component runs inside its own `ATask` at a configurable interval
-(`Controller.dt`, scaled by `sim_warp_factor`) and pushes state changes onto a
+(`--dt`, scaled by `--sim-warp-factor`) and pushes state changes onto a
 keyed WebSocket channel that any connected client can subscribe to and send
 commands back on (e.g. `{"TempCtrl": {"Soll": {"Temp": 65}}}`).