Stop AP/WLAN contention during setup Wi‑Fi connect

[Copilot]

Setup could complete over Ethernet but fail to bring up Wi‑Fi when AP mode was still active on the same radio. The Wi‑Fi test path also tolerated non-connected states, masking failures.

• Patch dogeboxd in flake build

  • Added a local patch override for the pinned dogeboxd package in flake.nix.
  • Keeps the fix scoped to this repo’s build without changing upstream pin.

• AP → client handoff in setup flow

  • In _dbxroot wifi-test, stop create_ap.service before starting wpa_supplicant on the selected interface.
  • Stop failure is logged as warning (non-fatal), so environments without create_ap don’t hard-fail.

• Tighten Wi‑Fi test correctness

  • Trim wpa_cli add_network output before reusing as network ID.
  • Return an error if wpa_state=COMPLETED is not reached, instead of logging-only behavior.

stopCreateAPCmd := exec.Command("systemctl", "stop", "create_ap.service")
if out, err := stopCreateAPCmd.CombinedOutput(); err != nil {
	log.Printf("warning: failed to stop create_ap.service: %v (%s)", err, strings.TrimSpace(string(out)))
}

id := strings.TrimSpace(string(networkID))

if !strings.Contains(status, "wpa_state=COMPLETED") {
	return fmt.Errorf("wpa_supplicant did not reach connected state")
}

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.