feat: althing v3.0.0 cutover (U9b) and the sec seat onto GPU0

Two operator-authorised changes on the same afternoon.

## althing v3 (U9b flag day, one-way, no rollback)

The post office replaced the v2 P2P bus on nh3-dev and nh3-extdev.
One container is the only stateful component; heralds are one per box
and dial out; waiters are one per session. Every v2 command was deleted
rather than deprecated, so a script calling althing-cli now fails loudly
instead of silently talking to nothing.

73 handles seeded from the v2 CLI, which is authoritative over the v2
database's 91 agent rows -- the extra 18 are superseded names, a typo,
an underscore variant, and two machine-qualified handles that v3 makes
a category error. Verified by set difference in both directions rather
than by counting; a peer's "72 rendered" was a line-count artifact.

Deleted 5,043 orphaned wake FIFOs. The reason there were five thousand
is that v2 named them per session with the PID and never reaped them;
v3 names them per handle, so the leak is bounded by construction. That
is a fix in v3, not a cleanup we performed.

nh3-extdev needed its own path: althing lives there as a system wheel
under /opt/uv-tools with entry points in /usr/local/bin, its daemons
were system units rather than user units, and uv is not on the login
user's PATH. Captured as a rerunnable playbook rather than shell
history.

The v2 database is left inert on disk. There is no import path and none
was improvised.

## sec onto GPU0

GPU1 carries the five resident fleet seats and had ~28 GB free against
the ~51 GB this seat reserves, so it could not start there at all. GPU0
has been idle since run 3c was stopped. The compose header, the GPU pin
default and the homepage label all carried the old card number and are
corrected together -- a label that names the wrong GPU is a record that
lies about where the work runs.

Both playbooks carry verify phases that assert effective state. Two of
those verifies failed on green deployments while I was writing them:
one used a Go template that collided with the runner's own {{ }}
substitution, one omitted --handle so it failed on identity rather than
reachability. Both are fixed with the reason recorded inline, because a
verify that reports FAILED on a working system trains you to ignore it.

stacks/litellm/conf/config.yaml

@@ -327,8 +327,8 @@ model_list:
   #     down, weights intact) if it is ever wanted back. Not repointed to mog-sec
   #     -- a security model is not an RP-reasoning model (no false aliases). ---
 
-  # --- sec (was mog-sec, renamed 2026-08-21) -> M.O.G.-SEC-27B pen-test seat (ana-ml2 GPU1 :8019, in the retired
-  #     fable slot). Blackfrost-Research/M.O.G.-SEC-27B-1M-CTX, stock-Qwen3.8-27B
+  # --- sec (was mog-sec, renamed 2026-08-21) -> M.O.G.-SEC-27B pen-test seat (ana-ml2 GPU0 :8019 — moved off GPU1
+  #     2026-08-28, GPU1 no longer had room). Blackfrost-Research/M.O.G.-SEC-27B-1M-CTX, stock-Qwen3.8-27B
   #     base, quantized in-house to mixed NVFP4+FP8 with MTP + vision preserved.
   #     Served at native 262K (NOT the card's 1M -- that needs YaRN + SGLang/DFlash2,
   #     not our vLLM path). presence_penalty deliberately 0.0, NOT the fleet's 1.5:

stacks/mog-sec/compose.yaml

@@ -1,5 +1,15 @@
-# mog-sec — the pen-test seat on ana-ml2 GPU 1 (:8019), in the slot the retired
-# fablefusion-charrp-probe used to occupy.
+# mog-sec — the pen-test seat on ana-ml2 GPU 0 (:8019).
+#
+# MOVED GPU 1 -> GPU 0 on 2026-08-28 (operator-directed). GPU 1 carries the five
+# resident fleet seats (gen 46 GB + embed + coder + rerank + reward = ~69.9 GB of
+# 97.9), leaving ~28 GB — less than the ~51 GB this seat reserves at
+# MOG_GPU_MEM_UTIL=0.52, so it could no longer start there. GPU 0 has been idle
+# since run 3c was stopped.
+#
+# ⚠ POWER: bringing this up re-arms the two-GPU load condition that tripped the
+# Anaheim rack breaker on 2026-08-26. One circuit feeds the whole rack including
+# ana-gw and ana-wg, so a trip costs the site AND the remote path in. Idle draw is
+# negligible (~6-13 W/card); the risk is sec and gen under concurrent load.
 #
 # Serves Blackfrost-Research/M.O.G.-SEC-27B-1M-CTX-BF16 (stock-Qwen3.8-27B-based,
 # vision-intact Qwen3_5ForConditionalGeneration, base-graft MTP head), quantized
@@ -108,7 +118,7 @@ services:
           devices:
             - driver: nvidia
               device_ids:
-                - "${MOG_GPU_ID:-1}"
+                - "${MOG_GPU_ID:-0}"
               capabilities:
                 - gpu
     healthcheck:
@@ -123,7 +133,7 @@ services:
       - homepage.group=AI - Inference
       - homepage.name=M.O.G.-SEC 27B (pen-test)
       - homepage.icon=mdi-shield-lock
-      - homepage.description=Uncensored security model, Qwen3.8-27B NVFP4+MTP, 262K — the `mog-sec` seat (ana-ml2 GPU 1)
+      - homepage.description=Uncensored security model, Qwen3.8-27B NVFP4+MTP, 262K — the `mog-sec` seat (ana-ml2 GPU 0)
       - homepage.href=http://10.250.50.54:${MOG_PORT:-8019}/docs
 
 networks: