supbuddy 3.1.22 → 3.1.23

package/dist/bin.js

@@ -19807,7 +19807,7 @@ function cliBuildKind(env3 = process.env) {
   return raw === "host" || raw === "npm" ? raw : "dev";
 }
 function cliVersion(env3 = process.env) {
-  return "3.1.22".trim() || "0.0.0-dev";
+  return "3.1.23".trim() || "0.0.0-dev";
 }
 function isDevBuild(env3) {
   return cliBuildKind(env3) === "dev";
@@ -28196,18 +28196,39 @@ var init_store = __esm({
         }));
       },
       setDoctorSummary: (s, report) => set2({ doctorSummary: s, doctorReport: report }),
+      // ── A WRITE THAT CHANGES NOTHING MUST NOT LOOK LIKE A CHANGE ───────────────────
+      //
+      // Both setters used to build a NEW proxyState object unconditionally, so writing the
+      // value that was already there still produced a fresh reference. The store subscriber
+      // publishes on `state.proxyState !== prevState.proxyState`, so a no-op write emitted
+      // `proxy-state-updated` to every client.
+      //
+      // That turned a read into a loop. `port-forwarding:status` — a QUERY — ends by calling
+      // `setPortForwardingEnabled(status.enabled)`, almost always with the value already
+      // held. The renderer re-probed whenever proxyState changed, so: poll → no-op write →
+      // emit → poll. Bounded only by IPC latency, which measured at **51 probes per second**,
+      // each opening a TCP connection to the redirected :443. Under that self-inflicted load
+      // some connects timed out, and each timeout was painted as `NOT ENFORCING` on a machine
+      // answering 30 of 30 sequential probes.
+      //
+      // The renderer's dependency was also fixed, but this is the half that matters: no UI
+      // should be able to induce a feedback loop by reading status. Equality-guard the write,
+      // and the loop cannot form.
       setPortForwardingEnabled: (enabled) => {
-        set2((state) => ({
-          proxyState: {
-            ...state.proxyState,
-            portForwardingEnabled: enabled
-          }
-        }));
+        set2((state) => state.proxyState.portForwardingEnabled === enabled ? {} : { proxyState: { ...state.proxyState, portForwardingEnabled: enabled } });
       },
       // Patch arbitrary proxy fields (restartAttempt/lastExit/networkingDegraded/…) without
       // touching status — used by the supervisor + the drift-gated networking repair.
+      //
+      // Same guard, generalised: the supervisor and the health paths call this on a timer
+      // with values that are usually unchanged, and each such call was a broadcast.
       setProxyFields: (fields) => {
-        set2((state) => ({ proxyState: { ...state.proxyState, ...fields } }));
+        set2((state) => {
+          const current = state.proxyState;
+          const changed = Object.entries(fields).some(([k, v]) => current[k] !== v);
+          if (!changed) return {};
+          return { proxyState: { ...state.proxyState, ...fields } };
+        });
       },
       updateSettings: (updates) => {
         set2((state) => ({

package/dist/daemon/worker.cjs

@@ -26296,18 +26296,39 @@ const useStore = create((set2, get2) => ({
     }));
   },
   setDoctorSummary: (s, report) => set2({ doctorSummary: s, doctorReport: report }),
+  // ── A WRITE THAT CHANGES NOTHING MUST NOT LOOK LIKE A CHANGE ───────────────────
+  //
+  // Both setters used to build a NEW proxyState object unconditionally, so writing the
+  // value that was already there still produced a fresh reference. The store subscriber
+  // publishes on `state.proxyState !== prevState.proxyState`, so a no-op write emitted
+  // `proxy-state-updated` to every client.
+  //
+  // That turned a read into a loop. `port-forwarding:status` — a QUERY — ends by calling
+  // `setPortForwardingEnabled(status.enabled)`, almost always with the value already
+  // held. The renderer re-probed whenever proxyState changed, so: poll → no-op write →
+  // emit → poll. Bounded only by IPC latency, which measured at **51 probes per second**,
+  // each opening a TCP connection to the redirected :443. Under that self-inflicted load
+  // some connects timed out, and each timeout was painted as `NOT ENFORCING` on a machine
+  // answering 30 of 30 sequential probes.
+  //
+  // The renderer's dependency was also fixed, but this is the half that matters: no UI
+  // should be able to induce a feedback loop by reading status. Equality-guard the write,
+  // and the loop cannot form.
   setPortForwardingEnabled: (enabled) => {
-    set2((state) => ({
-      proxyState: {
-        ...state.proxyState,
-        portForwardingEnabled: enabled
-      }
-    }));
+    set2((state) => state.proxyState.portForwardingEnabled === enabled ? {} : { proxyState: { ...state.proxyState, portForwardingEnabled: enabled } });
   },
   // Patch arbitrary proxy fields (restartAttempt/lastExit/networkingDegraded/…) without
   // touching status — used by the supervisor + the drift-gated networking repair.
+  //
+  // Same guard, generalised: the supervisor and the health paths call this on a timer
+  // with values that are usually unchanged, and each such call was a broadcast.
   setProxyFields: (fields) => {
-    set2((state) => ({ proxyState: { ...state.proxyState, ...fields } }));
+    set2((state) => {
+      const current = state.proxyState;
+      const changed = Object.entries(fields).some(([k, v]) => current[k] !== v);
+      if (!changed) return {};
+      return { proxyState: { ...state.proxyState, ...fields } };
+    });
   },
   updateSettings: (updates) => {
     set2((state) => ({

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "supbuddy",
-  "version": "3.1.22",
+  "version": "3.1.23",
   "description": "Run multiple Supabase projects at once on custom local domains with HTTPS. A headless CLI and daemon (proxy, DNS, Supabase/Compose lifecycle, MCP) for macOS and Linux.",
   "keywords": [
     "supabase",