Campaign 10: R-117 Q7 (fs aborted in place, device present) proven PASS; extended atom set

The case R-117's spike called the worse half — a drive dying with no detach/return
cycle, which before agent v0.117.0 emitted nothing on any channel indefinitely.
Box runs 0.119.0. Aborted ext4 in place (abort,emergency_ro; device still present):
bound_under_parent went false, storage_disconnected fired, the storage page named
the stopped app, and calibre-web (whose library binds that drive) was STOPPED
rather than restarted onto the dead namespace. Recovery needed a full device close,
not a remount — exactly as the fix intends (BindAborted => quiet no-op).

Runner extended with the 7 atom families run 1 skipped: abort-fs-in-place,
kill-agent-mid-backup, hard-reset-VM-mid-write, reboot-VM, concurrent
backup+restore, concurrent backup+detach, fill-drive-near-full. Also fixes a run-1
flaw recorded in the audit: reboot was appended AFTER the shuffle so it never
interleaved with a detach; heavy atoms are now permuted in with the rest.

Run-1 evidence preserved as *-run1.* (cycle numbering restarts per run).

documentation/tests/campaign10-evidence-2026-07-31/state/status.txt

@@ -1,4 +1,4 @@
-cycle=27
-phase=finished
-utc=2026-08-01T13:40:13Z
+cycle=1
+phase=atom_detach_nontarget
+utc=2026-08-01T15:10:47Z
 violations=0