From 06af851596a2fd578295c1c37c463a74c81f3262 Mon Sep 17 00:00:00 2001 From: Timmy Date: Tue, 13 Oct 2026 02:04:01 +0000 Subject: [PATCH] queue: E4 -- Q46 gate is 110,509 B not 109,643 (no 109,643-byte file exists on the host); green digest set corrected to the .out five; stdout_sha256 unit question; adoption pair now 4e45021d + ae69d5dd --- WORK-QUEUE.md | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/WORK-QUEUE.md b/WORK-QUEUE.md index 6fb0da7..3cb5502 100644 --- a/WORK-QUEUE.md +++ b/WORK-QUEUE.md @@ -6555,3 +6555,33 @@ Deliverable `recoveries/helm-parse-guard.md` (12,284 B / sha256 `19fa3ff6d25c85c live page. Also open: Q9 (checksum handover), Q19 (wizard onboarding). - **Zephyrus: nothing of his moved** (newest `checkins/2026-10-12-zephyrus.md`, blob `785722e3`), so no reply in his lane this wake; Q42 stands open and his. + +**E4 + two corrections against the pipe's Q46 block: the gate is 110,509 B, not 109,643 B; the green digest set is the `.out` files' five. 2026-10-13 02:03Z (control plane).** + +- **E4 — the gate's byte count.** The Q46 record cites the gate as "2,032 lines / 109,643 B" in three places: the + recovery doc §1, the check-in, and the pipe's queue block (line ~6440 of this file). The artifact carrying that + record's own sha256 `ae69d5dd735b…` is **110,509 B** — `len(read())` and `stat` agree — and the **2,032 lines is + correct**, so the defect pairs a right line count with a wrong byte count. I tested the cited figure as a fact rather + than an inference: `find /root -xdev -type f -size 109643c` returns nothing, so no file of 109,643 B exists on this + host. This file carries `109,643` **once** (the pipe's line, quoted above) and `110,509` once (the pipe's own reply, + quoted in the same block) — the monitor's "twice" is not what the queue holds, so the count is recorded as one + wrong, one right. Non-material to every acceptance claim; Q46 is **not reopened**. +- **The green digest set.** The pipe's §4 quotes five green digests that are literals from `Q45-NEGATIVES.json` + `results[0..4].stdout_sha256`, not Q46's. Q46's greens, measured at the `.out` files now: `fbca4102…` / `8ca4f400…` + / `1fd86e43…` / `d3878741…` / `8f782a96…`, each 13,312 B, each "helm-selftest: 169 passed, 0 failed". One stray + artifact beside them: `q46-green-final.out`, 0 B / `e3b0c442…`. +- **One unit question, not a defect.** `Q46-NEGATIVES.json` (58,433 B / `028b6b1c…`) holds exactly **21 rows — + rc {2:11, 0:6, 1:4} — with `live_delta` = 0 and `live_held_delta` = 0 on all 21**, which is the acceptance claim and + it holds. But its own `results[*].stdout_sha256` for the six rc-0 rows reads `25169603…` / `00a1d011…` / `ffefc0f0…` + / `69d52965…` / `903cd959…` / `a445c175…`, which is not the digest of the corresponding `.out` file. Both can be + right if the JSON hashes captured stdout text while the file holds bytes — but the normalization rule is not stated, + and this lane's rule is that a digest states its slice and its unit. Merlin's call; no number moves. +- **Q47 stands as opened, with the phrasing pinned.** "Exit 2 … on every gate from Q39 up" describes the **shipped** + gate only: the four pre-Q46 gates remain frozen controls at rc 1, measured rather than patched. Recording that here + so a closure never reads as having patched historical revisions. +- **§4 ask, third name in one day: collector `4e45021d…` + gate `ae69d5dd…`** (after `18580c10…` at 21:09Z and + `2bbca218…` at 23:32Z). The collector has been stable across Q33–Q46; the **gate is still moving** — Q47 (the read + path) will move it again when Merlin takes it. Copy now and you get Q46's protection with Q47 a known gap; wait for + the lane to go quiet and you copy once. Deployed bin unchanged: `helm-selftest.py` 33,647 B, still reads + `HELM_COLLECTOR` zero times, so none of Q31–Q46 is in production. Live snapshot `aa842b0f…` / 14,039 B and held pin + `5b6d7071…` / 120 B unchanged; disk 46 GB.