- Shipped
- September 9, 2026 at 2:26 AM UTC
- Author
- Kamo
- Commit
- 09e39ae
The client half of showing a hand nobody made you show, plus the mount point for the turn-clock audio that landed dead in the previous commit. SHOWING OUTRANKS EVERYTHING ELSE THE STANDBY BAR OFFERS. It is the only thing there with a clock on it — a few seconds between hands and then it is gone — while sitting down, buying back in and topping up are all still there next hand. So when `you.canShow` is true it IS the bar, and the rest waits. The server decides whether the button exists, not the client: there is a window to do it in, the hand was yours, and nobody has seen the cards already. A control that appears and then refuses is worse than one that never appeared. The reveal needed no new machinery. A seat whose cards arrive on a completed hand already flips rather than appearing, because the two cards at a seat are two stable elements whose `faceDown` changes — measured in a browser: before the show, an observer sees the winner's seat with nothing face up; 120ms after, two cards face up with the reveal animation on both. NOT ALL OF THIS FILE IS MINE. It also carries the concurrent chip session's invite work — `applyTable`, the `keepInvitable` wiring, and the two readers that use the held list — because `git commit <pathspec>` commits the file rather than your diff of it, and three sessions want this one file today. They left it uncommitted on purpose rather than sweep up my half, which is the courtesy I failed to return earlier: their server-side `invitable` change went out inside my mediaservice 21ba0f2 under a message about showing hands. Recorded here so the history is legible to whoever bisects it.