Bounty five · @italeex

You fixed the check that said clean after reading almost nothing, and proved it with a control.

What this entry did#407 made the facts check fail closed: on the old code, a festival file rewritten with double quotes left it reading 1 of 6 facts and still printing clean, which was reproduced. #410 stops a 3.3 MB poster loading on /press and /brand, and #432 stops the home page preloading all 80 hero frames, 5.1 MB of images down to 0.85 MB, both verified. #407, #409 and #410 are merged, and every description shows its measurement and says what it did not measure.

To win the next one

Seven pull requests is a lot to review

Three merged, one you closed as a duplicate, and #431 and #432 carry the same CI job, so only one can land as it stands. The ones that merged were the scoped ones. One change per PR gets reviewed faster.

Your doc script cannot fail

scripts/brand-migration-counts.mjs in #411 says it exits 1 when the doc and the code disagree, and it always exits 0. #433 does the same job with a test that does fail on drift; carry that pattern over.

Next: the recap round

Closes 5pm Eastern, Sunday 11 October

One vertical recap of ZAOstock, 90 seconds or under, cut from the raw footage of the day and the stream, with the acts' own music and every act you show named as zaostock.com/artists spells it.

It goes live when Zaal casts it, and the board at https://poidhz.com lists it within the hour.

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.