diff --git a/docs/session-ledger.md b/docs/session-ledger.md
index c651f32..4ff4907 100644
--- a/docs/session-ledger.md
+++ b/docs/session-ledger.md
@@ -176,7 +176,12 @@
 gw + egress 0% loss, netbox 302 + tailscale reachable behind it. That satisfies the D-127 verified-cold-boot
 gate, so **`virsh autostart office1-opnsense` is now ENABLED**. **`voffice1` autostart ALSO ENABLED this
 session** -- so BOTH foundational VMs now autostart per D-127 (POST-REBOOT TODO item 3 DONE; `vvr1-dc0/dc1`
-stay MANUAL and do not exist yet). **STILL PENDING:** (a) the vcloud HOST patch+reboot -- kernel **6.8.0-136
+stay MANUAL and do not exist yet). **LXD service-VM autostart VERIFIED (2026-07-17):** the two LXD VMs
+inside voffice1 -- `office1-netbox` (10.10.1.10) + `office1-tailscale` (10.10.1.11) -- both already carry
+`boot.autostart=true` (MEASURED via `sudo lxc config get`; confirms the D-127 guest-update note, no change
+made). So the autostart chain is now proven END TO END: vcloud->`voffice1`/`office1-opnsense` via `virsh
+autostart`; `voffice1`->netbox/tailscale via LXD `boot.autostart` -- a vcloud host reboot self-recovers the
+whole Office1 stack with no manual `virsh start`/`lxc start`. **STILL PENDING:** (a) the vcloud HOST patch+reboot -- kernel **6.8.0-136
 is pending in apt but NOT installed** (running -134, newest installed -134, no reboot-required flag), so a
 bare host reboot gains nothing: the real step is `sudo apt update && sudo apt full-upgrade` (lands -136 + ~9
 security pkgs) THEN reboot; (b) office1-opnsense itself is still on 14.3-RELEASE-p16 (guest OS not patched,