docs: record Unraid deployment evidence for the date-anchoring fix

This commit is contained in:
NuklearRabbit
2026-08-03 13:10:33 +02:00
parent 8989ffb23c
commit 728e380d63
+6
View File
@@ -540,5 +540,11 @@ scenarios, demo manifest, About page). Gap audit: `docs/demo-release/current-dem
today and `BK-DEMO-NEXT`/overlap bookings sit in the near future (today = 2026-08-03).
- Evidence: `pytest` **122 passed** (117 + 5 new/expanded seed tests), `ruff check .`
clean, `mypy app` clean (46 files, canonical `make` scope).
- Deployed to Unraid (commit `8989ffb`): pushed to Gitea, `git archive` tarball extracted
over `/mnt/user/appdata/mobilityops` preserving `.env`/volumes, `api` rebuilt (`db`/`web`
untouched — no frontend changes this batch), migrations confirmed at `e7b08389f47f
(head)`, reseeded, live-verified via `psql` that `BK-DEMO-RETURN`/`BK-DEMO-NEXT`/overlap
bookings sit at the same real-time-relative positions as local. `curl` to
`http://192.168.10.150:1236/` returns 200.
- Exact next action: `GET /api/v1/demo/manifest` + Dutch demo entry screen + permanent
demo badge (task #30), then the Demo Guide + scenario overview (task #31).