elitan cuts the Supabase cord

elitan ripped out Supabase, the hosted backend service that handled both sign-in and the database for this build of Mike, and replaced it with self-contained pieces: a standalone login system and a query layer that talks to plain Postgres. The clever part is that elitan wrote a small compatibility shim so the rest of the code keeps working as-is, rather than rewriting every database call by hand.

For anyone deploying, the README requirement drops from "a Supabase project" to "any Postgres database." That means no third-party account to provision, and the freedom to host the data wherever you already run things - your own servers, your own cloud, your own region. The trade-off worth knowing: that compatibility shim is custom code this fork now owns and maintains.