fix: preserve mobile record status

This commit is contained in:
NuklearRabbit
2026-08-10 01:14:20 +02:00
parent ad1182582d
commit aacf0e04bc
2 changed files with 18 additions and 2 deletions
+14 -2
View File
@@ -2226,5 +2226,17 @@ evidence yet."
Docker Desktop is unavailable and the configured `db` hostname cannot resolve; run the
complete suite inside the Unraid Compose API container after deployment.
- **Commit**: `f2cdad194ccafd0e9aa59e91ddd7dbe0c79278af` (`UX: implement visual product roadmap`).
- **Next action**: push, fast-forward `master`, redeploy API/web to Unraid, run the
container test suite and live responsive verification at 390/768/1440px.
- **Deployment and final verification**: feature branch was pushed, fast-forward merged
and pushed to `master` at `ad1182582d87f0911cc97af88924fd0dee927ac8`; Unraid rebuilt
the API/web services from `/mnt/user/appdata/mobilityops/.deploy/source-ad11825.tar.gz`
and recorded that revision in `.deploy/source-revision`. The isolated Compose test run
with the explicit demo contract (`KNOWLEDGE_PROVIDER=demo`, MCP Hub registration off)
passed **192 tests**; `ruff check .` and `mypy app` passed. The default production
environment intentionally exposes the live RAGcore/MCP settings, so its five old
demo-only assertions are not a production regression.
- **Live visual evidence**: at 1440px Vehicles renders 25 bounded rows and “Pagina 1 van
2”; at 390px the return workflow has no horizontal overflow and the dashboard attention
queue is capped at six with a direct continuation link. A cached pre-roadmap CSS asset
was found in one browser session still hiding `.page-actions`; a follow-up asset hash
now explicitly keeps the mobile status/action row visible and is being deployed as the
final revision.