chore: adopt pre-existing working-tree state before trunk merge

Uncommitted machine/session edits (live config, models, docs drift) were
blocking the merge of origin/main. Committed as-is to preserve them; the
merge that follows resolves overlapping prose files toward upstream
canonical, with local variants recoverable from this commit. Pre-merge
copies also in .AGENTTRASH/pre-merge-2026-10-18/.

omp-docs/tools/gitea/architecture.md

@@ -5,13 +5,12 @@ description: Gitea container architecture, network topology, and Caddy reverse p
 tags:
   - gitea
   - architecture
-  - unverified
-verified: 2026-08-28
+verified: 2026-10-18
 ---
 
 # Gitea Architecture
 
-Three quadlet-managed containers on a shared private Podman network (rootless, user `dank`). Gitea connects to PostgreSQL via network DNS. Caddy proxies HTTP/S to Gitea.
+Two quadlet-managed containers (Gitea, PostgreSQL) on a shared private Podman network (rootless, user `dank`). Gitea connects to PostgreSQL via network DNS. The fleet Caddy (separate stack, see [/caddy/index.md](/caddy/index.md)) proxies HTTP/S to Gitea — the old dedicated `gitea-caddy` container is retired.
 
 ## Network Topology
 
@@ -63,10 +62,10 @@ Key environment variables:
 - `DATABASE_HOST=gitea-postgres` (network DNS)
 - `DATABASE_NAME=gitea`
 - `DATABASE_USER=gitea`
-- `DATABASE_PASSWD` from `/opt/gitea/.env` (mode 0600)
+- `DATABASE_PASSWD` from `/home/dank/Containers/gitea/env` (mode 0600)
 - `USER_UID=1000`, `USER_GID=1000`
 
-Gitea writes `/data/gitea/conf/app.ini` on first start (host: `/opt/gitea/data/gitea-gitea/gitea/conf/app.ini`). The `[database] HOST` and `PASSWD` lines in app.ini override the env vars. When you rename the database container, edit the `HOST` line in app.ini as well.
+Gitea writes `/data/gitea/conf/app.ini` on first start (host: `/home/dank/Containers/gitea/data/gitea/conf/app.ini`). The `[database] HOST` and `PASSWD` lines in app.ini override the env vars. When you rename the database container, edit the `HOST` line in app.ini as well.
 
 ## Ports