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/sources/qrcode-sdk.md

@@ -5,13 +5,13 @@ sources: [qrcode-sdk]
 updated: 2026-06-16
 ---
 
-# Source: QRCode SDK v1.6.5 (GEE/Dingtian QR reader)
+# Source: QRCode SDK v1.6.5 (Dingtian DT-008 QR reader)
 
-Vendor SDK for the QR access reader ([[gee-qr-er80]]; also branded Dingtian). Defines the
+Vendor SDK for the QR access reader (the Dingtian [[dingtian-dt008-reader]]). Defines the
 reader↔server **HTTP protocol** — the missing piece the datasheet omitted. Files at
 `QRCode_sdk - QRCode_v1_6_5/sdk/` (config tool `QRCode_v1_6_5.exe`, demos in C#/PHP/VC++, protocol
 docs `readme.txt`, `qrcode_HTTP_GET.txt`, `VC++/how to.txt`). **Not copied into `raw/`** — bulky +
-binaries; this summary is the faithful capture. Entity: [[gee-qr-er80]].
+binaries; this summary is the faithful capture. Entity: [[dingtian-dt008-reader]].
 
 ## The protocol — HTTP GET poll, server replies the verdict
 
@@ -52,7 +52,7 @@ GET /qa/mcardsea.php?cardid=445D2C&mjihao=1&cjihao=HW256097&status=11&time=15404
 
 This is **host-in-the-loop, synchronous**: the GET *is* the access query; our JSON reply *is* the
 decision. So the backend endpoint must **decide (valid/invalid + direction) and reply** — richer
-than a fire-and-forget read. Direction comes from the `status` low digit. See [[gee-qr-er80]] +
+than a fire-and-forget read. Direction comes from the `status` low digit. See [[dingtian-dt008-reader]] +
 [[device-input-flow]].
 
 ## Defaults / misc