Eliminate discard flicker by deriving play state directly from fetcher data

[Copilot]

After a discard, optimistic UI disappeared when discardFetcher.state returned to idle, but the useEffect sync into local gameState had not yet committed, causing a brief render of stale state. This change removes that async gap by making render state synchronous and derived.

• State source of truth

  • Removed local gameState (useState) and both sync effects (useEffect) from app/routes/play.tsx.
  • Replaced with a single derived state for rendering:

    const currentGameState = discardFetcher.data ?? loaderData;
    const { sutehai, tsumohai, nextTsumohai, junme, kyoku, tehai, remainTsumo, score } = currentGameState;

• Reference migration

  • Replaced component references from gameState to currentGameState where base state is read.
  • Kept optimistic discard/tsumogiri calculation logic unchanged.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
✅ Deployment successful! View logs	hitori-mahjong	971ed61	Apr 24 2026, 05:51 AM