games: the casino moves out, and gets a clock of its own

The tables were living in the news app's shell: Pete's face in the header
and the footer, the channel nav, search, the reader, the weather canvas,
the PWA. A casino is not a news page with a felt on it.

So it gets its own layout. What carries over is the design language — the
four palette vars, Fredoka/Nunito, the fat rounded cards, the dropped
shadow. What doesn't is every control it has no use for. gamesPage stops
embedding the news pageData, which is what keeps the furniture from
drifting back one convenient field at a time.

It keeps a clock, but tells a different joke with it: Casinopolis by day,
Casino Night Zone from six, palette and felt and the sign over the door all
changing together. The rule lives in roomAt() for the first paint and again
in the browser, so a player abroad gets their own evening.

And the cards are cards now — corner indices in both corners, the bottom
one upside down as printed, pips on the three-by-seven grid every real deck
has used for four hundred years, courts as a letter with the suit over each
shoulder. Driven in a real browser, both rooms, dealt through to a payout.

internal/web/games_pages.go

@@ -2,6 +2,7 @@ package web
 
 import (
 	"net/http"
+	"time"
 
 	"pete/internal/games/blackjack"
 	"pete/internal/storage"
@@ -24,17 +25,47 @@ type gameTeaser struct {
 }
 
 var comingSoon = []gameTeaser{
-	{Name: "Hold'em", Emoji: "♠️", Blurb: "Six seats, and Pete's bots know how to play."},
+	{Name: "Hold'em", Emoji: "♠️", Blurb: "Six seats, and the house bots know how to play."},
 	{Name: "UNO", Emoji: "🎴", Blurb: "Normal rules, or no mercy."},
 	{Name: "Trivia", Emoji: "🧠", Blurb: "Faster answers score higher."},
-	{Name: "Hangman", Emoji: "🪢", Blurb: "Guess the phrase before Pete finishes drawing."},
+	{Name: "Hangman", Emoji: "🪢", Blurb: "Guess the phrase before the gallows finish."},
 }
 
 // betDenominations are the chips you build a bet out of.
 var betDenominations = []int64{5, 25, 100, 500}
 
+// The casino is not called Pete — the news app is Pete's, and this is somewhere
+// you go. It has two names, and which one is over the door depends on the hour:
+// the lights come on at six and the place turns into Casino Night Zone until
+// dawn. Same tables, different room.
+type room struct {
+	Slug string // drives the palette: html[data-room="…"]
+	Name string // what's on the sign
+}
+
+var (
+	roomDay   = room{Slug: "casinopolis", Name: "Casinopolis"}
+	roomNight = room{Slug: "casino-night", Name: "Casino Night Zone"}
+)
+
+// roomAt picks the room for an hour of the day. Daylight is 6am to 6pm; the rest
+// belongs to the neon. The browser re-runs this same rule against its own clock
+// (games_layout.html), so a player in another timezone sees their own evening —
+// this server-side pick only exists so the first paint isn't the wrong room.
+func roomAt(hour int) room {
+	if hour >= 6 && hour < 18 {
+		return roomDay
+	}
+	return roomNight
+}
+
+// gamesPage is deliberately *not* pageData. The casino shares Pete's design
+// language and nothing else — no channels, no weather, no sources, no push.
+// Giving it its own page struct is what stops the news app's furniture drifting
+// back in one convenient field at a time.
 type gamesPage struct {
-	pageData
+	Room          room
+	User          *SessionUser
 	Cap           int64
 	RakePct       int
 	Soon          []gameTeaser
@@ -58,10 +89,9 @@ func (s *Server) requirePlayer(w http.ResponseWriter, r *http.Request) bool {
 }
 
 func (s *Server) gamesPage(r *http.Request) gamesPage {
-	base := s.base(r)
-	base.NoIndex = true // the casino is for players, not for search engines
 	return gamesPage{
-		pageData:      base,
+		Room:          roomAt(time.Now().Hour()),
+		User:          s.auth.userFromRequest(r), // requirePlayer ran first, so this is non-nil
 		Cap:           storage.MaxChipsOnTable,
 		RakePct:       int(blackjack.DefaultRules().RakePct * 100),
 		Soon:          comingSoon,