docs: record the LattePanda deployment and the traps it turned up

The rack display has been running v2 since today and passed a physical swipe
test and a cold boot, so the hardware table now says what is actually in
service and what is merely intended: the Wyse 3040 has not been tried yet and
should not read as though it has.

notes/HARDWARE-NOTES.md gains the two traps that cost the most time during the
deployment, both of which will recur:

lightdm autologin fires when a seat starts, not after a logout, so `i3-msg
exit` does not test the autostart -- it strands a keyboard-less wall display at
a greeter that nobody standing at the rack can get past. Only a real reboot
tests the boot path.

And `ssh host 'sudo ...'` allocates no TTY, so sudo has nowhere to prompt and
fails; chaining the rest of the recovery behind `&&` then swallows it silently.
Use `ssh -t`, and `;` for steps that must run regardless.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

README.md

@@ -45,12 +45,12 @@ you left.
 
 ## Hardware
 
-| Part | What was used | Notes |
+| Part | What was used | Status |
 | --- | --- | --- |
-| Display host | LattePanda (Atom x5-Z8350, 1.9 GB) | Debian 11, i3 on X11 |
-| Display host | Dell Wyse 3040 (Atom x5-Z8350, 2 GB) | ~$35 used; 8/16 GB eMMC, DP out |
-| Panel | GeeekPi 9" 1280x720 3U touchscreen | ILITEK USB touch |
-| Mounting | [`cad/`](cad) — 19" rack adapter | 3D-print or laser-cut aluminium |
+| Display host | LattePanda (Atom x5-Z8350, 1.9 GB), Debian 11, i3 on X11 | in daily use |
+| Display host | Dell Wyse 3040 (Atom x5-Z8350, 2 GB), 8/16 GB eMMC, DP out | not yet tried |
+| Panel | GeeekPi 9" 1280x720 3U touchscreen, ILITEK USB touch | in daily use |
+| Mounting | [`cad/`](cad) — 19" rack adapter | printed and in the rack |
 
 Any Linux box with a USB or DSI touchscreen will do. It is deliberately modest
 hardware: the whole point is a display that idles at a few watts.