M19: harden performance and recovery

PROJECT_STATE.md

@@ -2459,3 +2459,24 @@ evidence yet."
   regenerated. E2E coverage now includes bulk queue assignment and full user editing.
 - Exact next action: split the frontend bundle, harden mobile layout and operational
   backup/deployment controls, then run clean full acceptance and redeploy.
+
+## M19 — performance and recoverable operations (2026-08-10)
+
+- Route-level React lazy loading reduced the initial production JavaScript chunk from
+  about **572 kB to 212 kB**; every operational page now ships as a separate bounded
+  chunk and the previous Vite large-chunk warning is gone. Both npm audits report zero
+  vulnerabilities.
+- Reflowed the five dashboard readiness metrics into a readable 3+2 mobile grid instead
+  of an overflowing horizontal strip at 390 px.
+- Compose now gates dependants on database-backed `/health/ready`. The optional bundled
+  n8n fallback is pinned to `n8nio/n8n:2.33.7`, matching the central server n8n version;
+  Unraid still starts no second n8n instance.
+- Added guarded Unraid PostgreSQL backup/restore scripts. Backups use custom format and
+  are structurally verified; restore requires an explicit confirmation, makes a safety
+  backup, stops API writes, recreates only the configured database and checks Alembic.
+  A disposable dump/restore drill recovered all **50 vehicles** into a second database.
+- Evidence: merged Compose configurations and shell syntax pass; frontend production
+  build and audits pass; full isolated PostgreSQL suite **225 passed, 1 warning**; ruff
+  and mypy are clean.
+- Exact next action: commit and deploy this milestone, run complete Playwright and visual
+  acceptance against Unraid, refresh final evidence, push and verify the live hash.