memory: snapshot — FV dark, Flash-Next seat built, power policy settled

Operator-invoked before heading to the Fountain Valley site visit.

Rewrites Current state / in-flight around the outage: FV dark since 06:56Z including the
BMC, will not self-recover, 19 of 30 gateway aliases down with no local fallback because
every free local model lived on fv-ml1 and irv-ml1 runs no chat seat. The section now
POINTS AT docs/runbooks/fv-site-dark-20260913.md rather than restating it, since the
runbook is the single source of truth for the visit.

Records what was built and verified before the power failed -- the Flash-Next seat on one
card with its 51B n-gram table in host RAM, gen-large on the gateway -- and what is
decided but unexecuted: the 250 W / 200 W power caps, the incomplete MTP campaign with one
off_A rep banked, and the ten stale Homepage labels that the staged bring-up fixes as a
side effect.

Closes a stale in-flight claim: the 'fv-ml1 cannot initiate to fleet LAN IPs' gap is
resolved, fixed by another session's scoped SNAT at 06:22Z with Beszel 18/18 verified.
Adds ana-ml3 as its own subsection, since conflating it with fv-ml1 caused two rounds of
wrong arithmetic today.

Auto-archival fired (index was 431 lines, over the ~300 cap) but reached only 2 entries.
The 14-day guard holds almost everything: this repo has had an exceptionally dense
fortnight and nearly every dated entry postdates 2026-08-30. Of the six entries old
enough, four carry open deferred-work pointers and were held back per the decision-loss
guard. The file stays over cap, which is the documented trade -- an over-cap file that
keeps live decisions beats a scannable one that lost one.

archival-memory.md

@@ -4,6 +4,13 @@ _Entries moved out of persistent-memory.md to keep the active file scannable. Re
 
 ## Recent decisions (archived)
 
+- `[2026-08-25]` **Run 2's base is an OPEN OPERATOR DECISION, deliberately not staged** — four options with materially different safety postures, detailed in Current state. Tracked at althing thread `01M0WQ8W5574KMEVCHCEKEXNS5`. ⚠ Do not let it get filed as a config knob; it is a reversal of the trainee-selection decision.
+  _Archived 2026-09-13._
+
+- `[2026-08-24]` **Serving the tuned ERP model: LoRA-on-NVFP4 PREFERRED, merged weights the expected fallback — and the recorded objection may be STALE.** Operator: "if you CAN load it as a lora, all the better, the issue is that we will want to run nvfp4 weights, which we had some serious trouble with loading loras on top of nvfp4." ⚠ **The archived root-cause says it was NOT NVFP4-specific**: `[2026-07-07]` vLLM 0.24.0 qwen3_5 LoRA application was a silent no-op (#47639, regression from #37912) — adapter loads HTTP 200, zero deltas at inference, proven **quant-agnostic (NVFP4 AND FP8 both inert)** and adapter-format-agnostic by a 3-peer dwarf panel. Fix PR #47640 was OPEN then. **ana-ml2 is FAR past 0.24.0 and the box runs a SPREAD, not one version** (measured 2026-08-24): `gen` on `nightly-311b3513` = **0.27.2rc1.dev150**, `mog-sec` on `nightly-e9d1398d` = 0.26.1rc1.dev1102, the small seats still on 0.24.0, and char-rp/trainee-bench pinned to v0.26.0. ⚠ **`vllm/vllm-openai:v0.27.1` is already ON DISK, unused** — a TAGGED release, which is the right retest target: no nightly variance, no pull, ~4 months past the diagnosis. So: RETEST hot-swap LoRA on **v0.27.1** before designing around merge — it is cheap, and if it works the post-tune gate can be two aliases on one engine. If it still no-ops, merged weights it is, which means the harness must EMIT merged weights and Eitri needs that in the contract while he is early. Tracked at this snapshot commit; settle it in the QLoRA sizing conversation.
+  _Archived 2026-09-13._
+
+
 - `[2026-08-28]` **althing v3 flag day (U9b) executed, then six releases to 3.1.1 in one afternoon — and the post office MOVED to nh3-docker.** Every v2 command deleted; 73 handles seeded and verified by set difference; 5,043 orphaned wake FIFOs deleted (v2 named them per-session+PID, v3 per-handle). Image now registry-pulled, digest-pinned, under the `claude-bot` namespace. → `persistent-memory.d/2026-08-28-althing-v3-cutover.md`
   _Archived 2026-09-12._