docs: record Unraid deployment evidence for Demo Guide/scenario overview batch

PROJECT_STATE.md

@@ -629,5 +629,14 @@ scenarios, demo manifest, About page). Gap audit: `docs/demo-release/current-dem
   from Rental Employee, restart-from-guide resets data and returns to login). Backend
   untouched this batch (no re-run needed; last backend gate was 127 passed/ruff/mypy
   clean in Batch 2).
+- Deployed to Unraid (commits `9fff84d`, then `14c2ad3` for a test-only fix): pushed to
+  Gitea, tarball extracted, `web` rebuilt (frontend-only batch), healthy. Live-verified:
+  ran `demo-guide.spec.ts` (6), `demo-entry.spec.ts` (4) and the five-minute demo script
+  directly against `http://192.168.10.150:1236` — **11/11 passed**. Caught and fixed one
+  real environment-sensitive test bug in the process: two tests navigated straight to
+  `/scenarios` right after a login click without waiting for the `/dashboard` redirect,
+  which raced harmlessly on localhost but flaked against Unraid's higher latency — fixed
+  by asserting the redirect first, no app-code change needed. Reseeded afterward to leave
+  the server demo-ready.
 - Exact next action: layer plain-language Dutch explanation onto the return flow, the 5
   data-quality panels, and fix the knowledge assistant's RAGcore-naming bug — task #33.