[eric] workflows: the restart-loop-guard pause notice called a nonexistent broadcast; it never reached the user (linter catch)

backend/apps/agents/manager/session/SessionPersistence.py

@@ -67,7 +67,9 @@ class SessionPersistence(AgentManagerProtocol):
         that cannot resume just keeps its amber chip."""
         for sid in list(getattr(self, "crash_resume_queue", []) or []):
             try:
-                await self.send_message(
+                # send_message lives on the Messaging mixin; AgentManager composes both.
+                p_send = getattr(self, "send_message")
+                await p_send(
                     sid,
                     "[Automated message from OpenSwarm itself, not written by your user] The app "
                     "restarted while you were mid-task; nothing was lost. Continue exactly where "

backend/apps/workflows/notifier.py

@@ -42,7 +42,7 @@ def notify_workflow_paused_by_guard(wf: Workflow) -> None:
                         "workflow, then re-enable its schedule."),
         }
         asyncio.get_running_loop().create_task(
-            ws_manager.broadcast("workflow:schedule_paused_by_guard", payload))
+            ws_manager.broadcast_global("workflow:schedule_paused_by_guard", payload))
     except Exception:
         logger.debug("guard-pause notify failed", exc_info=True)
 

backend/tests/test_wedge_verdict.py

@@ -3,7 +3,6 @@ be shot at the first deadline; a stale one must; nothing survives the late deadl
 kills in one loaded evening were every one of the "MCP disconnected" reports."""
 import os
 import tempfile
-import time
 from backend.apps.agents.manager.streaming.unwedge_sidecar import (
     HEARTBEAT_FRESH_S,
     LATE_WEDGE_SECONDS,