chore(althing): herald to 3.6.1 on nh3-dev only, operator-scoped 1 of 7

uv tool install --force --reinstall from ~/development/althing (clean tree, HEAD
== origin/master 719bc5f, pyproject declaring 3.6.1). althing-core 3.6.0 -> 3.6.1;
herald PID 2457743 -> 3690918 with the old process confirmed gone; version read
back from the running install; postbox status reachable/push/alive; journal clean
since restart. postbox, althing-listen and althing-route moved on the same install.

Six boxes stay queued and the plugin hop (0.1.6) is separate and not done, so this
is deliberately not a "fleet done" claim. Reported to forseti per box.

Records one verification trap worth keeping: POKE_TEXT in post_office_herald.py is
a four-part implicit string concatenation, so a line-oriented grep for the new poke
sentence returns empty on a CORRECT 3.6.1 checkout. The first pass came back empty
for both the new text and the old, which reads as "new absent, old removed" -- two
wrong conclusions from one wrong pattern, detectable only because both cannot be
true at once. Check the effective value: reconstruct the concatenation or import
the module and print the constant.

persistent-memory.md

@@ -1,6 +1,6 @@
 # Persistent memory — eshpfi-management
 
-_Last updated: 2026-09-09 23:15 PT (**Pfish-6** = run-6 NVFP4 is the standing seat, ana-ml2 :8021 ONLY; run 7 PURGED ~139 GiB; pfi-gx10 is an experimental/TRAINING box and carries no serving seat; all five ERP adapters now MIRRORED to ana-ml2 and inside restic; **BabyBronte / R49 author-voice regime is in PREP on gx10, carrier SETTLED = dense Qwen3**; checkpoints AND superseded merges PURGED both boxes, **~573 GB total**; only merged-run06 + the v6 quant survive)_
+_Last updated: 2026-09-09 23:20 PT (**Pfish-6** = run-6 NVFP4 is the standing seat, ana-ml2 :8021 ONLY; run 7 PURGED ~139 GiB; pfi-gx10 is an experimental/TRAINING box and carries no serving seat; all five ERP adapters now MIRRORED to ana-ml2 and inside restic; **BabyBronte / R49 author-voice regime is in PREP on gx10, carrier SETTLED = dense Qwen3**; checkpoints AND superseded merges PURGED both boxes, **~573 GB total**; only merged-run06 + the v6 quant survive)_
 
 > **Always check for `/tmp/infra-ops-handoff.md`** — if it exists and its
 > `Written:` stamp is under an hour old, read it (it carries the in-flight
@@ -207,11 +207,22 @@ preserved verbatim in `archival-memory.md` § Superseded in-flight snapshots._
   sharpest framing: **dense 4.089B still beats hybrid 0.765B by 33%** on 5.3x the params. Qwen3.5 stays
   staged (14.8 GB) — an `fla` install could revive it as a follow-up experiment, never a prerequisite.
   If anyone re-opens this, re-run `bench_lora_step.py` first: the argument is a measurement.
-- **📌 forseti shipped althing 3.6.1 (2026-09-09) — every box's herald needs a restart to pick up the
-  new poke text.** `uv tool install --force --reinstall <checkout>` + `systemctl --user restart
-  althing-po-herald`, expect `3.6.1`; the plugin also went to 0.1.6 (inbox.md no longer calls the
-  result reply "optional"). NOT DONE — deferred, nothing is blocked on it, and it is a fleet-wide
-  multi-box pass with its own verification burden.
+- **📌 althing 3.6.1 (forseti, 2026-09-09) — DONE on nh3-dev ONLY (1 of 7), operator-scoped.**
+  `uv tool install --force --reinstall .` from `~/development/althing` (clean tree, HEAD ==
+  origin/master `719bc5f`): althing-core 3.6.0→**3.6.1**, herald PID 2457743→3690918 with the old
+  process confirmed gone, `postbox status` reachable/push/alive, journal clean. postbox +
+  althing-listen + althing-route came along on the same install.
+  **STILL QUEUED (6 boxes):** nh3-docker, nh3-extdev, ana-docker, ana-ml2, irv-ml1, corviduo-dev.
+  ⚠ **nh3-extdev is a system WHEEL at `/opt/uv-tools`** — a user-level `uv tool install --force`
+  there updates nothing and reports success. The **plugin hop (0.1.6)** is separate and NOT done.
+  ⚠⚠ **DO NOT content-check the poke with a line-oriented grep.** `POKE_TEXT` in
+  `althing/post_office_herald.py` is a FOUR-PART implicit string concatenation, so
+  `grep 'reading it is only the first of three steps'` returns **empty on a correct 3.6.1 checkout**.
+  My first pass came back empty for BOTH the new text and the old — which reads exactly like "new
+  absent, old removed", two wrong conclusions from one wrong pattern, and is only detectable because
+  both cannot be true at once. Reconstruct the concatenation or import the module and print the
+  constant. Sibling of [[feedback_assert_effective_value_not_substring]]; it bites harder here because
+  the *negative* is the reassuring-looking answer.
 - **⏳ ana-ml2 storage follow-ups, operator's call** (the three actions themselves LANDED 09-09 02:02):
   (a) **ZFS pool-health ALERTING** — `tank` sat DEGRADED 04-23→09-05 with nvme7 physically absent and
   nobody knew (ZED mails `root`, no MTA on the box); (b) nvme7 / slot 0-5 keep-vs-replace —