0xc9d0...e6d0

Measured: 82.4 seconds, 1080x1920, h264, faststart, hosted where it plays. The reel is built on one idea, that the festival is free, the host speaks before Zaal, the end card holds zaostock.com for about seven seconds, and the claim explains plainly what went wrong with each earlier upload. Claims 8441, 8442, 8443, 8444 and 8446 are read as this one entry, as you asked.

Check the first frame before you upload. For the first nine seconds the title block and the captions are drawn on top of each other, and neither can be read. That is the stretch a muted viewer sees first.

Spell it ZAOstock. A caption reads 'Zal Stock'. Captions are the part people read; check the festival's name in every one.

One claim, corrected, beats five. Five claims for one reel make the bounty page harder to read for everyone judging it. Test the file link from outside your own network before the first claim, and the rest are not needed.

#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.

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.