New production up, the web on the API

What I did

Brought up a new production estate in Azure and pulled a full deploy through it for the first time: migrations, image, container app, web, tag.
Opened ingress on production; prod.bicepparam still had it off and would have cut production off again on the next deploy.
Disconnected the old ai-coach Vercel project from git so no migration can break it and it keeps running on the old sign-in and the old database; the two new Lifalign projects went up beside it.
Renamed Supabase to lifalign-prod, postponed staging and now deploy production straight from main; the free tier allows two projects and both are taken.
Pulled the design gallery back to the development server; its prerendered images had grown the deployment bundle from 1.74 MB to 52 MB.
Built the gateway to the .NET API and sent the first screen, Poznámky, across it.
Rewired the Lifalign web app’s sign-in from Smart Diary to the .NET API; Supabase is still the identity provider, the API is just the one that talks to it now.
A screen not yet behind the API throws at its first read and names the missing table, so the migration is visible; sign in, sign out, More and Poznámky work.
Wrote down how the columns of the live and target databases correspond, both ways; they are not two versions of one schema.
Ran the product locally against plain Postgres.
Cut the rest of the move into eighteen P0 tasks, Detail dne among them at five screens.

Served personal context, deleting a note, and the day’s plan timeline over HTTP, the last of those across eleven routes.
Gave the change trail an implementation, so writing a plan block no longer ends at an empty description.
Added a check that finds a merged, unapplied migration before a user does.
Capped the time category tree at three levels.
Straightened the naming: the epic is Detail dne and the section Na tento den; the fix for twelve glossary citations waits to merge.