docs(log): 043 — the four decisions parked for PLN, and where the branch really is

PLN folded tired and asked for the open questions written down rather than
answered. Each of these would change how the rig sounds or what audio exists, so
none of them is mine to guess:

  1. Tidal 10 sits 5.5 dB under baseline — restore, or capture as the new intent?
  2. something_about_drums' grid migration carries an overflow whose remedy is to
     comment out d3's live lines. Musical change, not a renumbering.
  3. 24 dead Take101 sources are confirmed unrecoverable and ready to drop; the
     apply needs Ardour quit, by the tool's own design.
  4. The Freebox mirror is 7 days stale and today's Take102 exists only on the
     laptop. Given the Freebox is the declared SSOT for audio, that is the real
     risk on the list, and the reason the space-reclaim thread stayed untouched.

Also records the deliberate branch/worktree split so a cold reader does not
'fix' it: origin/claude/rig-streamline is 779cf17d (merged), the shared main tree
is still 5468507b because it holds a peer session's uncommitted check-mix.py and
gig-log.py edits, and the live rig runs from that main tree. The merge lives in
../Tidal-wt-merge where the suite is green.

armada/tasks/043-open-decisions.md

+---
+log: 043
+title: "Four decisions parked for PLN, and where the branch actually is"
+date: 2026-09-05
+task: "n/a — resume point"
+tags: [rig, gate, ardour, resume]
+shareable: false
+---
+
+## Cap (what & why)
+
+PLN folded tired and asked for the open questions to be written down rather than
+answered. These are the things that are NOT code problems — every one of them
+needs a human judgement, and guessing at any of them would change how the rig
+sounds or what audio exists.
+
+## Prise — the four decisions
+
+**1. Fader baseline: `Tidal 10` is 5.5 dB down.**
+`tools/fader-baseline.py --check` → `Tidal 10  0.1 dB   baseline 5.6 dB`. One
+fader, nothing else drifted. Two answers, both one command:
+- it was a mistake → `tools/fader-baseline.py --restore` (Ardour must be closed)
+- those are the levels you want → `tools/fader-baseline.py --capture`
+Do NOT auto-restore. The last time a fader report was trusted without asking, it
+was measuring the archive session. Blocks gig-up.
+
+**2. `something_about_drums.tidal`: the grid migration would silence part of d3.**
+`migrate-columns.py --plan` wants 5 moves in this file plus **1 overflow** —
+d3's `^44` has no slot in the new grid. The tool's remedy for an overflow is to
+comment out every live line of that orbit and head it with a FIXME. That is a
+musical change, not a renumbering, so it was deliberately left alone (the other
+three files were migrated in `9381e22`). Either rewire d3's `^44` onto a free
+control by hand, or accept the FIXME. Blocks gig-up's "surface grid intact".
+
+**3. The Missing File modal: 24 dead sources, ready to drop, needs Ardour closed.**
+Confirmed unrecoverable: all 24 are Take101 (12 orbits × L/R), absent locally and
+absent from the Freebox mirror. That take's `.mid` files survive; only the audio
+is gone. One command, once Ardour is quit:
+
+    python3 tools/ardour-drop-missing-sources.py \
+      ~/Work/Sound/Ardour/"Tidal Live"/"Tidal Live.ardour" --apply
+
+It backs the session up first, refuses while Ardour is running, and refuses if the
+Freebox is unmounted. Dry run verified: `would drop: 24 source(s), 24 region(s)`.
+
+**4. The Freebox is 7 days behind, and today's take is not on it.**
+The mirror's audiofiles dir last changed **2026-08-29 22:41** and holds up to
+Take100. Take102 was recorded today (13:36) and exists ONLY on the laptop. Given
+that the Freebox is the declared SSOT for audio, that is the real risk in this
+list — and it is why nothing in the export/peaks space-reclaim thread was touched.
+Run `fbk` (see `/mnt/freebox/PLN/_setup/CLAUDE-RUNBOOK.md`, `fbk doctor` first).
+
+## Sel — where the branch is, exactly
+
+**This is the part a cold reader will get wrong.** The shared checkout and the
+branch are out of step on purpose:
+
+- `origin/claude/rig-streamline` = **779cf17**, which includes the merge of
+  master (6678acd) and everything from this session.
+- The **main working tree** (`~/Work/Sound/Tidal`) is still at **5468507**,
+  pre-merge. It was NOT fast-forwarded, because it holds another session's
+  uncommitted edits to `tools/check-mix.py` and `tools/gig-log.py`, and pulling
+  master in would have demanded stashing their in-flight work.
+- The merge was done and tested in a worktree at `../Tidal-wt-merge`
+  (`git worktree list`). 476 tests pass there; midiviz selftest passes.
+- **The live rig runs from the MAIN tree** via `~/.local/bin` symlinks, so what is
+  playing tonight is 5468507 — verified working. The peer's midiviz close-X and
+  close-latch are on the branch but not yet live locally.
+
+To resolve: once the peer commits `check-mix.py` / `gig-log.py`, fast-forward the
+main tree to `origin/claude/rig-streamline` and restart `parvagues-bridge`,
+`midiviz` and `perf-tray`. Until then, do further work in the worktree.
+
+## Sillage
+
+Everything mechanical from the gear-failure night is closed (log 042). What is
+left is four judgements and one backup run.