The two boot paths have drifted: seven untracked workers and two unset daemonAPI fields #189

2026-08-06T21:33:35+02:00

claude commented

2026-08-06 21:33:35 +02:00

Closes Vikunja #639.

Acceptance criteria and quality gate are in TASK.md on this branch.
Review the review, not the diff — leave comments and the agent will apply them via task start 639.

Closes Vikunja #639. Acceptance criteria and quality gate are in `TASK.md` on this branch. Review the review, not the diff — leave comments and the agent will apply them via `task start 639`.

claude added 2 commits 2026-08-06 21:33:35 +02:00

one boot path for the workers and the API (V-639) 73441bcc6c

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.

assert the two paths wire the same set (V-639) 896c32882a

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.

claude merged commit b5ac48c126 into master

2026-08-06 21:54:13 +02:00

claude deleted branch task/639-the-two-boot-paths-have-drifted-seven-un

2026-08-06 21:54:14 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: kami/Maven#189