docs: record Qarina production source

Author: level09

CLAUDE.md

@@ -34,6 +34,24 @@ uv run python checks.py           # Sanity checks (not pytest)
 docker compose up --build          # Full stack (Redis, PostgreSQL, Nginx)
 ```
 
+## Qarina production
+
+Qarina's canonical application is this STK repository. Do not deploy the
+standalone `~/projects/qarina` Starlette prototype to `try.qarina.org`.
+
+- Production: `try.qarina.org`
+- Server: Hetzner `try-qarina-demo` at `46.225.143.122`
+- Service: `try.qarina.org.service`
+- Runtime: `uvicorn run:app` on `127.0.0.1:5000`
+- Database: `/home/try/try.qarina.org/instance/stk.db`
+- Knowledge: `/home/try/try.qarina.org/stk/qarina/knowledge_store`
+- Releases: `/home/try/releases/<git-sha>`
+
+Production uses versioned release directories. Each release links the existing
+`.env`, `instance`, and Qarina knowledge store so deploys never replace user
+data. Caddy and systemd must point at the same release SHA. The legacy
+`qarina.service` is disabled and must remain inactive.
+
 ### Agent Operability
 
 Prefer these over guessing from files. Structured agent context lives in `.stk/context/` (architecture, commands, verification, frontend).