feat(anpr): subscriber-entry bridge + admin disable toggle

Wire the lane camera's vehicle event into the gated subscription flow: on a
vehicle/active push from an opt-in (config.anpr) camera, AnprBridge pulls a fresh
snapshot, runs ANPR, applies a stricter entry confidence floor, debounces, and —
matching the plate to a subscription BEFORE emitting — emits a kind:"plate" read.
The existing ReadDispatcher -> SubscriptionFlow then signs the entry/exit and opens
the barrier. A plate is never the sole authority: it routes through the same gate
(active/window/blocklist/car-count) as any credential. Fail-soft, fire-and-forget,
subscriber-only by construction. Field-verified end to end (plate AA504LX opened the
entry barrier and appended a signed vehicle_entry).

Add an admin master switch (site_config.anpr_entry_enabled, default ON) in Site
Settings that disables ONLY the barrier-driving bridge; advisory snapshot-ANPR and
lane busy/free are unaffected. Read live per event, so toggling takes effect with no
restart. Migration 0013 (additive ALTER ADD COLUMN, default 1).

- New: apps/server/src/anpr-entry.ts (AnprBridge) + tests (9)
- hikvision-alarm.ts hands vehicle detections to the bridge (fire-and-forget) + wiring tests (3)
- server.ts reorders the read flows above the hik-alarm registration
- snapshot.ts exports buildCamera for reuse
- env: VISION_ENTRY_MIN_CONFIDENCE (0.85), ANPR_DEBOUNCE_MS (12000)
- site route + SiteSettings checkbox + i18n (sq/en parity)
- wiki: lane-presence-and-anpr-entry / lpr-camera / index / log -> BUILT

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

wiki/concepts/lane-presence-and-anpr-entry.md

@@ -13,8 +13,8 @@ Two related things a camera's vehicle detection feeds, worked out over a long fi
 detection area" conclusion):
 
 1. **Lane busy/free** — BUILT. An advisory barrier light on the booth.
-2. **ANPR subscriber entry** — PLANNED. A subscriber's plate, read from the lane camera, drives
-   their entry/exit through the EXISTING [[subscription]] flow. The "bridge" below.
+2. **ANPR subscriber entry** — BUILT (2026-06-22). A subscriber's plate, read from the lane camera,
+   drives their entry/exit through the EXISTING [[subscription]] flow. The "bridge" below.
 
 The camera (Hik `DS-2CD1043G2-LIU`) only emits `VMD` events with `eventState=active` and a
 `targetType` of `vehicle`/`human` — a coarse **presence** signal, never an identity. Everything
@@ -46,11 +46,24 @@ nothing** (never blocks a ticket or opens a barrier; the standing rule).
   also clears promptly after departure.
 - A `both`-direction camera marks both lanes. Pushed over the existing `/api/ws` (kind `lane-status`).
 
-## 2. ANPR subscriber entry — THE BRIDGE (PLANNED, not built)
+## 2. ANPR subscriber entry — THE BRIDGE (BUILT 2026-06-22)
 
-> **"Bridge" = a HANDLER FUNCTION in `apps/server` (≈40 lines, e.g. `anpr-entry.ts`). NOT a new
+> **"Bridge" = a HANDLER CLASS in `apps/server/src/anpr-entry.ts` (`AnprBridge`). NOT a new
 > service / container / app.** It is in-process glue that calls things that ALREADY exist.
 
+**As built:** `hikvision-alarm.ts`, on a `vehicle`/non-`inactive` push from an `anpr`-opted-in
+camera, hands the deviceId to `AnprBridge.onVehicleDetected()` (fire-and-forget, never awaited on the
+camera's 200). The bridge: debounce (camera-level, pre-snapshot) → `captureSnapshot` (fresh pull, via
+the reused `snapshot.ts buildCamera`) → `vision.analyze` → entry confidence floor
+(`VISION_ENTRY_MIN_CONFIDENCE`, 0.85) → normalize plate → **`subscriptionFlow.match()` (match BEFORE
+emit)** → if a subscriber, `deviceEvents.emitRead({kind:"plate"})`; if not, record an advisory
+`anpr-skip` device_event and stop. The existing `onRead → ReadDispatcher → SubscriptionFlow.run()`
+then does the gated entry/exit + barrier open. Constructed in `server.ts` (the flows were reordered
+above the hik-alarm registration so the bridge can take `subscriptionFlow`). Fail-soft throughout —
+any snapshot/vision error degrades to the subscriber's card/QR, never throws into the push handler.
+Two new env knobs: `VISION_ENTRY_MIN_CONFIDENCE` (0.85), `ANPR_DEBOUNCE_MS` (12_000). Covered by
+`anpr-entry.test.ts` (7) + `hikvision-alarm.test.ts` wiring (3).
+
 The goal (narrowed deliberately — see Rejected below): **a subscriber's plate, read by the lane
 camera, admits them through the same gated flow a QR/card scan uses.** Scope was cut to subscribers
 ONLY — no queue segmentation, no per-car tracking, no make/model, no ticket-button gating.
@@ -64,7 +77,7 @@ Almost everything already exists; the bridge is the one missing wire:
 | Read the plate | ✅ [[opencv-anpr-service]] `/analyze` (~50 ms on the DEV PC; appliance TBD) |
 | Match a plate → subscriber | ✅ `subscription-flow.ts` `match()` + `subscription_plates` (`via:"plate"`) |
 | Plate read → gated entry/exit | ✅ `read-dispatch.ts` + SubscriptionFlow (active/window/blocklist/car-count) |
-| **Emit the plate onto the read bus** | ❌ **the bridge** — today the snapshot ANPR only RECORDS the plate as advisory telemetry; it does NOT `emitRead`. hik-alarm.ts literally says "NOT a DeviceReadEvent yet". |
+| **Emit the plate onto the read bus** | ✅ `anpr-entry.ts` (`AnprBridge`) — on a vehicle push from an `anpr` camera it snapshots → analyzes → matches a subscriber → `emitRead({kind:"plate"})`. (Built 2026-06-22.) |
 
 **The bridge logic:** on a camera `vehicle`/`active` event from an **opt-in** camera (`config.anpr`),
 snapshot → `vision.analyze` → if a plate clears a **HIGH** confidence floor → **debounce** → emit