tfaour
a518cbdbaf
After a successful home WiFi connect, frame_client_run() now redraws the panel as a two-row checklist (WiFi row with a checkmark, server row) so the connection sequence is visible on-device rather than only in serial logs. Refreshes once with the server row pending, probes the tools server with a plain HTTP HEAD (any response, even 404, confirms the socket-level connection works -- there's no real server yet), then refreshes again with the final result. Two refreshes rather than one to actually show staged progress, at the cost of the extra refresh time inherent to this panel. Also fixes a second hardware-verified bug in the same area: on a failed STA connect falling back to provisioning, wifi_init_softap()'s esp_wifi_init() call was aborting with ESP_ERR_INVALID_STATE, because frame_wifi_connect_sta() only stopped the WiFi driver on failure rather than fully deinitializing it (and destroying the STA netif) before handing back control.