memory: vLLM release status for #51113 — no stable yet; gemma4 CoT is decoupled

Checked upstream. Latest stable is v0.27.1 (Aug 11) and it does NOT contain
#51113 -- the v0.27.0..v0.27.1 compare is only "DSpark Markov heads" plus three
CI commits. The #51113 cherry-pick (khluu, Aug 9, "v0.27.0 cherry picks"
milestone) is staged on the release-0.27 branch but no v0.27.2 stable has been
cut; only v0.27.2rc1 / the pinned nightly carries the fix. So the standing
follow-up (move gen off the nightly) still waits on a v0.27.2 stable cut.

Key decoupling: #51113 fixes the Qwen3.8 MTP + prefix-caching accuracy drop
(#43559). It is irrelevant to Gemma-4 seats, which have no MTP head. So the
meromero/gemma4 CoT test does NOT need the nightly and does NOT need #51113 -- it
can run on the latest stable v0.27.1, which is newer than the seat's current
v0.24.0 and where per-request chat_template_kwargs is expected to work.

persistent-memory.md

@@ -222,7 +222,7 @@ _As of 2026-08-21 00:35 — **the Heretic-300 session, and its reversal** (see t
 
 - **⚪ LFM2.5-2.6B RETIRED PERMANENTLY 2026-08-20 (operator directive).** `vllm-lfm25` (:8021, GPU1) removed: service deleted from `stacks/vllm/compose.yaml` + pushed live (backup `compose.yaml.bak-pre-lfm25-retire-20260820`), container `docker rm -f`'d, `lfm2.5-2.6b` alias deleted from the LiteLLM config (live + canonical; backup `config.yaml.bak-pre-lfm25-retire-20260820`, 28→27 models). **Freed 8,721 MiB on GPU1.** Justification: it was an EVAL-ONLY bake-off seat vs `granite-4.1-8b` (brokkr R-target 2026-08-10) that never received the operator ruling it was pending; the comparator was retired from the roster 2026-08-15; it was deliberately never in any default/fallback routing chain; and spend logs showed **0 calls in the 4-day window**. Weights remain in the shared HF cache — nothing deleted from disk. The held gateway restart fired at 23:46 alongside the `qwen3-reranker` removal (one ~84s blip covered both); `lfm2.5-2.6b`, `qwen3-reranker` and `granite-4.1-8b` all now 400 cleanly. `vllm-granite`'s dead service block was removed in the same pass.
 
-- **OPEN FOLLOW-UPS (parked):** ask Brokkr whether the duplicate `reranker-a3-bge-v2-m3` alias can go; move gen seat off pinned-nightly to stable once #51113 ships; Lobe one-time TTS UI pass; delete the 1.8GB litellm dump; `harden-esh-docker-vm` (park id 28, PROMOTED — Tier-1 done, `/mnt/books` stays hard w/ watchdog); chatterbox-fast build-context divergence; #363 research-wing ingest (no deadline); optionally attach our MTP reproducer to vllm#47087 (needs a GitHub identity — operator's call).
+- **OPEN FOLLOW-UPS (parked):** ask Brokkr whether the duplicate `reranker-a3-bge-v2-m3` alias can go; move gen seat off pinned-nightly to stable once #51113 ships **[STATUS 2026-08-21: NOT YET. Latest stable = v0.27.1 (Aug 11), confirmed to LACK #51113 — the v0.27.0..v0.27.1 compare is just DSpark Markov heads + 3 CI commits. The #51113 cherry-pick (khluu, Aug 9, 'v0.27.0 cherry picks' milestone #34) is staged on the release-0.27 branch but no v0.27.2 STABLE has been cut — only v0.27.2rc1/the pinned nightly carries it. Watch for v0.27.2 stable; that's the clean gen pin. ★ #51113 is Qwen3.8-MTP+prefix-cache-SPECIFIC (closes #43559); it is IRRELEVANT to Gemma-4 seats (no MTP), so the meromero/gemma4 CoT test can use latest STABLE v0.27.1, decoupled from this wait]**; Lobe one-time TTS UI pass; delete the 1.8GB litellm dump; `harden-esh-docker-vm` (park id 28, PROMOTED — Tier-1 done, `/mnt/books` stays hard w/ watchdog); chatterbox-fast build-context divergence; #363 research-wing ingest (no deadline); optionally attach our MTP reproducer to vllm#47087 (needs a GitHub identity — operator's call).
 
 - **althing monitor** ARMED (handle `infra-ops`). ⚠️ Re-arm ONLY after a real FIRE (rc0), never after a plain operator turn (bounces rc3); spawn `althing-wake-listener` as its OWN `run_in_background` task, never chained with `&` (orphans it — hit this twice 2026-08-17, `stop-monitor` reclaims).