Now: Selecting SNOOZE inserts a second row and leaves the primary betting button partly clipped below the mobile app scroller.

Change to: Recover at least 48px in the mobile frame/form spacing, or place the existing yes/no choice within the Snooze control's allocated space, so the complete 44px action remains above the scroller's bottom in every market. Keep the current visual system and all betting controls.

Why: The brief requires the hamster frame and bet panel on the first mobile screen; changing the betting market should keep its main action visible.

Now: The shared help popover aligns its right edge to the trigger. The live-pass trigger sits near the left side, so most of its explanation opens outside the viewport and cannot be read.

Change to: Add a placement for the odometer help that aligns its left edge with the odometer, and clamp its width/position within the viewport. Keep the existing help text and close the gap without adding another panel.

Why: Visitors need the explanation that this is an approximate hardware counter and does not settle bets; essential betting context must remain readable at mobile widths.

Now: Above the mobile breakpoint, the chat launcher floats directly over page content. At 800px it covers the required “See jackpot” link in the compact strip and intercepts its central click target.

Change to: Extend the existing 64px mobile utility region to intermediate widths through 1100px, placing the chat button below the app scroller, and use right:18px at wider widths so the launcher sits in the outer gutter. Preserve the requested floating drawer control on every tab.

Why: The home brief explicitly requires a usable link to the Jackpot tab; a utility control must not hide or intercept another action.

Now: The Jackpot tab opens with “The jackpot jar.”, then repeats “The jackpot jar” inside its single card before showing the amount.

Change to: Delete the inner heading, move its existing rules-help control beside the betting-hour selector, and remove the heading’s margin so the jar and amount move up into that space. Keep the page heading and all rules, amounts and actions.

Why: The brief asks to remove duplicated or decorative content that does not help betting; naming the same jar twice adds no decision-making information.

Now: Ticket guesses in My bets use raw bigint interpolation, and Share.tsx:44/52 renders the raw line in the PNG and post text. A line shown as 2,100 on the betting panel becomes 2100 in these surfaces.

Change to: Reuse the existing number() formatter for displayed ticket guesses and share-card/post line values, preserving raw numeric values in inputs and contract arguments. Expected copy is “Ticket 2,100” and “Line: 2,100 passes”.

Why: The brief explicitly requires comma-grouped numbers throughout the site.