docs: refresh what today's work made stale — booth asks (inline placement promoted to its own section), ana-ml2 nvme7 settled by the scrub result, nh3-dev booth entry + the CLI-on-PATH fix, run-07 runbook outcome + serving state

servers/ana-ml2/README.md

@@ -44,8 +44,19 @@ at import. While it was missing `tank` was DEGRADED, and Debian's `zfsutils-linu
 (`/usr/lib/zfs-linux/{scrub,trim}`) only touches pools whose health is `ONLINE`, so tank
 got **no scrub and no trim from 04-12 to 09-06**. ZED's `ZED_EMAIL_ADDR=root` has no
 MTA behind it, so the 4½-month degradation alerted nobody. `media_errors=2084` on
-nvme7 is a lifetime counter; the 2026-09-09 scrub is the first fresh measurement
-(baseline 2084 at 00:32 PT — compare after any future event, growth = replace).
+nvme7 is a lifetime counter.
+
+**Settled by the 2026-09-09 scrub** (00:29–02:02 PT, `scrub repaired 0B in 01:32:44
+with 0 errors`, then `zpool clear tank` → CKSUM 2 → 0): `media_errors` read **2084
+before and 2084 after** a full 6.84 TiB verify, so the counter is prior-life
+history, not an active fault, and the 2 CKSUM were the stale-block artefact of the
+09-05 late resilver. **nvme7 stays in service; watch the counter at every visit and
+replace on growth** (`zpool replace tank nvme7n1 <new>`; any PM1725b 1.6 TB or
+larger). Slot 0-5 itself deserves a reseat / cable check at the next hands-on
+visit — a bay that dropped a drive for 4½ months is the likelier fault than the
+drive. Playbook: `playbooks/ana-ml2-pool-health.yaml` (idempotent; rerunning is a
+no-op). ⚠ **Nothing alerts on this** — see the open follow-up in
+`persistent-memory.d/2026-09-09-ana-ml2-pool-actions-done.md`.
 
 ## Key paths
 

servers/nh3-dev/README.md

@@ -25,6 +25,15 @@ local Bash already executes here — no SSH-to-self needed for non-privileged wo
 - **The Booth** — ephemeral media drop board (`:8090`, `booth.service`), from
   eshpfi `services/booth/`. Lets CC sessions surface A/B renders + smoke results
   (and browser uploads for pickup) to the operator; 24h TTL, Homepage-linked.
+  Since 2026-09-09 it also carries **asks** — a session poses a multiple-choice
+  question in a booth, the operator answers a radio form + notes in the browser,
+  and the pick lands as an answer sidecar the session reads (`booth ask` /
+  `booth answer --wait`). ⚠ The **`booth` CLI is on PATH via
+  `~/.local/bin/booth` → `services/booth/scripts/booth`**, symlinked 2026-09-09;
+  before that it was on no PATH at all, so every session following the global
+  link-board convention was hitting `command not found` unless it used the full
+  path. `~/.zshenv` puts `~/.local/bin` in PATH for non-interactive `ssh nh3-dev
+  '<cmd>'` too.
 - **jackdaw-compose** — JackDAW AI Composer `/compose` backend (`:8787`,
   `jackdaw-compose.service`), a thin stateless `bun server/index.ts` from
   `~/development/jackdaw` → LiteLLM `gen`. Origin-gated (INV-BK04/BK05), reached