The 3 beellama composes still defaulting to the old self-hosted
multiarch-b9459-07ac3ce (the 2 singles + the gemma-q4ks dual) and the two
single-card registry status_notes predate the #296 BEELLAMA_IMAGE
centralization. b9459 is the pre-v0.3.0 build — the gemma-q4ks dual even
documented that its default "STILL has the [multi-GPU DFlash] bug". A direct
`docker compose up` (no launcher) would pull that stale image.
- image: defaults → ghcr.io/noonghunna/beellama-cpp:multiarch-v0.3.0-efe856397
(matches the q8kxl duals; broad sm_86/89/120 compat for direct-compose).
- Caveats / Pull-the-image / status_note prose → launchers inject Anbeeld's
official server-cuda-v0.3.0 (sm_86/89); 5090/sm_120 uses the multiarch build.
- Drop the obsolete "no official Docker yet (v0.3.0 WIP)" claim; note the
v0.3.0 prose-DFlash acceptance regression (code unaffected) instead.
- Preserve the two historical b9459 references (the 2026-05-30 benchmark
attribution + the old-build prose-accept comparison).
Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
