M29: polish recruiter engineering story

2026-08-10 18:13:18 +02:00
parent 6365586e82
commit 29325b6c27
57 changed files with 717 additions and 349 deletions
@@ -2647,3 +2647,28 @@ evidence yet."
  error or traceback appears in post-deployment logs.
 - Exact next action: none for the selected scope. Optional secret rotation and new n8n
  execution evidence remain intentionally deferred by the user.
+
+## M29 — recruiter-facing product polish and engineering evidence (2026-08-10)
+
+- Added a passwordless **90-second Highlights** entry that presents three directly
+  verifiable engineering stories: transactional vehicle returns, human-controlled data
+  correction and citation-bound knowledge. Rebuilt the Engineering page around domain
+  ownership, commit-before-orchestration, AI evidence, architecture and honest live/demo
+  integration states.
+- Return completion now carries its persisted correlation ID into a dedicated audit
+  processing trace, linking the return, vehicle state, transactional outbox and delivery
+  evidence. Data-quality detail pages lead with the human rule name instead of a raw
+  identifier; Knowledge Hub source titles, staged progress and provider diagnostics are
+  clearer without overstating RAGcore index evidence.
+- Improved recruiter entry metadata and social preview, route skeletons, 360 px touch
+  targets, reduced-motion behaviour, trilingual content and deterministic guide fallbacks.
+  Added automated recruiter and mobile-overflow coverage plus reproducible evidence
+  screenshot tooling. Refocused README, architecture and portfolio documentation on
+  inspectable product and reliability claims.
+- Validation: isolated backend **239 passed**; Ruff clean; mypy clean across 58 files;
+  frontend lint/build passed; full Playwright **150 passed in 5.2 minutes**; full and
+  production npm audits report zero vulnerabilities; screenshot capture **1 passed** and
+  desktop/mobile output was visually inspected.
+- Exact next action: commit and push M29, create and verify a live database backup,
+  deploy the committed archive to Unraid, then run live health, migration, browser and
+  acceptance checks before recording the final production evidence.