elitan collapses Mike into a single app

Mike originally ran as two pieces: a separate backend server and a Next.js web app talking to it. elitan has merged them. The backend code now lives inside the frontend project, and a single catch-all route inside Next.js dispatches incoming API calls to the right place - authentication to one handler, everything else routed through a layer called oRPC (a typed request router) with a compatibility shim so the old backend routes keep working unchanged.

The direction of travel is clear from the surrounding work: drop the separate backend, drop the hosted database dependency, ship Mike as one Next.js app plus a Postgres database and a file store. Fewer moving parts, one process to run, one thing to deploy. The compatibility shim is doing real work here - it's what lets elitan move fast without rewriting every route.