docs: #8 record the VM deployment in README and AGENTS.md

AGENTS.md

@@ -78,5 +78,13 @@ as they land.
 
 The finished app runs on the group VM: client under
 `http://it2810-19.idi.ntnu.no/project2` behind Apache, GraphQL API on port
-3001, PostgreSQL reachable only from the VM. No Docker. See `docs/VM-setup.md`
-(from M2).
+3001, PostgreSQL reachable only from the VM. No Docker, no external service.
+
+- PostgreSQL 18, role `t19`, database `crate`, local connections only
+- `crate-api.service` runs `server/dist/index.js` on port 3001
+- Apache `ProxyPass /graphql` to `127.0.0.1:3001`, client at `/var/www/html/project2`
+- CI runs on a self-hosted runner on the same machine and deploys on push to `main`
+
+Until M2 lands `server/`, the VM's `~/T19-Project-2` is a manual copy of an
+early prototype rather than a git clone, so `crate-api` is running code that
+is not in this repository.

README.md

@@ -54,6 +54,16 @@ All four must pass. CI runs the same thing.
 `client/` currently renders mock data. `server/` (PostgreSQL + GraphQL Yoga)
 arrives in M2 and `e2e/` (Playwright) in M4.
 
+## Infrastructure
+
+The database and the GraphQL API run directly on the group VM, not in
+containers and not on an external service. Live at
+<http://it2810-19.idi.ntnu.no/project2>, GraphQL on port 3001 behind an
+Apache `ProxyPass`. PostgreSQL is local to the machine and is not exposed.
+
+CI runs on a self-hosted runner on the same VM. Pushes to `main` build the
+client and publish it to Apache.
+
 ## Working in this repository
 
 `main` is protected - you cannot push to it directly. Work on a branch and