PLN asked three questions this morning and each one landed on a different
failure of mine, so the log gets a part III rather than a tidy epilogue.

The demucs OOM he spotted was a fossil: the killed first attempt (8.2 GB, 2 of
14 sections) sits in the journal forever beside the rerun that succeeded at
7.6 GB. A unit's history is not its state — verify the artefacts.

The +5-vs-+8 recommendation is corrected. I had called +8 "the conservative end"
against a generic genre norm; against OPAL v4, the master he actually signed off,
CosmicFest is already 6.6-8.1x brighter above 4 kHz on a third of the sub. So
+5, and the lesson is about naming the reference: a genre norm and the artist's
own shelf can point opposite ways, and only one of them answers "does it sit with
my other release". Recorded with the caveat that most of that table is the
recording, not the master — and that the unspent lever for harmony is the LOW end,
not the shelf we A/B'd all night.

And the gig metadata was never missing. His own repo held the date, the location,
the stage and the lineup; his backlog held the five movements. The blocker was
that I had not looked, and in that gap I had written an unsourced 2026-08-23 into
the spec. Wrong by a day, with the answer two files away.

Plus the three things that only running the pipeline could show: POST /tracks is
dead AND burns the S3 upload first, --force never worked for the case it was
named after, and the catalog gap was a cycle rather than a stale cache.