fix(surface): finish the column remap on the tracks actually in play
The #94 remap was run against a setlist, not the catalog, so conformance was never a property of a track — it was a property of having been on that list. Two days of desk edits then pushed listed tracks back out: swapping jeudrill's d9 and d10 bodies moved the orbits but not their knobs, so d4's effect was sitting in d5's column again. Migrated, one simultaneous permutation per file, 24 moves across six tracks: jeudrill 6 the d9/d10 swap's knobs follow their orbits liquid_nite 4 the four PLN had not reached by hand rose_rouge 3 techno_orage 9 cyber_hump 1 siberie_samuel 1 liquid_nite is the one that prompted this — PLN saw it in the catalog, wanted it in the set, and found it half-migrated: he had walked the buttons down a column by hand (^42 -> ^41, ^43 -> ^42) and stopped. The knobs are now on their own columns too, and it evaluates clean. VERIFIED, not assumed: re-plan reports 0 moves on all six; silent-eval --seeded is OK on five. techno_orage still FAILS, on the same d2 that was already silent before this commit — unchanged, and still PLN's call to fix or cut. pvlint: 0 errors, 21 warnings, all pre-existing shapes (PV013 missing family mutes, PV005 double declarations). One is worth reading: PV008 says techno_orage's ^58 drives d5 AND d6, which is the overflow the tool annotated rather than commented — a $-step cannot be commented out without breaking the block's arity, so that button really does fire across two columns until gSel folds it. AND THE TOOL NO LONGER TALKS TO ITSELF. Every run stacked another byte-identical FIXME paragraph above the same line: cafe_glace carried the same note three times, and 90 files in the corpus carry 114 duplicate lines between them. An overflow is a standing condition, not an event, so it earns one note. The comment-out still runs on a repeat pass — if a line came back to life it is firing across columns again whatever the note says — only the note is deduplicated. Proven by applying twice and diffing: 15/13 both times. Corpus-wide, 154 files still want 709 moves with zero clashes. Not tonight.
Showing
Please
register
or
sign in
to comment