docs: models.test.ts now verified against live Postgres

Fixed Windows-to-WSL2 Docker connectivity (real dockerd runs inside
the WSL Ubuntu distro, not Docker Desktop) so the Phase 13 test that
had been written but unrun could actually be exercised. api (98/98)
and frontend (39/39) suites both pass against real Postgres/Redis/
MinIO now.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015tKdPZt78zbPUZMXWzKEKt

README.md

@@ -213,9 +213,12 @@ test.
 
 Verified via real `cargo build`/`cargo test --lib` (worker, 65/65 passing, up from 52) and a real
 `./gradlew :forge-1_12_2:compileJava` against the actual legacy ForgeGradle toolchain for the mod
-side. `api`'s new `models.test.ts` (mirrors `textures.test.ts`'s pattern) was written but **not run
-against a live Postgres** — Docker isn't available in this dev environment, the same honestly-
-documented gap Phase 11 already carries; `bunx tsc --noEmit` is clean.
+side. `api`'s new `models.test.ts` (mirrors `textures.test.ts`'s pattern) has since been run against
+a real throwaway Postgres — 4/4 passing — once Docker connectivity was fixed (the dev machine's real
+`dockerd` runs inside WSL2, not Docker Desktop; Windows' `DOCKER_HOST` had nothing listening on the
+other end until a systemd drop-in exposed it on `tcp://127.0.0.1:2375`). Full `api` (98/98) and
+`frontend` (39/39) suites both pass against real Postgres/Redis/MinIO, closing the same "Docker
+unavailable" gap Phase 11 had also carried (see "Running tests" below).
 
 ## Running