@rubytech/create-maxy 1.0.786 → 1.0.787

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rubytech/create-maxy",
-  "version": "1.0.786",
+  "version": "1.0.787",
   "description": "Install Maxy — AI for Productive People",
   "bin": {
     "create-maxy": "./dist/index.js"

package/payload/platform/scripts/wifi-provision-server/server.js

@@ -655,8 +655,22 @@ function handleRequest(req, res) {
         // Use async open+write to avoid blocking the event loop (a FIFO
         // write blocks until a reader opens the other end).
         connecting = true;
-        res.writeHead(202, { "Content-Type": "application/json" });
-        res.end('{"status":"connecting"}');
+        // Return success immediately with the post-connect URL info.
+        // Why not poll for verification? The AP and station modes are
+        // mutually exclusive on a single radio: as soon as the bash
+        // script tears down hostapd to run `nmcli connect`, the phone
+        // loses its connection to 192.168.4.1 and any subsequent
+        // `/result` poll dies. The success page must be in the phone's
+        // hands BEFORE the AP goes away. We send the hostname (.local
+        // resolution works on iOS/macOS) and the operator can paste
+        // the URL into a browser if .local fails on their device.
+        res.writeHead(200, { "Content-Type": "application/json" });
+        res.end(JSON.stringify({
+          success: true,
+          hostname: HOSTNAME,
+          // ip is intentionally absent: we don't yet know the new
+          // home-WiFi IP and the AP IP (192.168.4.1) is about to die.
+        }));
 
         const fifoData = `${ssid}\n${password}`;
         fs.open(CONNECT_FIFO, "w", (err, fd) => {