Add debug to packer build

docs/TODO.md

@@ -162,6 +162,17 @@ boot LAN.
     `${systemdsystemunitdir:-/usr/lib/systemd/system}` fallback and `return 1`
     if the unit didn't land, so the build fails loudly instead of shipping a UKI
     that can't connect its root.
+    Second gotcha: the build assertion `lsinitrd … | grep -q 'nvmf-connect.service'`
+    was a **false negative** — `grep -q` exits on first match, closes the pipe,
+    `lsinitrd` dies of SIGPIPE, and under `pipefail` the pipeline reports failure
+    even though the unit IS present. This masked the fact that the systemd unit
+    install was working all along. Fix: `lsinitrd > file; grep -q … file` (no
+    pipe). Never `lsinitrd | grep -q` under pipefail.
+    Bonus: the survivor listing confirmed nvme-cli's native autoconnect bits ARE
+    in the initramfs (`/usr/sbin/nvmf-autoconnect.sh`,
+    `/etc/udev/rules.d/95-nvmf-initqueue.rules`) — so the fully-native
+    `rd.nvmf.discover` autoconnect path is available as a fallback if the unit
+    doesn't fire on boot.
     **⚠ The secure path has the same dependency on the
     (absent) nvmf autoconnect** — when 802.1X is re-enabled, the macsec0 path
     must likewise drive `connect-all` (or the network-manager port #1 must wire