From 8836f73b57cd18f53eeca941849e28b203ebb1a3 Mon Sep 17 00:00:00 2001 From: Timmy Date: Tue, 13 Oct 2026 12:24:39 +0000 Subject: [PATCH] queue: PR #75 merged (5744969faf18 two-parent, tree==PR head 445a5cde) and released as daily-2026-10-13 (published 12:13:00Z, SHA256SUMS OK, 146/146 at the merged tree); #15 still open; Gitea merged=false now five wide; Mercury's R1 falsifies the syslog rate and its census confirms state.db 3.75 GB + the relocated swap --- WORK-QUEUE.md | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) diff --git a/WORK-QUEUE.md b/WORK-QUEUE.md index e4932c9..00b418d 100644 --- a/WORK-QUEUE.md +++ b/WORK-QUEUE.md @@ -7171,3 +7171,40 @@ Read-only, set in the harness (`/root/troupe-harness/mercury-task.txt`): **R3** **Binding:** nothing deleted, moved, rotated, pruned, stopped, restarted, disabled or reconfigured; a disposable-looking file is a proposal with its measured size; commands, exit codes, byte counts and digests only; no quoted file contents, service log lines, environment files, profile, cron-job or personal names. **Done means:** a check-in carrying both readings — every command, its exit code, the byte counts and digests — with R3 attributed to a holder and R4 either explained or graded Unrecovered. + +**PR #75 merged and released; Mercury's disk census lands with two independent confirmations of this lane's findings. 2026-10-13 12:24Z (control plane).** + +- **The merge is real and the released tree is the tested tree.** `5744969faf18` has **two parents** — `9cf23df448` + (`main`) and `46f961668f` (the PR head) — authored and committed by `rockachopa ` at 12:05:19Z, + and `git merge-base --is-ancestor 9cf23df448 46f961668f` is **yes**, so it was a clean three-way merge rather than a + replay. **`tree(5744969) == tree(46f9616) == 445a5cdedb86e707…`**, which is what makes the green CI run on the PR head + (`success`, 08:24:17Z) cover exactly what shipped; `main`'s pre-merge tree was `721f807a2516…`, so nothing else rode in. + Gitea again records `merged: false` / `merged_at: null` / empty `merge_commit_sha` on a PR that is `closed` at + 12:05:31Z — the same tracker defect this lane has logged for #68–#74, now five wide; the two-parent count is the + instrument that settles it. Open pulls went 7 → 6, and **issue #15 is still open**, which is the honest state. +- **The release record recomputes.** `daily-2026-10-13`, target `5744969faf18`, published 12:13:00Z, two assets — + demo 9,235,200 B and tar.gz 216,790 B, the sizes the monitor reports. `/root/timmy-releases/2026-10-13-5744969faf18/` + holds the pair, and `sha256sum -c SHA256SUMS` returns **OK** for both. At the merged tree, `git status --porcelain` is + clean and `node --test` returns **146 pass / 0 fail** in 7.2 s — so the declared `146/146` is a measurement I + reproduced, not a carried figure. The 10-12 (8174920 / 201033 B) and 10-11 (8039211 / 196566 B) releases bracket it, so + the daily series targets each day's head as it should. +- **This shipped without a hostile review, and that is now the standing shape of the repo.** The PR had **0 reviews and + 0 comments** through its whole life, Praetorian's lanes still fail `No Codex credentials stored`, and the merge went + ahead on CI plus the author's own receipts. Nothing here is a defect in the work — the pins I hashed myself and the + 146 tests both hold — but the release carries no independent adversarial pass, and that is worth Alexander knowing + rather than assuming. +- **Mercury's check-in (`fd5a5fe061e5`, 12:02:48Z) is answered and needs nothing from this lane.** The pipe replied at + 12:14:47Z (`reply 04 (mercury)`) and closed the unit in the queue at 12:14:50Z, so no second reply is written here. + What it adds that this lane should record: its **R1 measurement falsifies the syslog-rate figures** — `syslog + 263899491 → 263913851 over 120 s = 119 B/s = 9 MiB/day`, against the pipe's 153 MB/day and this lane's own corrected + 143.4 MB/day. Those describe different objects at different times (the disk-fill rate was the dashboard loop's flood, + and the loop is stopped now), but at 12:0xZ the *syslog* was growing at 9 MiB/day, so any live-still-flooding claim is + dead. Its disk census also **independently confirms two of this lane's findings**: `/root/.hermes/state.db` at + 4,026,343,424 B (3.75 GB, still growing) and the vanished `/root/sovereign-music-daily/cpu-render.swap` — which is the + relocation to `/mnt/workbench_data` this lane recorded at 18:45Z on 10-12, seen from a second instrument. Its + read-only census also re-measures the two reclaimable trees: `.hermes/backups` 6.1 G and `.hermes/cache` 12 G. +- **Standing, unchanged.** §4 `cp` of collector `4e45021d…` + gate `a951dbe8…` (the only human action between Q31–Q50 + and production protection), the `manifest_match` pin stale since 2026-10-08, the Q13 publication call, and — from + this tick — **the GPU authorization that would let `scripts/record_worker_benchmark.mjs` produce the one missing + receipt for #15's criterion 4** (a single A40 session, ~$0.59/hr, against the prepaid credit). Nothing else is + stalled.