- Shipped
- September 7, 2026 at 5:13 AM UTC
- Author
- Kamo
- Commit
- 426c709
`useMediaTopic` holds ONE message slot and overwrites it, so two frames arriving in the same tick are batched by React into a single render and only the last is ever seen. That is not a theoretical race here. Awarding a member who vaulted two levels publishes once per level, microseconds apart — precisely the case that produces two frames at once — and the card that gets dropped is the LOWER one, so the member is congratulated on III having never been told about II. It was recovered on their next page load, which could be hours. So a frame is now a payload AND a cue: it is merged for the instant path that the ordinary single unlock wants, and it also re-reads the pending queue from the table, which is the record. Anything the socket flattened arrives a round trip later instead of tomorrow. Still not polled — a timer would be a request per member per interval to discover, almost every time, that there is nothing to say. Also fixes the render test's framer-motion mock, which typechecked as `never` and dropped its animation props by accident rather than on purpose.