Remove UHPPOTE/ZKTeco; Dingtian is the only access driver

Neither UHPPOTE nor ZKTeco is used — the Dingtian relay controller was chosen
and verified. Remove their code and re-scope the wiki.

Code:
- delete access-uhppote.ts, uhppoted.d.ts, access.ts (zkteco/esp32-relay stubs),
  and the three uhppote-*.mjs hardware test scripts.
- remove the `uhppoted` npm dependency from @parking/devices and @parking/server.
- unregister uhppote/zkteco/esp32-relay from the driver registry; drop their
  exports. Catalog access drivers = dingtian only. Build green (5/5).
- refresh now-stale example comments (registry/interfaces/setup/api) to use
  current examples; keep the two "UHPPOTE blocker" references that explain why
  the precondition capability exists.

Wiki (kept pages, re-scoped):
- uhppote-controller, zkteco-controller -> rejected/historical with callouts;
  uhppote-vs-esp32 -> historical (detection-vs-prevention lens still useful).
- re-point all "current device" framing (standing-decisions, bom, overview,
  open-questions, device-registry, device-discovery, index) to dingtian-relay.
- transferable concepts (network-isolation, event-log-ingestion, barrier-not-a-
  door, threat-model) untouched. Raw source immutable. Links lint clean.

wiki/entities/uhppote-controller.md

@@ -1,33 +1,37 @@
 ---
 type: entity
-tags: [parking, hardware, access-control, current-choice]
+tags: [parking, hardware, access-control, rejected, historical]
 sources: [parking-system-architecture]
 updated: 2026-06-15
 ---
 
-# UHPPOTE Controller (current choice)
+# UHPPOTE Controller (rejected — historical)
 
-The starting access-control hardware: a **UHPPOTE Wiegand 26/34 network controller (4-door)** —
-a cheap reader-plus-relay frontend, acceptable **provided you understand its limits**. The plan
-is UHPPOTE now → ZKTeco later (see [[bom]]). (See [[parking-system-architecture]] §6.)
+> **❌ NOT USED. Replaced by the [[dingtian-relay]] controller** (and its driver/test code
+> removed). Kept as the record of *why* — its firmware-fixed push-button blocker
+> ([[access-controller-button-flow]]) is what drove the switch to a board with decoupled inputs.
+> The transferable lessons below (network isolation, append-only log ingestion, "a barrier is not
+> a door") still apply to any access device.
 
-> **⚠️ Entry-flow blocker (verified on hardware):** the push-button input **auto-opens the relay
-> in firmware** — there's no command to make it report-without-opening — so it **cannot** do
-> ticket-first entry (`button → print → open`). Fine as a host-**commanded relay** and for
-> [[wiegand]]/permit lanes, but **not** the button-driven entry lane as wired. Full detail and
-> options: [[access-controller-button-flow]].
+The original starting hardware: a **UHPPOTE Wiegand 26/34 network controller (4-door)** — a cheap
+reader-plus-relay frontend. (See [[parking-system-architecture]] §6.)
+
+> **⚠️ The fatal limit (verified on hardware):** the push-button input **auto-opens the relay in
+> firmware** — no command makes it report-without-opening — so it **cannot** do ticket-first entry
+> (`button → print → open`). This is *the* reason it was dropped: full detail and the resolution in
+> [[access-controller-button-flow]].
 >
-> **Verified working on the real unit** (serial 225088491, fw 09120): host-commanded `openDoor`
-> on doors 1 & 2 (physically actuated, `reason="remote open door"`); button presses captured live
-> (`reason="push button ok"`); [[device-discovery]] scan. Test scripts: `apps/server/scripts/`.
+> **What was verified on the real unit** (serial 225088491, fw 09120) before retiring it:
+> host-commanded `openDoor` on doors 1 & 2 (physically actuated, `reason="remote open door"`);
+> button presses captured live (`reason="push button ok"`); UDP-broadcast [[device-discovery]].
+> The driver, `uhppoted` dependency, and test scripts have since been removed from the codebase.
 
-> **Implementation:** integrated via the official **`uhppoted`** npm package (MIT, by the
-> `uhppoted` org — `github.com/uhppoted/uhppoted-lib-nodejs`), added to `@parking/devices` as the
-> `uhppote` access driver ([[device-registry]]). It exposes exactly the protocol commands this
-> design needs: `openDoor`, `getStatus`, and the event-log set (`getEvent`, `getEventIndex`,
-> `setEventIndex`, `recordSpecialEvents`) plus `setListener`/`listen` for auto-push — see
-> [[event-log-ingestion]]. Transport defaults to **UDP** (broadcast `…:60000`), with optional
-> per-call TCP on newer firmware. The driver also implements **[[device-discovery]]**
+> **Past implementation (removed):** was integrated via the official **`uhppoted`** npm package
+> (MIT — `github.com/uhppoted/uhppoted-lib-nodejs`) as the `uhppote` access driver. It exposed
+> exactly the protocol commands the design needs: `openDoor`, `getStatus`, and the event-log set
+> (`getEvent`, `getEventIndex`, `setEventIndex`, `recordSpecialEvents`) plus `setListener`/`listen`
+> for auto-push — see [[event-log-ingestion]]. Transport defaulted to **UDP** (broadcast `…:60000`),
+> with optional per-call TCP on newer firmware. The driver also implemented **[[device-discovery]]**
 > (`getDevices` broadcast) so the setup wizard can scan for controllers. Note: the lib pulls one
 > trivial extra dep (the npm `os` shim) and uses UDP broadcast, which needs socket broadcast
 > permission on the host.