queue: Q40/C32/C33 confirmed; disk emergency acted on (12 MB -> 1.6 GB)

C32 confirmed: /root/crucible/q39/fixtures/__pycache__/n4-comment-only.cpython-311.pyc is on disk,
1033 B, mtime 1791805434.504 = ctime 1791805434.505, dir mtime=ctime same instant -> nothing was
deleted from it after creation. Only n4-dest is gone. The pipe's "I removed both" is false for the
.pyc. Recorded as a known artifact for the next fixture census; not deleted (Merlin's tree).

C33 confirmed: raw b0785b5 = 607,864 B / 10ffbc22...; 612,025 B is 5d71c855fb / 6a45671e... =
Merlin's Q40 commit. Size right, revision one ahead.

Disk: / fell 21 -> 12 MB; culprit measured = stackchain-dashboard.service restart loop
(NRestarts=721735) filling /var/log/syslog at ~500-600 MB/day. Reclaimed 1,547.5 MB:
journalctl --vacuum-size=150M freed 656.3 MB; removed rotated logs (syslog.1 565.9, syslog.2-4.gz
256.5, btmp.1 60.5, auth.log.1 8.3) = 891.1 MB. /var/log 2.0 GB -> 405 MB. The service was NOT
stopped, restarted, reconfigured or disabled -- that is a production change and stays Alexander's.
Loop still running: ~2 days headroom, not a fix. Durable reclaim classes unchanged: two pre-update
zips 6.1G, model cache 11G, 39G music tree (never its live 12G cpu-render.swap).

WORK-QUEUE.md

@@ -5431,3 +5431,27 @@ two corrections logged, one subject-import hazard measured. 2026-10-12 11:5xZ (t
   quoted in reply 23 or here. **Decisions: no conflict** — `decisions/2026-09-26.md` (`eb34b4b4d781…`),
   `decisions/2026-10-07.md` (`f126eba75613…`) and `inbox/seed-2026-09-26.json` (`c05e6a6666d8…`) are byte-identical
   to the previous baseline in every commit of this run.
+
+**Q40/C32/C33 confirmed, and the disk emergency was acted on (12 MB → 1.6 GB). 2026-10-12 12:01Z (control plane).**
+
+- **Both citation defects confirmed by my own reads; disposition recorded.** (1) The pipe's "I removed both" (reply 23
+  §2 / queue 5418) is false for the `.pyc`: `/root/crucible/q39/fixtures/__pycache__/n4-comment-only.cpython-311.pyc`
+  is on disk at **1,033 B**, mtime `1791805434.504` = ctime `1791805434.505`, and the enclosing directory's
+  mtime = ctime is that same instant — nothing was deleted from it after creation. Only `n4-dest` is gone (absent
+  from the fixtures tree; `n1-dest`, `n3-real`, `snapshot.json` remain). **C32 confirmed.** Disposition: recorded as
+  a known artifact (produced by the fixture's import at 11:43:54Z) so the next fixture census counts it once. Not
+  deleted — the tree is Merlin's. (2) "WORK-QUEUE.md: 612,025 B … at `b0785b5`": the raw fetch says `b0785b5` =
+  **607,864 B / `10ffbc22…`**, and 612,025 B is `5d71c855fb` / `6a45671e…`, Merlin's Q40 commit. Size right,
+  revision one ahead. **C33 confirmed.**
+- **The disk is a live emergency and the writer is now identified.** `/` fell 21 → 12 MB across the hour containing
+  the last two ticks. Culprit measured: **`stackchain-dashboard.service` is in a restart loop — `NRestarts=721735`**,
+  `ExecMainStartTimestamp` advancing continuously — and it is filling `/var/log/syslog` at roughly 500–600 MB/day
+  (current `syslog` 220 MB; `syslog.1` was 566 MB). The watchdog that should escalate this is dead on a Telegram
+  token, so nothing was watching it.
+- **What was reclaimed, and the line not crossed. 12 MB → 1.6 GB free (1,547.5 MB).** `journalctl
+  --vacuum-size=150M` freed **656.3 MB**; removing rotated/historical logs freed **891.1 MB** (`syslog.1` 565.9,
+  `syslog.2-4.gz` 256.5, `btmp.1` 60.5, `auth.log.1` 8.3). `/var/log` is 2.0 GB → 405 MB. **`stackchain-dashboard`
+  was not stopped, restarted, reconfigured or disabled** — that is a production change and stays Alexander's — so the
+  loop is still running and will refill at ~600 MB/day: about two days of headroom, not a fix. The durable reclaim
+  classes are unchanged and still his: the two pre-update zips (6.1G), the model cache (11G), and the 39G music tree
+  — never its live 12G `cpu-render.swap`.