feat: Add WiFi setup screen with QR code on LilyGo display

[marcodejongh]

When WiFi isn't configured, the device now:

• Starts in AP mode with SSID "Boardsesh-Setup"
• Shows a setup screen with QR code linking to http://192.168.4.1
• Defers BLE initialization until WiFi is connected

This provides a better first-time setup experience where users can
scan the QR code to configure WiFi credentials via the web interface.

Changes:

• WiFiUtils: Add AP_MODE state and startAP/stopAP methods
• LilyGoDisplay: Add showSetupScreen() with QR code
• main.cpp: Defer BLE init until WiFi configured
• esp_web_server: Handle AP mode in status endpoint

Co-Authored-By: Claude Opus 4.5 noreply@anthropic.com

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
boardsesh	Building	Preview, Comment	Feb 6, 2026 10:34am

[claude]

Claude Review

✅ Ready to merge - Minor issues noted below, but nothing blocking.

---

Issues

1. Non-display builds don't start AP mode on connection failure - main.cpp:417-428: The CONNECTION_FAILED case only starts AP mode when ENABLE_DISPLAY is defined. Non-display builds will remain in CONNECTION_FAILED state without starting AP mode, which may not be intentional.

2. Credentials saved but not in AP mode on handleWiFiConnect - esp_web_server.cpp:464: The connect() call doesn't pass true for the save parameter, so credentials entered via the AP mode web interface won't be persisted. After a reboot, the device will return to AP mode.

3. Missing getAPSSID in WiFiUtils - The test mock adds getAPSSID() but WiFiUtils class doesn't have this method. While tests pass (mocks are separate), this represents incomplete API symmetry.

[claude]

Claude Review

✅ Ready to merge - Minor issues noted below, but nothing blocking.

Issues

1. embedded/libs/wifi-utils/src/wifi_utils.cpp:157-159 - Unreachable code: The AP_MODE case in checkConnection() is dead code since the function returns early at line 129 when in AP mode. Consider removing it to avoid confusion.

2. embedded/projects/board-controller/src/main.cpp:219-226 - When ENABLE_DISPLAY is not defined, the AP mode starts but there's no way for users to know the device IP or that setup is needed (no display, no visual feedback). Consider logging more prominently or providing alternative feedback (e.g., LED pattern).

Test Coverage

Tests are well-written and cover the key AP mode functionality including edge cases like credential clearing and state transitions.