docs: the performing session is 'Tidal Live', not 'Tidal Multi'

PLN: 'wtf tidal multi? we made everytihng on tidal live remember that please'. He was
right and this line was the source of the error: check-mix.py had hardcoded the Tidal
Multi path, so it parsed a stale archive session and confidently reported five faders at
-inf that were actually up in the live session. A mixer auditor reading the wrong mixer is
worse than no auditor.

Both sessions are real — Tidal Multi still holds the ~398 G of historical per-orbit
recordings — so this documents the distinction rather than renaming one away.

CLAUDE.md

@@ -17,7 +17,11 @@ ParVagues' main livecoding workspace.
 - **`../tidal-ears/`** — audio analysis + **post-prod mastering** tooling
   (Python). See `../tidal-ears/MASTERING.md` for the canonical mastering
   recipe; `tidal-ears master {analyze,boundaries,mix}` is the workflow.
-- `../Ardour/Tidal Multi/` — single Ardour session, records all orbits as stems
+- `../Ardour/Tidal Live/` — **THE session used for performing** (records all orbits as
+  stems). This is the one to inspect for faders/routing; `tools/check-mix.py` resolves it
+  from the running Ardour process. Do not confuse it with `../Ardour/Tidal Multi/`, the
+  older archive session holding the historical per-orbit recordings — auditing that one as
+  if it were live produced a confidently wrong fader report on 2026-07-28.
 - `../Prod/` — Audacity projects + rendered masters
 - `../../Tools/pulsar-parvagues-hud/` — Pulsar HUD package