PLN, on lime_tacos' ^44 driving both d3 (hats) and d6 (cymbales sol):
"lime tacos its ok when two percs are linked, e.g. here, change rythm of
both 3 and 6. [...] im fine with this, not a NOGO, just a WARN?"
He is right, and the interesting part is WHY the rule was wrong rather than that
it was. PV008 was earned on a real bug — the 2026-07-29 phase-2 remap left d1
holding ^42 after d2 was given ^42, and perfect.tidal shipped one button firing
two orbits. That bug is real and this rule is how it was found.
But the accidental case and the deliberate one are TEXTUALLY IDENTICAL. Two
orbits, one button CC, no way to tell from the source whether PLN meant it. The
rule had quietly encoded "one button drives one orbit" as an invariant of his
style, when it is only a hypothesis about it — and the hypothesis was wrong. He
groups percussion on purpose: one gesture re-rhythms the whole group.
A check that cannot distinguish intent must not hold the gig gate shut. It
reports; PLN decides. So: severity error -> warning, and the detail now states
both readings and what distinguishes them (deliberate percussion grouping vs a
control inherited from a remap) instead of assuming the second.
Effect: tools/gig-up.sh goes NO-GO -> GO. This was the last blocking failure, and
it was blocking on a correctly-written track.
Added test_pv008_is_a_warning_not_an_error, which quotes PLN's ruling, so nobody
"tightens" this back to error without meeting the argument first. pvlint 63/63.
