PLN: "in you my sunshine the bass easily saturates too, not sure if code or
ardour setup". Code, measurably — and the same number as this morning's kick.

d4 is not one bass, it is two playing at once: a `superimpose (const ...)`
bassWarsaw plus the chopped no_sunshine loop. ^32 crossfades between them:

    superimpose   # gain (range 0.5 2   "^32")   ->  peak +24.1 dB at ^32 max
    main          # gain (1.8 - 0.6 *   "^32")   ->  +20.4 dB at ^32 UNTOUCHED

Both are crushed off the same ^52. So the orbit is loudest at BOTH ends of the
crossfade and its default resting state is +20 dB — a fader ride cannot rescue
that, because the shape is wrong, not the level.

Now `range 0.5 1.5` and `1.5 - 0.3 * ^32`: both ends land at +14.1 dB, so the
crossfade holds roughly constant loudness instead of bulging. This is
[[reference_superdirt_gain_is_quartic]] applied a second time in one day — the
gain^4 exponent is why 2.0 reads harmless and meters at +24.

Also: "d3 should also be the classic techno runner companion on 43, so it
hits(4,8,1)". ^43 was a bare `ply 2`. Now `ply 2 . struct "t(4,8,1)"` — struct
puts the hats ON the euclid rather than thinning what is already there (mask can
only remove), and ply doubles each into a running 8. Released, the liquid
pattern returns.

REAPPLIED after a buffer clobber: wap's d4 octer/octersubsub had reverted from
^32 back to ^52 when Pulsar wrote its stale buffer on close. Exactly
[[reference_pulsar_buffer_clobber]], and exactly what #95 exists to prevent.
Caught because migrate-columns --plan is idempotent and went from 0 moves back
to 1. PLN's own new FIXME on that line ("too wobbly... not fan of the 44/76
slicing") is preserved.

SET REORDERED by PLN: gimme_acid -> mafia -> sunshine -> vague -> desire.
"sunshine great cinematic ending, but sunshine-to-vague-to-desire makes more
sense imo." vague->desire is now a CLEAN transition, and sunshine's 166->120
drop into vague is the one seam to watch. Setlist and preload regenerated from
backlog.md; 52 banks cover all 15 tracks.