Earlier public releases.

26 updates in this release

This release includes: Show active games without waiting for notifications; Keep final poker actions visible at showdown; Clarify sealed delivery latency diagnostics; Show poker replay actions and positions; Refresh hand history after showing cards; Bomb pot opening animation; and 20 more changes.

1. Show active games without waiting for notifications

   The activity page shows resume controls as soon as game lists arrive, while the notification badge updates independently.

   • Preserves fresh game lists and notification read-state synchronization.

2. Keep final poker actions visible at showdown

   Keep action labels visible through reveals and settlement so opponents’ final decisions remain readable.

   • Clear the previous action labels when the next hand starts.

3. Clarify sealed delivery latency diagnostics

   Slow deal alerts explain the ticket-to-card delivery interval and distinguish independent probes from delivery timing.

   • Preserves existing slow request thresholds and alerts.

4. Show poker replay actions and positions

   The hand timeline shows each player’s position, action and amount, with tap-to-seek replay.

   • Preserves raise-to totals and avoids guessing when position data is missing.

5. Refresh hand history after showing cards

   Fix history retaining hidden cards when a reveal arrives during a pending history request.

   • Preserve partial reveal positions and keep unshown cards hidden.

6. Bomb pot opening animation

   A bomb drops onto the felt with a gold ripple when a bomb pot begins, without delaying cards or actions.

   • Plays only for an actual bomb pot and respects reduced motion.

7. Separate Bot and human-only statistics and history

   Filter statistics and history by all games, Bot games or human-only games, with matching pagination and net totals for reconciliation.

   • Mixed games with bots count as Bot games; legacy records with unknown participants stay outside human-only results.

8. Recover stalled network connections

   Poker, Zha Jin Hua, Niu Niu and other rooms retry stalled foreground connections instead of waiting indefinitely.

   • Preserves a handshake grace period after background resume and avoids replaying stale actions

9. Restore your cards after refreshing the table

   Reconnect uses the server-confirmed seat to recover private cards when the saved seat is outdated.

   • Only your own private cards are restored; opponents remain hidden.

10. Read chat history without jumps

    Incoming messages preserve your position while reading chat history and continue to follow the conversation when you are at the bottom.

    • Keeps following new messages when the retained chat history reaches its limit

11. Prompt squid rejoin choices immediately

    Show squid entry choices immediately on mid-hand rejoin, synchronize departed seat state, and keep waiting players outside poker until admission.

    • Same-seat rejoin cannot inherit old marks or choices

12. Recover the table connection when returning to H5

    H5 checks its connection when the table returns to the foreground and restores stale connections so players can act and resume their seat.

    • Uses the same connection recovery as the app; seat and squid state remain server authoritative.

13. Squid admission governs poker participation

    Newcomers can join the current squid round from the next hand, or wait without cards or bets until the round ends and join automatically.

    • Waiting seats post no blinds and have no current-round penalties or rewards; joining preserves existing progress

14. Reveal your full leaderboard stats

    Opening the table leaderboard reveals your full row so buy-in, VPIP and win rate are not clipped.

    • Preserves profit ranking and manual scrolling during live updates

15. Optional timed blinds for poker rooms

    Choose optional blind levels of 5, 10, 15 or 20 minutes when creating a poker room. Disabled by default; timing starts with the first hand and changes apply between hands.

    • Fixed blinds remain the default, with durable blind clock recovery

16. Add a cross-platform poker guide for four friends

    The friend guide explains iPhone and Android play, four-seat private-table settings, account requirements and network verification limits, with matching public answers and AI summaries.

    • Steps for four-seat rooms, with bots and spectators turned off

17. Poker guide clarifies free play and mode choices

    The bilingual poker guide adds a citable overview, free and membership boundaries, and shortcuts to bot practice, friend rooms and public tables.

    • Visible answers, structured FAQ and AI summaries share the same source

18. Performance dashboard shows recent slow routes and player experience

    Recent server windows rank slow routes and show handler coverage and in-flight work. A separate player report shows completions, failures and timeouts. Trends separate request types and show pointer tooltips, with explicit missing, stale and restart states.

    • Poker, Zha Jin Hua and Niu Niu appear first
    • Recent server counters remain separate from 24-hour experience
    • Separate real actions from connection probes

19. Clarify lifetime stats on table avatars

    Label avatar statistics as lifetime history and direct players to table standings for the current table’s net.

    • Label avatar statistics as lifetime history and direct players to table standings for the current table’s net.

20. Fix avatar save completion

    Keep profile editing open until the avatar save finishes, prevent repeated actions, and ignore delayed responses from a previous account.

    • Keep profile editing open until the avatar save finishes, prevent repeated actions, and ignore delayed responses from a previous account.

21. Actionable slow-request phases

    Measure response-header and data-ready boundaries, identify evidence gaps and point to admin diagnostics.

    • Alerts distinguish measured slow phases from insufficient diagnostic evidence.

22. Mention players by tapping chat avatars

    Tap chat avatars to mention players. Hold or right-click for the secondary report and block menu.

    • Mention with one tap; moderation stays in a secondary menu.

23. Consistent table and chat avatars

    Resolve table and chat avatars from the same user identity and update both after profile edits.

    • Resolve table and chat avatars from the same user identity and update both after profile edits.

24. Chat player actions

    Tap a chat avatar to mention, report or block that player. The standalone safety entry has been removed from chat history.

    • Tap a chat avatar to mention, report or block that player. The standalone safety entry has been removed from chat history.

25. Live tables on the admin home

    Show ongoing tables, human players and release occupancy first on the admin home, with refresh and table details.

    • Check human-table release occupancy on the home page and open table details.

26. Distinguish background requests from interactive latency

    Successful background requests remain in telemetry without triggering interactive latency alerts. Action acknowledgement alerts explain the limits of server timing coverage. Thresholds for foreground, unknown-visibility and failed requests are unchanged.

    • Keep background success samples without treating browser suspension as interactive latency
    • Distinguish action acknowledgements from independent connection probes

14 updates in this release

This release includes: Hide spectator seat entry at full tables; Table chat for spectators; Latency alerts include timing evidence; Operations dashboard and grouped administration; Rebuy response and action confirmation timing fixes; Monetization diagnosis and action suggestions; and 8 more changes.

1. Hide spectator seat entry at full tables

   Hide Take a seat when no seats are empty and restore it when a vacancy appears.

   • Keep the spectator banner visible without an unavailable seat action

2. Table chat for spectators

   Spectators can chat with table players while gameplay actions remain restricted.

   • Spectator chat is available in the phone drawer and desktop rail.

3. Latency alerts include timing evidence

   Latency alerts show same-request server timing, time outside that span and investigation guidance, explicitly flagging missing or inconsistent timing without treating the residual as network latency.

   • Preserve slow-request thresholds and explicitly flag missing or inconsistent timing evidence

4. Operations dashboard and grouped administration

   Unify the dashboard around activity, growth, revenue and queues; group detail pages by purpose and remove device associations.

   • Keep detailed activity in a submenu
   • Open the relevant queue directly from the dashboard

5. Rebuy response and action confirmation timing fixes

   Handle top-ups, cancellations and busted-seat rebuys during bot thinking while preserving authorization, chip rules and bot deadlines.

   • Acknowledge rebuys without waiting through consecutive bot turns or changing live-hand chips
   • Recognize canonical zero-chip call acknowledgements and close unresolved timing when a hand ends

6. Monetization diagnosis and action suggestions

   Separate USD and SGD order receipts and show evidence-based hypotheses using exposure, checkout and entitlement signals.

   • Separate facts from hypotheses and include validation measures

7. Product insights becomes an owner dashboard

   Focus on new-player experience, actionable investigation leads and popular games, with evidence and AI export available on demand.

   • Clarify metric limits without treating missing settlements as churn or error records as people

8. Usage analytics leads with observations and priorities

   Usage analytics highlights page priorities, evidence limits and outcome links, with expandable detail and clear distinctions between clicks and success.

   • Start with page priorities and evidence limits; expand details when needed

9. Latency percentile verification corrected

   Browser acceptance waits for UI updates between percentile toggles to verify filled and dashed curves and hover values.

   • Filled and dashed legends identify client and server curves with matching percentile toggles and hover values

10. Quality page focuses on latency

    Keep latency charts and essential filters, removing diagnostic reports and explanatory copy while retaining stored quality data.

    • Filled and dashed legends identify client and server curves with matching percentile toggles and hover values

11. Simpler admin detail navigation

    Remove the redundant dashboard card from admin details while keeping the back navigation to the dashboard.

    • Fewer redundant links in admin details

12. HTTP latency alerts include phase evidence

    Correlate slow HTTP requests with status and body progress, separating read waits, wake scheduling, validation and enqueue phases while preserving the threshold.

    • Bounded diagnostics drop optional alerts under backpressure without blocking requests

13. Table-wide warning with two squid left

    Warn the whole table once per round at two remaining squid, without repeating at one or blocking actions.

    • Visible to every seat and spectators

14. Upgrade table interaction effects

    Table throwables gain coloured flight trails, double shockwaves and sparks while retaining item-specific impacts and reduced-motion support.

    • Flight echoes and coloured impact effects
    • Bounded effects cleaned up when the tab hides

Fix waiting-table standings and player history

Bought-in players appear in standings before the first hand; player cards show lifetime poker hands, VPIP, win rate and net.

• Show buy-ins and zero net before play starts
• Show lifetime stats for yourself and other players

2 updates in this release

This release includes: Verify poker host controls; Poker host controls.

1. Verify poker host controls

   Verify host permissions, standing and rejoining with preserved chips, table closure, and confirmation controls.

   • Correct ordinary Chrome acceptance result reading
   • Verify real stand, spectate, rejoin and end-table flows

2. Poker host controls

   Hosts can stand players up or end a friend table between hands while preserving chip records.

   • Host controls and confirmations in the More menu
   • Server checks host permission and current occupants without interrupting active hands

20 updates in this release

This release includes: Bound outstanding telemetry requests; Add tournament WS upgrade diagnostics; Combine live admin tournament list reads; Identify tournament WS validation failures; Fix ownership checks for QA role cleanup; Reuse the admin tournament read connection; and 14 more changes.

1. Bound outstanding telemetry requests

   Limit telemetry to two concurrent requests and 48KiB of aggregate request bodies, cancel stalled sends after five seconds, and drop optional events at capacity without queueing or retries.

   • Preserve diagnostic privacy and concurrent failure correlation
   • This fix does not establish the cause of historical slow requests

2. Add tournament WS upgrade diagnostics

   Local QA captures upgrade response status from scoped diagnostics and reads back owned publication before subscribing, preserving privacy checks without request headers or identity data.

   • Calibrate404 upgrades against an already cancelled owned edition
   • No claim of original root-cause fix or functional/performance acceptance

3. Combine live admin tournament list reads

   Keep an independent fresh authorization check while combining editions, status counts and metrics into one data query; empty lists retain metrics, and latency improvement requires measurement.

   • Preserve current counts, metric filters and response shape
   • Return metrics once and keep tournament display rules in Rust

4. Identify tournament WS validation failures

   Local QA retains strict privacy checks and records fixed codes for connection, decoding and projection failures without raw cards or identity data.

   • Check spectator frames before a tournament table exists
   • No functional or latency acceptance claim

5. Fix ownership checks for QA role cleanup

   Coordinate temporary local QA roles with persistent ownership across calls, allowing cleanup after gameplay writes while rejecting conflicting grants.

   • Serialize grants and cleanup for the four owned QA identities without overwriting other sessions
   • Save ownership journals atomically and retain strict row-version checks for legacy journals

6. Reuse the admin tournament read connection

   Share one database checkout across fresh staff authorization and admin tournament list reads, preserving current counts and error responses; latency still requires measurement.

   • Reduce repeated pool checkout while retaining connection health checks
   • Release the connection before response assembly without changing transactions or caching

7. Extend WS entry and owned QA cleanup checks

   Add protocol and recovery checks for Sic Bo social actions, tournament spectators and owned qualification fixtures; runtime and performance results require execution evidence.

   • Cover card privacy, reconnect, stale action rejection and owned qualification termination
   • Bound local QA resources and shared deadlines, with business cleanup and role restoration checks
   • Preserve real player qualification, existing business data and fee workflows

8. Improve API and WS verification and queries

   Extend popular game protocol checks, batch tournament counts, combine reopen notification queries, and add guarded measurement tools.

   • Verify reconnect, card privacy, accounting and released membership
   • Preserve authorization, freshness, notifications and database data
   • Retain full performance samples, restoration evidence and scoped monitoring overhead

9. Generate usage reports in the background

   Generate usage statistics through the isolated report worker, serve prepared results, and show their update time.

   • Retain time, platform, page filters and internal-account exclusions
   • Explicitly reject expired or unavailable reports instead of presenting missing statistics as zeros
   • Record local performance acceptance separately

10. Compare client and server latency

    Performance trends compare client end-to-end latency with server processing on one timeline, with mobile platform filters.

    • Show independent sample counts and missing timings; clarify WS probe scope to avoid attributing all unmeasured time to the network.

11. Fix public poker bean settlement

    Commit sealed-dealer public-table hands and bean ledger entries in one transaction without duplicate settlement on retry.

    • Keep pending-settlement protection until commit to prevent spending balances before losses are posted.

12. Reuse Apple sign-in connections

    Share a connection pool between public-key retrieval and token exchange to avoid duplicate connection setup during cold sign-in.

    • Retain token, signature and nonce verification and bounded request timeouts.

13. Reduce database exchanges for usage reports

    Batch fixed transaction settings and read report time with internal identity exclusions, retaining all-history exclusion rules.

    • Preserve report results, read-only consistency and pooled connection settings isolation
    • Performance improvement awaits local measurement

14. Reduce database exchanges for quality trend reads

    Send fixed transaction settings together before trend queries, retaining timeouts and planner limits.

    • Preserve report results and transaction-local settings isolation
    • Performance improvement awaits local measurement

15. Combine room reopen read and claim checks

    Read the original room and apply an authorized claim in one database query, retaining the original configuration and a separate successor lookup.

    • Preserve invalid-room, host-authorization and concurrent-reopen handling order
    • Retain room creation, notifications and cleanup; performance improvement still requires measurement

16. Reuse the database connection for reopen checks

    Reuse one connection for the original-room read, claim and successor lookup, preserving separate commits and releasing the connection before creation or cleanup.

    • Preserve authorization, concurrent-reopen limits and notification persistence order
    • Reduce connection checkouts and returns; latency improvement still requires measurement

17. Add performance accounting for the sealed dealer

    Show separate game-server and dealer latency samples, including delivery commits and rejections, with unavailable reporting when reads fail.

    • Count dealer HTTP routes and WebSocket operations independently
    • Retain commit-wait, cancellation and rejection samples; missing data is not zero traffic
    • This extends measurement coverage and does not establish that every latency target has passed

18. Reduce private room creation and reopen waits

    Send the hosted-room cap lock and the post-lock count together while preserving separate statements and the existing transaction boundary.

    • Read fresh capacity after lock waits to preserve concurrent creation limits
    • Preserve atomic room code, room and host-seat persistence; performance targets still require measurement

19. Reduce login response read latency

    Combine profile, membership tier and subscription-state reads for authentication responses while retaining the existing read-failure fallback. Password verification, account recovery and session rotation remain unchanged.

    • Remove two database round trips from the normal response path
    • Read login campaign grants after session commit; performance targets still require measurement

20. Reduce club list read latency

    Read account eligibility and the member’s own clubs in one database query, preserving membership privacy and list order. Return no data when storage is unavailable.

    • Deny guest, missing and deleted accounts
    • Return service unavailable for database failures; performance targets still require measurement

7 updates in this release

This release includes: Improve API performance visibility and game processing timing; Extend poker startup and dealing-input timing; Add server performance accounting and slow-operation attribution; Reduce login and hand review waits; Daily reports show all played games; Squid results grouped by round; and 1 more change.

1. Improve API performance visibility and game processing timing

   Show server latency and P99 intervals by HTTP method, retaining WebSocket samples through queueing, cancellation and rejection.

   • Distinguish passing, insufficient and incomplete observations
   • Narrow block-list lookups when joining a room
   • This change does not claim that every endpoint meets the 10 ms target

2. Extend poker startup and dealing-input timing

   Retain poker startup and seed-round completion timing through downstream processing and result submission, ending the processing span before waiting for the next independent input.

   • Preserve original receipt times and required persistence timing
   • Improve local validation sample capture and incomplete-run reporting

3. Add server performance accounting and slow-operation attribution

   Count instrumented fast, slow and failed requests independently of alerts, showing pending operations and routes without samples. Extend queue and settlement timing and identify slow-operation origins.

   • Separate full observation counts from alerts above 100ms
   • Display current-process counters separately from historical trends

4. Reduce login and hand review waits

   Remove a duplicate login query and parallelize hand detail reads. Latency trends show low-sample percentiles, maxima and counts above 10ms.

   • Reduce serial server database round trips
   • Expose slow-request peaks alongside percentiles

5. Daily reports show all played games

   Expand completed-game rankings to the top three, include other played room games, and omit inactive solo games.

   • Show games with recorded activity and omit inactive entries

6. Squid results grouped by round

   Each round combines all penalty payments and shows each player’s calculation and net result.

   • History retains complete rounds without cutting off payer records

7. One entry for feedback contacts

   Login, registration and help now link to one feedback page with WeChat, Telegram and WhatsApp contacts, accessible without sign-in.

   • Centralize feedback contacts to reduce clutter

2 updates in this release

This release includes: Separate server and client latency alerts; Show latency as area trends.

1. Separate server and client latency alerts

   Add 100ms server processing alerts; alert on client requests over 1000ms only after more than five occurrences in a rolling minute.

   • Observe server and network timing separately

2. Show latency as area trends

   Display P50, P95 and P99 as green, amber and red areas, with visible isolated buckets and honest gaps for missing samples.

   • Display P50, P95 and P99 as green, amber and red areas, with visible isolated buckets and honest gaps for missing samples.

7 updates in this release

This release includes: Load hand history after seating; Enter the table before preparing bot play; Fix offline seat cleanup retries; Alert on slow requests; Show overall performance trends by default; Refine ratings and room recovery diagnostics; and 1 more change.

1. Load hand history after seating

   Wait until bot table admission before loading hand history to avoid unrelated errors while creating a guest session.

   • The table and your seat still appear first.

2. Enter the table before preparing bot play

   Show the table and your seat before room creation, connection and dealing complete.

   • Late room creation responses cannot enter a stale table after leaving or switching accounts.

3. Fix offline seat cleanup retries

   Preserve members awaiting connection when leaving and safely release old room seats after public table reassignment.

   • Prevent premature public table detachment and keep replacement room seats unchanged during old room cleanup.

4. Alert on slow requests

   Observed HTTP and WebSocket operations exceeding 500 ms enter alerting, with a separate bounded budget for slow observations.

   • Include slow successful requests and timeouts in aggregated alerts.

5. Show overall performance trends by default

   Combine request samples for overall trends first, with optional breakdowns and clear sample counts when percentiles are unavailable.

   • Overall trends by default with optional detailed series.

6. Refine ratings and room recovery diagnostics

   Close submitted ratings, avoid duplicate rating alerts, confirm rooms before resuming, and preserve safe rejection diagnostics.

   • Name Guiyang Chicken Mahjong in admin insights.

7. Correct leave and bet-lock timing in game verification

   Production verification waits for Niuniu seats to be released before the next scenario and checks the Sic Bo bet-lock boundary against server time.

   • Retain cleanup ownership until seats are released
   • Preserve bet-lock rejection, pre-roll state, settlement and persistence checks
   • Bound and reuse verification HTTP connections across the bet-lock window

7 updates in this release

This release includes: Reduce first-seat poker queries; Reduce session wallet initialization waits; Improve performance acceptance and source verification; Fix session history summaries; Improve production game end-to-end verification; Improve poker and ZJH performance verification tools; and 1 more change.

1. Reduce first-seat poker queries

   Reuse known configuration and empty-seat state when creating a public poker session, avoiding redundant reads while preserving balance locks, concurrent admission and rollback protection.

   • Optimize only sessions created within the current transaction
   • Retain existing checks for established tables and re-entry

2. Reduce session wallet initialization waits

   Reset existing session wallets and record their ledger adjustments in one database round trip while preserving transactions, locking, and balance accounting.

   • Preserve concurrent first-wallet creation safeguards
   • Verify reset receipts, statistics, and concurrent rollback

3. Improve performance acceptance and source verification

   Repair historical probe path dependencies, distinguish runtime and probe revisions, and preserve original sample counts and latency thresholds.

   • Reuse original evidence where accepted behavior and relevant code are unchanged
   • Continue targeted verification of incomplete or unsuccessful batches

4. Fix session history summaries

   Fix a SQL field-name collision that prevented session history lists and summaries from loading.

   • Qualify JSON seat values separately from numeric seat columns

5. Improve production game end-to-end verification

   Correct betting-window and seat-synchronization test setup, complete game action, settlement and recovery checks, and retain connection-failure diagnostics.

   • Test rounds stay within 180 seconds and continue unfinished cases in targeted runs
   • Browser tests reuse a bounded connection pool while preserving business assertions

6. Improve poker and ZJH performance verification tools

   Preserve local performance probes for runtime identity, business acknowledgements, complete fan-out and test-data cleanup; this entry does not claim all performance targets passed.

   • Preserve established sample counts and latency thresholds
   • Mark protocol commands without business acknowledgements as not applicable

7. Improve game-page screenshot verification

   Screenshot verification identifies the ordinary Chrome window by process and unique bounds, reducing failures when the window title is unavailable.

   • Continue to verify foreground ownership and a unique match before capture

4 updates in this release

This release includes: Reduce room creation and river analysis work; Improve room creation and wallet initialization; Anchor action labels proportionally to avatars; Isolate worktree build caches.

1. Reduce room creation and river analysis work

   Combine account validation with new-room persistence queries, and reuse identical holding comparisons within each river range analysis.

   • Preserve account-state checks, membership constraints and wallet transaction guarantees
   • Reuse already computed results when the same holding is sampled again within an analysis
   • Preserve sampling order, weights and trial stopping behavior

2. Improve room creation and wallet initialization

   Reduce repeated work during room creation while preserving complete balance records, membership-conflict checks and recovery.

   • Persist dealer rooms and their first member together within one transaction
   • Initialize card-table wallets within the admission transaction to avoid duplicate initialization

3. Anchor action labels proportionally to avatars

   Call, raise and fold labels slightly overlap their avatar using the same proportional positioning on phones and tablets.

   • Remove fixed pixel gaps and small-screen offset overrides
   • Verify nine-seat phone and portrait tablet layouts

4. Isolate worktree build caches

   Each worktree uses its own build cache so parallel development cannot clear or overwrite another worktree’s artifacts.

   • Serialize builds within one cache and reject reuse across worktrees
   • Builds no longer prune caches automatically; existing artifacts are preserved

11 updates in this release

This release includes: Preserve existing data during release upgrades; Migrate checkpoint recovery checks; Simplify local verification; Restore scratch rooms after session recovery; Experience quality latency trends; Include account email in feedback alerts; and 5 more changes.

1. Preserve existing data during release upgrades

   Release upgrades add reporting tables and indexes while retaining accounts, balances and game history.

   • Failed transactional upgrades roll back
   • Normal releases never clear the database

2. Migrate checkpoint recovery checks

   Checkpoint recovery tests reuse the existing database while retaining chip, rollback and idempotency assertions; add single-process ownership-lock checks.

   • Verify fixture-only cleanup after failures and timeouts
   • Other legacy database and process-recovery tests still await migration

3. Simplify local verification

   Local tests reuse the existing environment and database; remove multi-environment load scaffolding and broad browser shortcuts.

   • Keep ordinary E2E within one three-minute budget
   • Mark capacity results incomplete when resource evidence is missing

4. Restore scratch rooms after session recovery

   After a temporary authentication outage clears, restore the saved scratch room with its pending ticket and settlement state.

   • Resume the existing room after session recovery
   • Verify reload recovery, settlement, and leaving

5. Experience quality latency trends

   Explore latency charts from ten minutes to one week or a custom range precise to seconds, backed by incremental statistics.

   • P50, P95 and P99 curves with sample tooltips
   • Dedicated statistics preserve missing and insufficient-sample gaps

6. Include account email in feedback alerts

   New feedback and follow-up alerts include the account email, retain guest and registered labels, and omit synthetic addresses. Also avoid reporting normal table departures as reconnect timeouts.

   • Help support identify feedback accounts for follow-up
   • Correct reconnect monitoring after normal table departures

7. Preserve pending mobile release status

   Mobile fixes stay pending until publicly available in stores, independently of website releases.

   • Keep website and mobile store release status separate

8. Poker setup antes follow the selected blind

   Ante choices show off, small blind and big blind amounts, preserving the chosen tier when standard or custom blinds change.

   • Retains the server limit of one big blind.

9. Show four-digit room codes in practice poker

   Practice poker uses real four-digit room codes shown in the table header after creation and reconnect, while retaining host-only access.

   • Restore room code display for practice tables and reconnects

10. Squid award collection animation

    Awarded Squid tokens fly from the top-left counter to the recipient with a glow, including the final award of a round, without replaying on reconnect.

    • Supports hero and opponent awards, including multiple tokens.

11. Restore poker table countdown

    Show total duration before play, then remaining time and expiry notices directly on the table.

    • Restore the ticking table clock and preserve the notice for an unfinished Squid round.

2 updates in this release

This release includes: Reduce database startup contention and repeated report computation; Table-wide poker Squid round announcements.

1. Reduce database startup contention and repeated report computation

   Preconnect for measured startup demand to reduce concurrent background connection waits, eliminate repeated quality-report work, and add transaction and pool diagnostics.

   • Prepare expected startup connections without increasing pool capacity
   • Preserve 1/7/30-day report semantics
   • Keep the 100 ms alert threshold and add diagnostic context

2. Table-wide poker Squid round announcements

   Show table-wide Squid round animations; Blood Battle settles immediately when one tokenless player remains or the pool runs out.

   • Visible from every seat and spectator view, bilingual and non-blocking

3 updates in this release

This release includes: Resolve cross-platform build diagnostics; Private-card recovery and best-effort monitoring; Enforce zero-diagnostic main merges.

1. Resolve cross-platform build diagnostics

   Resolve backend, web and mobile build diagnostics and update native mobile APIs and plugin tooling.

   • Extend merge checks to WebAssembly compilation and mobile toolchain validation

2. Private-card recovery and best-effort monitoring

   Recover slow private-card connections within the existing deadline and keep latency monitoring off business-critical paths.

   • Align recovery in the real client and network acceptance runner
   • Correct production browser readiness and screenshot targeting
   • Defer monitoring work and discard diagnostics under backpressure

3. Enforce zero-diagnostic main merges

   Add source-bound backend, H5, website and mobile checks that block merges on warnings or errors.

   • Verify dependencies and evidence before reusing successful checks

8 updates in this release

This release includes: Synchronize the public source reference; End-to-end API and WebSocket latency monitoring; Restore a clean client formatting baseline; Anchor the dealer button to its player; Simplify poker table information; Align latency diagnostics at 100 milliseconds; and 2 more changes.

1. Synchronize the public source reference

   The public source matches the current build configuration, with the deployed source link pointing to a verified immutable revision.

   • Published source subset verified byte for byte

2. End-to-end API and WebSocket latency monitoring

   Admin reports P50, P99 and P99.9 for request totals and measured phases, separating connections, server processing and unattributed time with sample coverage.

   • API timing ends when its response is usable; WS distinguishes connection, probe, action acknowledgement and private-card delivery
   • Only fixed endpoint categories and timings are collected, without request parameters, identities or cards
   • Insufficient or unmeasured phases remain explicit; residual time is not attributed solely to the public network

3. Restore a clean client formatting baseline

   Format seven client files and verify the final committed source at the merge entrypoint to prevent formatting regressions.

   • Preserve game behavior and interface content

4. Anchor the dealer button to its player

   The D button slightly overlaps its player avatar edge instead of floating between seats, following the revealed card edge at showdown without covering cards or hand labels.

   • Mirrored rail positioning makes dealer ownership clear

5. Simplify poker table information

   Move the room code to the header, show the configured squid amount beside its icon, and include straddle in the stakes.

   • Move the room code to the header, show the configured squid amount beside its icon, and include straddle in the stakes.

6. Align latency diagnostics at 100 milliseconds

   Apply 100 millisecond thresholds to database slow queries, long transactions and client upload diagnostics, with stricter startup wait filtering.

   • Database notifications include long transaction counts and threshold
   • Existing stricter diagnostic thresholds remain in place

7. Reduce duplicate builds and temporary storage

   Reuse locked build caches, share backend compilation across standard and hotfix releases, and reclaim regenerable intermediates.

   • Bound developer compiler caches while protecting concurrent work
   • Keep release retry artifacts while reclaiming build intermediates

8. Close idle account cleanup transactions

   Close the database transaction immediately when no accounts need cleanup, preventing idle cleanup transactions from triggering long-transaction alerts.

   • Empty cleanup batches explicitly await transaction rollback.

Fix blood-squid timeout recovery when returning to a table

Defer timeout departure while the blood-squid roster is locked, recover stuck timeout seats, and avoid redundant start requests when returning to an existing table.

• Preserve blood-squid settlement obligations and chip accounting
• Do not automatically restart a table that has already begun

2 updates in this release

This release includes: Streamline human game history and account data; Use a 500ms slow-query alert threshold.

1. Streamline human game history and account data

   Retain history for games involving people and improve account cleanup, notifications and rewards.

   • Skip completed AI-only history while retaining opponent details needed for human replays
   • Wait for departure and settlement before account erasure to protect other players
   • Preserve existing sign-in methods with a simpler database schema

2. Use a 500ms slow-query alert threshold

   Separate slow-query alerting from diagnostic logging while retaining lower-latency evidence.

   • A single query reaching 500ms triggers an alert; faster queries do not count as slow.

Compact table action labels

Shorten Chinese raise and fold labels beside player avatars.

• Compact Chinese raise and fold labels beside avatars

Link to specific answers and preserve game-entry language

Add stable links to tool and Dou Dizhu answers, preserve language at game entry, clarify virtual claw collections, and measure website entries using bounded source categories.

• Stable links to existing answers
• Game links carry the selected language; claw prizes are explicitly virtual
• Entry measurement records source categories and signals, not raw referrer URLs or conversations

4 updates in this release

This release includes: Fresh service and database with one year of Max; Clearer Dou Dizhu, Guandan and poker tool guides; Find games by play style and group size; Review the biggest net BB swing in each hundred-hand block.

1. Fresh service and database with one year of Max

   Keep account sign-in information while restarting game balances, history and analytics. Existing accounts receive one year of Max membership.

   • Redeploy with the current database schema and remove historical upgrades and old-data compatibility.
   • Give server events a separate queue, with pooled and concurrency-bounded overflow writes.
   • Fix concurrent account deletion, history review marks, and notification receipt consistency.
   • Revise history and report reads while preserving pagination, filtering, and reporting-window semantics.

2. Clearer Dou Dizhu, Guandan and poker tool guides

   Add worked farmer-team examples for Dou Dizhu, explain Guandan partnerships and online play, and make the poker equity calculator easier to find.

   • Dou Dizhu farmer teamwork examples and basic rules
   • Guandan online play and fixed partnerships
   • Direct poker calculator access and tool selection guide

3. Find games by play style and group size

   Improve poker, Zha Jin Hua and Niuniu game pages, update the poker Squid guide, and add a no-download game guide with group-size suggestions and related play styles.

   • Clearer poker, Zha Jin Hua and Niuniu rules and friend play
   • Poker Squid guide adds settlement examples and practice entry
   • Choose no-download games by preference, group size and similar play styles

4. Review the biggest net BB swing in each hundred-hand block

   For each completed hundred-hand block, select the largest absolute net BB result and show the range and result in the notification.

   • Fixed hundred-hand blocks ranked by absolute net BB result

13 updates in this release

This release includes: Improve player-content safeguards; Improve loading recovery after backgrounding and error tracing; Feedback details no longer need 10 characters; Restore live poker spectating and show spectator avatars; Fill human-table vacancies with AI and start; Frontend formatting maintenance; and 7 more changes.

1. Improve player-content safeguards

   Add baseline filtering for public names and chat, report and block controls in multiplayer chat, and curated public avatars.

   • Reports require verified shared table or match context; blocking follows player identity.
   • Existing custom avatars remain in the account but are no longer shared publicly.

2. Improve loading recovery after backgrounding and error tracing

   Background suspension no longer consumes loading recovery time. Staff can correlate errors using opaque account and client references, with request diagnostics retained for startup and sign-in failures.

   • Resume asset repair in foreground while preserving failed resource targets
   • Accept stalled-recovery diagnostics correctly
   • Distinguish account correlation, client correlation and unknown identity

3. Feedback details no longer need 10 characters

   Send product feedback with a subject and non-empty details (up to 4,000 characters).

   • Fix the Send feedback button staying disabled without explanation when details were under 10 characters.

4. Restore live poker spectating and show spectator avatars

   Spectate active full sealed-dealing tables and view current and past spectators below the standings.

   • Fix false table-ended errors while preserving live public updates and private-card secrecy.
   • Current spectators appear bright; departed spectators stay grey and brighten on return.

5. Fill human-table vacancies with AI and start

   Human tables with AI opponents gain a host-only fill-and-start action in the top-right menu, preserving seated humans.

   • Poker, Golden Flower, Dou Dizhu and other human tables with AI opponents gain fill-and-start.
   • Host authority, chip and game-state checks remain in place; AI occupies vacant seats only.

6. Frontend formatting maintenance

   Normalize formatting in three source files to restore frontend static checks, with no gameplay or visual changes.

   • Fix formatting checks for the protocol test, winner banner and shared styles.

7. Grant and revoke club administrator roles

   Club managers can grant or revoke administrator access. Administrators can review join requests and manage members, while the creator remains protected.

   • Role changes require confirmation, and revoked permissions immediately block management actions on the server.

8. Add spacing to club application guidance

   Add horizontal spacing around application guidance to keep the first character and wrapped lines clear.

   • Apply consistent paragraph spacing in Chinese and English.

9. Improve iOS game continuity

   Restore post-game actions in the native app and improve game connection recovery when returning to the foreground.

   • Post-game hosting and play-again actions in the native app
   • Immediate game connection checks on app resume

10. Keep poker room configuration visible

    Keep room code, total duration, stakes and configured rules visible during play; remove redundant player counts from waiting prompts.

    • Live remaining time and rule progress remain available in details.

11. Custom pot multiples for quick raises

    Replace the fixed 3/4 option with one custom size and save any pot multiple from 0.1 to 9.9, including decimals.

    • Keep 3–5 quick sizes; existing 3/4 preferences migrate to custom 0.75.

12. Consistent poker dealer placement

    Place D at each avatar’s forward-left corner facing the table center; heads-up shows only D and hides blind badges.

    • Dealer marker follows seat orientation
    • Only D is shown heads-up

13. Move table chat to the bottom right

    Move poker table chat and its unread count to the bottom right for easier access.

    • Preserve the chat drawer and unread indicators.