Same latent state as #60, second consumer: the hasCompletedOnboarding onChange guards on syncthingManager.isRunning only; with a background-started engine it calls start(), which maps the Go floor's 'already running' to a userError. Barely reachable during onboarding (no bookmark -> background sync bails), but the adopt helper from #60 would fix it in three lines. Also from #60 follow-ups: residual dead-bridge state shows 'Ready' instead of a stopped state (cosmetic), and the silent-push path is not unit-pinnable (Environment-pattern refactor).
Same latent state as #60, second consumer: the hasCompletedOnboarding onChange guards on syncthingManager.isRunning only; with a background-started engine it calls start(), which maps the Go floor's 'already running' to a userError. Barely reachable during onboarding (no bookmark -> background sync bails), but the adopt helper from #60 would fix it in three lines. Also from #60 follow-ups: residual dead-bridge state shows 'Ready' instead of a stopped state (cosmetic), and the silent-push path is not unit-pinnable (Environment-pattern refactor).