docs(gig): the evening's state — set settled, surface coherent, faders not

The tracker now leads with the one thing no tool can fix from outside: seven
orbit faders sit at -inf in the saved Ardour session, so from a fresh launch
more than half the rig is silent and looks exactly like Tidal emitting nothing,
because Ardour's meters are post-fader. gig-up already restores the baseline in
the Ardour-closed window, which is why this is a checklist line and not a fire.

It matters more tonight than this morning: the orbit compaction moved melodies
onto d5 and d6, two of the seven.

TODO_GIG.md

@@ -160,6 +160,64 @@ Open, highest leverage first:
   args, via `tools/setlist.py` → `backlog.md`, walks bombe_dj / wap / do_it_right /
   take_5_drops. The Thursday arc lives only in `armada/setlist_thu24.txt`. Pass paths
   explicitly, or give backlog.md a Thursday section, before trusting any default.
+## Tue 22 — evening. The set is settled and the surface is coherent.
+
+- [ ] **YOU, FIRST THING: seven orbit faders are at −inf in the SAVED Ardour session.**
+  `tools/check-mix.py` reads Tidal 04, 05, 06, 07, 08, 10, 12 all at −inf, Master −0.5 dB.
+  `tools/fader-baseline.py --check` calls it: 8 faders drifted, and the baseline wants
+  04 −0.4 / 05 0.6 / 06 0.6 / 07 0.6 / 08 1.5 / 10 5.6 / 12 6.0 dB. From a fresh Ardour
+  launch, **seven of twelve orbits are silent**, and it looks exactly like Tidal emitting
+  nothing because Ardour's meters are post-fader. This is not new — the archived 6 Sept
+  notes have PLN's own words on it ("tidal 12 -inf is random i might turn on/off any
+  fader ... i save random") — and the fix is already wired: `gig-up.sh` runs
+  `fader-baseline.py --restore` in the Ardour-closed window. So either **gig-up at the
+  venue**, or close Ardour and run `tools/fader-baseline.py --restore` yourself. It needs
+  Ardour CLOSED; while it is open the tool refuses.
+  This now matters MORE than it did this morning: the orbit compaction moved melodies onto
+  d5 and d6, which are two of the seven.
+- [x] **THE SET: 17 tracks, AI ENGINEER** (fe4441d) — `armada/setlist_thu24.txt`, in play
+  order, three movements (START / NUJAZZ PARADIZE / FINALE COMEDOWN), ~9 min each. PLN's
+  own arc, and the shape moved with his ear: cyber_hump, wap and bombe_dj are out ("too
+  sample heavy its a nujazz/chill dnb set"). **All 17 pass `silent-eval --seeded`**, ten of
+  them never validated for this gig before. pvlint over the set: **0 errors**.
+  - [ ] **YOU: `ete_a_mauerpark` — confirm the d9 effects** (his note).
+  - [ ] **YOU: `sept1` — fix to the new controller** (his note).
+  - [ ] **YOU: A/B two crush buses** (ff084fa) — `love_first` d12 and `cafe_bouillant` d11
+    were both writing `crushbus 41` alongside d4, so the two parts traded crush amounts
+    every cycle. Moved to 121 and 111, the numbering the corpus already uses. Each part
+    should now answer its own knob; worth one listen since it is an audio-graph edit.
+- [x] **Preload covers the new set** — regenerated as a union: **125 → 132 banks**, nothing
+  lost, exactly the 7 the new tracks needed gained (`hh27`, `jungle_bass`, `movie_cat`,
+  `nujazz_bassp120`, `nujazz_fx120`, `nujazz_guitar120`, `rampleS57`). Both gates exit 0.
+  Mode 0600 preserved, backup in the session scratchpad. **Warms at the next
+  `systemctl --user restart parvagues-sc`** (~15 s of silence, safe when not playing).
+- [x] **Corpus-wide column remap DONE** (3827b62) — 685 moves in 148 files, 0 clashes.
+  Button conformance **78.9% → 93.3%**. Zero CC refs landed in the Ardour-learned or gF
+  ranges; every bus slot byte-identical.
+- [x] **Orbit compaction DONE** (f6be520) — 150 moves in 133 files, band {5,6,7} derived
+  from the family maps so a move is inaudible; d4 (bass) and d8 (percs) never touched.
+  7 orbits refused for carrying an explicit `# orbit N`.
+- [x] **Both migrations verified against the baseline** — `silent-eval --seeded` re-run
+  over all 703 files after each, diffed per file against
+  `docs/2026-09-22-catalog-playability.tsv`: **zero verdict changes, twice**. 597 playable,
+  85 compile-fail, 21 silent-orbit, and not one file swapped sides.
+- [x] **midiviz has a sun theme, a menu and a tray** (949b992) — `--theme {dark,light,sun}`,
+  `d` cycles, right-click menu, tray to hide into, choices persisted at
+  `$XDG_CONFIG_HOME/parvagues/midiviz.json` and unkillable by a corrupt config. Dark proven
+  pixel-identical to before. **The tray itself is UNVERIFIED** — headless has no status
+  area, so only the degrade path was proven. Look for the icon before relying on it.
+- [ ] **midiviz state layer** — design in `docs/2026-09-22-midiviz-state-wire.md`. The
+  readout cannot show rest state from the wire (no readback, deltas, nothing at boot); the
+  driver owns the values and would publish them as one small atomically-replaced file with
+  a seq counter. First slice is the three DJFs as three zones with the **centre detent**
+  drawn, since zero is 64 and not 0. Post-gig. The Pulsar-style feed needs no new producer:
+  `~/.cache/parvagues/eval-events.jsonl` is already written, one line per ctrl+enter.
+- [ ] **Post-gig cleanups**: 90 files carry 114 duplicate FIXME lines from the old
+  non-idempotent migrator (fixed at the source, the existing ones are cosmetic) · 36
+  PV011 bus-slot collisions remain outside the set · `tools/lcxl3-driver.py`'s `parse_bpm`
+  collapses into `setlist_samples.declared_bpm` · corpus pvlint 3718 warnings, mostly
+  PV013 missing family mutes, which `tools/fix-mute-roles.py --fill` can do in bulk.
+
 - [ ] **techno_orage d2** (line 158) silent even seeded — fix or cut. PLN's call.
 - [ ] **Preload gaps**: `bass2`, `humps` lazy-load mid-set. Regenerate after the arc is picked.
 - [x] **The picker now holds the whole catalog** — the Set Builder showed 14 hand-written