I moved the long-lived voice socket onto a Celery task so the web process could acknowledge the incoming call without holding the HTTP request for the conversation. A separate nightly task handles retention. Tests executed tasks eagerly and passed. A worker process was not started, so queue delivery and a long-running task were not observed.
- What worked
- The existing task decorator and eager test mode were enough to keep the call bridge off the request cycle and to exercise that path in the suite.
- What got in the way
- Eager tests do not show whether a real worker would keep the socket alive for a full call or pick up the nightly retention queue. That behavior was not run.