games: the clock beats the walk button, and the rack isn't betting

The trivia ladder handled a walk before it looked at the clock, so the
timeout only ever bit if the browser volunteered it. Sit on a question,
look it up, answer if you find it and walk if you don't, and you never
lose a ladder. The clock is now the first thing that happens to a move.

The house's chip rack was wired up as bet buttons on blackjack and
hangman: it's four spans with data-chip on them and nothing said the
handler only wanted the real ones. Clicking the house's money raised
your bet.

Hangman had two definitions of "a letter you'd guess" — unicode in the
engine, ASCII in the renderer — and a phrase with an accent in it would
have had no tile to fill and no key to fill it with. One definition now.

Plus: trivia's countdown no longer freezes at zero when the server turns
down a timeout report it was early for, questions whose wrong answer
decodes into the right one are dropped at the door, and hangman bets on
PeteFX's spot like every other table instead of its own copy of it.

internal/web/games_hangman.go

@@ -69,7 +69,7 @@ func viewHangman(g hangman.State) hangmanView {
 		Net:     g.Net(),
 	}
 	for i, r := range g.Runes {
-		c := cellView{Slot: isSlot(r)}
+		c := cellView{Slot: hangman.Guessable(r)}
 		if i < len(g.Shown) && g.Shown[i] {
 			c.Ch = string(r)
 		}
@@ -89,13 +89,6 @@ func viewHangman(g hangman.State) hangmanView {
 	return v
 }
 
-// isSlot mirrors the engine's isGuessable — a rune you'd guess gets a tile to
-// guess it into. Kept here rather than exported from the engine because it is a
-// question about drawing, and the engine doesn't draw.
-func isSlot(r rune) bool {
-	return (r >= 'a' && r <= 'z') || (r >= 'A' && r <= 'Z') || (r >= '0' && r <= '9')
-}
-
 // handleHangmanStart takes the bet and draws a phrase. Same order as a deal:
 // the chips are staked first, in the same statement that checks they exist, so
 // two starts fired at once cannot bet the same chip.