docs(morning): Monday brief — the set is done, the FADERS are the blocker

Last KRK day. The chart PLN asked for, and the honest reading of it: the SET is
finished and derived rather than maintained, the TOOLING is done and should stop
there, and the long pole is REHEARSAL — 11 of 14 tracks played, three never
heard this cycle, and those three are the FINALE and ENCORE.

gig-up is NO-GO on exactly one thing and it is not code: nine of twelve Ardour
faders sit at -inf in the saved session (#124, third recurrence). Mechanism now
suspected — he ends a set with faders down and that is what Ardour saves, so the
saved session is a snapshot of end-of-set silence. Thirty seconds to fix today,
but #20's template is the real answer before Saturday.

Pacing measured for the first time rather than guessed: Take95 ran 61.2 min for
11 tracks = 5:34 each, so 14 tracks is ~78 min against a 90 min slot. Twelve
minutes of slack.

Also carries the buffer-clobber warning for tomorrow's editing session: close
and reopen any tab open yesterday, because Window: Reload does not do it.

MORNING.md

-# ☕ Sunday 2026-08-02 — J-6, the one-before-last KRK rehearsal
+# ☕ Monday 2026-08-03 — J-5. The last KRK day.
 
-Supersedes Saturday's file. `master` clean, **everything pushed** (0 ahead / 0 behind).
-`tools/gig-up.sh` = **GO**, 10/10 cold checks.
+Supersedes Sunday. `master` clean, **everything pushed**.
+`tools/gig-up.sh` = **NO-GO on one thing only**, and it is not code (see §1).
 
-**The KRKs go home after tomorrow.** Everything below that says "listen" is a thing only
-you can settle, and this run plus one more is the whole remaining budget.
+**The KRKs go home tonight.** Everything below marked 🎧 needs your ears and cannot
+move without them.
 
 ---
 
-## The set is 15 tracks now, not 13
+## 1. The one thing standing between you and GO
 
-Your SSOT ruling got applied for the first time yesterday, and the backlog disagreed with
-every tool in the repo. **`ouais_je_funk` and `lime_tacos` are in the set** and have never
-been played in sequence. `you_my_sunshine` now comes **before** `mafia_sans_serif`.
+```
+  ✗ ardour faders
+      Tidal 02,03,04,05,06,07,08,10,12  =  -inf dB  — NINE of twelve SILENT
+```
+
+Third recurrence, and I think we finally have the mechanism (#124). You end a set with
+the faders pulled down — natural — and **that is the state Ardour saves**. The saved
+session is a snapshot of end-of-set silence. Boot from it at OPAL and nine orbits start
+dead while you're on stage.
 
-That drift had already cost you something audible: preload was warming 50 banks where the
-set needs 53, so `dr`, `gfunk_bass` and `h2ogmcy` were lazy-loading off disk on first play.
-That is the crackle you heard on the `take_5_drops` transition — the same bug, still live,
-just smaller. **Now 54/54 warm.** If you hear crackle on a first play today, it is
-something new and I want to know.
+**Fix now, 30 seconds:** open Ardour, raise the twelve Tidal faders to where you want
+them, **Ctrl+S**, re-run `tools/gig-up.sh`.
 
-`backlog.md` is now the only place you change the set. `gig-up --converge` regenerates the
-list and the preload plan from it; a plain `gig-up` fails loudly if they have drifted.
+**Fix properly, before Saturday (#20/#124):** save a *"Tidal Live START"* template at
+unity that the performance never overwrites. Right now the gate can only ever say "the
+session boots correct", and the honest answer today is that it doesn't.
 
 ---
 
-## 15 tracks × 90 min = 6:00 each (was 6:55)
+## 2. Where the line to live actually is
 
-Worth feeling on this run specifically — the set got two tracks longer without getting
-longer. If it runs over, the encore is the cheapest thing to cut.
+```
+                   J-5 (today)          J-3/J-2              J-1 / SAT 8th
+  SET          ████████████████ done ─────────────────────────────────▶ play it
+  RIG          ██████████░░░ #124 ────▶ #20 template ────────────────▶ boot from template
+  REHEARSAL    ███████░░░░░░ 11/14 ──▶ #127 tail ──▶ #14 full run ──▶ ✓
+  TOOLING      ████████████████ done (stop here — it is enough)
+  RELEASE      ███░ Take95 export ─────────────────────────────────▶ post-gig
+```
+
+**The set is finished.** 14 tracks + soundcheck, ordered, all compile, 0 lint errors,
+0 pending remaps, preload covers every bank. It is also now *derived* rather than
+maintained: you edit `backlog.md` and everything downstream follows. That stopped being
+a chore this weekend.
+
+**Rehearsal is the long pole, not code.** You have played 11 of 14. Three have never
+been heard this cycle and two of them changed underneath you.
 
 ---
 
-## Per-track: what to listen for
-
-**NEW** = added since your last run, never heard. Ten tracks have something new in them.
-
-| # | track | bpm | what to listen for |
-|---|---|---|---|
-| 1 | bombe_dj | 124 | **NEW** riser on d10 |
-| 2 | wap | 133 | **NEW** riser on d10 |
-| 3 | do_it_right | 89 | the 133→89 drop — deliberate half-time, or does the arc sag? |
-| 4 | take_5_drops | 124 | **d5 FIX.** `>\|` → `\|>`: the slice rhythm should now SURVIVE while ^57/^53 change pitch. Before, `slow 4` was replacing the rhythm with one event per 4 cycles. This is the "d5 steals structure" bug — TODO @PLN verify |
-| 5 | piment_bresilien | 124 | d10 is Menace, not a riser (relocation deferred — see below) |
-| 6 | **ouais_je_funk** | 120 | **NEW TO THE SET.** d10 SynMenace read `gF3 $ gF3`, so *nothing could mute it* — now `gF3 $ gM3`; check the mute actually drops it. 17 idle slots / 10 borrowed |
-| 7 | **lime_tacos** | 110 | **NEW TO THE SET.** Cymbales sol moved **d6 → d12** — Tidal 12 is **+9.8 dB hotter** than Tidal 06, so ride the fader, don't re-gain the pattern. **NEW** riser d10. ^44 still linked to d3 on purpose. 23 idle slots, least integrated track in the set. Also the 110 BPM dip mid-block |
-| 8 | perfect | 128 | all 12 orbits declared = your **free reset point**, anything can follow anything into it. No d10 riser possible |
-| 9 | gimme_acid | 160 | no d10 riser possible (12 orbits). Leaves 3 ghosts behind |
-| 10 | vague_de_crime | 120 | the reference riser. 160→120 is the second big drop |
-| 11 | you_my_sunshine | 166 | **NEW** riser d10. Your `??TRANSITION???` seam is right before this |
-| 12 | mafia_sans_serif | 160 | **NEW** riser d10. Your `?transition?` seam is right before this |
-| 13 | desire | 129 | **NEW** riser d10, plus your own edit — lpf sweep out, room 0.4 / sz 0.5 / dry 1.1 in, crushbus 2.5→3.5 |
-| 14 | the_revolution | — | no d10 riser possible (12 orbits) |
-| 15 | electric_hammer | — | **NEW** riser d10 |
-
-### The 7 new risers are all the same thing
-
-Your designated safe idiom, copied verbatim from `vague_de_crime`:
-
-```haskell
-d10 $ gF1 $ gM3 $ mask "<t f!7>" $ "risers:8"
-```
+## 3. 🎧 What only you can settle — ranked
 
-1-in-8, so it cannot run away; `gM3` mutes it, `gF1` filters it. **d10 = riser** is now
-true in 10 of 15 tracks. The one thing to judge: 1-in-8 was tuned on a 120 BPM track — ask
-whether it still reads at 160–166 (`you_my_sunshine`, `electric_hammer`).
+| # | what | why it's ranked here |
+|---|---|---|
+| 1 | **desire / REVOLUTION / electric_hammer** (#127) | never played this cycle. They are your FINALE and ENCORE — the last thing the room hears. `desire` has unheard edits *and* a new riser |
+| 2 | **take_5 d7 `# cutoff 3500`** | the muffled choir. Taste it: 2500 = warm pad, 3500 = choir, 6000 = buzz |
+| 3 | **mafia d7** | your own "FIXME ACID WEIRD NOT GOOD" — it was sharing `cut 4` + two buses with the bass. Should stop stuttering |
+| 4 | **do_it_right kick @ 1.5** | was +24 dB, a 10 dB outlier over its own bass. If it reads thin now, raise the OTHERS |
+| 5 | **sunshine d4** | both ends of the ^32 crossfade now land +14 dB instead of bulging to +24 |
+| 6 | **ouais_je_funk d10** | the scale climb is gone, replaced by a motif. Does it hook? |
+| 7 | **the new buttons** | do_it_right ^43 (hat opening) + ^44 (octave down), ouais ^42 (clap roll), sunshine ^43 (techno runner), piment ^59 (updowndown) |
 
 ---
 
-## Ghosts: 9 of 14 transitions, 18 orphans
+## 4. The new order, and its seams
 
-The two new tracks actually *helped* — `piment → ouais → lime → perfect` is four clean
-transitions in a row, the longest clean stretch in the set.
+```
+  SOUNDCHECK  quand_on_decolle
+  OUVERTURE   bombe_dj 124 → wap 133 → do_it_right 89
+  NUJAZZ      take_5 124 → piment 124 → ouais_je_funk 120 → perfect 128
+  NUIT        gimme_acid 160 → mafia 160 → sunshine 166 → vague 120
+  FINALE      desire 129
+  ENCORE      REVOLUTION → electric_hammer
+```
+
+Your reorder bought a clean seam: **vague → desire is now GHOST-FREE.** Remaining
+ghosts, worst first:
 
 ```
-  clean   bombe_dj       → wap
-  GHOST   wap            → do_it_right      d7(wap), d9(acidOto3091, vec1_acid)
-  GHOST   do_it_right    → take_5_drops     d6(daft)
-  GHOST   take_5_drops   → piment           d11(take5), d12(take5)
-  clean   piment         → ouais_je_funk
-  clean   ouais_je_funk  → lime_tacos
-  clean   lime_tacos     → perfect
-  GHOST   perfect        → gimme_acid       d6(meth_bass), d7(acidOto3092)
-  GHOST   gimme_acid     → vague_de_crime   d9(molotov), d11(vocal_bordel), d12(molotov)
-  GHOST   vague_de_crime → you_my_sunshine  d7(crimewave)              ← your ??TRANSITION???
-  GHOST   you_my_sunshine→ mafia            d6, d9, d11 (no_sunshine)  ← your ?transition?
-  clean   mafia          → desire
+  GHOST  gimme_acid → mafia        d9(molotov), d11(vocal_bordel), d12(molotov)
+  GHOST  REVOLUTION → hammer       d7(FMRhodes1), d8(jungle_breaks), d12(like_sugar)
+  GHOST  sunshine   → vague        d9, d11 (no_sunshine)
   GHOST  desire     → REVOLUTION   d6(aeolian, superzow)
-  GHOST   REVOLUTION     → electric_hammer  d7(FMRhodes1), d8(jungle_breaks), d12(like_sugar)
+  GHOST  mafia      → sunshine     d7(acidOto3091)
+  clean  vague      → desire
 ```
 
-Under pressure the answer is `hush` between the two. Both seams you marked with `??` are
-ghosting seams — probably not a coincidence, and worth knowing before you fix the order.
+Under pressure the answer is still `hush` between the two.
+
+### Pacing — measured, not guessed
+
+Take95: **61.2 min for 11 tracks = 5:34 each.** At that rate 14 tracks ≈ **78 min**
+against a 90 min slot. You have ~12 minutes of slack, which is the first time this
+number has been comfortable.
 
 ---
 
-## What I want from your ears, ranked
+## 5. What changed under you since yesterday
 
-1. **take_5_drops d5** — did the fix restore the rhythm, or change the feel in a way you
-   dislike? It is the only change that alters an existing sound rather than adding one.
-2. **lime_tacos cymbals at +9.8 dB** — fader ride, or does the pattern want re-gaining?
-3. **The 7 risers** — right density at 160+?
-4. **The two `??` seams** — sunshine before mafia is the truth now; does it play?
-5. **Any crackle at all.** It should be gone.
+- **Every set track is now on the standard column mapping.** The remap had never been
+  systemic because it read the *generated* setlist file, which was stale — so
+  `ouais_je_funk` and `lime_tacos` were the only two it never touched. That's why you
+  found the bass on `^89`. Fixed at the tool, then applied: 22 moves across 4 tracks.
+- **`lime_tacos` is out**, `quand_on_decolle` is in as SOUNDCHECK.
+- **Two new lint rules** you asked for (bus-on-wrong-orbit = warning, shared bus =
+  error). They diagnosed mafia's acid on their first run.
+- **`do_it_right` did not compile** for part of your run — a TODO comment had eaten the
+  `3` off `gM3`. One parse error kills the whole block, so that track was silent.
 
----
+⚠️ **Pulsar clobbered `wap.tidal` when you closed it** — its stale buffer reverted a
+committed migration. Reapplied. The gate now checks for this (§6). **Before editing
+today, close and reopen any `.tidal` tab that was open yesterday** — `Window: Reload`
+does *not* do it.
 
-## Deferred by choice, your call to overrule
+---
 
-**`piment_bresilien` d10 (Menace) and `ouais_je_funk` d10 (SynMenace) did NOT move.**
-You asked me to consider it, and considering it turned up the cost: orbit N is
-simultaneously the LCXL column, the Ardour track and the cut/crushbus group. Moving them
-means two CC remaps (`^18` → `^17` / `^20`), a cut-group change, and both synths landing
-**+8.2 dB louder** on hotter Ardour channels — on material you have not rehearsed since.
+## 6. What I did to the gate
 
-And the decider: `perfect`, `gimme_acid` and `the_revolution` use all 12 orbits, so
-**d10 = riser caps at 12/15 no matter what**. Paying that cost to go 10 → 12 seemed wrong
-six days out. ~20 min if you want it.
+`tools/check-drift.sh` was documented as guarding the gate. It wasn't wired in at all,
+and wasn't executable either. Now it is, plus a check that `migrate-columns --plan`
+reports zero moves — which is what actually caught the clobber. Proven by mutation.
 
 ---
 
-## Still open on my side
+## 7. Running in the background
 
-- **#122** — does Tidal resume by itself after a watchdog recovery, or does it need a
-  ctrl+enter? Unverified. Until it is, treat watchdog recovery as *half* a recovery: if
-  the music does not come back on its own, ctrl+enter in Pulsar.
-- **#110** — the full 1h30 safety recording. If this run is being recorded, it may already
-  be done.
+**Take95 master/album export (#125).** Stem analysis is running (~24 min). Then master
+FLAC → per-track split → MP3 album. Tracklist already recovered from the gig-log:
 
-## Not gig-blocking, but you named it
+```
+  1. bombe_dj 3:53   2. wap 3:19        3. do_it_right 8:25   4. take_5 10:19
+  5. piment 4:30     6. ouais 4:54      7. lime_tacos 1:49    8. perfect 6:52
+  9. gimme_acid 5:19 10. vague 6:47    11. sunshine 5:04
+```
 
-`python3 tools/set-coherence.py --suggest` already answers "what is this track missing" —
-per orbit, with suggestions by role, including the d8 break stacks (`slice/chop`,
-`loopAt + rev`). 153 idle slots across the set: `lead=51 perc=33 fx=33 bass=18 kick=12
-breaks=6`. Your breaks are the *most* finished part of the set; the leads are where the
-empty hands are.
+Metadata will say **rehearsal take, 2026-08-02** — not a gig. No venue, no lineup.