elitan tries to fold Mike's two servers into one
A proposal to run the whole app as a single deployable instead of a separate backend service plus a frontend - though it never made it in.
Right now this fork ships as two things: a standalone backend service and the frontend it talks to. elitan's proposal was to collapse them into one, moving all the server logic to live inside the frontend app so the whole thing builds and deploys as a single unit. Fewer moving parts, simpler operations.
The change also started wiring in tighter, type-checked plumbing between the browser and the server, so calls are less likely to silently break when someone changes one side. File uploads, downloads, and live updates were deliberately left on the old paths to avoid breaking anything mid-migration. elitan reported it passed a clean build and basic smoke tests. But the pull request was closed within a couple of minutes of opening and never merged, so none of it actually landed here - it reads more like a mis-filed or superseded submission than a rejected one.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?