paperwork: refresh STATUS.md + CLAUDE.md; finalize 4b

STATUS.md:
  - Mark 4b done (both Postgres migration + NFS decoupling)
  - Add arch decisions for gitea remote + prefer-elway policy
  - Add tooling entries for elway + tea CLI
  - Document 2026-04-24 session milestones (irv-ml1 AI stacks,
    elway, task-board, 4b finish)
  - Expand memory-pointer list with the files added this session

CLAUDE.md:
  - Tell new sessions to use elway for SSH-driven work, point at
    the smoke playbook template
  - Document the task-board plugin + MCP-tool contract so assistant
    sessions with the plugin enabled know the assistant should call
    task_start / task_update / task_wait / task_complete at
    meaningful checkpoints

.claude/settings.json:
  - Project-level env: TASK_BOARD_SESSION=Infra so every Claude Code
    session opened here labels its task-board cards "Infra"

playbooks/decouple-pfi-postgres-from-ana-nas.yaml:
  - Finishes the DB-off-NFS migration on pfi-postgres. Already ran
    against prod today; fstab clean, unmounted, no systemd mnt-db
    unit. Verify 3 was mis-expressed on first run (`grep -q active`
    matched "inactive") — fixed to invert systemctl exit code
    directly.

.claude/settings.json

@@ -0,0 +1,5 @@
+{
+  "env": {
+    "TASK_BOARD_SESSION": "Infra"
+  }
+}

CLAUDE.md

@@ -2,6 +2,24 @@
 
 This workspace is for managing PFI infrastructure — servers, Docker stacks, and related configs. Spawn a dedicated Claude Code session here when working on infra so it doesn't clutter AIPA-MCP development context.
 
+**New session starting here?** Read [`docs/orientation.md`](docs/orientation.md) first — fleet topology, backup architecture, governing principles, and all the NFS/DSM/naming gotchas that have cost past sessions time.
+
+**For SSH-driven work: use `scripts/elway`.** Write a playbook under
+`playbooks/<name>.yaml` and run
+`scripts/elway <host> --playbook ...` instead of chaining
+`ssh -t host 'sudo …'` commands — handles sudo once lazily,
+structured pass/change/fail reporting, idempotency via
+`creates:` / `when:` / `changed_when:`. Template:
+[`playbooks/elway-smoke.yaml`](playbooks/elway-smoke.yaml).
+
+**Task visibility via task-board.** If the Claude Code session has
+the `task-board` plugin enabled (installed from
+`git@gitea.phasefinal.com:vh/task-board.git`), a card at
+`http://10.250.50.70:7878/` tracks work in progress. Hooks flip the
+card on turn boundaries automatically; call `task_start` /
+`task_update` / `task_wait` / `task_complete` MCP tools to set the
+activity subheader and post meaningful log entries.
+
 ## Purpose
 
 - Inventory of servers and their state
@@ -53,7 +71,8 @@ Observed and standardized across servers:
 
 | Name | IP | Site | Role | Details |
 |------|-----|------|------|---------|
-| ana-ml2 | 10.250.50.54 | Anaheim (`10.250.0.0/16`) | GPU / AI inference (bare metal) | `servers/ana-ml2/README.md` |
+| ana-ml2 | 10.250.50.54 | Anaheim (`10.250.0.0/16`) | GPU / AI inference (bare metal, dual RTX 6000 Ada) | `servers/ana-ml2/README.md` |
+| irv-ml1 | 10.100.79.3 (WG) | Irvine — reachable only via WireGuard tunnel from NH3 | GPU / AI inference (bare metal, RTX 3090 + RTX A6000, native stacks) | `servers/irv-ml1/README.md` |
 | ana-docker | 10.250.50.70 | Anaheim | General-purpose Docker host (non-GPU VM on pfi-pve) | `servers/ana-docker/README.md` |
 | pfi-ana-webhost | 10.250.50.52 | Anaheim | VM on pfi-pve (VMID 110) — web workload | `servers/pfi-ana-webhost/README.md` |
 | ana-filebot | 10.250.50.53 | Anaheim | LXC on pfi-pve (CT 112) — file-task automation | `servers/ana-filebot/README.md` |
@@ -62,18 +81,24 @@ Observed and standardized across servers:
 | pfi-postgres | 10.250.50.80 | Anaheim | VM on pfi-pve (VMID 105) — shared Postgres (vaultwarden/gitea/paperless) | `servers/pfi-postgres/README.md` |
 | ana-wg | 10.250.50.252 | Anaheim | LXC on pfi-pve (CT 113) — WireGuard | `servers/ana-wg/README.md` |
 | pfi-pve | 10.250.250.31 | Anaheim | Proxmox VE hypervisor | `servers/pfi-pve/README.md` |
+| pbs-ana | 10.250.50.90 | Anaheim | Proxmox Backup Server — fleet primary (VM on pfi-pve, NFS datastore on ana-nas) | `servers/pbs-ana/README.md` |
 | sfsrv-ana | 10.250.250.115 | Anaheim | **SureFire client (PFI-managed)** — Proxmox VE hypervisor | `servers/sfsrv-ana/README.md` |
 | sf-ana-container | 10.250.150.100 | Anaheim | **SureFire client (PFI-managed)** — container workload on sfsrv-ana | `servers/sf-ana-container/README.md` |
 | sf-r630 | iDRAC 10.250.250.110 | Anaheim | **SureFire client (PFI-managed)** — physical Dell R630, iDRAC-managed from PFI side | `servers/sf-r630/README.md` |
 | nh3-docker | 10.100.50.40 | NH3 (`10.100.0.0/16`) | General-purpose Docker host (non-GPU VM on nh3-pve) | `servers/nh3-docker/README.md` |
 | nh3-pve | 10.100.250.60 | NH3 | Proxmox VE hypervisor | `servers/nh3-pve/README.md` |
+| nh3-nas | 10.100.50.50 | NH3 | Synology RS2418+ — NFS exports, rest-server-nh3, PBS-NH3 datastore backend | `servers/nh3-nas/README.md` |
+| pbs-nh3 | 10.100.50.90 | NH3 | Proxmox Backup Server — DR mirror (VM on nh3-pve, NFS datastore on nh3-nas); syncs from pbs-ana | `servers/pbs-nh3/README.md` |
 | esh-docker-vm | 10.0.50.45 | ESH home lab (`esteban.net`, `10.0.50.0/24`) | Home-lab Docker host (VM on esh-pve) | `servers/esh-docker-vm/README.md` |
 | vm-esh-nas | 10.0.50.154 | ESH home lab | NAS-adjacent Docker host (VM on esh-pve-nas) | `servers/vm-esh-nas/README.md` |
 | esh-pve | 10.0.250.35 | ESH home lab | Proxmox VE hypervisor | `servers/esh-pve/README.md` |
 | esh-pve-nas | 10.0.50.55 | ESH home lab | Proxmox VE hypervisor (storage / media) | `servers/esh-pve-nas/README.md` |
+| esh-vm-db | 10.0.50.60 | ESH home lab | DB VM — PostgreSQL (paperless-ng) + MongoDB; bare-metal VM, no Docker | `servers/esh-vm-db/README.md` |
 
 **Placement rules:**
-- GPU-required stacks → `ana-ml2`.
+- GPU-required stacks → `ana-ml2` (primary, Anaheim) or `irv-ml1`
+  (secondary, Irvine — bigger VRAM ceiling at 72 GB total). Access
+  to `irv-ml1` requires WireGuard.
 - Anaheim non-GPU services → `ana-docker`.
 - NH-site non-GPU services → `nh3-docker`.
 - ESH home-lab workloads (`esteban.net`) → `esh-docker-vm` (general) or `vm-esh-nas` (needs direct NFS mounts from 10.0.50.50). Not part of the PFI colo topology, but shares monitoring/backup tooling.

STATUS.md

@@ -1,16 +1,23 @@
 # Status + Open Issues
 
-Last updated: 2026-04-21
+Last updated: 2026-04-24
 
 Snapshot of fleet state and open work. Refresh this file when a pass of
 significant work lands — don't let it drift quietly.
 
+**New session? Read [`docs/orientation.md`](docs/orientation.md) first.**
+
 ## What's in place
 
-### Backup coverage
+### Backup coverage (2-layer, fully operational)
 
-- **VM-level vzdump:** 24/24 guests across pfi-pve, nh3-pve, esh-pve, esh-pve-nas.
+- **PBS fleet-wide.** All 5 hypervisors (pfi-pve, nh3-pve, esh-pve,
-- **File-level restic:** 6/6 hosts configured with systemd timers:
+  esh-pve-nas, sfsrv-ana) → `pbs-ana` (primary, VM on pfi-pve with
+  NFSv3 datastore on ana-nas). Per-hypervisor namespaces to avoid
+  VMID collisions. DR mirror at `pbs-nh3` (VM on nh3-pve with NFSv3
+  datastore on nh3-nas Synology) pulls daily at 06:00. Verify jobs
+  armed on both sides.
+- **restic 8/8 hosts** with resticprofile + systemd timers at 01:00:
   | Host | Target rest-server | DB hooks |
   |---|---|---|
   | ana-docker | rest-server-ana (local) | synapse, seafile, vaultwarden-pg, gitea (native dump), openwebui |
@@ -19,17 +26,48 @@ significant work lands — don't let it drift quietly.
   | esh-docker-vm | rest-server-ana (cross-site) | paperless-pg, HA SQLite, CWA SQLite, pgadmin SQLite, uptime-kuma SQLite |
   | vm-esh-nas | rest-server-ana (cross-site) | — |
   | nh3-dev (workstation) | rest-server-nh3 (local) | — |
+  | irv-ml1 | rest-server-nh3 (via WG) | — |
+  | esh-vm-db | rest-server-ana (cross-site) | pg_dumpall, mongodump |
+- **Cross-site restic rsync.** `ana-nas → nh3-nas` at 04:00 daily
+  (mirrors rest-server-ana data). `nh3-nas → ana-nas` at 05:00 daily
+  (mirrors rest-server-nh3 data, runs as root since DSM writes files
+  as admin mode 400). Tracked at `configs/rsync/{ana-nas-to-nh3,nh3-nas-to-ana}/`.
 
 ### Inventory
 
-- **18 tracked hosts** under `servers/` (5 Docker + 4 Proxmox + 1 workstation +
+- **~22 tracked hosts** under `servers/` across ANA / NH3 / ESH / IRV sites.
-  6 PFI VMs + 3 SureFire tenant + 1 NH3-dev workstation... audit the actual count
+  SSH config aliases in `~/.ssh/config` for every host — `ssh <name>` just works.
-  vs this when updating).
+- **Homepage** at <http://10.0.50.45:5100> — function-first layout
-- **Homepage** at <http://10.0.50.45:5100> shows function-first layout with
+  (Main / Infrastructure / Toolchain tabs), per-group icons, four
-  Main / Infrastructure / Toolchain tabs. Per-group icons, row-count
+  Infra sub-groups (ANA / NH3 / IRV / ESH). Docker auto-discovery
-  layout, useEqualHeights.
+  active for 5 hosts (ana-docker, ana-ml2, nh3-docker, esh-docker-vm,
-- **FortiGate + UniFi discovery** scripts produce TSVs; gap analysis
+  irv-ml1).
-  against `servers/*` for unmanaged IPs.
+- **FortiGate + UniFi discovery scripts** produce TSVs; gap analysis
+  against `servers/*/` for unmanaged IPs.
+
+### Architecture decisions (durable)
+
+- **DB data on local disk, not NFS.** pfi-postgres migrated 2026-04-23;
+  fstab + NFS mount removed 2026-04-24 (pfi-postgres now fully
+  decoupled from ana-nas). Mongo on esh-vm-db confirmed already local.
+  Removes the biggest ana-nas blast-radius risk. Memory:
+  `project_db_migrate_off_nfs.md`.
+- **Backups must not risk production.** Rule adopted after
+  2026-04-23 ana-nas self-backup crash. Memory:
+  `feedback_backups_must_not_risk_production.md`.
+- **offen sidecars retired fleet-wide 2026-04-23.** restic covers
+  equivalent scope; reclaimed 16 GB of redundant tarballs on
+  `/mnt/backup/docker/esh-vm-docker/`.
+- **Gitea remote for this repo (2026-04-23).** `origin` is
+  `vh/esh-pfi-infrastructure` on `gitea.phasefinal.com`. Also:
+  `vh/task-board` (new 2026-04-24) hosts a Claude Code plugin +
+  marketplace serving the assistant task-state dashboard.
+- **Prefer elway for multi-step SSH work (2026-04-24).** The new
+  `scripts/elway` mini-playbook runner replaces chained `ssh -t sudo …`
+  commands — handles sudo once up front, structured reporting,
+  idempotency (creates/when/changed_when). Memory:
+  `feedback_use_elway.md`; template playbook:
+  `playbooks/elway-smoke.yaml`.
 
 ### Tooling
 
@@ -40,29 +78,39 @@ significant work lands — don't let it drift quietly.
   `scripts/discover-gaps.sh` for network-level inventory discovery.
 - `scripts/deploy-stack.sh` + `scripts/sync-stacks.sh` for compose push/pull.
 - `scripts/add-host.sh` for new-host registration.
+- **`scripts/elway`** (2026-04-24) — mini-ansible playbook runner over
+  SSH. Playbooks live under `playbooks/`. Tier 1 (creates/when) + tier
+  2 (changed_when) idempotency; handlers + register + multi-host
+  fan-out deferred as gitea issues #3–#5.
+- **`tea` CLI** at `/usr/local/bin/tea` — gitea CLI, already logged in
+  as `vh`. Use for issue / PR work instead of inventing URLs.
 
 ## Open issues
 
 ### 🟥 Quick wins (do next)
 
-1. **Fix Backrest's `esh-docker-vm` URI** — Backrest is pointed at
+1. ~~**Fix Backrest's `esh-docker-vm` URI**~~ — done.
-   `10.100.50.50` (NH3 Synology) for that repo, while the actual backup
-   writes go to `10.250.50.70` (rest-server-ana). Edit `config.json` in
-   the backrest container, swap the host portion. ~5 min.
 
-2. **Verify SSH on the 9 newly-registered hosts** and pull first snapshots:
+2. ~~**Push SSH keys + pull snapshots for 6 unrefreshed hosts**~~ —
-   ```
+   **done 2026-04-23**. 4 VMs (pfi-ana-webhost, pfi-pteradactyl,
-   scripts/refresh-server-info.sh --validate-only all
+   pfi-tacticalrmm, pfi-postgres) took the workstation key via
-   scripts/refresh-server-info.sh pfi-ana-webhost ana-filebot pfi-pteradactyl \
+   `ssh-copy-id` with `lkraven@`. 2 LXCs (ana-filebot, ana-wg)
-     pfi-tacticalrmm pfi-postgres ana-wg
+   needed key installed via `pct push` from pfi-pve because
-   ```
+   `PermitRootLogin prohibit-password` blocked `ssh-copy-id`.
-   ssh-target files were guessed (`lkraven@` for VMs, `root@` for LXCs) —
+   Minor: pfi-pteradactyl's `server_inspect` Docker section is blank
-   first run surfaces mismatches.
+   because lkraven is not in the `docker` group there — `sudo usermod
+   -aG docker lkraven` + re-login to fix.
 
-3. **Patch out `forget` schedules from all 6 restic profiles.** They fail
+3. ~~**Patch out `forget` schedules from all 6 restic profiles**~~ — done.
-   nightly against `--append-only` rest-servers. One-liner per host:
+
-   comment out `schedule:` under the `forget` block in profiles.yaml;
+3b. ~~**Discover sf-r630 OS-side IP**~~ — **resolved 2026-04-23**:
-   redeploy; run `resticprofile unschedule forget` on each host. ~15 min.
+    the R630 with iDRAC `10.250.250.110` is the same physical box
+    that runs `sfsrv-ana` (Proxmox VE at `10.250.250.115`). No
+    separate OS IP to find. `servers/sf-r630/` now clarifies it as
+    the hardware/BMC-only inventory entry; `servers/sfsrv-ana/` is
+    the OS view. `servers/ana-ml2/README.md` updated with its own
+    distinct BMC IP (`10.250.250.50`, Supermicro) to prevent future
+    confusion between the two physical chassis.
 
 <!-- 2026-04-21: Dropped the "nightly-restart safety net" idea — user
      confirmed Backrest UI chokes even right after startup, so periodic
@@ -73,63 +121,81 @@ significant work lands — don't let it drift quietly.
 
 ### 🟧 Real work (dedicated session each)
 
-5. **Rotate exposed secrets** (captured in session transcripts 2026-04-20/21):
+4b. ~~**Migrate DB data directories off NFS onto local VM disk.**~~ —
-   - `vaultwarden` Postgres password (on pfi-postgres)
+    **done 2026-04-23/24.** Postgres on pfi-postgres migrated
-   - `gitea` Postgres password — currently literally `gitea` (trivially weak)
+    04-23; mongodb on esh-vm-db confirmed already local (and serves
-   - `paperless-ng` Postgres password — currently literally `paperless-ng` (trivially weak)
+    zero user data in practice — paperless uses Postgres 15 on the
-   - `ana-docker` rest-server htpasswd + repo passphrase
+    same VM). fstab entry + NFS mount for `/mnt/db` on pfi-postgres
-   - `ana-ml2` rest-server htpasswd (repo passphrase rotated during wipe/reinit)
+    removed 2026-04-24 via
-   - `esh-docker-vm` rest-server htpasswd + repo passphrase
+    `playbooks/decouple-pfi-postgres-from-ana-nas.yaml`. pfi-postgres
+    has zero remaining dependency on ana-nas. Only residue: cold
+    archive of pre-migration data still on ana-nas (`/mnt/db/pfi-*`);
+    harmless, can sit indefinitely.
 
-   For each: rotate at the source (DB `ALTER USER …` / `htpasswd` /
+5. ~~**Rotate exposed secrets**~~ — **done 2026-04-23**. All six
-   `restic key add` + `restic key remove`) → update consumer config
+   rotated: vaultwarden/gitea/paperless-ng Postgres passwords
-   files (`/etc/restic/restic.env`, `/etc/restic/dbcreds.env`, compose
+   (hardcoded `compose.yaml` literals moved to gitignored `.env`
-   env files, Backrest config.json) → restart consumer services. ~45 min
+   files in the process), ana-docker + ana-ml2 + esh-docker-vm
-   batched.
+   rest-server htpasswd entries, and rest-server repo passphrases for
+   ana-docker + esh-docker-vm (ana-ml2's was already rotated during
+   prior wipe+reinit). Also discovered along the way: paperless uses
+   a separate `esh-vm-db` VM (10.0.50.60), not pfi-postgres as the
+   old notes implied.
 
-6. **Cross-site rsync** between `rest-server-ana` data dir
+6. ~~**Cross-site rsync**~~ — **done 2026-04-23, both directions**.
-   (`/mnt/backup/restic/repo/ana/`) and NH3 Synology data dir. Planned
+   - **ana → nh3** (04:00 daily): `ana-nas:/mnt/backup/restic/repo/ana/`
-   since initial rest-server setup; not built. Needs Synology SSH
+     → `nh3-nas:/volume1/Backup/restic-ana-mirror/`. Runs on ana-nas
-   access first (item 8). ~20 min once access is there.
+     as lkraven. 15.6 GB initial sync completed 07:18 UTC.
-   - Note: cross-site mirroring for the VM-image layer is being
+   - **nh3 → ana** (05:00 daily): `nh3-nas:/volume1/Backup/restic/`
-     addressed by the PBS deployment (item 6b) — this rsync is now
+     → `ana-nas:/mnt/backup/restic-nh3-mirror/`. Runs on nh3-nas as
-     scoped to restic repos only.
+     root (rest-server-nh3 container writes mode-400 files; only
+     root can read them on Synology). 2.31 GB initial sync completed
+     07:42 UTC.
+   - Tracked at `configs/rsync/ana-nas-to-nh3/` and
+     `configs/rsync/nh3-nas-to-ana/` respectively.
 
-6b. **PBS deployment across the fleet.** Runbook lives at
+6b. **PBS deployment across the fleet.** Runbook at
-    `docs/runbooks/pbs-deployment.md`. Primary at ANA (VM on pfi-pve,
+    `docs/runbooks/pbs-deployment.md`. Phases 0–6 **done** (2026-04-22):
-    NFS datastore on Debian NAS), DR mirror at NH3 (VM on nh3-pve,
+    PBS-ANA on pfi-pve with NFS datastore on Ana NAS (NFSv3 for ZFS
-    local datastore). One-way sync from ANA → NH3 nightly. All 5
+    case-insensitivity), PBS-NH3 on nh3-pve with NFS datastore on NH3
+    Synology (NFSv3 + Linux-mode POSIX 777 to avoid syno_acl
+    interference), per-hypervisor namespaces, API tokens, verify jobs
+    on both, one-way sync ANA → NH3 at 06:00 daily, and all 5
     hypervisors (pfi-pve, nh3-pve, esh-pve, esh-pve-nas, sfsrv-ana)
-    migrate off local-dump vzdump jobs onto PBS.
+    onboarded to PBS-ANA.
-    - Closes: SureFire's zero-coverage gap (currently no vzdump at all on sfsrv-ana)
+    Remaining phases:
-    - Closes: "cross-site redundancy for VM images" scope item
+    - Phase 7-8 — one week burn-in, then retire legacy vzdump targets
-    - Provides: cross-fleet block-level dedupe, dirty-bitmap incrementals,
+      on each hypervisor (keep until 2026-04-29 earliest)
-      real safe-prune retention, per-host encryption keys
+    - Phase 9 — homepage cards for PBS-ANA + PBS-NH3 web UIs,
-    - Est. 4–6h spread across sittings. 9 phases in the runbook.
+      memory/doc updates, `servers/pbs-ana` + `servers/pbs-nh3` dirs
 
-7. **SureFire tenant backup plan decision.** Three options documented in
+7. ~~**SureFire tenant backup plan decision**~~ — **resolved 2026-04-23**
-   `servers/sfsrv-ana/README.md`:
+   by folding sfsrv-ana into the fleet-wide PBS deployment (dedicated
-     - Tenant handles own backups
+   `sfsrv-ana` namespace on PBS-ANA, replicates to PBS-NH3 via the
-     - PFI provides dedicated scoped repo on rest-server-ana
+   same sync job as the rest of the fleet). Hosting-agreement option
-     - Shared vzdump target
+   chosen: PFI provides backup coverage as part of managed hosting.
-
-   Blocks any actual SF backup work until the hosting-agreement side of
-   this is clear.
 
 ### 🟨 Prereqs / polish
 
-8. **Synology SSH setup** — tabled earlier. Unlocks: cross-site rsync
+8. ~~**Synology SSH setup**~~ — **done 2026-04-22**. Dedicated
-   (item 6), rest-server-nh3 healthcheck deploy, easier `.htpasswd`
+   `syncuser` account (admin-group membership) with key auth,
-   edits on the NH3 side.
+   registered as `servers/nh3-nas/`, reachable as `ssh nh3-nas`.
+   Unlocks cross-site rsync (item 6), rest-server-nh3 healthcheck
+   deploy, and `.htpasswd` edits on the NH3 side.
 
 9. **`scripts/restic-prune.sh`** — temporarily flip `--append-only` off,
    run forget + prune across all hosts, flip back on. Needed quarterly
    for disk hygiene. Not urgent; blocks only the "I need to reclaim
    disk space now" scenario.
 
-10. **Retire `offen/docker-volume-backup` sidecars on esh-docker-vm** once
+10. ~~**Retire `offen/docker-volume-backup` sidecars**~~ — **done
-    restic has ~1 week of clean runs. Paperless + pgadmin currently run
+    2026-04-23**. Removed from paperless-ngx and pgadmin composes on
-    offen sidecars that write tarballs to `/mnt/backup/...` redundantly.
+    esh-docker-vm (only hosts in the fleet that had them). 16 GB of
+    orphan tarballs at `/mnt/backup/docker/esh-vm-docker/` reclaimed.
+    Restic coverage verified equivalent: `/var/lib/docker/volumes` in
+    source + pre-backup hook handles the DB dumps for paperless
+    (against esh-vm-db), HA, pgadmin, CWA, uptime-kuma. Obsolete
+    `*_offen_backup_data` exclude also removed from the restic profile.
 
 11. **Clean up retired mattermost dir** on ana-docker — compose dir at
     `/opt/docker/compose/mattermost/` may still linger. Single `rm -rf`
@@ -159,6 +225,25 @@ significant work lands — don't let it drift quietly.
     lands. Consider a `scripts/status-regen.sh` if manual updates
     slip.
 
+## Session milestones — 2026-04-24 (the "tooling day")
+
+- **irv-ml1 AI stacks deployed** as Docker: ComfyUI (port 8188, host-
+  writable workflows), Parakeet ASR (port 8765, rewritten on
+  sherpa-onnx after the Shadowfita FastAPI wrapper hit two unfixed
+  upstream bugs), CosyVoice 3 (port 8190, GLaDOS voice cloned + live).
+- **irv-ml1 restic profile extended** to cover
+  `/worktank/{comfyui/basedir/{user,custom_nodes,input},cosyvoice/voices}`;
+  bulk weights + scratch dirs stay excluded.
+- **`scripts/elway`** shipped — ~800-line Python playbook runner with
+  tier 1 + tier 2 idempotency; handlers / register / multi-host /
+  content-hash are deferred (gitea #3–#6).
+- **task-board** built end-to-end (separate repo, `vh/task-board` on
+  gitea) and shipped as a Claude Code plugin. Green/red cards per
+  session via UserPromptSubmit + Stop hooks; four MCP tools expose
+  explicit activity tracking.
+- **pfi-postgres NFS decoupling** finished item 4b — zero residual
+  dependency on ana-nas for that VM.
+
 ## Session milestones — 2026-04-20 / 2026-04-21
 
 - Homepage reorganized to function-first with tabs (Main / Infrastructure / Toolchain).
@@ -181,10 +266,20 @@ significant work lands — don't let it drift quietly.
 Relevant `~/.claude/.../memory/` entries:
 
 - `server_split.md` — host placement rules
-- `feedback_ssh_sudo.md` — use `ssh -t` for remote sudo
+- `feedback_ssh_sudo.md` — use `ssh -t` for remote sudo (mostly
+  superseded by elway, but still applies to ad-hoc ssh)
 - `feedback_git_autonomous.md` — handle git commits without asking
 - `feedback_git_commits.md` — no Claude attribution in commit messages
-- `project_backup_pipeline_gaps.md` — user's explicit goal of "all hosts +
+- `feedback_use_elway.md` — write elway playbooks; don't chain ssh+sudo
-  configs + DBs backed up"
+- `feedback_backups_must_not_risk_production.md` — rule adopted after
+  the 2026-04-23 ana-nas self-backup crash
+- `project_backup_pipeline_gaps.md` — user's explicit goal of "all
+  hosts + configs + DBs backed up"
+- `project_db_migrate_off_nfs.md` — DB-off-NFS decision + status
 - `project_surefire_tenant.md` — SureFire tenancy boundary awareness
-- `storage_ana_nas.md` — ana NAS is Debian, not TrueNAS
+- `reference_gitea_remote.md` — origin is `vh/esh-pfi-infrastructure`
+  on gitea.phasefinal.com; `tea` CLI logged in as `vh`
+- `reference_task_board.md` — task-board plugin + tools contract
+- `storage_ana_nas.md` — ana NAS is Debian LXC (CT 109), not TrueNAS
+- `storage_nh3_nas.md` — NH3 NAS via `syncuser`, not `admin`
+- `incident_ana_nas_spof.md` — blast-radius matrix for ana-nas outages

playbooks/decouple-pfi-postgres-from-ana-nas.yaml

@@ -0,0 +1,95 @@
+# Finish the 2026-04-23 DB-off-NFS migration by removing pfi-postgres's
+# residual dependency on ana-nas's /mnt/db NFS export.
+#
+# Postgres on pfi-postgres is already running from local disk
+# (/var/lib/postgresql/13/main); /mnt/db is still mounted but
+# nothing writes to it. This playbook pulls the fstab line, unmounts,
+# and removes the empty mountpoint — eliminating ana-nas from
+# pfi-postgres's fault domain entirely.
+#
+# The old pre-migration data directories on ana-nas (pfi-mongo/,
+# pfi-postgres/) are NOT touched. They remain as a cold archive of
+# the pre-migration state and cost nothing to keep.
+#
+# Usage:
+#   scripts/elway pfi-postgres --playbook playbooks/decouple-pfi-postgres-from-ana-nas.yaml
+#
+# Safe to re-run: every mutation is creates-gated or when-gated, so a
+# second invocation is a no-op.
+
+vars:
+  fstab: /etc/fstab
+  mount_point: /mnt/db
+  nfs_source: "10.250.50.50:/mnt/db"
+
+steps:
+  # ── pre-flight confirmations ────────────────────────────────────────
+
+  - name: Confirm Postgres IS running off local disk (not /mnt/db)
+    # changed_when: false — we're attesting, not changing. Fails hard
+    # if Postgres somehow ended up on the NFS path we're about to
+    # unmount.
+    shell: ps -ef | grep -v grep | grep 'postgres.*-D' | grep -q '/var/lib/postgresql'
+    changed_when: "false"
+
+  - name: Confirm /mnt/db has no open files (nothing writing to it)
+    # lsof exits non-zero if no matches found — that's what we want.
+    # Invert with `!`. If the mount point IS in use we want the
+    # playbook to halt so the user can investigate.
+    shell: "! sudo lsof +D {{ mount_point }} 2>/dev/null | grep -v '^COMMAND'"
+    sudo: true
+    changed_when: "false"
+
+  # ── unmount + fstab ────────────────────────────────────────────────
+
+  - name: Remove fstab entry for {{ nfs_source }}
+    shell: sed -i "\\|^{{ nfs_source }}[[:space:]]|d" {{ fstab }}
+    sudo: true
+    # Idempotency: if the line is already absent, the sed is a no-op
+    # but still reports "changed" since sed always rewrites the file.
+    # `when:` gate below makes it truly idempotent.
+    when: "grep -qE '^{{ nfs_source }}[[:space:]]' {{ fstab }}"
+
+  - name: Unmount {{ mount_point }}
+    shell: umount {{ mount_point }}
+    sudo: true
+    # Only run if currently mounted.
+    when: "mountpoint -q {{ mount_point }}"
+
+  - name: Remove empty mountpoint dir
+    shell: rmdir {{ mount_point }}
+    sudo: true
+    # Only if the dir exists AND is empty (rmdir fails on non-empty,
+    # which is the safety we want). The `creates: null` pattern
+    # doesn't apply here; we use a when: that checks both conditions.
+    when: "[ -d {{ mount_point }} ] && [ -z \"$(ls -A {{ mount_point }} 2>/dev/null)\" ]"
+
+  # ── tell systemd to forget the old mount unit ──────────────────────
+
+  - name: Reload systemd so the synthesized mnt-db.mount unit clears
+    shell: systemctl daemon-reload
+    sudo: true
+    changed_when: "false"
+
+verify:
+  - name: fstab no longer references /mnt/db
+    shell: "! grep -qE '^{{ nfs_source }}[[:space:]]' {{ fstab }}"
+    changed_when: "false"
+
+  - name: /mnt/db is not a mountpoint
+    shell: "! mountpoint -q {{ mount_point }}"
+    changed_when: "false"
+
+  - name: No systemd mnt-db.mount unit remains active
+    # Don't grep for "active" — "inactive" contains it as a substring.
+    # `is-active` returns 0 only when the unit is truly active; invert.
+    shell: "! systemctl is-active mnt-db.mount >/dev/null 2>&1"
+    changed_when: "false"
+
+  - name: Postgres is still running (we didn't accidentally break it)
+    shell: systemctl is-active postgresql
+    changed_when: "false"
+
+  - name: Postgres still listening on :5432
+    shell: "ss -tln | grep -q ':5432'"
+    changed_when: "false"