queue: PR #75 verified -- pins hash exactly to deploy/worker/receipts.json and 146 tests pass; the release sheet's two claims are hard-coded literals; modelSeen has two readers; 0 reviews and no hostile lane

WORK-QUEUE.md

@@ -6897,3 +6897,34 @@ it: Alexander's `cp` of collector `4e45021d…` + gate **`a590170f…`**, the `m
 - **This tick's wake, verified — own-commit only, counterparty-free.** `branch-head` moved `26e519a` → `8329ef5`, both `Timmy <timmy@stackchain.ai>`, and that line is the whole of the monitor's diff; the `head` line did not move (`abe1f0b8c8b4`, Merlin, 2026-10-13T06:45:12Z). All **8** commits since Merlin's `abe1f0b` are this pipe's — `f1537be`, `a0fbe0a`, `af3222d`, `2ff8bf3`, `a59e640`, `5aa32b3`, `26e519a`, `8329ef5`. Newest counterparty commits: Zephyrus `23837a4` (2026-10-12T13:12:30Z), Mercury `e9efb23` (2026-10-12T12:00:38Z), Cassian `7aff3c0` (2026-10-07). The live monitor output, stripped of its trailing newline, hashes to the stored baseline `00e1c421…`, so the state read is the state the gate signed. **No reply file: no counterparty ask, per convention (b).**
 - **Convention (b) from the next tick, named because the last two ticks did not follow it.** `26e519a` (07:11Z) and `8329ef5` (07:27Z) were each woken by this pipe's own commit and each answered with another commit — which buys the next wake, so the chain is self-sustaining, the exact thing convention (b) (`:6393`) exists to stop. This append is the exception it has to be: a false figure standing in the record outranks the tick it saves. **From the next own-commit-only tick this lane closes with no commit at all**, which is the last step needed to end the chain, since the monitor's own docstring states the gate skips the agent when the output is unchanged.
 - **Standing, read this tick and unchanged.** Q49 open and unclaimed — 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 (authority questioned: add our note, escalate to author and publisher) controls over its `proposed_action` ("publish the corrected wording to the live magazine-091 page"), recorded at `:187` and `:19`–`:21` of `decisions/2026-09-26.md`; no conflict resolved in the execution direction.
+
+**PR #75 verified on `timmy-talking-turd`: the pins hash exactly to the receipts and the 146 tests reproduce; the release sheet's two claims are hard-coded. 2026-10-13 08:45Z (control plane).**
+
+- **PR #75, open and unmerged.** Head `46f961668f` on `timmy/15-container-worker-receipts`, base `9cf23df448` (`main`),
+  **27 files / +1167 / −14** (net 1153 — the enumerated rows sum exactly), **mergeable**, **0 comments, 0 reviews**, one
+  CI status on the head = **success**. Open PRs in the repo went 6 → 7. Nothing deployed; `main` unchanged.
+- **The pins are real — I hashed the weights myself.** `SmolVLM2-2.2B-Instruct-Q4_K_M.gguf` = 1,112,602,656 B /
+  `0cf76814555b8665…` and `mmproj-SmolVLM2-2.2B-Instruct-Q8_0.gguf` = 592,523,200 B / `ae07ea1facd07dd3…`, both
+  **byte-equal to `deploy/worker/receipts.json`**, which also carries llama.cpp commit `6d05498314db…` and the two CUDA
+  base-image digests `da6791294b0b…` / `517da2300c18…` for `cuda:12.4.1-devel` / `-runtime-ubuntu22.04`. The drift guard
+  is real, not asserted: the same digests appear in `deploy/worker/Dockerfile`,
+  `scripts/bootstrap_selfhost_smolvlm.sh` and `tests/selfhost-bootstrap.test.js`.
+- **The 146 tests reproduce** at the head: `# tests 146 / # pass 146 / # fail 0 / # skipped 0 / # todo 0`, 9.2 s.
+- **The record-reading risk is structural, not a reading hazard.** `scripts/build_release.py:277–278` emits
+  `"worker_container_receipts": "passed"` and `"worker_post_load_readiness": "passed"` as **literals**, and
+  `tests/ci-workflow.test.js:142–143` asserts those literals. So the release sheet reads "passed" on a host where the
+  image was never built and no GPU receipt exists — disclosed in the PR body ("instrumented but **not measured**"; "this
+  host has no CUDA to build") and in `AI-EVIDENCE.md`, but the artifact itself cannot tell the two states apart.
+- **`modelSeen` has two readers, not one.** The brief says `app.js` is the only reader of the widened readiness contract;
+  `src/vision-readiness.js:37` reads it too (`status.modelSeen !== true`). The value is produced in
+  `src/vision-config.js` (four branches) and sent by `server.mjs:52`; `app.js:181` renders the amber not-loaded state
+  with manual logging available, which is the user-visible half and matches the brief.
+- **No issue movement, checked both ways.** The tracker returns 43 open *including the 7 PRs* = **36 non-PR issues**,
+  unchanged since the 10-12 merge; the newest are still `#62`–`#65` (2026-08-22). #15 is open, unassigned, labelled
+  `area/model` + `priority/P0` + `type/ops`, with its one `[EVIDENCE] agent=timmy` comment at 08:21:13Z saying the PR
+  "advances this issue without closing it" — the right call, since criterion 4 is unmeasured.
+- **The merge call is Alexander's, and it would be an unreviewed merge.** Mergeable, CI green, three criteria
+  receipt-backed — but **0 reviews**, and Praetorian's lanes still fail `No Codex credentials stored`, so the only
+  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.