Limbo Rider

{
  "game": {
    "name": "Limbo Rider",
    "catalog_name": "Limbo Rider",
    "wordmark_in_game": "LIMBO Rider (matches catalog name; no shortened splash form found on any captured frame)",
    "provider": "Turbo Games",
    "game_kind": "instant_win (limbo-type crash variant: player sets a target multiplier and a bet, presses one button, and a random result multiplier is revealed instantly; there is no cash-out control and no ascending in-round animation to watch and react to)",
    "theme": "1980s synthwave / retrowave night-drive theme: a stylised sports car viewed from directly behind, parked on a glowing neon grid 'road' in front of a giant gradient sun and a silhouette mountain range, evoking an arcade racing / VHS-cover aesthetic. No characters, no narrative, no traditional slot symbols.",
    "art_style": "Flat 2D vector digital illustration in a synthwave/retrowave style: flat gradient fills for the sky and sun disc, combined with thin glowing neon wireframe line art for the grid floor and mountain silhouettes; the car body uses glossy chrome-style gradient highlights (streaks of light blue/white over magenta/purple panels) rather than photorealistic shading. High-contrast neon palette (magenta/pink and cyan/blue) glowing against near-black or deep-purple backgrounds. UI chrome is flat rounded rectangles with thin neon-pink outlines and soft outer glow, no skeuomorphic textures. Camera angle is a fixed, low, straight-on rear view of the car (no top-down or side perspective). Overall mood is a stylised, energetic, slightly futuristic arcade-retro night scene rather than a cartoon-casual or photorealistic look; no in-game characters are depicted.",
    "documentation_purpose": "Exhaustive accessibility documentation (blind/low-vision screen-reader users, deaf/hard-of-hearing, color-blind users of all types, motor-impaired users) built from 11 desktop screenshots (1280x800) captured by the slot-capturer agent plus TL gate-1 probes, cross-checked against manifest.json notes (balance deltas, DOM text, control coordinates).",
    "method_notes": "Numbers taken verbatim from on-screen text and from manifest.json fields that were themselves derived from live balance deltas / DOM reads (win_chance_vs_rtp, win_ceiling_scope, bet_limits_verified). Nothing in this document was invented; items that remained unclear are listed in 'unreadable_or_uncertain'.",
    "language": "English"
  },

  "color_palette": {
    "page_background_outside_panel": "Deep indigo/navy-purple at the top of the page, blending into brighter magenta/pink glows in the bottom-left and bottom-right corners of the browser viewport.",
    "game_panel_frame": "The whole game widget (display + bet controls + bet feed) sits inside a thin bright pink/magenta rounded-rectangle outline on a near-black panel background.",
    "display_scene": "Near-black night sky at the top fading into a large semicircular sun disc that is a soft gradient from violet/purple at the rim to bright magenta/pink at the center. Below the sun, a neon wireframe grid in pink/magenta and cyan/blue lines represents a horizon and mountains, all silhouetted in dark navy/black.",
    "car": "Two-tone retro sports car body: magenta/purple panels on the left, light cyan/blue panels and roof on the right, with diagonal white-blue chrome highlight streaks across the rear glass and hood. Full-width rear light bar glowing red/orange in horizontal striped segments. Small rectangular license plate: yellow background, black text 'TURBO'. Dual chrome exhaust pipes flank the plate. The car floats on a soft pink glow/halo above the grid floor.",
    "result_readout_digits": "Large digital/LCD-style 7-segment font centered on the sun. Colour encodes the outcome: off-white/pale lavender for the idle default '1.00X', bright lime/lemon green for a WIN result (e.g. '2.10X'), coral/salmon red-orange for a LOSS result (e.g. '1.63X'). The same two colours repeat in a small mini history readout in the bottom-right corner of the display, stacking the last results (most recent frames show a green line above a red line).",
    "top_bar": "Dark navy-purple strip. Circular back button and the two circular icon buttons (sound, settings) are dark circles with a thin pink outline and white glyphs. The 'Balance:' value box has a thin pink/magenta outline on a dark navy fill.",
    "logo_wordmark": "'LIMBO' in a bold italic 3D chrome font shaded blue/cyan with white highlight edges; 'Rider' immediately after it in a pink/magenta cursive-script font.",
    "bet_controls": "Input fields ('Bet Amount', 'Multiplier') are dark navy rounded boxes with thin pink/magenta borders and white text; small labels above them in muted lavender-grey. The 'min' / '-' / '+' / 'max' buttons are light lavender-blue rounded rectangles with dark navy text. The stepper next to 'Multiplier' is a pink/magenta rounded box holding white '-' and '+' glyphs.",
    "place_bet_button": "The single largest control: a bright lime/yellow-green gradient rounded rectangle with a cut (parallelogram) right edge, bold dark navy/indigo text 'Place bet'.",
    "bet_feed": "Tab row: the active tab ('All Bets') is filled with a pink-to-magenta gradient with white text; inactive tabs ('Top bets', 'My bets') are dark translucent boxes with muted grey text. Table header text is light lavender; row text is white/light-grey on a dark translucent purple background.",
    "modals_settings_rules_limits": "Dark charcoal-purple rounded panels floating over the dimmed game scene, with white/light-grey headings and body text; section dividers are thin dark-grey hairlines; chevron icons (up = expanded, down = collapsed) in muted grey.",
    "demo_mode_badge": "A separate small black vertical rectangular tab fixed to the right edge of the browser viewport (outside the pink game-panel border), with white vertical text 'DEMO MODE' above a small red circular icon (a red disc with a diagonal white bar, no-entry style). This is the PROVIDER's own demo-wrapper chrome around the whole page, not a watermark added by our capture tooling."
  },

  "layout": {
    "top_bar": {
      "position": "Full-width strip above the game panel.",
      "left": "Circular back/menu button ('‹' left-chevron, white on a dark circle with pink outline) at the far left, next to the game wordmark logo 'LIMBO Rider'.",
      "right": "'Balance:' label followed by a bordered value field showing the numeric balance (e.g. '$1000', '$1001'), then two circular icon buttons: a speaker/sound toggle and a gear/settings button, in that order left to right."
    },
    "display_area": {
      "position": "Large rectangular area occupying roughly the top two-thirds of the game panel, pink-bordered.",
      "content": "The synthwave sun/car/grid scene described in color_palette, with the current or last result multiplier printed centered in large digits over the sun, and a small 2-line result history stacked in the bottom-right corner of this area."
    },
    "bet_panel": {
      "position": "A horizontal row directly below the display area, still inside the pink panel border.",
      "left_group": "'Bet Amount' labelled field (with a small 'ⓘ' info glyph next to the label) showing the stake value, e.g. '$1.0'; directly below it a row of four buttons: 'min', '-', '+', 'max'.",
      "middle_group": "'Multiplier' labelled field showing the target multiplier, e.g. 'x2' or 'x1000'; a combined '-'/'+' stepper sits to its immediate right; below the field, the text 'Win Chance: NN.NN%' updates live as the target multiplier changes.",
      "right_group": "One large 'Place bet' button, the primary and only round-starting action, occupying the full height of the bet panel on the right edge."
    },
    "bet_feed": {
      "position": "Below the game panel, a separate section with its own thin border.",
      "tabs": "'All Bets' (selected by default), 'Top bets', 'My bets'.",
      "table": "Columns 'Game', 'Player', 'Time', 'Bet Amount', 'Multiplier', 'Payout'. Rows show live wagers from MULTIPLE games on the Turbo Games platform (observed on captured frames: Mines, Towers, Turbo Plinko, Dice Twice, Fruit Towers, Turbo Mines, and occasionally Limbo Rider itself), with player nicknames, timestamps and payouts that differ between every captured frame. This is a shared platform-wide live-bet ticker, not a history specific to Limbo Rider, and its row content is not a stable property of this game — not enumerated further."
    }
  },

  "controls": [
    {"name": "Back / menu button", "position": "top-left, circular", "state": "always enabled", "function": "Navigates back (out of the game), per its left-chevron icon; exact destination not tested (would leave the demo)."},
    {"name": "Sound toggle", "position": "top-right, circular, left of the gear icon", "icon": "speaker", "function": "Toggles game sound; state not distinguishable from the icon alone in the captured frames (no visible muted/crossed-out variant was captured)."},
    {"name": "Settings (gear) button", "position": "top-right, circular, rightmost", "function": "Opens the Settings overlay (nickname field, Limits button, Rules button, two volume sliders)."},
    {"name": "Bet Amount field", "position": "bet panel, left", "function": "Numeric stake entry; editable text field.", "default": "$1.0"},
    {"name": "min / - / + / max buttons", "position": "row of four directly under Bet Amount", "function": "'min' sets the field to the printed minimum bet ($0.1); 'max' sets it to the printed maximum bet ($100); '-'/'+' step the value. Verified live: clicking 'min' set the field to $0.1 and clicking 'max' set it to $100, matching the Limits dialog exactly (manifest.bet_limits_verified)."},
    {"name": "Multiplier field", "position": "bet panel, middle", "function": "Numeric target-multiplier entry, range 1.01-1000 per the Rules booklet.", "default": "x2", "stepper": "'-'/'+' buttons to its right"},
    {"name": "Place bet button", "position": "bet panel, right, largest control on screen", "function": "Single action button: submits Bet Amount + Multiplier and instantly resolves the round. No separate 'spin' or 'start' step, no cash-out step."},
    {"name": "All Bets / Top bets / My bets tabs", "position": "top of the bet-feed section, below the game panel", "function": "Switch the live bet-feed table between platform-wide bets, top bets, and the current player's own bets."}
  ],

  "game_mechanics": {
    "flow": "1) Player sets 'Bet Amount' (default $1.0) and a target 'Multiplier' (default x2, range 1.01 to 1000). 2) Player presses 'Place bet'. 3) A random result multiplier is generated and displayed instantly in large digits over the sun (e.g. '2.10X' or '1.63X'); there is no rising/ascending animation to watch and no manual cash-out — the round resolves in a single step.",
    "win_rule": "If the random result is GREATER than the player's target multiplier, the player wins; payout = Bet Amount x target Multiplier. If the result is LESS THAN OR EQUAL to the target, the entire bet is lost.",
    "win_rule_source": "rules_p1.png, 'How to Play?' section: 'Set target multiplier you want' / 'Press \"Place Bet\" to generate a random number instantly' / 'If your target multiplier is less than the result, you win and multiply your bet.'",
    "win_rule_verified_by_balance": "Bet $1, target x2, result 2.10X (greater than target, printed GREEN): balance went from $1000 to $1001, i.e. a $2 payout = $1 stake x x2 target (win_screen.png). Bet $1, target x2, result 1.63X (less than target, printed RED): balance stayed at $1000, i.e. the $1 stake was lost with no payout (base_game_loss.png).",
    "result_color_coding": "Result digits and the small history readout are GREEN for a win and RED/coral for a loss. This is the ONLY place outcome is colour-coded; see accessibility notes for whether it is backed by non-colour cues.",
    "win_chance_field": "A 'Win Chance: NN.NN%' text below the Multiplier field updates live and is inversely tied to the chosen target multiplier (higher target = lower quoted chance)."
  },

  "technical_summary": {
    "rtp_percent": 95.0,
    "rtp_is_range": false,
    "rtp_source": "rules_p2.png, Rules booklet -> 'Game Details' -> 'RTP' subsection: 'Game relies on a coefficient called \"RTP\" (Return to Player) which is the statistical average of payouts over billions of rounds. Limbo Rider has RTP 95.0%.' This is a single flat printed number, not a range (unusual for this provider, whose other titles more often print a range).",
    "rtp_vs_measured_win_chance_discrepancy": {
      "note": "The game ALSO prints a live 'Win Chance' percentage next to the target-multiplier field. This is a second printed source in the same build, and it does NOT arithmetically agree with the printed 95.0% RTP.",
      "samples_target_to_win_chance": {"1.5": "66.00%", "2": "49.50%", "5": "19.80%", "10": "9.90%", "100": "0.99%", "1000": "0.10%"},
      "samples_source": "TL gate-1, live session, port 8822 (manifest.json field win_chance_vs_rtp)",
      "arithmetic": "target x win_chance = 0.9900 for every sampled target except x1000, where the printed value is rounded to two decimals (0.10% instead of 0.099%) and multiplies out to 1.0000 -- a display-rounding artefact, not a different underlying constant.",
      "implication": "Given the verified payout rule (payout = bet x target on a win), an expected value derived from the printed Win Chance field would be 99%, not 95.0%.",
      "verdict": "This document reports RTP as the PRINTED field: 95.0% (source rules_p2.png). The 99% figure is OUR arithmetic derivation from a different printed field (Win Chance) and must not be reported as a second official RTP. Recorded here explicitly so a future pass does not 're-discover' 99% as a new finding -- the two printed sources of this one build simply disagree, and only the RTP-labelled figure (95.0%) is the game's own claim about itself."
    },
    "target_multiplier_range": "1.01 to 1000, set via the 'Multiplier' field (min/step controls -/+ ; no dedicated min/max buttons for this field, unlike Bet Amount).",
    "target_multiplier_max_source": "rules_p2.png: 'Set the desirable multiplier value from 1.01 to 1000.'",
    "bet_min": "$0.1",
    "bet_max": "$100",
    "max_profit": "$10000",
    "limits_source": "limits.png (Limits dialog, opened from Settings): 'Min bet $0.1' / 'Max bet $100' / 'Max Profit $10000'. Independently confirmed live: clicking the 'min' button set Bet Amount to $0.1 and the 'max' button set it to $100 (manifest.bet_limits_verified) -- two independent channels agree.",
    "max_win_ceiling_scope": {
      "storefront_claim": "x1000 (matches the printed target-multiplier ceiling in the Rules booklet).",
      "measured": "The interface ACCEPTS a $100 bet together with an x1000 target with no error or clamp (fields stayed at $100 / x1000, Win Chance showed 0.10%), tested with three pairs: ($100, x1000), ($100, x100), ($1, x1000). This shows the $10000 Max Profit cap is enforced at PAYOUT time, not at input time.",
      "conclusion": "x1000 is only reachable as an actually payable win at a bet of $10 or less ($10 x 1000 = $10000 = the cap). At higher bets the effective multiplier ceiling is 10000 / bet. The storefront/booklet 'x1000' figure is correct as a MULTIPLIER ceiling but does not by itself describe the money ceiling; the two figures describe different things and do not contradict each other.",
      "source": "manifest.json field win_ceiling_scope, measured live by TL on gate-1."
    },
    "currency_symbol": "$ (dollar sign) on every printed money value observed (Balance, Bet Amount, limits, payouts); this is the demo currency display, not necessarily the real-money currency of a live deployment.",
    "demo_default_balance": "$1000",
    "demo_default_bet": "$1.0",
    "game_version": "\"1.0.1\"",
    "rng_version": "\"2.0.0\"",
    "version_source": "rules_p4.png, Rules booklet -> 'Version' section. No second place in this build shows a version number (checked: the Settings overlay only contains Nickname / Limits / Rules / two volume sliders) -- this is a single, uncorroborated source and is reported as such.",
    "cash_out": "None. The round resolves in one instantaneous step after 'Place bet'; there is no ascending multiplier animation and no cash-out button to click before a 'crash'.",
    "keyboard": "Not tested / not documented on the captured frames.",
    "reels_or_grid": "None -- this is not a reel-based or grid-based game; there are no symbols and no paytable."
  },

  "features_present": {
    "free_spins": false,
    "bonus_buy": false,
    "autoplay": false,
    "provably_fair_dialog": false,
    "win_screen": true,
    "cash_out": false,
    "notes": "Confirmed absent by two independent channels each (per manifest.not_captured): (1) full document.body.innerText across the game plus every opened dialog (Settings/Rules/Limits) contains no occurrence of 'autoplay'/'auto bet'/'auto-bet', no occurrence of 'fair'/'seed'/'hash', and no occurrence of 'buy'/'bonus'; (2) an enumerated control map (scene_probe.py DOM channel, 90 controls total) contains only Place bet, the Bet Amount min/-/+/max buttons, the Multiplier -/+ stepper, and the Settings/Rules/Limits entry points -- no third action control (autoplay panel, provably-fair icon, or a buy button) exists anywhere in the DOM.",
    "provably_fair_storefront_caveat": "Turbo Games' storefront marketing describes its games generally as provably fair (cryptographic seed verification), but this specific demo BUILD has no such dialog anywhere in its DOM. This is recorded as 'not found in this demo interface', not as proof the mechanism doesn't exist server-side in a live deployment."
  },

  "screens": {
    "preview": {
      "type": "preview",
      "content": "Full-black loading/splash frame showing only the Turbo Games PROVIDER wordmark, centered: a red circular badge containing a white 'X' shape (like a stylised no-entry/target cross) to the left of the white text 'TURBO' stacked above 'GAMES' in a bold blockish sans font. No game-specific art or the 'Limbo Rider' name appears on this frame -- it is the provider's own loading branding, not the game's logo.",
      "purpose": "Shown briefly during load, before the base game UI appears."
    },
    "base_game": {
      "type": "base_game",
      "content": "Idle/default state: display shows '1.00X' in off-white digits over the sun, Balance '$1000', Bet Amount '$1.0', Multiplier 'x2', Win Chance '49.50%'. Full description of layout/colors is in the 'layout' and 'color_palette' sections above.",
      "color_blind_notes": "The idle readout uses a neutral off-white colour (no win/loss colour coding applies until a bet is placed)."
    },
    "base_game_loss": {
      "type": "base_game",
      "content": "Result frame after an unsuccessful round: target x2, result '1.63X' printed in coral/red, centered over the sun. Balance unchanged at $1000 (bet of $1 fully lost). A small mini-history readout appears bottom-right of the display for the first time, stacking two entries: '2.10X' (green, from the previous win_screen round) above '1.63X' (red, this round).",
      "color_blind_notes": "Loss is signalled by the printed word-equivalent state (no payout change / balance unchanged) as well as by red digits; a screen-reader relying on the balance value change would correctly detect 'no win' without needing colour."
    },
    "base_game_max_target": {
      "type": "base_game",
      "page": 2,
      "content": "TL gate-1 probe frame: Bet Amount field shows '$1' (max button was pressed just before, field briefly rendered without the trailing '.0'), Multiplier field pushed to its ceiling 'x1000', Win Chance reads '0.10%'. The display still shows the previous round's red '1.63X' loss result (no new bet was placed on this frame) and the same two-line green/red mini-history in the corner.",
      "purpose": "Used to verify the target-multiplier ceiling and its interaction with Max Profit (see technical_summary.max_win_ceiling_scope)."
    },
    "win_screen": {
      "type": "win_screen",
      "content": "Result frame after a successful round: target x2, result '2.10X' printed in bright lime/green, centered over the sun; the same value repeats small at the bottom-right corner of the display in the same green. Balance field increased from the pre-bet '$1000' to '$1001' (visible in the top-right Balance box), reflecting a $2 payout on a $1 stake at an x2 target.",
      "color_blind_notes": "Win is doubly signalled: green digits AND a visible balance increase in the top bar -- the balance-text channel does not depend on colour perception."
    },
    "settings": {
      "type": "settings",
      "title": "Settings",
      "position": "Dark rounded panel anchored to the top-right of the game panel, overlapping the right portion of the display area; 'X' close button at its top-right corner.",
      "content": "A 'Nickname' label above an editable text field showing a demo player nickname (captured value: 'Objective Perch' -- this reads as an auto-generated placeholder handle, not a fixed game element, so it should not be treated as stable content). Two full-width menu buttons below: 'Limits' (target/bullseye icon) and 'Rules' (document/page icon), each opening its own dialog. Two horizontal volume sliders below that: one with a speaker icon (game sound effects) and one with a musical-note icon (game music), both shown with their round handle positioned near the right/full end of the track in the captured frame.",
      "color_blind_notes": "Slider fill (teal/green) vs track (dark) gives a colour cue for volume level, but the HANDLE POSITION along the track is the primary, colour-independent cue for how loud each channel is set."
    },
    "limits": {
      "type": "info",
      "title": "Limits",
      "position": "Centered modal dialog over the dimmed game panel; 'X' close button at its top-right.",
      "content": "Three stacked label/value rows: 'Min bet' -> '$0.1'; 'Max bet' -> '$100'; 'Max Profit' -> '$10000'."
    },
    "rules": {
      "type": "rules",
      "modal_title": "Rules",
      "intro_line": "'Limbo Rider is a fast-paced crash game with retrowave vibes' followed by a small decorative pixel-style glyph (appearance uncertain at this resolution -- looks like a small 8-bit sparkle/joystick icon; not confidently identifiable, listed in unreadable_or_uncertain).",
      "structure": "An accordion of five collapsible sections, each with a chevron indicator (pointing up when expanded, down when collapsed): 'How to Play?', 'Game Details', 'Settings', 'Bets History', 'Version'. All five section headers are visible on every rules_pN frame; exactly one section is expanded per captured frame.",
      "page_1_how_to_play": {
        "page": 1,
        "frame": "rules_p1.png",
        "expanded_section": "How to Play?",
        "content": "Bulleted list: 'Set target multiplier you want' / 'Press \"Place Bet\" to generate a random number instantly' / 'If your target multiplier is less than the result, you win and multiply your bet.'"
      },
      "page_2_game_details": {
        "page": 2,
        "frame": "rules_p2.png",
        "expanded_section": "Game Details",
        "content": "'Place Bet' subsection: 'Enter a valid amount in the field \"Amount\".' / 'Set the desirable multiplier value from 1.01 to 1000' / '\"Win chance\" depends on multiplier you've settled. The greater multiplier, the greater risk. Don't get too ambitious!' / 'Multiply your bet if the result is greater than your target multiplier.' / 'If the result is less than target multiplier, the bet will be lost.' Then an 'RTP' subsection: 'Game relies on a coefficient called \"RTP\" (Return to Player) which is the statistical average of payouts over billions of rounds. Limbo Rider has RTP 95.0%.'"
      },
      "page_3_settings_help": {
        "page": 3,
        "frame": "rules_p3.png",
        "expanded_section": "Settings",
        "content": "'Click the gear icon in the top right corner of the screen to open the settings menu. In Settings you can:' followed by a bulleted list: 'change the nickname' / 'view bet limits: Minimum bet, Maximum bet, Maximum Profit' / 'turn on/off sounds & animation'."
      },
      "page_4_version": {
        "page": 4,
        "frame": "rules_p4.png",
        "expanded_section": "Version",
        "content": "'Game version: \"1.0.1\"' and 'RNG version: \"2.0.0\"'."
      },
      "bets_history_section": {
        "expanded_on_any_captured_frame": false,
        "note": "The 'Bets History' accordion header is visible (collapsed) on every rules_pN frame, but no captured frame shows it expanded, and its body text was not relayed to this documentation pass. Per manifest.json ('sections' field) it was checked via a full DOM-text read alongside the other four sections, but the exact wording of its content is not available here -- listed honestly in unreadable_or_uncertain rather than guessed. It most likely documents the bottom-of-page 'All Bets / Top bets / My bets' live feed, but that is an inference, not a read fact."
      }
    }
  },

  "accessibility_observations": {
    "screen_reader": "Control layout is stable across screens: back button + logo at top-left, Balance + sound + settings at top-right, Bet Amount/min/-/+/max on the lower-left of the bet panel, Multiplier + stepper + Win Chance in the middle, the single large Place bet button on the right. The Rules content is a fully linear 5-item accordion (no pagination/scrolling needed within a section on the captured content).",
    "motor": "Only two inputs must be set before every round (Bet Amount, Multiplier), each with dedicated min/max shortcut buttons that remove the need for repeated stepping to reach an extreme value. A single 'Place bet' button (the largest control on screen) resolves the round -- no timed reaction step, no cash-out button to click under time pressure (unlike ascending crash games).",
    "color_blind": "PARTIAL RISK: the win/loss outcome is conveyed primarily by digit COLOUR (green vs red/coral) on the main result readout and its mini-history. This IS backed by a non-colour cue for the win case (the Balance number visibly increases, e.g. $1000 -> $1001) but a loss produces NO textual/numeric change other than the coloured digits themselves staying red and the balance staying the same -- a user who cannot distinguish the red digit colour and does not separately track 'did the balance change' has no other on-screen cue that a round was lost. This should be flagged for the accessibility backlog: a persistent 'WIN'/'LOSE' text label alongside the multiplier would remove the colour dependency entirely.",
    "deaf_hard_of_hearing": "No audio-only information observed. Sound and music are separately toggleable via sliders in Settings and are decorative; all game state (balance, bet, target, win chance, result) is conveyed in text/digits."
  },

  "unreadable_or_uncertain": [
    "Exact wording/content of the 'Bets History' accordion section in the Rules booklet -- header seen collapsed on every captured frame, never captured expanded; per manifest it was checked via DOM text but the text itself was not relayed to this documentation pass.",
    "The small decorative glyph next to the Rules intro sentence ('...retrowave vibes [glyph]') -- appearance not confidently identifiable at capture resolution (possibly an 8-bit sparkle or joystick icon); not described further to avoid guessing.",
    "Keyboard shortcuts (if any) for placing a bet -- not tested on the captured frames, unlike the SPACE/ENTER convention documented for some other titles.",
    "Sound-toggle button's visual 'muted' state -- only the default (unmuted-looking) icon was captured; no frame shows it after being toggled off.",
    "Whether the live bet-feed's per-row Multiplier/Payout values carry any colour coding of their own (win vs loss) -- text was legible via OCR but colour differences among rows were not confidently distinguishable at the captured resolution; not described to avoid guessing."
  ],

  "anomalies_and_cross_checks": [
    "The header widget (back button + two circular icon buttons at x~1026/1068) does not exactly match either variant described in the provider playbook's header table; both a pixel-channel check (frame inspection) and a DOM-channel check (scene_probe.py) agree on the same layout, so this is treated as a genuine third header variant used by this build, not a capture error.",
    "Printed RTP (95.0%, flat number) and the printed Win Chance field disagree arithmetically once translated into an expected-value calculation (95.0% vs. an implied 99%) -- see technical_summary.rtp_vs_measured_win_chance_discrepancy for the full breakdown; only the RTP-labelled figure is reported as this game's RTP.",
    "Storefront max-win claim (x1000) and the printed Max Profit cap ($10000) do not contradict each other once their different scopes are recognised -- see technical_summary.max_win_ceiling_scope."
  ]
}