Without this it drifts again on the next wiring line: every daemonAPI field
set on a fully wired deployment, and the worker set by name at the full set and
at the floor.
run() wired the daemon twice and the lists drifted: seven workers started
untracked on the unlock path, a shadowed WaitGroup hid the voice server, and
nexus and getMCPServers were never set after a passkey unlock.
newDaemonAPI and startBackground in cmd/mavend/boot.go are the one place both
paths go through now. backgroundWorkers is the pure list behind the second, so
the set is assertable without a running daemon.
claude