M39: harden application and acceptance gates

README.md

@@ -2,7 +2,7 @@
 
 **A recruiter-ready operations platform for vehicle rental and service teams.**
 
-[Open the live demo](http://192.168.10.150:1236) · no password required · choose **Highlights in 90 seconds** for the shortest tour.
+**Try it in two commands** (`cp .env.example .env && make demo`, then open `http://localhost:1228`) · no password required · choose **Highlights in 90 seconds** for the shortest tour. The reference deployment runs on a private LAN (see [deploy/unraid/README.md](deploy/unraid/README.md)); ask for a link if you want the hosted version.
 
 Fleet Ops turns fragmented vehicle, booking and procedure data into one controlled operational workspace. It is a complete synthetic-data product demo: the company and records are fictional, while the workflows, persistence, validation, authorization, audit trail and integration boundaries are implemented.
 
@@ -65,7 +65,7 @@ make demo
 
 - Web: `http://localhost:1228`
 - API readiness: `http://localhost:8128/health/ready`
-- Existing n8n server: configure `N8N_BASE_URL`; Fleet Ops does not create a second n8n instance.
+- Existing n8n server: point `N8N_WEBHOOK_URL` at its return-processing webhook (see `.env.example`). The bundled `n8n` service in `compose.yaml` is a local fallback only; production reuses the server's central n8n (`compose.unraid.yaml` disables the bundled one).
 
 The deterministic local knowledge provider supports clean-checkout acceptance without pretending to be the live RAGcore integration. Configuration is documented in `.env.example`; operations and recovery are in [docs/17-runbook.md](docs/17-runbook.md).
 
@@ -78,7 +78,7 @@ make e2e     # complete Playwright browser acceptance
 cd frontend && npm run build
 ```
 
-Current verified results and production evidence are recorded in [artifacts/evidence/final-summary.md](artifacts/evidence/final-summary.md) and [PROJECT_STATE.md](PROJECT_STATE.md).
+Current verified results and production evidence are recorded in [artifacts/final-acceptance/summary.md](artifacts/final-acceptance/summary.md) (historical M7 evidence: [artifacts/evidence/final-summary.md](artifacts/evidence/final-summary.md)) and [PROJECT_STATE.md](PROJECT_STATE.md).
 
 ## Repository map
 
@@ -89,6 +89,6 @@ Current verified results and production evidence are recorded in [artifacts/evid
 - `n8n/` — importable workflow definitions for the existing server
 - `seed/` — deterministic synthetic dataset
 - `docs/` — architecture, security, UX, testing and runbooks
-- `artifacts/evidence/` — current acceptance evidence and screenshots
+- `artifacts/` — acceptance evidence and screenshots per release (`artifacts/final-acceptance/summary.md` is the definitive one)
 
 “MobilityOps” remains the repository/deployment identifier; **Fleet Ops** is the product name shown to users.