elitan folds Mike's backend into the frontend and ships it as one app
The separate server is gone - elitan merged it into the web application so the whole fork deploys as a single unit.
elitan tore out Mike's standalone backend and relocated everything inside the web app. Instead of running two pieces, this fork now hands all traffic to one entry point that quietly sorts it - sign-in, app calls, and everything else - and routes it onward. The payoff is a simpler thing to deploy and reason about.
The catch worth knowing about: rather than rewrite the old server logic, elitan wrapped it in a compatibility layer so it keeps running unchanged inside the new structure. That kept the change contained, but it leaves a non-standard layer in the middle that anyone adopting this fork inherits. There's also a tie to Cloudflare Workers - Cloudflare's platform for running code at the network edge - that the team flags as worth re-checking if you deploy somewhere else.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?