Document Phase 8/10 real-hardware validation in PLAN.md and refresh READMEs

- PLAN.md: mark Phase 8 (dashcam retrieval) verified on real hardware, add
  Phase 10 documenting the OOM/multipart and Cloudflare body-size fixes plus
  the chunked/resumable upload redesign, both verified end-to-end against
  real dashcam footage. Update architecture decision #3 (Mongo -> Postgres
  supersession), add unraid/Pi deploy notes and memory-budget gotcha.
- readme.md: refresh feature list (remote upload, chunked dashcam uploads,
  toggle) and project status (all 10 phases done, only cellular fallback
  untested).
- server/README.md: document the new chunked upload endpoints and the
  Cloudflare body-size-limit rationale behind them.

readme.md

@@ -36,8 +36,13 @@ i have a dream
 - 📶 **Self-hosted WiFi hotspot** so you can load the web UI on your phone from inside the car,
   with automatic fallback to your home WiFi when in range (`http://yaris.local` — no port number)
 - 🎥 **Dashcam file retrieval** — detects a USB dashcam automatically (any brand/folder layout,
-  no hardcoded device path) and copies its footage locally
-- 🗄️ Local SQLite trip logging, with an optional MongoDB remote sync path
+  no hardcoded device path), copies its footage locally, verified against real hardware
+- ☁️ **Remote upload** — a self-hosted server (Flask + Postgres, `server/`) receives trip/GPS
+  logs and dashcam footage over the internet (via Cloudflare Tunnel or a plain port-forward).
+  Dashcam videos upload in resumable 40MB chunks (works around tunnel body-size limits and keeps
+  the Pi's memory footprint flat regardless of file size); a UI toggle can pause dashcam uploads
+  independently while trip logs keep syncing
+- 🗄️ Local SQLite trip logging, retried/synced to the remote server with automatic backoff
 - 🔌 Runs fully headless as a `systemd` service, autostarting on boot
 
 ## Hardware
@@ -66,8 +71,12 @@ The app serves on `http://<host>:5000`. On the Pi it also runs as a `systemd` se
 (see [deploy/](./deploy)) and is reachable with no port number at `http://yaris.local` once the
 mDNS + port-redirect setup described in [PLAN.md](./PLAN.md) is installed.
 
+For the remote server (receives trip logs + dashcam uploads), see [server/README.md](./server/README.md).
+
 ## Project status
 
-This project was revived after a couple of years on the shelf. Progress is tracked phase-by-phase
-in [PLAN.md](./PLAN.md) — currently through **Phase 8** (dashcam retrieval), with the remote
-server/upload phase still to come.
+This project was revived after a couple of years on the shelf. All 10 planned phases are done and
+the full pipeline — OBD/GPS logging, offline web UI, WiFi hotspot, dashcam retrieval, and remote
+upload — has been verified against real hardware end-to-end, including a full real dashcam import
+and upload run. Only the SIM868 cellular fallback (for uploading while out of WiFi range) remains
+untested, pending a SIM card. Full phase-by-phase history in [PLAN.md](./PLAN.md).