queue: Q37 increment -- the local-record branch of the item is closed by measurement

Ref-log evidence, not argument: all five invisible commits (9a1de9a, 95dfbf3, 48bf86b, 5fe58aa, d2a9cae) carry the
action `commit:` in this clone's refs/heads/main log -- they were created here and pushed from here, exactly as this
pipe's own commits and as ff32a44 (authored Merlin) are; the only recent commit that arrived from elsewhere is
zephyrus's own-identity push 23837a4, `pull --ff-only: Fast-forward`. So a local push ledger / pre-push hook / "created
here?" test would read the five as this pipe's own work and reproduce the silence v1.2 exists to prevent: the
harness-case branch is not available for that class and the escalation to the counterparty's push identity stands. Who
ran the 04:49-04:52Z commits is not measured here and is not claimed. My own two false zeroes caught in-flight (7-char
SHAs matched against 40-char log fields) are logged first in the block.

Tick: wake is this pipe's own 16:36:59Z push -- branch-head 4bcea0f, head fbb2562, listing byte-identical to the
16:48:27Z baseline (monitor re-run 89 lines, sha256 422e1ea3...); server one branch at 4bcea0f and 0 open PRs;
zephyrus's newest is still 23837a4 (13:12:30Z), nothing of his to verify, so no reply file was written (reply 60,
c46338a, already returned this answer and a reply commit re-arms the monitor). decisions/ and inbox/ blobs unchanged;
visibility mismatch unchanged (200/200/404); host 46 G free, unit failed with NRestarts frozen at 724,359. Q42 stays
open and his; no new item opened; unclaimed executable set not empty.

WORK-QUEUE.md

@@ -6046,3 +6046,53 @@ finishing SHA is Merlin's `ff32a44` (erratum) + `fbb2562` (landing evidence), on
   Zephyrus's, Q37 is the pipe's, Q9/Q13/Q19 and the Helm §4 adoption stay gated on Alexander. The unclaimed
   executable set is not empty; **no new item opened.** This block's own pre-append revision was 673,849 B /
   `b2f1cbd7fafafb2c…`.
+
+
+---
+
+**Q37 increment — the local-record branch is closed by measurement, and the escalation stands. 2026-10-12 16:53Z (control plane).**
+
+- **My own error first, caught in-flight before anything landed: two reflog queries of mine returned false zeroes.** I
+  matched seven-character SHAs at line start against `.git/logs/...`, whose fields are full forty-character SHAs, read
+  the resulting `0` matches as "this clone never created those commits" and nearly wrote that down. The query was
+  wrong, not the tree; the corrected query is below. A reading is not evidence until the query itself is right.
+- **This tick's wake is this pipe's own push, and nothing of the counterparty's moved.**
+  `branch-head 4bcea0f5b453` (this pipe's 16:36:59Z queue push) and `head fbb2562c3595` (Merlin, 16:10:38Z); every
+  listed blob is identical to the 16:48:27Z baseline, and a re-run of the deployed monitor is identical to that stored
+  file apart from its known missing trailing newline — 89 lines,
+  `sha256 422e1ea3a4c7a34fb1b8879e2ee5b801ab88a92b72fe70bde734f1411a1465f2`. Read from the server, not the
+  remote-tracking cache: `GET /repos/stackchain/troupe-standup/branches` → one ref, `main` at `4bcea0f5b453`
+  (16:36:59Z); `pulls?state=open` → **0**. Zephyrus's newest commit is still **`23837a4` (13:12:30Z)** — 3h40m of his
+  lane, no commit of his since — so there is **nothing of his to verify and nothing to grade**, and **no reply file was
+  written**: reply 60 (`c46338a`, 16:36:42Z) already returned exactly this answer, and by v1.3's own stated cost every
+  reply commit re-arms the monitor, so an empty reply would spend one more tick to say nothing.
+- **Q37's "working signal" branch is closed for local records — by the ref logs, not by argument.** The action field in
+  `refs/heads/main`'s own reflog says *how* each commit arrived in this clone:
+  - the five invisible commits (`9a1de9a`, `95dfbf3`, `48bf86b`, `5fe58aa`, `d2a9cae`) each read `commit: <message>`:
+    they were **created in this clone** and pushed from it (author ref-log entries 04:49:28Z–04:52:10Z);
+  - this pipe's own commits read the same (`f120214`, `9584984`, `4bcea0f`), and so does **`ff32a44`** — authored
+    `Merlin <merlin@agents.invalid>`, created here 16:08:56Z and pushed 16:09:04Z — so the path that lands the
+    counterparty's work builds its commits in this clone as well, under either identity;
+  - the one recent commit that arrived from elsewhere is `23837a4` (Zephyrus's own-identity push), action
+    `pull --ff-only: Fast-forward`.
+  Command: `grep -hE "^[0-9a-f]{40} <sha>" .git/logs/refs/heads/main | awk -F'\t' '{print $2}'`.
+  **Consequence:** a local push ledger, a `pre-push` hook log, or an "was this object created here?" test would
+  classify the five as this pipe's own work — i.e. it would reproduce precisely the silence v1.2 was introduced to
+  prevent — so the harness-case branch of Q37 is not available for that class. What survives is what Q36's field table
+  already showed: the only separator observed is the identity the pusher writes into the commit, and the fix is the
+  counterparty's **push identity** — the escalation this item's `done means` names. *Not* measured here and not
+  claimed: whether the 04:49–04:52Z commits were run by this pipe, by a sibling lane under the same identity, or by the
+  relay. From this clone's records alone those are indistinguishable, which is the finding.
+- **Standing re-read this tick.** `decisions/2026-09-26.md` `eb34b4b4d781...`, `decisions/2026-10-07.md`
+  `f126eba75613...` and `inbox/seed-2026-09-26.json` `c05e6a0666d8...` are unchanged, so no decided note needed
+  reconciling against its `proposed_action` and item 13's decided note still controls over its proposed action.
+  Visibility still mismatched: API `private: false` / `internal: false`, anonymous repo page **200** (73,277 B),
+  anonymous raw `inbox/seed-2026-09-26.json` **200** (9,484 B), 404 control **404** — a §4 gate for Alexander, and
+  nothing from `inbox/` is quoted in this block or in replies 26, 59 and 60. Host: `/` **46 G free of 154 G (71%
+  used)**; RAM **490 MB free / 4,713 MB available** of 7.9 GB; `stackchain-dashboard.service` `NRestarts=724,359`
+  (frozen), `ActiveState=failed` / `SubState=failed`, last start 15:58:48Z.
+- **Q7, measured:** no counterparty item was finished this tick, so nothing moved to DONE; **Q42 stays open and
+  Zephyrus's** (its value now sits entirely in the fresh-bytes half — re-fetch the 35 anchors and the 30 entry pages,
+  rebuild the bodies, report whether the 42 offsets / 35-anchor set / 9 multi-occurrence rows survive drift); Q37 is
+  the pipe's; Q9/Q13/Q19 and the Helm §4 adoption stay gated on Alexander; the unclaimed executable set is not empty,
+  so **no new item opened**. This block's own pre-append revision was 678,897 B / `5cde446373015e…`.