queue: PR #74 merged + #73 closed; my disk-rate figure corrected (143 MB/day, not 500-600)

#74 landed as a real two-parent merge: 9cf23df448dd = a1777a72 + 5c759078, authored by the
rockachopa <alexpaynex@gmail.com> account at 12:02:29Z; #73 closed 12:02:31Z. 13 files / +189 / -19.
Open queue 36 issues / 6 PRs (#60-#65). The neighbouring merge a1777a7 (PR #72) carries the same author
and a 12:02:42Z author date, so both merges appear to have been made seconds apart today by that
account; the Git author alone cannot distinguish a UI action from a job holding that credential.

Gitea's PR object still says merged=false / merged_at=null / merge_commit_sha=null / merged_by=null,
0 reviews, 0 comments -- the standing four-wide merged-flag defect, not a missing merge. Reconcile by
two-parent count; main = 9cf23df448ddea036ad24310d83ccbe4639d695c.

Residual risk as measurement, not accusation: the merged head's required check is red (combined status
on 5c759078 = failure, the act_runner ENOSPC abort of 08:10:38Z, the only context, never re-run) and 0
reviews exist. A P1 fail-closed change landed on an unreviewed, red-gated head.

30/30 -> 21/21 confirmed at the merge head by my own run: node --test the three files = pass 21,
fail 0 (5+3+13); analysis.test.js 9/9. The record's 30/30 double-counts the analysis row above it.

My own figure corrected, append-only: 500-600 MB/day described history (the Oct-11 rotated file held
566 MB), not the present. Measured over 60 s now: syslog 1,741 B/s = 143.4 MB/day, so "about two days
of headroom" understates it -- ~10 days on syslog alone. Free 1.4 GB and falling faster than syslog
alone explains; NRestarts 722,045 and climbing. Row components 565.9+256.5+60.5+8.3 = 891.2 MB vs the
printed 891.1 MB subtotal: the subtotal came from exact bytes before rounding.

Mercury's check-in e9efb23 (12:00:38Z) reproduces; no correction owed.

WORK-QUEUE.md

@@ -5528,3 +5528,34 @@ two corrections logged, one subject-import hazard measured. 2026-10-12 11:5xZ (t
   (`eb34b4b4d781…`) and `decisions/2026-10-07.md` (`f126eba75613…`) unchanged with no new decided note to reconcile
   against its `proposed_action`. The public-with-pending-material mismatch stays a §4 gate for Alexander. Nothing
   from `inbox/` is quoted here or in reply 03.
+
+**PR #74 merged, #73 closed, and my own disk-rate figure corrected. 2026-10-12 12:28Z (control plane).**
+
+- **#74 landed as a real two-parent merge and #73 is closed.** `9cf23df448dd` = `a1777a72` + `5c759078`, message
+  "Merge pull request #74 … (#73)", authored by the **`rockachopa <alexpaynex@gmail.com>`** account at 12:02:29Z;
+  #73 closed 12:02:31Z (labels `area/model`, `priority/P1`, `state:review` — the review label outlives the close).
+  13 files / +189 / −19, matching the API's own counts. Open queue: **36 issues / 6 PRs (#60–#65)**. The neighbouring
+  merge `a1777a7` (PR #72) carries the same author and a **12:02:42Z** author date, so both merges appear to have been
+  made seconds apart today by that account; that identity is also the one the control plane uses, and a commit's Git
+  author alone cannot distinguish a UI action from a job holding that credential.
+- **Gitea's PR object still says `merged=false` / `merged_at=null` / `merge_commit_sha=null` / `merged_by=null`, with
+  0 reviews and 0 comments.** That is the standing four-wide merged-flag defect, not a missing merge — reconcile by
+  two-parent count (`9cf23df` has exactly two; `main` = `9cf23df448ddea036ad24310d83ccbe4639d695c`).
+- **Residual risk, stated as measurement and not as accusation: the merged head's required check is red.** The
+  combined status on `5c759078` is `failure` — the act_runner ENOSPC abort of 08:10:38Z, the only context, never
+  re-run — and 0 reviews exist. A P1 fail-closed change therefore landed on an unreviewed, red-gated head. The review
+  step remains the gap the previous tick named; the fix itself was verified at the boundary before the merge.
+- **30/30 → 21/21 confirmed at the merge head by my own run.** `node --test tests/vision-corpus.test.js
+  tests/vision-boundary.test.js tests/release-demo.test.js` on this host: **pass 21, fail 0** (5+3+13);
+  `analysis.test.js` 9/9. The record's `30/30` double-counts the analysis row above it. Not a false pass — the row
+  is mislabelled.
+- **My own figure corrected, append-only.** The 500–600 MB/day syslog rate I recorded at 12:01:23Z describes history,
+  not the present: the Oct-11 rotated file held 566 MB, but measured over 60 s now syslog grows at **1,741 B/s =
+  143.4 MB/day**, so "about two days of headroom" understates it — on syslog alone, ~10 days. Free space is
+  **1.4 GB** and still falling faster than syslog alone explains (this lane's commits, the monitor's `/tmp` copies and
+  its test runs all write here); `NRestarts` is 722,045 and climbing, service `activating`. Also: that row's
+  components (565.9 + 256.5 + 60.5 + 8.3) sum to 891.2 MB while the printed subtotal read 891.1 MB, because the
+  subtotal was computed from exact bytes before the components were rounded.
+- **Mercury's check-in `e9efb23` (12:00:38Z) reproduces** — collector `ee0b36a8` / 27,907 B, snapshot `aa842b0f` /
+  14,039 B, dry body `efc9a241` / 18,952 B, census 121 = 1 corroborated + 115 documented + 5 testimony. No
+  correction owed on this lane's part.