feat: initialize serverAppConfigs with podman stacks for Dankserver and Dankclaw

- Dankserver stack: RomM, Copyparty, Calibre-Web, node-exporter
- Dankclaw stack: Gluetun VPN (SearXNG tunnel), SearXNG+Valkey, ComfyUI
  (CPU backend), OpenWebUI, Hermes, Gitea+Postgres (migrated), Caddy
  reverse proxy, Grafana+Prometheus+Loki+Alloy observability
- Caddyfiles with .local hostname convention and basicauth homepage
- bind-mount storage policy, no named volumes
- deploy.sh mirroring vllmScripts git workflow (push -> pull -> restart -> health)
- docs/ Obsidian vault: per-service docs from frank-default-small research
  subagents (promtail EOL -> Alloy; gitea SECRET_KEY preservation; ComfyUI --cpu)
- bats test suite at 6 seams — 22 tests green

docs/Dankclaw/Postgres.md

@@ -0,0 +1,68 @@
+# Postgres
+
+PostgreSQL is the database backend for Gitea. It runs on the same podman network as Gitea and holds the repository metadata, users, and issue data.
+
+**Host:** Dankclaw — **Docs:** https://www.postgresql.org/docs
+
+## Facts
+
+| Item | Value |
+|------|-------|
+| Image | `docker.io/library/postgres:16-alpine` |
+| Port | 5432 (internal only) |
+| Data volume | bind mount at `/var/lib/postgresql/data` |
+
+## Configuration
+
+```yaml
+services:
+  postgres:
+    image: docker.io/library/postgres:16-alpine
+    restart: unless-stopped
+    environment:
+      POSTGRES_USER: gitea
+      POSTGRES_PASSWORD: "${GITEA_DB_PASSWORD}"
+      POSTGRES_DB: gitea
+    volumes:
+      - /opt/gitea/data/gitea-postgres:/var/lib/postgresql/data
+```
+
+## Gitea Connection
+
+Gitea reaches the database over the podman network:
+
+```yaml
+environment:
+  DATABASE_TYPE: postgres
+  DATABASE_HOST: postgres
+  DATABASE_NAME: gitea
+  DATABASE_USER: gitea
+  DATABASE_PASSWD: "${GITEA_DB_PASSWORD}"
+```
+
+## Migration
+
+The live Gitea stack on Dankclaw already runs this image with the data at `/opt/gitea/data/gitea-postgres`. The migration keeps the bind mount in place; see [[Gitea]].
+
+## Healthcheck
+
+Use `pg_isready`:
+
+```yaml
+healthcheck:
+  test: ["CMD-SHELL", "pg_isready -U gitea"]
+  interval: 30s
+  timeout: 5s
+  retries: 3
+```
+
+## Gotchas
+
+- The database password must match between the `postgres` service and Gitea's `DATABASE_PASSWD`; both come from the same `.env` variable.
+- Do not change the Gitea `SECRET_KEY` or `INTERNAL_TOKEN` after migration — encrypted data becomes unreadable.
+- Back up with `pg_dump`; see [[Gitea Data Persistence]] (knowledge base).
+
+## See Also
+
+- [[Gitea]]
+- [[Dankclaw Stack]]