bug-postmortem
The log that remembers both players
The shared game log learns to show two players at once, PvP gets a live panel of its own, and a scoring bug that only hurt guests surfaces along the way.
One word at a time
Two long words typed at once could break the whole duel layout. The fix drops the side-by-side grid for a single panel that follows whoever is acting.
Fifty-six turns of twenty
A Daily Challenge that can never exceed twenty words showed a game log toggle claiming fifty-six turns. Fruit events were counting as turns.
The crash that used to win
A player ahead on score could just ram the wall and win. PvP duels get lives, hearts, and a reason not to crash on purpose.
The score that almost got away
A tab switch could strand a finished Daily Challenge with no way to submit it. The fix merges two screens into one and stops trusting the client for the score.
The apple moved overnight
A date-seeded apple invalidates the daily recording route, so the scripted player learns to search for a verified two-word opener.
Giving the logic a name
Two days pulling shared logic out of stores and routes into small, named, independently tested modules, one of which immediately surfaced a real duel bug and got its own same-day fix.
The clock comes off
The thirty-second per-word timer added three weeks ago comes out entirely, scoring reverts to pure word length times rarity, and a UI freeze traced to backdrop-filter blur turns up in three more dialogs with a blunter diagnosis than the first time.
The screen that would not respond
A WCAG reflow fix that became a permanent layout rule, assisted mode deleted nine days after it shipped, and an end-game screen that froze the browser until profiling found why.
Thirty seconds to decide
A tuning pass over daily mode: a per-word timer with a speed bonus, a background-timer bug that punished new players for reading the tutorial, and a board size that flip-flopped within the same day.