Queue recovery fix
Default queue workers now include durable tasks that inherit the application's default connection when scanning for overdue work, missing resume tasks and deadlines. Previously, a worker using a resolved name such as redis could skip a task whose stored connection was implicit.
Other connections and queues remain isolated. Existing API and lease defaults are preserved.
Source qualification and published-package verification are recorded in Workflow #751.