accessibility
Everything looked urgent
Separating primary action from danger, fixing fruit contrast, and making pill controls describe what they actually do.
The board becomes readable
The game board stops being hidden from assistive technology and becomes a read-only grid that can be explored without taking control away from word input.
The number was never the decision
A PvP host can now pick a turn time limit from 30 seconds to 3 minutes, for accessibility. Almost everywhere the old fixed 60 seconds showed up, the actual design underneath it never depended on that number at all.
Fast, but not zero
Speeding up the e2e suite by cranking animation speed risked breaking the one test that watches an animation happen. Reduced motion turned out to be the wrong kind of fast.
One tooltip, anywhere on the page
Detail tooltips reach the fruit on the board itself, and the "only one open at a time" rule stops being a property of the game log and becomes a property of the page.
The interface does not end at the board
Physical-key feedback, host sleep, and an iOS zoom gesture expose three boundaries the game still needs to design around.
Let the game explain itself
Game-log chips gain explanation-on-demand tooltips, while the recording script learns to demonstrate the game it claims to show.
The narrow screen gets to decide
Foundation tokens make a mobile-first redesign tractable, then a second design review turns layout stability and colour contrast into regression tests.
The week the game started watching itself
A three-PR refactor trio makes the word-submission pipeline immutable and side-effect-free, then the newly-launched game gets its first stats page, a same-week AI tuning pass informed by it, docs finally caught up to the Postgres stack, and a WCAG 2.2 audit closes the week.
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.