Text-embedding path: first live validation

# Text-embedding path: first live validation Repos: **lounge** (turn on) + **conductor-client** (consumer) + **legit-embedding** (worker). Was Solo todo 664. **Independent** — runnable on the CURRENT worker; also becomes a #205 smoke. ## Why The text wire-format + XADD pipelining shipped (8f040c6) but the text path has **NEVER run live**. Cheapest way to prove the text pipeline end-to-end (single-app, no routing needed) — and it's the natural first second-model exercise for Track B. ## Do 1. Ensure the text consumer daemon is up (lounge `conductor:consume-text-results` / package `conductor:consume-results text`). 2. Queue a small text backfill batch (lounge text backfill command). 3. Confirm: completed text `Embedding` rows land with the RIGHT dimensions (verify the emitted text model + dims — the registry `EmbeddingModel` row must match what the worker emits; plan §4.5) and base64_fp32 decodes (`ResultMessage::vector` / `Embedding` storage). 4. Confirm telemetry rows for the text workers. ## Notes Runs on the existing (A) worker (single-app global stream — no `reply_to` needed). Later, re-run against the #205 single-process worker as its text smoke. **Dims gotcha:** the consumer write-side only validates `len % 4 == 0`, not `len == dim*4` — a wrong-dimension vector passes write and only blows up at read (`Embedding::getVector`). ## Status Draft (idea). Independent.