Adding pinned uuid for rootfs

docs/TODO.md

@@ -113,6 +113,23 @@ boot LAN.
   writable → multi-user.
 - This validation **gates** item #1 (network-manager port) and item #3
   (errata → design v3).
+- **Bench findings (boot debug, 2026-06-14):**
+  - Initramfs has no resolver (dracut writes `resolv.conf` only via its own
+    DHCP path, not a manual `dhclient`), so the NVMe discovery address must be
+    an **IP**, not a DNS name — build with `-var nvmet_traddr=192.168.50.10`.
+    Old UKIs carrying `nvme.fleet.lab` can't connect early in boot.
+  - NVMe controller indices are **not stable**: a transient discovery
+    controller can take `nvme0`, pushing the I/O controller to `nvme1`. The
+    hardcoded `/dev/nvme0n1` in the cmdline was a latent brick. **Fixed:**
+    namespace UUID pinned on the target (`spdk-setup.sh` `add_ns -u
+    f1ee7000-0000-4000-8000-000000000001`) and the cmdline now references
+    `/dev/disk/by-id/nvme-uuid.<uuid>` (`extract-artifacts.sh`). The two
+    constants MUST stay in sync; make them version-specific for #6.
+  - `nvme_tcp`/`nvme_fabrics` must be loaded before `/dev/nvme-fabrics` exists
+    (dracut's `nvmf` module does this in a normal boot; at `rd.break` modprobe
+    manually).
+  - SPDK: add the listener to the discovery subsystem explicitly
+    (`nqn.2014-08.org.nvmexpress.discovery`) to silence the deprecation warning.
 
 ## [ ] 6. Rolling fleet updates (multi-version serve → cohort reboots)