pod: the HARDWARE RIO on COM1 (L4CONTROLS=RIO:COM1,KEYBOARD)

The real cockpit board now drives the cab instead of PadRIO, frozen in the
profile so all five tester launchers get it.  Nothing above the seam changed
-- the 109-mapping L4 control table installs exactly as on a desktop, and the
cab keeps the GLASS display stack.  BT_PLATFORM=pod is NOT the way to this;
that would drag in the 1995 gauge path.  RIO:COM1 -> \.\COM1 at 9600 8N1.

Evidence the link is real, not just "the port opened":
  RIO successfully initialized!
  FAILURE.LOG: 4 missing boards (Slot 3:0, 3:2, 4:0, 5:0), 16 dead lamps
  [ctrlmap] push stick x=0.0595238 y=0   <- physical stick outside deadband
A specific 4-of-many board inventory is the proof: a dead serial line reports
the WHOLE address space missing.  Reproduced after deleting FAILURE.LOG.  The
dead lamps are the boards this partial crash cart does not have.

Banner honesty: "GLASS (PadRIO ...)" was hardcoded, so a wired cab reported
PadRIO on the very line you read to check which device won.  It now names the
resolved one -- GLASS (hardware RIO; plasma off [L4PLASMA]).

Recorded in pod-hardware.md, including that RIO and PAD are mutually exclusive
(both assign rioPointer, last token wins) and that a CENTRED stick reads x=0,
which is indistinguishable from no data -- so the by-hand check of stick,
throttle, pedals, buttons and the Ranger calibration is still outstanding.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Rw7No5wLTpkaUgA3ANbtZZ

context/pod-hardware.md

@@ -339,6 +339,39 @@ Steam MP needs the **client installed and logged in** (AppID 480/Spacewar, so an
 purchase); installed on the cart 2026-08-06. ⚠ **#68: a failed JOIN/HOST exits the process
 SILENTLY** — "Steam not running" and a real crash look identical to a player.
 
+### The HARDWARE RIO is live on the cart (2026-08-06) [T2]
+`L4CONTROLS=RIO:COM1,KEYBOARD` in the frozen profile — the real cockpit board instead of PadRIO.
+The whole stock path above the seam (mapper, lamps, streamed `.CTL` mappings) runs unchanged; the
+109-mapping `L4` control table installs exactly as it does on a desktop. **This is independent of
+the platform profile** — the cab keeps the GLASS display stack (panels + RGB split) and only the
+input device changes, which is what the glass/PadRIO seam was built for. Do NOT reach for
+`BT_PLATFORM=pod` to get it.
+
+- **Wiring:** `RIO:COMn` → `\\.\COMn` at **9600 8N1** (`L4SERIAL`); bare `RIO` defaults to COM1.
+  Reads are non-blocking (`ReadIntervalTimeout=MAXDWORD`, totals 0), so an absent or dead board
+  cannot hang the game — it just goes quiet.
+- **RIO and PAD are MUTUALLY EXCLUSIVE** — both assign `rioPointer` in the `L4CONTROLS` parser, so
+  the last token wins. Selecting the hardware RIO turns the XInput pad OFF on that machine.
+  `KEYBOARD` is safe alongside: it only sets `flags.keyboardExists` and never touches
+  `primaryControlType`.
+- **The board's own self-test is the diagnostic.** `RIO::RIO` runs it (`perform_tests = True` by
+  default) and writes `content\FAILURE.LOG` pages `RIOBoardErrors` / `RIODeadLamps` / `RIOErrors`,
+  deleting them first so the file is always current. On the cart, reproducibly: **4 missing boards**
+  (`Slot=3:Address=0`, `3:2`, `4:0`, `5:0`) and **16 dead lamps** (`AuxUpperRight1-8`,
+  `AuxUpperCenter1`, `TeslaRelay1/3`, `PanicButton`, `IcomAmpEnableRelay`, `IcomIncRelay`,
+  `FloorEntry`, `undefined_0x17`) — the crash cart is a PARTIAL cab, and those are the boards it
+  does not have. **A specific 4-of-many inventory is itself the proof the link is good**: a dead
+  serial line reports the whole address space missing, not four slots.
+- **Input reaching the mech** was seen live as `[ctrlmap] push stick x=0.0595238 y=0` with nobody
+  at the cab — the physical stick sitting just outside the 5% deadband. NB when the stick is
+  centred this reads `x=0`, which is indistinguishable from no data: a centred-stick zero proves
+  nothing either way. ⚠ **Not yet checked by hand:** that stick/throttle/pedal travel and the
+  physical buttons drive the mech correctly, and whether the cab's pots match the `Ranger`
+  calibration baked into `RIO::RIO` (`JoystickX -96..96`, `JoystickY -97..108`, `Throttle 0..800`,
+  pedals `0..470`). A mismatch shows up as drift or short travel, not as an error.
+- The boot banner names the resolved device — `GLASS (hardware RIO; plasma off [L4PLASMA])`. It
+  used to hardcode "PadRIO", which is a lie on a wired cab and exactly the line you read to check.
+
 **Working on the cart, remotely.** SSH over Tailscale lands in **session 0**, which has a dummy
 "WinDisc" display and CANNOT see or enumerate session 1's windows — GUI work must go through
 `schtasks /run /tn BT411Run` (task registered `/IT`), and window enumeration over SSH silently