Initial setup: OpenResto deployment for Lunkaberg breakfast booking

Adapts upstream's release docker-compose.yml to run behind this server's
Nginx Proxy Manager on the shared my-main-net network instead of publishing
host ports. Includes docs/ for session continuity.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014vNjtg18oTQcv8dtjwnT69

docs/TODO.md

@@ -0,0 +1,24 @@
+# TODO — Lunkaberg Frukost (OpenResto)
+
+## Next up
+1. Bring the stack up (`docker compose up -d`) and confirm all three
+   containers report healthy.
+2. Per: add DNS A record for `frukost.lunkaberg.se` → `64.112.127.212`.
+3. Create NPM proxy host: `frukost.lunkaberg.se` → `lunkaberg-reverse-proxy:80`,
+   request Let's Encrypt cert, force SSL.
+4. Log into the admin dashboard with the generated credentials (see .env),
+   change the admin password from the generated one via the UI if it
+   offers that, and set up the restaurant's first location (timezone,
+   hours, tables, floor sections).
+5. Push the initial commit to Gitea once Per confirms he's ready.
+
+## Open questions for Per
+- Who is the actual admin user for the client (Per, or someone at
+  Lunkaberg)? Affects ADMIN_EMAIL and whether Per hands off credentials.
+- Want booking confirmation emails? Needs SMTP creds — likely a new mailbox
+  at lunkaberg.se via Migadu, separate from Per's personal one.
+- Any interest in push notifications or Apple/Google Wallet passes, or
+  leave those disabled (current default)?
+- Branding: restaurant name / primary color / icon are configurable live
+  from the admin dashboard, no redeploy needed — revisit once client has
+  a look.