update docs

docs/developer/boot.md

@@ -13,8 +13,9 @@ are never used as cartridge identities.
 
 The software boot path has passed on an ARM virtual machine using the actual
 FDS Pi kernel. That does not verify Pi firmware, NVMe, RP1, display output, USB
-power or physical boot speed. Those checks are deferred until the machine is
-assembled. M5 now provides an ordinary-user `FDS>` console with a temporary home
+power or physical boot speed. Those checks still require physical testing; follow
+the [real-hardware setup guide](../hardware-setup.md). M5 now provides an
+ordinary-user `FDS>` console with a temporary home
 and measured boot events. Password login remains locked; this is an intentional
 local single-user session. The M2 test VM separately offers a temporary root
 development shell. See [native init](init.md) and [performance reports](performance.md).

docs/developer/dasung.md

@@ -105,6 +105,8 @@ No world-writable USB rule, systemd unit, or runit service is installed.
 The video timing was confirmed on the original AMD workstation, **not on a Pi**.
 The original USB-C video connection is not a Pi cabling prescription. Pi connector,
 cable/adapter, mode acceptance, and picture stability require hardware validation.
+For the current HDMI video plus USB control procedure, including separate monitor
+power and a reversible native-EDID experiment, use the [display guide](../dasung.md).
 Desktop 2× scaling is separate from EDID timing; a console uses its own font size.
 
 FDS configures `display.enabled=false` and `hotplug="none"`: the daemon handles