feat: add direct PostgreSQL and ACK deployment support

.env.example

@@ -35,11 +35,27 @@ ZHINIAN_WORKER_POLL_INTERVAL_MS=5000
 ZHINIAN_WORKER_LOCK_TIMEOUT_MS=300000
 ZHINIAN_WORKER_RETRY_BASE_MS=10000
 ZHINIAN_WORKER_RETRY_MAX_MS=300000
+ZHINIAN_WORKER_REQUEST_TIMEOUT_MS=120000
 
-# Supabase SaaS data layer. If empty, the app uses .runtime/data/web-app-state.json.
-NEXT_PUBLIC_SUPABASE_URL=
-NEXT_PUBLIC_SUPABASE_ANON_KEY=
-SUPABASE_SERVICE_ROLE_KEY=
+# Data layer. Use local only for development/single-instance operation.
+# Production must explicitly select postgres; it never falls back to container-local JSON.
+ZHINIAN_DATA_BACKEND=local
+DATABASE_URL=
+# Migration runner only: PostgreSQL role used by the Web DATABASE_URL.
+DATABASE_APP_ROLE=
+DATABASE_SSL_MODE=disable
+# For RDS SSL, set verify-full and mount the downloaded CA certificate at this path.
+DATABASE_CA_CERT_PATH=
+DATABASE_POOL_MAX=10
+DATABASE_IDLE_TIMEOUT_MS=30000
+DATABASE_CONNECTION_TIMEOUT_MS=5000
+DATABASE_STATEMENT_TIMEOUT_MS=30000
+DATABASE_APPLICATION_NAME=zhinian-web
+
+# Obsolete: the direct PostgreSQL adapter does not use Supabase/PostgREST variables.
+# NEXT_PUBLIC_SUPABASE_URL=
+# NEXT_PUBLIC_SUPABASE_ANON_KEY=
+# SUPABASE_SERVICE_ROLE_KEY=
 
 # Image creation engine: jimeng, evolink, or bailian.
 IMAGE_GENERATE_ENGINE=jimeng