fix(velox): trace the dead touchpad to its own connector, and repair two lost todo headings

The touchpad fault was an interrupt line that never fired: the device
enumerated, hid-multitouch bound, and the handler sat correctly on amd_gpio
pin 8, but the count stayed at zero across all 24 CPUs under active use and
the i2c-HID reset timed out at every boot. A live USB reproduced it exactly,
which ruled out software. The fix was the touchpad's own connector — the
input-cover ribbon I reseated first fixed the phantom power button and left
this untouched, and the 4-pin connector beside the silkscreen is GND and VCC
only, so it could never have carried i2c. Both faults from the mainboard swap
are now closed.

Two task headings had been overwritten by inserts at the top of Open Work, and
I recovered both verbatim from the commits that introduced them. One displaced
task had ridden an archived parent into Resolved, so an open bug had been
sitting outside Open Work for weeks.

Filed the install placeholder passwords still live on this laptop as an [#A],
graded on severity alone rather than the frequency matrix: full-disk encryption
protected by a dictionary word does no work at all on a machine that travels.

Corrected the ARCHSETUP_DIR line in the reinstall runbook. It carried a tilde on
the right-hand side of an assignment, which zsh does not expand, so following it
would have produced an ISO with the installer silently absent.

1 files changed, 8 insertions, 1 deletions

diff --git a/working/velox-reinstall/velox-reinstall-runbook.org b/working/velox-reinstall/velox-reinstall-runbook.org
index 02671e2..0c14946 100644
--- a/working/velox-reinstall/velox-reinstall-runbook.org
+++ b/working/velox-reinstall/velox-reinstall-runbook.org
@@ -22,8 +22,15 @@ Fallback ordering if the test finds a real gap:
   the microcode vendor-detection fix (archsetup, 2026-08-08) and was built
   without ARCHSETUP_DIR at all.
   #+begin_src sh
-  cd ~/code/archangel && sudo ARCHSETUP_DIR=~/code/archsetup ./build.sh
+  cd ~/code/archangel && sudo ARCHSETUP_DIR="$HOME/code/archsetup" ./build.sh
   #+end_src
+  Two traps in that one line, and either alone silently produces a bare ISO
+  with archsetup absent (archangel, 2026-08-20). The =VAR=value= form is
+  required because sudo's =env_reset= discards an exported variable. And
+  =$HOME= is required because zsh does not expand a tilde on the right-hand
+  side of an assignment — the earlier =ARCHSETUP_DIR=~/code/archsetup= here
+  passed the literal string. build.sh now warns and reports baked/not-baked
+  in its closing summary, so the failure is visible rather than silent.
 - [ ] build.sh fixes before the final rebuild (archangel repo):
   - rsync exclude for =.ai= (keeps =archsetup/.ai/private-design/= — the
     credential audit — off the portable USB stick).