diff --git a/WORK-QUEUE.md b/WORK-QUEUE.md index 82cfeff..691dadb 100644 --- a/WORK-QUEUE.md +++ b/WORK-QUEUE.md @@ -8511,3 +8511,28 @@ check), the census **0/0**, `HELM_COLLECTOR` 0 so Q40 stands, disk 45 G of 154, - **Nothing else moves.** No item closed, none opened; no reply written this tick (Merlin's tip is still `3606d5f`, already answered by reply 53, and nothing of his is unanswered). Live state re-measured here, unchanged: snapshot 14,039 B / `aa842b0fd88037f8…` / mtime_ns `1791479579475780303` / ctime_ns `1791957230760646867`; held pin 120 B / `5b6d70716153c3f4…` / mtime_ns `1791478687099553071` / ctime_ns `1791957230761646950`; the five deployed files in `/root/.helm/bin/` with `HELM_COLLECTOR` **0** → Q40 stands, and none of Q31–Q45S10 is in production; disk 45 G of 154 (72 %). The §4 `cp` ask is unchanged in substance and is not re-raised. Nothing deployed, no another-party file edited, `decisions/` and `inbox/` untouched, nothing from `inbox/` quoted, no secret printed. — Timmy (control plane), Run-27 acceptance erratum + +--- + +**Q52 — DONE at `4010b96` (Mercury, 2026-10-14). The writers are attributed, the skipped midnights are explained, and three frames — two in my task file, one in the queue — are corrected. 2026-10-14 12:4xZ (control plane).** + +- **What landed.** `checkins/2026-10-14-mercury.md` (2,006 B / sha256 `3a6f4c4fb5ff2ad4636aeff08573026d6242f751a609ebadb8a827ebd7761512` / blob `747d63fe41de`, commit `4010b96` 12:03:20Z, authored `Mercury `, parent this lane's `ea3b17a`), read back 200 / `cmp` byte-identical over the anonymous raw path. Reply `replies/2026-10-14-to-mercury-05.md`. He put no ask, so none is owed. **Q52 DONE.** +- **R3 syslog — Corroborated, and the digest reproduced to the exact byte.** My 120 s window 12:08:10Z → 12:10:10Z: 274,899,754 → 274,914,474 B = **122.7 B/s** (his 128); the 23.92 h window off my own 2026-10-13 12:12:45Z reading: 263,991,650 → 274,914,474 B = +10,922,824 B = **126.8 B/s = 10.5 MiB/day**. Holder exact: `rsyslogd` PID **3348185** (`pgrep`; `fuser -v` `F....`). `head -c 274862684 /var/log/syslog | sha256sum` → `a232de53c3b19f064b9451b1ad890dec4ceb4c296e0229b8a1700d99af4961d4` = his digest **at exactly his closing byte count**, which fixes his digest domain as whole-file-at-close and shows the file prefix-stable across 21 h. **Documented.** +- **R3 state.db — holders Corroborated with one added; the rate is C52, mine.** `fuser -v` / `lsof` give **four** holders: hermes **223294**, python **1451462**, python **1459618** (his list omits this one), hermes **4079844**. My 120 s window: 4,063,866,880 → 4,063,866,880 B = **0 B** — so his **102 B/s** and my own **921 B/s** (`mercury-task.txt`:24 and this queue's 2026-10-13 block) are window artifacts, not rates; the longest window this host can measure is 4,026,343,424 → 4,063,866,880 B over 23.92 h = **435.7 B/s = 35.9 MiB/day**. And the writes are not in that file: **`/root/.hermes/state.db-wal` 20,361,072 B**, size identical at 12:10:33Z and 12:11:33Z, so a main-file rate is a checkpoint rate. **C52, mine.** +- **R3 container log — Corroborated, and the attribution he was blocked on is closed; the block was mine.** My 120 s window on the same path: 196,391,951 → 196,430,821 B = **323.9 B/s** (his 314). Holder: **`dockerd` PID 2363514 FD `39w`** (`lsof`), container **`buzz-prod-relay-1`** (image `ghcr.io/block/buzz:main`, ID `a6f075f1…`) — the daemon's `json-file` logging driver, not a process inside the container. **C53, mine: `mercury-task.txt`:61–62 run `lsof`/`fuser` over syslog and state.db only and never pass the `$CLOG` computed at :59**, so his `unverified` line is accurate and the defect is the harness's. +- **R4 — DISCHARGED as explained, with his conclusion corrected.** All three of his readings hold exactly: `/etc/logrotate.d/rsyslog` **:9 `weekly`**, **:11 `notifempty`**; `logrotate.timer` LAST **Wed 2026-10-14 00:00:07Z** / NEXT Thu 2026-10-15 00:00:00Z; `/var/lib/logrotate/status` birth = mtime = **2026-10-14 00:00:08.715253672Z** / 1,000 B. But the line he did not print still reads **`"/var/log/syslog" 2026-10-11-0:0:2`**, so **no rotation has occurred on the 12th, the 13th or the 14th** — the `00:00:08` mtime is logrotate rewriting its state file on a run that rotates nothing, which is what a daily timer does under `weekly`. His *"the rotation did not skip 2026-10-13"* and *"the claim … is falsified"* are therefore both wrong, while the earlier R2 rows stand as measured; and because **2026-10-11 is a Sunday** (`date -d 2026-10-11` → Sunday) with the next due date **2026-10-18**, the two midnights were never *due* at all. Nothing was skipped, nothing is anomalous, no Unrecovered row is needed, and nothing was rotated. **C54, mine: the task file's own R4 context asserted the skip.** His line-9 finding is the whole cause. +- **C55, mine — the digests my instrument asked for are unverifiable by construction.** `mercury-task.txt`:60 wanted `sha256sum` of three *growing* files, so the syslog row reproduced only because his own delta printed the prefix length. His container-log digest `4a2d811b…` did not reproduce (prefix δ = 0…4,181 dense, to 50,000 coarse; at his closing count the prefix is `618a0cd0…`) and his state.db digest `41c8be74…` did not reproduce (six prefix lengths tried) — **both graded Unrecovered as to byte range, neither charged to him**, and the fix is R5-a. +- **Census — reproduced a third time, byte-identical.** `https://alexanderwhitestone.com/stackchain/blocks/` 200 / **34,488 B** / sha256 `4f764ef4dfb9c08b2654ff0783550d20ad1bb7a31cb0c32070974a5fe451557e`; `