The server performance block reported a movement_warnings count with no way to attribute it. Measured: the counter went 0 -> 107 in under a minute and then stopped, so it is a burst from one event, not the server degrading. A count cannot say whether that is a player joining, a bot reconnecting, or the whole simulation falling behind, and the vanilla lines that carry the answer were not published anywhere -- the HF log stream served a frozen window and /voyager/status strips its log tail on purpose.
performance.movement_warning_samples now carries up to five of those lines, truncated to 200 characters each, so the entity is visible. They are deduplicated on the message rather than the raw line: every entry in a burst has its own timestamp, so comparing raw lines would fill the payload with five copies of one problem instead of showing five distinct ones. Verified directly: 40 warnings from one bot collapse to one sample, and adding a second bot's warning produces two.
This is diagnos…
Add Gemini CLI Flash Lite companion bot and server stability telemetry
