- Shipped
- September 8, 2026 at 3:15 PM UTC
- Author
- Kamo
- Commit
- 3e14b71
The bar is fixed chrome and already crowded — greeting, branches, availability, the compliance clock, the bell, chat, language, account — and a balance is not something anybody acts on from there. It now sits at the top of the Games menu, one click in, directly above the games it is spent on: less bar, and the wallet and the thing it buys in the same place. `NavToolButton` gains a `header` slot, rendered above the sections in all three variants. It is a node rather than a section because a section's items are themed by that component and a header is not — which is the constraint that shapes the panel: it renders in a LIGHT popover from the top bar AND inside the DARK expanded rail, so it carries its own colours instead of inheriting either. Verified in a browser on both grounds; it also reads as a distinct card rather than as the menu's first row, which is right for a state among a list of destinations. The panel shows the balance and the last four movements, so the separate popover the chip used to open is gone entirely — one less layer, and a popover inside a popover was never going to be good. It also stops asking on page load. The popover renders its children only while it is open, so the request happens when a member opens the menu rather than on every page for a number nobody is looking at. Dates use `dayAwareTime`, not `dateTime`: the long form renders "September 8, 2026 at 7:03 AM", and a browser showed that crowding the amount off a 232px row. A statement is a feed of things arriving over time, which is what dayAwareTime is for — today's buy-in is a time, last week's claw machine is a date. `useGamesEnabled` is removed with the chip that needed it; GamesButton gates the panel on the sections it already has.