fix(reader): correct the QR reader's identity — Dingtian DT-008, not "GEE"

An early wrong assumption named the QR/RFID access reader "GEE" /
"GEE/Fondvision" / "GEE-QR-ER80" (and summarized a raw GEE PDF as its
datasheet). There is no GEE device — it's the Dingtian DT-008
(dingtian-tech.com/en_us/qr_code_reader.html), the same vendor as the relay
board, which is why it integrates the identical HTTP-GET-push way.

Code:
- Driver symbol geeQrReaderDriver → dingtianQrReaderDriver; label →
  "Dingtian DT-008 QR/RFID reader (HTTP push)"; comments/description rewritten
  to the real DT-008 facts (Wiegand 26/34, TCP/IP, USB, RS485 — not RS-232;
  QR/barcode + ID/IC/NFC — not DataMatrix/1D).
- Persisted driverId "gee-qr-reader" → "dingtian-qr-reader" (the registry
  lookup key + the row created on assign in qr-reader.ts).
- Migration 0015 rewrites existing devices.driver_id rows so configured readers
  keep resolving (applied to the dev DB — 2 rows; the booth applies it on boot).
  Behaviour is unchanged: naming + the persisted id only.

Wiki + memory:
- Renamed entities/gee-qr-er80.md → dingtian-dt008-reader.md and
  sources/gee-qr-er80.md → dingtian-dt008.md; rewrote both to the real DT-008
  product-page specs while KEEPING all the verified-on-hardware protocol facts
  (cjihao serial, .jsp path, Connection: close). Fixed every cross-reference +
  "GEE" mention in 6 other pages. Memory gee-reader-serial-binding →
  dingtian-reader-serial-binding. The only surviving "GEE" mentions are
  deliberate naming-correction notes, the raw PDF filename, and the
  append-only log history.

Full workspace build/lint/test green; dev DB readers verified resolving to the
registered dingtian-qr-reader driver.

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

wiki/entities/subscription.md

@@ -237,7 +237,7 @@ LPR/ANPR plate identity** (the plate binding below):
     (a chosen value could be guessable or collide). The UI sends a blank QR credential; the server
     mints the value and returns it (so the UI can print it). **An RF credential, by contrast, carries
     the physical card id, so it is operator-entered.**
-  - **Reader output = TCP/IP full string** (decided 2026-06-18, the [[gee-qr-er80|host-in-the-loop
+  - **Reader output = TCP/IP full string** (decided 2026-06-18, the [[dingtian-dt008-reader|host-in-the-loop
     QR reader]] path): the reader delivers the whole decoded string, so the code length is free
     (unguessable token). *If a site ever wires the reader as **Wiegand 26/34** instead, a scanned
     QR truncates to a 24-/32-bit number — the generated code would then have to be a numeric id in
@@ -255,7 +255,7 @@ LPR/ANPR plate identity** (the plate binding below):
 - **RF tag / chip / card — selectable later, NOT live yet.** An RFID/proximity credential, read
   **host-side** (reader → host → `pulseOpen`). **LIVE since 2026-06-18** — the operator selects RFID
   and **reads the card off a physical reader** (see "Enrolling a card" below) rather than typing the
-  number. The GEE readers are combo QR + RFID (ID/IC/NFC), so the same device captures both. A
+  number. The Dingtian DT-008 readers are combo QR + RFID (ID/IC/NFC), so the same device captures both. A
   Wiegand-out reader keeps a future autonomous path open ([[entry-exit-readers]]); the
   [[dingtian-relay]] has no onboard card list.
 - **Plate (LPR/ANPR) — matching is BUILT, the live SOURCE is the one missing wire.** When plate-bound
@@ -296,7 +296,7 @@ traffic, so capture must **borrow one reader briefly without blocking the other*
 A subscription is a one-to-many aggregate: it may hold **several credentials at once** — e.g. a QR
 **and** an RFID card (and later NFC). Each is its own `subscription_credentials` row; any of them
 resolves the same subscription at the barrier. (NFC works today as an `rf` credential on the combo
-GEE reader; a distinct `nfc` `kind` is a small future labelling-only addition.)
+Dingtian DT-008 reader; a distinct `nfc` `kind` is a small future labelling-only addition.)
 
 Crucially, **entry and exit are NOT bound to the same credential.** Originally the session was keyed
 by the exact credential value read, so you had to leave with whatever you arrived with — an