docs(wiki): decide vision service packaging — apps/vision/ in the monorepo

Settle WHERE the host-side ANPR service lives and how it joins the build: in this
monorepo at apps/vision/ (not a separate repo), still a separate OS process called
over localhost HTTP, wired into the Turbo graph via a thin package.json shim whose
scripts shell to Python tooling (uv/uvicorn/ruff/pytest). Co-located source honors the
vision-service runtime+license isolation decision (AGPL reach is a linking boundary,
not a folder); the fast-alpr MIT baseline removes most of the split-repo pressure
anyway. New page vision-service-packaging; updates vision-service, opencv-anpr-service,
the CLAUDE.md layout, index, log. Not built yet — packaging decision only.

Claude-Session: https://claude.ai/code/session_01Xcm6ikLgGoCxxHrxtjkk5V

wiki/entities/opencv-anpr-service.md

@@ -34,7 +34,9 @@ recognition **host-side on ordinary IP-camera snapshots**, replacing the dedicat
 
 - A **Python service** (e.g. FastAPI) running **on the appliance**, called by the Node backend over
   **localhost HTTP** (`POST /analyze` with the JPEG bytes the camera driver already pulls — see
-  [[lpr-camera]] "driver/storage boundary": `Snapshot.bytes`).
+  [[lpr-camera]] "driver/storage boundary": `Snapshot.bytes`). **Source lives in this monorepo at
+  `apps/vision/`** (Turbo shim; `uv`-managed deps) — co-located source, separate process; see
+  [[vision-service-packaging]].
 - **Fully offline** ([[offline-first]]): all inference is local, no cloud. Model weights ship on the
   appliance.
 - **Process isolation is deliberate** — it keeps a heavy Python/native/AGPL stack out of the