queue: Q43 leg sandbox verified (gate c22601ec, 17/17 live_before==live_after); disk 46 GB -- music tree and live swap MOVED to /mnt/workbench_data, fstab has no swap line

WORK-QUEUE.md

@@ -6185,3 +6185,38 @@ and the protected file's (sha256, mtime_ns, ctime_ns) around every invocation
 (`/root/crucible/q43z/timmy_verify_q43.py`, `replies/2026-10-12-to-merlin-27.md` §5). Alexander's `cp` decision is
 **not** a precondition: the pair stays undeployed and this unit runs in scratch. With Q43 closed and Q44 opened, the
 Helm lane has one executable item again.
+
+**Q43 (leg sandbox) verified here; the disk went 7.0 GB → 46 GB because the music tree and the live swap were MOVED, not deleted. 2026-10-12 18:45Z (control plane).**
+
+- **Q43 closes the residual this lane named at 12:01Z** — "the legs still run the original subject". Gate `c22601ec…`
+  = **88,468 B / 1,612 lines** (superseding `9b09f328…` at 1,412), subject unchanged `4e45021d…` (720 / 29,954). The
+  wrapper's own text installs the rule: any subject leg runs the **rewritten copy**, "whose every `SNAPSHOT_PATH`
+  assignment points at a per-invocation sandbox", while a subject naming the live snapshot or passing `--pin` is
+  refused because "neither is redirectable". The rewritten leg copies are on disk
+  (`variants/helm-legs-0ut0sizv/subject-legs.py`, `variants/helm-legs-v8tq2tyo/`). Landing rows are byte-exact at
+  `0fb8b20`: 13,561 / `7c5111aa`, 691,024 / `90399c0f`, 75,361 / `fc4e750b`.
+- **The falsifier answers, on artifacts I re-read rather than re-ran.** `out/Q43-NEGATIVES.json` = **17 rows, all 17
+  with `live_before == live_after`**; `out/Q43-RESIDUALS.json` holds four named results — `r3_rewrite_is_behaviour_preserving:
+  true`, `r3_diff_keys: []`, both r3 sizes 20,570 B, `r2_pin_deploy_rc: 0` writing into the scratch tree — so the
+  enumerated total is **21 recorded invocations (17 + 4), not the declared 20**, which is the two count/arithmetic lines
+  returned to Merlin for a one-line correction. Five green runs at `out/q43-green-1..5.out` are 12,248 B each with
+  "166 passed, 0 failed", `VERDICT: ALL GATES PASS`, 18 legs watched. I did not re-run his scripts: they overwrite the
+  JSON artifacts the record rests on.
+- **My own probe on the clobbering shape refuses — and I record what it does *not* prove.** The `{}`-writing fake that
+  clobbered the snapshot at 07:17Z gets **rc 2, stdout 0 B, live delta 0** from the Q43 gate, refusal text
+  "`Q35 REFUSAL: the subject collector /root/.helm/bin/helm-collect.py carries no destination rule`". So the gate
+  refuses on the **deployed subject**, and my `--subject` argument is never reached: the probe confirms the refusal
+  path, **not** the leg sandbox. The sandbox evidence is the wrapper text, the committed JSON rows, the on-disk leg
+  copies, and the monitor's two `argvlive` rows (ctime and sha/mtime unmoved; ctime moved with sha+mtime restored).
+  The live snapshot reads `aa842b0f…` / 14,039 B / mtime_ns `1791479579475780303` before and after, nothing to restore.
+- **Disk: 46 GB free of 154 GB, up from 7.0 GB — and the earlier 39 GB was relocated, not reclaimed.** `/mnt/workbench_data/`
+  now holds `sovereign-music-daily/` (16:24Z) and `cpu-render.swap` at **12,884,901,888 B**, and `/proc/swaps` shows the
+  swap **live from the new path** (2.9–3.0 GB used). `/root/sovereign-music-daily` is now an empty directory. So this
+  was a move across filesystems by someone outside this lane, at 16:08–16:28Z, and the record says that rather than
+  implying a reclaim. **Two follow-ups it creates:** `/etc/fstab` carries **no swap line**, so it is unverified whether
+  the 12 GB swap survives a reboot; and any job still hard-coded to `/root/sovereign-music-daily/...` will now fail.
+  The dashboard remains `failed`; `act_runner` is `active`.
+- **Standing §4 ask, restated with the current pair:** adopt subject **`4e45021d…`** + gate **`c22601ec…`** into
+  `/root/.helm/bin/`. The deployed gate `7ed1bca8…` has no subject-selection path, so none of Q31–Q43's protection is
+  in production until the `cp` lands. If Alexander approves it, that is the moment to send Praetorian the exact pair
+  read-only — with the caveat that Praetorian's provider route is still dead.