- Shipped
- August 26, 2026 at 2:48 AM UTC
- Author
- kamo
- Commit
- 31503e8
Its own layer inside .hex-scale: that element already animates transform for the hover grow, and two animations on one element do not compose — the second replaces the first, so a thump mid-hover would drop the hover scale. Keyed rather than class-toggled, or two messages in quick succession thump once. Gated the scale-pulse on a `.thumped` class present only after a real thump: the key change makes `.hex-thump` a fresh DOM node both on a real thump AND on first mount, and CSS cannot tell those two apart from the key alone, so the brief's literal wiring would have played the pulse on every head a restored session spawns — the "screenful of pulsing hexagons" shouldThump exists to prevent.