chore(deploy): set production LOG_LEVEL to error

Configure production deployments to use LOG_LEVEL=error for minimal log volume.

- Add LOG_LEVEL=error to docker-compose.yml environment

- Add LOG_LEVEL: error to K8s ConfigMap

- Update .env.example with dev/prod LOG_LEVEL guidance

Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent)

.env.example

@@ -2,6 +2,10 @@
 PORT=5174
 # 可选，默认为 ./data/assistant.db
 # DATABASE_PATH=./data/assistant.db
+# 可选，默认 info，可选值：debug/info/warn/error
+# 开发环境建议：LOG_LEVEL=info
+# 生产环境建议：LOG_LEVEL=error
+# LOG_LEVEL=info
 # 必填，运行 openssl rand -hex 32 生成
 ENCRYPTION_KEY=
 

docker-compose.yml

@@ -13,6 +13,8 @@ services:
       - assistant_data:/app/data
     env_file:
       - .env
+    environment:
+      LOG_LEVEL: error
     depends_on:
       qdrant:
         condition: service_healthy

k8s/gitea-assistant.yaml

@@ -10,6 +10,7 @@ metadata:
     app.kubernetes.io/part-of: gitea-assistant
 data:
   PORT: "5174"
+  LOG_LEVEL: "error"
   # All settings (Gitea connection, webhook secret, admin password, review engine,
   # Feishu, memory, etc.) are managed through the Admin Dashboard Web UI.
   # They are auto-seeded with secure defaults on first boot.