Dioxus onboarding Try Again gets stuck on checking daemon status

[dirvine]

Summary

The v0.12.4 Dioxus macOS onboarding gate can get stuck indefinitely on Checking x0x daemon status... after pressing Try Again from a failed install/start state.

Steps observed

1. Launch /Users/studio1/Applications/Communitas-Dioxus-0.12.4.app.
2. Click Install x0x.
3. Installer succeeds and starts x0xd, but app fails with x0x installed but failed to start: daemon error: x0x binary not installed because of issue macOS onboarding cannot find x0x installed in ~/.local/bin #20.
4. Add temporary compatibility symlink ~/.x0x/bin/x0x -> ~/.local/bin/x0x; daemon is healthy at http://127.0.0.1:12700/health.
5. Click Try Again.

Expected

Try Again should re-run daemon state detection and proceed to the main app when x0xd is healthy.

Actual

The UI remains indefinitely on Checking x0x daemon status.... The daemon health endpoint returns healthy, e.g. {"ok":true,"status":"healthy","version":"0.21.2","peers":17}.

Likely cause

In communitas-dioxus/src/components/onboarding_gate.rs, the daemon state check is run in a use_future on mount. The failed-state retry sets gate back to GateState::Checking, but does not appear to trigger a new daemon state check. The retry handler should explicitly rerun the async check or drive it from a retry signal/dependency.

[dirvine]

Local fix is in the current worktree: Dioxus onboarding retry now re-runs the daemon state probe instead of only setting the gate back to Checking, and daemon health probing is bounded so a stale API endpoint cannot leave the UI spinning indefinitely. Rebuilt and redeployed the patched Dioxus app to the studio; launched via the remote GUI and verified it opens past onboarding into the space UI/Board view.