docs(backlog): visuals done — and the correction needed correcting

'The refs work as designed' held only on the box that authored the image.
resolve() never tried the derived twin when the absolute source was absent, so
every ref resolved to null on the XPS24 with the mp4 already synced. 0 of 5
targets resolved before the HUD fix, 5 of 5 after.

backlog.md

@@ -2044,38 +2044,44 @@ url: "/home/pln/Work/Art/GLITCHWAVE/outputs/bg_live4.gif"
 Floated during the session that got rose_rouge playing, not done. Full context:
 `armada/tasks/completed-archive.md` (top entry) + `docs/2026-09-06-ardour-fresh-jig.md`.
 
-## Visuals last mile — it is a SYNC, not a restructure
-
-**Correction (2026-09-06, after xps22 came up).** The entry here previously said
-"one home `visuals/scenes/`, compress the gifs, rewrite the 16 refs
-repo-relative so a fresh clone gets visuals like it gets code". All three were
-wrong, and two were already decided the other way:
-
-- `visuals/scenes/` **already exists** on xps22 — 14 mp4s, 197 M — and the HUD's
-  `scenesDir` default already points at it (`package.json:101`).
-- The gifs are **already compressed**: `rose_bloom{,_fast,_noir,_rebloom}.mp4`
-  are 65-204 KB, encoded 2026-08-29.
-- Committing them was **deliberately rejected**: `.gitignore:53-56` ignores
-  `visuals/scenes/` with the reason written in.
-- The "16 dangling `-- url:` refs" are **working as designed**. See
-  `scenes.js:_preferDerived()`: the header points at the SSOT source (a
-  GLITCHWAVE gif, a Downloads loop), the source stays put, and the HUD
-  substitutes the derived `<stem>.mp4` from scenesDir. Nothing to rewrite.
-
-So the only real gap is that this box lacks the derived media, correctly, because
-it is gitignored. **Remaining work: finish the copy.** The first attempt got 3 of
-14 files (7.2 M) before xps22 dropped off the network mid-transfer, dying on the
-120 MB `decollage.mp4`; `rose_bloom*` did NOT land. Retry with `-H --partial`:
-`decollage.mp4` and `decolle.mp4` are hardlinks of the same 120 MB file, so `-H`
-alone cuts the transfer from 197 M to ~77 M.
-
-    rsync -aH --partial --info=progress2 \
-      xps22.local:'~/Work/Sound/Tidal/visuals/scenes/' visuals/scenes/
-
-Also absent on this box and worth a decision: `~/Work/Art/GLITCHWAVE` (3.1 G, 24
-gifs, 18 mp4s) is the SSOT *source* tree, needed only to re-run
-`npm run scenes:ingest`, never to play. Do not sync it to the gig laptop unless
-we intend to author scenes there.
+## Visuals last mile — DONE 2026-09-06
+
+Two corrections happened here, and both are worth more than the task was.
+
+**First**, the plan in this slot ("one home `visuals/scenes/`, compress the
+gifs, rewrite the refs repo-relative") proposed three things that were already
+done or already decided against: the home exists and is the HUD's `scenesDir`
+default (`package.json:101`); the gifs were compressed 2026-08-29
+(`rose_bloom*.mp4`, 65-204 KB); and committing them was deliberately rejected
+in `.gitignore:53-56` with the reason written in. A fence got kicked before
+anyone read why it was there.
+
+**Second**, the correction was itself half-wrong. "The refs work as designed,
+nothing to rewrite" is true only on the box that authored the image.
+`scenes.js:resolve()` tried an absolute spec and nothing else, and
+`_preferDerived()` — the twin lookup — is only reached through a source that
+EXISTS. So on the XPS24 every ref resolved to null with the mp4 sitting right
+there, and the derived-twin mechanism was quietly conditional on being the
+machine that made the gif.
+
+Fixed in the HUD (`pulsar-parvagues-hud` 78b1755, **committed not pushed** —
+that repo is on `main`): an absolute miss falls back to the stem against
+scenesDir, the name `scene-ingest.cjs` already writes. SSOT design untouched;
+it just stops requiring the SSOT to be local. Measured over the real corpus:
+**0 of 5 distinct scene targets resolved before, 5 of 5 after**, and a target
+with no twin still resolves to null.
+
+Media synced: `visuals/scenes/`, 13 mp4s. Use `-H` — `decollage.mp4` and
+`decolle.mp4` are hardlinks of one 120 MB file, so the 197 M source tree lands
+as 124 M:
+
+    rsync -aH --partial xps22.local:'~/Work/Sound/Tidal/visuals/scenes/' visuals/scenes/
+
+Still open, and a deliberate choice rather than an oversight:
+`~/Work/Art/GLITCHWAVE` (3.1 G) is the SSOT *source* tree. It is needed only to
+re-run `npm run scenes:ingest` for a NEW scene, never to play one. Do not sync
+it to the gig laptop unless we intend to author scenes there — which is also
+the answer to "why was it in Downloads": authoring happens on xps22.
 
 ## Sound / mix
 - ~~**`Tidal 12` fader is at `-inf dB`**~~ **DONE, and the framing was wrong.**