docs: mark RESUME NEXT STEPS #1/#2 done; VM durable stack verified

RESUME-cubefs-daemon.md

@@ -84,13 +84,20 @@ Two separate bugs hid behind the "FUSE write didn't reach the daemon" symptom:
   assertion; `run_fs_tests` is now backend-agnostic (self-seeds its fixture).
 
 ## NEXT STEPS (remaining, low priority)
-1. Add a `--features mount` build to the VM IMAGE BUILD STEP (the run_vm / build
+1. DONE 2026-08-13 — `build_vm.sh` now rebuilds cube binaries with
-   script) so a from-scratch image bake includes the FUSE adapter — the host
+   `--features cubefs/mount` into a clean staging dir before copying, and aborts
-   `./check` already covers it; only the image-provisioning script is behind.
+   if `cubefs-mount` is missing. A from-scratch image bake can no longer silently
-2. Optionally surface `DaemonBackend::put` failures as FUSE EIO instead of
+   omit the FUSE adapter. (Prior to this the script copied from host
-   eprintln-only (best-effort today, acceptable).
+   `target/debug`, so a fresh host with no `mount` build would ship a broken image.)
-3. Visually launch the "CUBE Shell" desktop launcher to confirm end-to-end (file
+2. DONE 2026-08-13 (commit f40b448) — `DaemonBackend::put` failures now surface as
-   level already verified: cube-term -> cubec -> /run/cube/cube.sock).
+   FUSE EIO via `put_checked` instead of eprintln-only.
+3. NOTE: VM is not auto-started on host boot. To bring the cold stack up:
+   `bash /root/run_vm_window.sh` (owned by luulu; shows the GTK window) — or
+   `launch_vm_detached.sh` for headless. The `fixed-durable-20260813` snapshot
+   captures the working durable stack.
+4. OPTIONAL (cosmetic): visually launch the "CUBE Shell" desktop launcher to
+   confirm end-to-end at the file level. Already verified wired:
+   cube-term -> cubec -> /run/cube/cube.sock.
 
 ## KEY FILES
 - /home/CUBELinux/CUBELinux-2/cubesys/src/commands.rs  (raw* commands + helpers)