Second pass on the audit. "Am i Doing it Right?" was reported as file-not-located;
it exists as live/techno/do_it_right.tidal. No slug guess matched the title — it
was identified by `setcps (89/60/4)` = 89 BPM against the backlog's [89*] marker.
Recording that as a method: when title-to-slug guessing fails on this repo, the
tempo line is the reliable identifier, not the filename.

It changes the finding in a way that strengthens the conclusion rather than
weakening it. The track DOES have a riser, so the count is 3/12 not 2/12 — but it
is a third, mutually incompatible idiom:

  d10 $ mask "<f!4 t f!3>" $ loopAt 4 $ "risers:8" # gain 1 # cut 10

An 8-cycle period firing on cycle 5, but loopAt 4 stretches the sample over 4
cycles while the mask only opens for 1 — so what plays is a slice of a slowed
riser, not a complete build. Could be deliberate (at 89 BPM a full 4-cycle build
is very long) or a leftover; flagged for PLN either way.

So the real headline is not the absence of risers, it's the inconsistency of the
ones that exist. Three tracks, three idioms, disagreeing on all three axes:
- phase: fires-last-8 (Take Five) vs fires-first-1 (Vague de CRIME) vs
  fires-cycle-5-of-8 (Do It Right);
- gain: 0.8 vs unset vs 1 — the riser will not read consistently to the room
  across three tempos;
- wrapping: Take Five AND Do It Right both lack gF/gM, so they are the only
  streams in the set the global filters and mutes cannot touch. Reach for gF1
  during either build and everything ducks except the riser.

That third point is the one that could actually bite live, and it now affects two
tracks rather than one. It also makes the gRiser proposal stronger: harmonizing is
no longer "add the missing 9", it's "reconcile 3 disagreeing implementations and
then add the missing 9", which is exactly the kind of thing worth doing once in a
helper instead of nine times by hand at J-10.