targets: lemer complete — all 6 quant slots verified e2e

Added gguf Q8_0 and gguf BF16 target rows. Lemer now has six fully
paired quant variants across both inference backends, each validated
end-to-end through eval.py with its own type-and-quant-scoped canon:

mlx Q4 → LetheanNetwork/lemer-mlx vs lthn/lemer-mlx
mlx 8bit → LetheanNetwork/lemer-mlx-8bit vs lthn/lemer-mlx-8bit
mlx BF16 → LetheanNetwork/lemer-mlx-bf16 vs lthn/lemer-mlx-bf16
gguf Q4_K_M → hf.co/LetheanNetwork/lemer:Q4_K_M vs hf.co/lthn/lemer:Q4_K_M
gguf Q8_0 → hf.co/LetheanNetwork/lemer:Q8_0 vs hf.co/lthn/lemer:Q8_0
gguf BF16 → hf.co/LetheanNetwork/lemer:BF16 vs hf.co/lthn/lemer:BF16

Pre-requisite: generated Q8_0 and BF16 gguf for LetheanNetwork/lemer
earlier this session via llama.cpp convert_hf_to_gguf.py + llama-quantize,
and fixed pipeline_tag on that repo (was any-to-any, HF's llama.cpp
manifest endpoint requires image-text-to-text or text-generation).

Lemer e2e done. The family rollout for lemma/lemmy/lemrd is now a
mechanical replication of this pattern — same conversion/upload script
per model, same targets.yaml expansion, same smoke process.

Co-Authored-By: Virgil <virgil@lethean.io>

targets.yaml

@@ -23,9 +23,9 @@ defaults:
 
 targets:
 
-  # Lemer — Gemma 4 E2B. Three mlx quants + gguf Q4_K_M live and paired
-  # end-to-end. Q8_0 / BF16 gguf will be added once LetheanNetwork/lemer
-  # has the matching base quants (TODO: llama-quantize + upload).
+  # Lemer — Gemma 4 E2B. Six fully paired quant slots:
+  #   mlx  Q4 / 8bit / BF16
+  #   gguf Q4_K_M / Q8_0 / BF16
 
   - name: lemer
     type: mlx
@@ -51,6 +51,18 @@ targets:
     base: hf.co/LetheanNetwork/lemer:Q4_K_M
     this: hf.co/lthn/lemer:Q4_K_M
 
+  - name: lemer
+    type: gguf
+    quant: Q8_0
+    base: hf.co/LetheanNetwork/lemer:Q8_0
+    this: hf.co/lthn/lemer:Q8_0
+
+  - name: lemer
+    type: gguf
+    quant: BF16
+    base: hf.co/LetheanNetwork/lemer:BF16
+    this: hf.co/lthn/lemer:BF16
+
   # Lemma / Lemmy / Lemrd — pending the same treatment as lemer.
   # (LetheanNetwork bases in matching formats, naming alignment, etc.)