the desktop app kept saying it could not reach the gateway, and it looked like an app problem until i looked at the server side. the dashboard backend had been crash-looping since an update: it started, tried to build its web ui, failed, exited, and the service manager restarted it, nineteen plus times, so its port never answered.
the build failure was a beautiful bit of rot. fourteen stale javascript files dated weeks old were sitting in a shared source folder. the bundler resolves that package to that folder and picked the old files instead of the fresh sources, and the old files simply did not have the new functions the updated ui imports, so the build died with ten missing export errors. they were gitignored build leftovers, invisible to version control, quietly poisoning every build after the update. that is why it only showed up after the update added those imports.
the fix was anticlimactic. moved the fourteen files out of the way, nothing deleted, rebuilt the ui in six seconds, restarted the service, zero restarts since. the lesson is that build artifacts can live longer than they deserve and a folder full of stale output will win over fresh sources every time the resolution order favors it.