fix: commit refilled energy back to player state

Greptile caught this on review: the refill-tick loop computed incremented
energy/lastLogin into local variables but never wrote them back to
playerState, so the displayed energy counter stayed stale between real
account-change notifications. The previous BN-based version got away with
mutating playerState.energy in place and relying on the same effects
setTimePassed/setEnergyNextIn calls to force a re-render - that trick got
dropped when the local let variables were introduced. Now commits the
computed values via setPlayerState explicitly, only when something changed.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Author: Harsh-H-Shah

tokens/token-2022/nft-meta-data-pointer/app/contexts/GameStateProvider.tsx

@@ -108,15 +108,21 @@ export const GameStateProvider = ({ children }: { children: React.ReactNode }) =
             let timePassed = (currentTime - lastLoginTime) / 1000;
 
             let energy = playerState.energy;
+            let lastLogin = playerState.lastLogin;
             while (timePassed >= Number(TIME_TO_REFILL_ENERGY) && energy < MAX_ENERGY) {
                 energy += 1n;
+                lastLogin += TIME_TO_REFILL_ENERGY;
                 timePassed -= Number(TIME_TO_REFILL_ENERGY);
             }
 
             setTimePassed(timePassed);
 
             const nextEnergyIn = Math.floor(Number(TIME_TO_REFILL_ENERGY) - timePassed);
             setEnergyNextIn(nextEnergyIn > 0 ? nextEnergyIn : 0);
+
+            if (energy !== playerState.energy || lastLogin !== playerState.lastLogin) {
+                setPlayerState({ ...playerState, energy, lastLogin });
+            }
         }, 1000);
 
         return () => clearInterval(interval);