docs(board): second pre-compact — R2 closed, four decisions, four next moves

Refreshes the resume state. The R1-R5 block from the first pre-compact is now
partly stale — R2 closed (PLN raised the faders and saved; check-mix reports all
12 orbits reaching master), both R5 test items fixed, and the suffix question
answered by evidence rather than taste.

Three things landed after those resume points that a cold reader needs: pytest
tools/tests/ had been running ZERO tests because one file's module-level
sys.exit aborts collection, and behind that invisibility the OPAL setlist's
first track was a soundcheck, so every tool reading it believed the set had 16
tracks opening on Quand on décolle. Both fixed; suite is 274 green in one
command.

Separated what is genuinely PLN's from what is merely undone, because that
distinction is the whole value of this block. Four decisions block everything
(--go on the 14, /desire specifically, CosmicFest tone, gig page as-performed vs
as-released) plus one ears question about nine faders moving where four were
broken. Four next moves need nobody, and the first is a 15-minute audit of
whether anything consumed the phantom setlist positionally.

TASKS_DUMP.md

@@ -2215,3 +2215,95 @@ were ever derived from the setlist rather than from measured boundaries. OPAL is
 safe (its v4 came from ear-verified boundaries) and CosmicFest came back clean
 from the generation lens, so this may be harmless — but it is unverified, and the
 class of error is exactly `feedback_report_the_whole_timeline`.
+
+---
+
+# 🧭 BOARD STATE — 2026-09-05, second pre-compact (SUPERSEDES the R1–R5 block above)
+
+The R1–R5 resume points earlier in this file were written mid-session. **R2 is now
+closed** and three new things landed after them. Read this block, not that one.
+
+## ✅ Closed since those resume points were written
+
+| was | now |
+|---|---|
+| R2 · Ardour faders at -inf (3rd recurrence) | **CLOSED by PLN** — *"done and ardour saved and closed :)"*; `check-mix: OK — all 12 Tidal orbits reach the master bus` |
+| R5 · `test_orphan_orbits` fails 16-vs-13 | **FIXED** `21f83b5` — stale fixture, counts now DERIVED from the setlist file |
+| R5 · `test_lcxl3_display` collects 0 | **FIXED** `21f83b5` — 30 real tests, proven able to fail |
+| (undiscovered) `pytest tools/tests/` ran ZERO tests | **FIXED** `e8f7066` — **274 passed, 2 skipped, 0 failed** in one command |
+| (undiscovered) OPAL setlist's first track was a soundcheck | **FIXED** `e8f7066` — 15 entries, opens on Ceci n'est pas Une Bombe |
+| Open: OPAL suffix policy | **ANSWERED by evidence** — suffix new uploads; see `dfab5ca` and the CosmicFest section |
+
+## 🔴 THE FOUR DECISIONS THAT ARE PLN'S, AND NOTHING ELSE MOVES WITHOUT THEM
+
+1. **`--go` on the 14 OPAL deletes.** Manifest generated, dry-run clean (14 deletable,
+   0 refused), artwork archived, every target private and every one still has its FLAC
+   on disk. ⚠️ **Transport unproven** — no DELETE has ever been issued from this
+   codebase against api-v2; if it 403s, wire `delete_manifested()`'s existing `deleter`
+   callable to `scbrowser.Browser.api("DELETE", …)`.
+   Command in R1 above. **Do not pass `--go` without his word.**
+2. **`/desire` specifically** — the one manifest entry that is not a duplicate. No v4
+   replacement exists, so deleting it removes Desire from SoundCloud entirely. FLAC safe
+   locally. Cut from the release ≠ off the platform.
+3. **CosmicFest tone approval** — still not landed, and the board's rule is do not
+   upload its split before it does. The 2 missing tracks are a re-run, not a new
+   release decision, but they belong to a release he has not signed off.
+4. **OPAL gig page: as-performed (15, Desire included) or as-released (14)?** Desire's
+   row carries an unverified v3 timecode until this is answered.
+
+Plus one **ears** question, not a decision: **were orbits 02–06's −8 to −10 dB trims
+deliberate gain staging, or drift?** Nine of twelve faders moved when four were broken;
+02–06 went from a coherent −8/−10 dB set to roughly unity (~9 dB balance shift, master
+unchanged at −0.2). One listen decides it. Hypothesis (NOT established): the LCXL3's
+faders are absolute-position, so touching one snaps the DAW value to the pot — and note
+the board's "v3 retires pot-pickup" claim covers the endless ENCODERS only; the eight
+faders are still absolute, so that class survives the upgrade.
+
+## 🟢 NEXT, in order, all of it unblocked and doable without PLN
+
+1. **`setlist_to_segments.py` audit (~15 min, do this first).** The setlist parser had a
+   phantom at index 0 for a month, so anything consuming `entries()` **positionally**
+   was shifted by one. Check whether any gig's segments were ever derived from the
+   setlist rather than from measured boundaries. OPAL is safe (ear-verified v4) and
+   CosmicFest came back clean from the lens, so this may be harmless — **but nobody has
+   checked**, and the class of error is `feedback_report_the_whole_timeline`.
+2. **R4 · one parser per gig-track concept.** `tools/gig-metadata.py` vs
+   `armada/tide-table/build_gig_tracksjson.py`: the latter never computes the
+   `styleDistribution` that `LiveEvent.js` renders, and they disagree on REVOLUTION's
+   style (jazz vs nujazz). Until one owns the concept and the other calls it, use
+   `gig-metadata.py --only-played` for a REGEN of an existing gig.
+3. **R3 · 14 uncatalogued gigs** (25 catalogued vs 39 gig pages). The hard part is the
+   track↔gig mapping, not the parsing — `feedback_locate_matrix_method`, ear-gate it,
+   never trust a low-z locate. Also still open from the reconciler: 3 DIVERGENT tracks
+   (Blue Gold, Love First, Clameur) and 2 conflicts (Atari-ght, Ere de Jeu).
+4. **`mix/` vs tidal-ears' mastering CLI** — two toolboxes that both master a set
+   (`a14aee7` committed it so the overlap is visible in one tree). PLN's call which is
+   the spine, but the comparison can be written up for him.
+
+## 🟡 Small, named, still true
+
+- **Three captain's logs claim `log: 025`** (which `025-fifteen-intros` owns) and use
+  dated filenames against the README's `NNN-slug.md`. Their 2026-08-14 dates land them
+  BEFORE 039, so the next free numbers read out of order. PLN's archive, PLN's spine.
+- **`TODO.md` deliberately untracked** — a paused 2026-06-22 board would be a second
+  answer to "what's next". Fold its live items in and delete, or keep it out of git.
+- **www `feat/paradiso`**: 1 unmerged commit (`b130192`).
+- **`claude/rig-autoconnect-regression`**: 1 unmerged commit (`a4da75e`, *"the two
+  reconcilers that lived only in $HOME — five orbits reached no Ardour track"*). Five
+  orbits reaching no track and four orbits at -inf may be the same wound — worth one
+  look before merging or discarding.
+
+## ⚠️ SHARED-CHECKOUT HAZARD (unchanged, still the top trap)
+
+`/home/pln/Work/Sound/Tidal` is on **`claude/rig-streamline`** — another live session,
+tip moving (last seen `151c3d9`). **`git push origin master` from a non-master HEAD
+exits 0 and pushes nothing.** Verify HEAD before every commit; verify the push moved
+the remote (`git rev-list --left-right --count origin/master...master` must read `0 0`).
+Commit to master through a temporary worktree; never `git checkout` in that tree.
+Because it is on that branch, `pytest tools/tests/` still reports "no tests ran"
+**there** — the fix is on master and that is expected, not a regression.
+
+That branch also holds uncommitted duplicates of work already on master
+(`tools/check-mix.py`, `tools/gig-log.py`, `tools/ardour_session.py`,
+`armada/tide-table/build_delete_manifest.py`) — `rm`/restore before rebasing or they
+double-apply. And PLN's own live `.tidal` edits, which are not ours.