queue: PR #75 block (control plane's) re-verified figure for figure from this host -- /pulls/75 open/mergeable/head 46f9616/27 files +1167-14/0 reviews, status success, reviews [], npm test 146/146, both weights hashed here to the receipts' pins (0cf76814555b.../ae07ea1facd0... = deploy/worker/receipts.json models[0]/[1]), the two literals at build_release.py:277-278 asserted by ci-workflow.test.js:142-143, modelSeen's two readers, 36 issues + 7 PRs = 43, and no reviewer lane (praetorian's three jobs all openai-codex with no credential, last error 08:32:59Z); two corrections logged -- #62-#65 are PRs not the newest issues (newest issue is #53, 2026-08-21) and the model/mmproj drift guard is worker-container.test.js:34-35/50-51, not selfhost-bootstrap.test.js, which pins only the llama commit and drives test-double hashes; own-side wake, no counterparty ask, no reply file per (b), and this is the last commit from an own-commit-only wake

WORK-QUEUE.md

@@ -6928,3 +6928,20 @@ it: Alexander's `cp` of collector `4e45021d…` + gate **`a590170f…`**, the `m
   reviewer available is a human read of the diff. If it merges, #15 stays open with criterion 4 named as the blocker; the
   blocker itself is a **spend decision** (the A40 secure-cloud recipe, ~$0.59/hr, yields the cold/warm + VRAM receipt
   inside an hour) and that authorization is his to give.
+
+
+**Own-side wake carrying a third-party block (control plane): its PR #75 verification reproduces figure for figure on my own instrument, with two claims corrected. 2026-10-13 09:05Z (troupe pipe).**
+
+- **The wake, read and named.** The monitor's diff is one line: `branch-head` `c3f230c` -> `bf15fb3`, both authored `Timmy <timmy@stackchain.ai>`; the `head` line did not move (`abe1f0b8c8b4`, Merlin, 2026-10-13T06:45:12Z). Newest counterparty commits are Zephyrus `23837a4` (2026-10-12T13:12:30Z) and Mercury `e9efb23` (2026-10-12T12:00:38Z); **nothing of a counterparty's moved and no ask arrived**, so **no reply file**, per convention (b). `decisions/2026-09-26.md` `eb34b4b4d781` and `inbox/seed-2026-09-26.json` `c05e6a0666d8` are unchanged, so no decided note needed reconciling against a `proposed_action` and nothing from `inbox/` was read out. The appended block itself is the control-plane session's, written under the same identity — an own-side wake, not a counterparty one.
+- **PR #75 (`stackchain/timmy-talking-turd`), read over the loopback API, HTTP 200.** `state: open`, `merged: false`, `mergeable: true`, head `46f961668fb937b5...` (`timmy/15-container-worker-receipts`), base `9cf23df448dd...` (`main`); additions **1167**, deletions **14**, changed_files **27**, comments **0**, review_comments **0**, labels `[]`; `/pulls/75/reviews` returns `[]` (zero reviews). `git show --stat 46f9616` -> 27 files changed, 1167 insertions(+), 14 deletions(-). Commit status on the head: `state: success`, one status (`Quality gates / quality (pull_request)`, 2026-10-13T08:24:17Z).
+- **146 tests, re-run at the head, not relayed.** `npm test` in `/root/timmy-talking-turd` at `46f9616` -> `# tests 146 / # pass 146 / # fail 0 / # cancelled 0 / # skipped 0 / # todo 0`, node-reported duration **7072 ms**. (The block's "9.2 s" is the outer wall time; the count is the claim and it reproduces.)
+- **The pins, hashed here rather than asserted.** `sha256sum /root/model-spikes/models/smolvlm2-2.2b/SmolVLM2-2.2B-Instruct-Q4_K_M.gguf` (**1,112,602,656 B**) = `0cf76814555b8665...`; `mmproj-SmolVLM2-2.2B-Instruct-Q8_0.gguf` (**592,523,200 B**) = `ae07ea1facd07dd3...` — byte-equal to `deploy/worker/receipts.json` `models[0].sha256` / `models[1].sha256`, and the same two sizes the block states. The weights exist on this host at that path, so the pin is checkable rather than assertion-only. llama.cpp `6d05498314db...` and the two CUDA digests `da6791294b0b...` (build) / `517da2300c18...` (runtime) also match `receipts.json` and `deploy/worker/Dockerfile:10-12,16,32`.
+- **The hard-coded literals, read by line.** `scripts/build_release.py:277` = `"worker_container_receipts": "passed"`, `:278` = `"worker_post_load_readiness": "passed"`; `tests/ci-workflow.test.js:142-143` assert those two literals. So on a host where no image was built the release sheet still reads "passed" — the structural risk the block names is real.
+- **`modelSeen` has two readers — confirmed.** `src/vision-readiness.js:37` (`status.modelSeen !== true`) and `app.js:181` (the amber loading banner); produced in `src/vision-config.js:45,51,54,56` and sent at `server.mjs:52`.
+- **The tracker, both ways.** `/issues?state=open&type=issues` -> **36**; `/pulls?state=open` -> **7**; total **43**. `#15` is open, assignee `none`, labels `area/model` + `priority/P0` + `type/ops`, with its one comment (`rockachopa`, 2026-10-13T08:21:13Z, `[EVIDENCE] agent=timmy ... advances this issue without closing it`). The "6 -> 7 open PRs" step is derivable: `#75` is the newest of the seven and was created 2026-10-13T08:20:45Z; the other six are `#60`-`#65`.
+- **No reviewer lane, checked rather than assumed.** `/root/.hermes/profiles/praetorian/cron/jobs.json`: `4b23b7393ad1`, `e48a39ca9b1b`, `de5ea76f361a` are all pinned `provider_snapshot: openai-codex` / `model_snapshot: gpt-5.6-sol` with no codex credential stored; all three read `last_status: error` / `RuntimeError: No Codex credentials stored`, most recent fire 2026-10-13T08:32:59Z. Zero automated review capacity stands, so the block's conclusion holds.
+- **Correction 1 (mine to log): "#62-#65 are the newest" is a mislabel.** That sentence's subject is the 36 non-PR issues, but `#62`-`#65` are **PRs** (created 2026-08-22T20:59:19Z-23:20:50Z). The newest non-PR issue is **`#53`** (`EPIC: Private subpage staging for Alexander release testing`, 2026-08-21T13:20:52Z). The 43 = 36 + 7 arithmetic is right; only the label is wrong, and it is the kind of wrongness a later reader would cite.
+- **Correction 2 (mine to log): the drift-guard sentence names the wrong test.** `tests/selfhost-bootstrap.test.js` does **not** carry the shipped model/mmproj digests: it asserts the llama.cpp commit (`:61`, `checkout --detach 6d05498314db...`) and runs the script against its own test-double hashes (`:53-54`, `:84-85` = `98ad61a2...` / `ce52f16b...`). The model/mmproj drift guard is `tests/worker-container.test.js:34-35` + `:50-51` — Dockerfile `ARG MODEL_SHA256` / `MMPROJ_SHA256` must equal the bootstrap script's defaults, which is the mechanism `receipts.json` names — and the two CUDA digests appear only in `deploy/worker/Dockerfile:16,32` and `receipts.json`. Still a real guard, at a different path than the sentence claims.
+- **Standing, unchanged and unclaimed.** Q49 open (name the argv that moved the live pin, or record the negative); nothing of Merlin's moved, so no reply is owed. Alexander's `cp` of collector `4e45021d...` + gate `a590170f...`; the `manifest_match` pin stale since 2026-10-08; the Q13 publication call. `magazine-091` remains decided-with-caveat — its decided note (add our note, escalate to author and publisher) controls over its `proposed_action` (publish the corrected wording to the live page);
+- **The decision that is his, named plainly.** PR #75 is mergeable with green CI and receipt-backed pins, but with 0 reviews and no working reviewer profile the only reviewer left is a human read of the diff, so merging it would be an unreviewed merge. #15's criterion 4 (cold/warm latency and VRAM on the target GPU) is instrumented but unmeasured, and its blocker is a **spend** (~$0.59/hr A40 secure cloud; recipe in the runpod-gpu-rendering skill) — not mine to authorize. Nothing deployed; `main` unchanged.
+- **Convention (b), applied rather than restated.** This append is the exception for a defective third-party block whose defects a later reader would cite, the same exception `c3f230c` named. It is the last one: from the next own-commit-only wake this lane writes nothing at all.