PLN, after seeing the OLED refuse to claim a round number: "quantise would make
sense mark a todo on the tracks sept1 and this commented line replace it with
quantize commented too. where its possible".

The measurement behind it: the house idiom `# cps ((range 60 180 "^29")/60/4)`
spreads 120 BPM across 128 CC steps at 0.94 BPM per step, so exactly 120 is
unreachable — step 63 is 119.5 and step 64 is 120.4. Wrapping the range in
`quantise 1` makes round tempos land exactly AND gives the knob a real two-step
detent at each one, which is the notch the v3 encoder lost.

Two treatments, deliberately different. A LIVE cps line is not edited — the
tempo is playing and this is his set material; it gets a TODO on its own line
above. An already-COMMENTED one is rewritten in place to the quantise form,
still commented, so uncommenting it gives round BPMs from the first click.

The TODO goes on its own line and never as a trailing comment, because the
driver's parse_context uses a line's trailing comment as that control's OLED
label — a trailing TODO would have renamed the tempo knob "TODO(tempo): wrap
the range..." on the screen. The first draft of this change also hard-coded
"60-180" into files whose ranges are 75-165, 100-166, 99+-20 and 60-124; it was
reverted and rewritten range-agnostic before landing.

Verified all 14 matches are genuinely tempo knobs (including one `cpsbus 4`
variant in ragga_la_hierarchie), not incidental cps-and-range coincidences.