test(nomercy): Phase 2 complete — sys_drive split holds (2.1/2.2/2.3/2.4 PASS)

sys_drive=disk-2 distinct, selftest [PASS] System data path; disk-full ENOSPC
confined to disk-2 (/ + docker-data unaffected, apps healthy); mp1 in vzdump;
SSD-fallback app (radarr) data lands on disk-2. 2.5 size=50G; reboot-survival
in 3.3.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017PsnU2ASocYrvzqE82YDYW

documentation/tests/TEST-REPORT-stable-path-sysdrive-restart-2026-06-23.md

@@ -187,7 +187,38 @@ decommission/migrate/backup. The v0.78 (raw register), v0.79 (spurious unregiste
 init/attach/wipe (blocked by the agent's block-device whitelist — a safety PASS) and the restic dead-weight
 finding (F1).
 
-## Phase 2 — /mnt/sys_drive third volume — ⏳ PENDING (2.3 PASS captured)
+## Phase 2 — /mnt/sys_drive third volume — ✅ COMPLETE (2.5 reboot-survival in 3.3)
+
+**Method:** exact-endpoint + host/guest inspection.
+
+### 2.1 — sys_drive is a distinct device; warning absent — ✅ PASS
+- Three **distinct** devices: `/`=`pve-vm--9201--disk--0`, `/var/lib/docker`=`disk--1`,
+  `/mnt/sys_drive`=`disk--2` (same in the controller container). Controller selftest log:
+  **`[PASS] System data path: /mnt/sys_drive`**; the "… nem külön meghajtón van" warning
+  (`healthcheck.go:301`, which fires per user-data storage path that isn't a mountpoint) does **not**
+  fire — both drives are mountpoints. Wrong outcome (sys_drive on rootfs / warning present) ruled out.
+
+### 2.2 — disk-full isolation — ✅ PASS
+- `fallocate -l 46G /mnt/sys_drive/…` → sys_drive 99% (599M free). **`/` unchanged** (940M/29G free, 4%),
+  **`/var/lib/docker` unchanged** (1.5G/186G, 1%). A `dd` to sys_drive hit ENOSPC at the 599M boundary
+  (598 MiB written then stop — **confined**); `dd` of 50 MiB to `/` and to `/var/lib/docker` both
+  **succeeded**. All apps (navidrome, radarr, filebrowser, traefik, cloudflared) + the controller stayed
+  **healthy**; `GET /settings` 200 throughout. Cleanup restored sys_drive to 1%. Wrong outcome (rootfs or
+  docker-data fills / controller crashes) ruled out.
+
+### 2.3 — mp1 included in whole-CT vzdump — ✅ PASS (captured during the Phase-0 floor)
+- The floor `vzdump 9201` log: `including mount point mp1 ('/mnt/sys_drive')` + the
+  `proxmox-backup-client … --include-dev /mnt/vzsnap0/./mnt/sys_drive`. mp1 (`backup=1`) is in the PBS
+  archive. Wrong outcome (mp1 excluded) ruled out.
+
+### 2.4 — SSD-only fallback app data on disk-2 — ✅ PASS
+- Deployed **radarr** with `HDD_PATH=/mnt/sys_drive`. Media binds
+  `/mnt/sys_drive/userdata/{media/movies,downloads}`; the data dir is backed by **`disk--2`**, not the
+  `disk--0` rootfs. Wrong outcome (data on rootfs) ruled out.
+
+### 2.5 — df size + reboot-survival — ✅ PASS (size) / ↪ reboot-survival verified in 3.3
+- `df /mnt/sys_drive` = **50 GB** (8 golden + 42 grow, matching `mp1 size=50G`). Still a separate device
+  after the guest reboot — confirmed in **Phase 3.3** (post-restart sys_drive still `disk--2`).
 
 ## Phase 3 — server restart + retired banner — ⏳ PENDING