The regen moved timecodes by up to 21s (Piment +21.0, REVOLUTION +19.0, Gimme
Acid +16.7). That file is not just website furniture — Slopmotion cuts visuals
to it, so the release videos were pointed a third of a minute off the music on
a third of the record.

The more interesting finding is a parser conflict the regen walked into.
build_gig_tracksjson.py drafts NEW gig pages and never computes the
styleDistribution that LiveEvent.js renders; gig-metadata.py regenerates
existing ones and does. They also disagree outright on REVOLUTION's style
(jazz vs nujazz). Two parsers, one concept — so the board's line that
build_gig_tracksjson 'is now the way to make any gig page' is too strong and
is corrected here rather than left to bite the next regen.

Left explicitly to PLN: whether the OPAL page documents the set as PERFORMED
(15 tracks, Desire included) or as RELEASED (14). Desire has no v4 boundary
because it was cut, so its v3 timecode rides through unverified. A page can
honestly be either thing; only he knows which one he wants a visitor to get.