fix(grid): finish the #94 column remap on the three files it skipped
gig-up's "surface grid intact" blocker was NOT the CosmicFest false positive again — that was the first thing to rule out, because check-drift.sh once reported "drift" that was really PLN's own in-progress set prep and proposed `git checkout` on 13 files as the remedy. Checked: check-drift.sh passes, and it clears all five currently-modified .tidal files individually. None of PLN's open edits are implicated. The failure is gig-up's stricter composite (gig-up.sh:343), which also demands `migrate-columns.py --plan` report zero moves. It reported 10, across four files that are all COMMITTED and all untouched by b5ad8b6c ("finish the #94 column remap", 2026-08-23) — `git show --stat` has no match for any of them. Three were last edited 2026-08-21, before that commit; the remap-finish simply missed them. So the direction is forward onto the authored grid, not a reversion of anyone's work — a standing migration debt, not a clobber. Two of the three are SWAPS (^52<->^32 in perfect, ^89<->^57 in vague_de_crime), which is exactly where a naive rewriter eats itself: renumber ^52->^32 first and the following ^32->^52 sees the value it just wrote, collapsing both onto one control. Checked the tool before letting it near the tracks — rewrite() maps each line in a single `CC_REF.sub` pass, so every match is resolved against the ORIGINAL text and a swap is atomic. Confirmed in the diff: both directions flipped, all four occurrences in vague_de_crime, nothing collapsed. Verified after: pvlint 3 tracks, 0 errors; silent-eval --seeded OK (every declared orbit still emits events); migrate-columns --plan now reports 0 moves for these three. Deliberately NOT applied: something_about_drums.tidal. Its five moves come with an overflow (d3's ^44 has no slot in the new grid), and the tool's remedy for an overflow is to COMMENT OUT every live line of that orbit and head it with a FIXME. That silences part of d3 until it is rewired by hand — a musical consequence, not a mechanical renumbering, so it is PLN's call and gig-up will keep flagging the grid until he makes it. Also noted, not touched: perfect.tidal:61 carries a pre-existing PV010 warning (d5 gates on ^89, momentary row F, wants ^57 on the latching row E), and the commented-out alternative at the_revolution_will_be_sampled.tidal:47 still names ^52 — the rewriter deliberately never edits comments, since a commented ^NN is an alternative PLN may re-enable.
Showing
Please
register
or
sign in
to comment