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>

notes/PLAN-v2.md

@@ -1,8 +1,11 @@
 # socktop-swipe v2 — release plan
 
-Status: **implemented**, 2026-09-09. Milestones 1-7 are done on branch `v2-rust`;
-milestone 8 (the Wyse 3040 validation) is the remaining acceptance gate. Where the
-built thing differs from this plan, `notes/DESIGN.md` is authoritative.
+Status: **implemented and in service**, 2026-09-09. Milestones 1-7 done on branch
+`v2-rust` (PR #1); the LattePanda rack display has been running v2 since, and
+passed a physical swipe test and a cold boot. Milestone 8, the Wyse 3040 install
+following only the README, is the remaining acceptance gate.
+
+Where the built thing differs from this plan, `notes/DESIGN.md` is authoritative.
 
 v1 is three POSIX shell scripts driving lisgd and tmux. It works and is running on
 the rack display today, but it hard-codes a single linear carousel of socktop hosts,