Clarify timeout comment and camera log message

Tweak wording for clarity in two places: update STOP_WORKER_TIMEOUT comment to better describe waiting in the STOPPING state before scheduling background reaping, and reflow the MultiCameraController critical log message into a single, spaced string to avoid awkward concatenation. These are documentation/logging refinements only and do not change runtime behavior.

Files modified:
- dlclivegui/services/dlc_processor.py: adjust timeout comment
- dlclivegui/services/multi_camera_controller.py: reformat and clarify critical log message

Author: C-Achard

dlclivegui/services/dlc_processor.py

@@ -21,7 +21,7 @@
 from dlclivegui.temp import Engine  # type: ignore # TODO use main package enum when released
 
 logger = logging.getLogger(__name__)
-STOP_WORKER_TIMEOUT = 10.0  # seconds to wait for worker thread to stop before STOPPING state and reaping
+STOP_WORKER_TIMEOUT = 10.0  # # seconds to wait in STOPPING state before scheduling background reaping
 
 try:  # pragma: no cover - optional dependency
     from dlclive import (

dlclivegui/services/multi_camera_controller.py

@@ -271,9 +271,9 @@ def stop(self, wait: bool = True) -> None:
                 self._expected_cameras = 0
 
                 LOGGER.critical(
-                    "Force stop failed for camera threads: %s."
-                    "Sending all_stopped to leave GUI in running state,"
-                    "but background camera threads may still be active and interfere with future camera starts."
+                    "Force stop failed for camera threads: %s. "
+                    "Sending all_stopped to leave GUI in running state, "
+                    "but background camera threads may still be active and interfere with future camera starts. "
                     "Application restart may be required.",
                     still_running,
                 )