Safe removal (R-1044), found on Tester 1 G4: the drive gate leaves a safely removed drive alone (no false RETURNED/ABSENT, no mail); presence = backing device, not the agent's state

Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS

CHANGELOG.md

@@ -33,6 +33,11 @@ Not released yet (bake → vouch → floor, `09` §3 decision 247). Design: felh
   `TestRun_SecondRunWritesNothing` (red-proved: the measured repeated qBittorrent writes).
 - **Fixed on Tester 1 (Part G1):** qBittorrent 5 answers a good login with HTTP 204, not 200 — the wiring refused it
   (`login: HTTP 204`). Both logins accept 204; the test fake now answers 204 as the real app does (red-proved).
+- **Fixed on Tester 1 (Part G4), two safe-removal faults:** (1) the periodic drive gate saw the drive still bound during
+  the 32-second removal and called it RETURNED, then ABSENT with a „disconnected" mail — a safely removed drive is now the
+  removal pass's alone (`TestPlanDriveGates_SkipsSafelyRemovedDrive`, red before the fix); (2) the removal pass read the
+  agent's `state`, which stays „attached" for a registered disk that is gone — presence is now a backing device
+  (`TestEjectStep_G4` from the two measured records, red-proved).
 - **Old Sonarr/Radarr installs repaired by themselves (R-1047)** — only when /media is no longer bound: same-path root
   folder, `moveFiles:false` editor, rescan, old root removed, Radarr's collections too. `TestRepairOldRoot_K7`
   (red-proved: moveFiles=true is caught).