You said what was wrong, how you knew, and what you ran, and every part of it held up.

To win the next one

1. 1

   #334 does not save the bytes it says it saves, and this was measured rather than reasoned

   The comment reads 'Phones on cellular shouldn't have to download the full autoplay video', and the change is display: none on the video under 768px. display: none does not stop an autoplaying video downloading - the element stays in the DOM and the fetch still fires. Run in Chromium at 390px against a control: with the rule active the computed display is none AND the browser still made one request for ellsworth.mp4; the control with the rule inert made one as well, so the counter works and the difference is zero. The phone still pays 1.82 MB and now sees a poster instead of the video it paid for, which is worse than before the change. This is the exact trap the round was written about, and another entry in this round describes it in its own PR: autoplay wins over preload=none. To actually save it the element has to not be rendered, or its src has to be withheld until it is wanted.

2. 2

   The next rung up got taken while this was being written

   LocalStartTime.tsx:24 calls setState synchronously inside an effect, and that was the obvious step up from a lint fix - a change with real runtime behaviour behind it. Another entrant claimed it the same night with useSyncExternalStore. That is the round working rather than a reason to be discouraged. What is still open and still not cosmetic: nothing in this repo stops the next warning landing, because lint exits zero however many there are.

3. 3

   #363 found a real bug, and it needs one more change

   The old check misses Toronto, Detroit, Louisville and Indianapolis, so viewers there see the redundant start-time line, and your tests catch it. Reading window in a useState initializer returns null on the server and a value in the browser, which is a hydration mismatch, and the file has since been rewritten on main. Rebased onto main with the new zone check inside the existing useSyncExternalStore snapshot, it is a welcome merge.

Next: the recap round

What bounty five was judged on

• Does somebody landing on the site from a phone have a better time than they did before.
• Did you ask for feedback and use it. The round text promised answers while it was running, and that promise is the reason these notes exist before the close rather than after.
• Could it ship this week. Nothing here is graded on ambition it cannot finish.
• Open pull requests count as complete entries, and merged wins ties. Nothing has been merged, on purpose - merging an entry mid-round would be picking a winner quietly.