Ψ-W2-T1 remediation: scrim the card name over the waveform, hedge two SDK claims, fix a UTF-8-truncation empty-label bug, file the legibility DAW deferral

docs/TODO.md

@@ -194,6 +194,34 @@ Forward-looking follow-ups. Deferred by decision, not oversight — each entry r
 
 **Done looks like.** Not stated in the source beyond choosing one of the three placement options.
 
+## Confirm the card name strip reads legibly at the shipping cell size (Ψ-W2-T1 DAW verification)
+
+**Context.** Ψ-W2-T1 (`capture-naming`) put the capture's label on the docked panel card,
+across the top of the cell, drawn OVER the waveform thumbnail. Review found the strip's
+text/primary was measured at ~1:1 contrast against the accent-lime waveform fill at the
+shipping 140×84 cell size — a loud capture's peak reaches into the strip on 12 of its 13
+rows — and remediated it with a bg/base scrim behind the name (`kCardNameScrimAlpha`,
+`core/ui/theme.h`) sized so the composite clears the WCAG 4.5:1 body floor against both the
+bare fill and bare bg/cell (pinned in `test_theme.cpp`).
+
+**The wart.** The floor math is verified; the actual on-screen read is not. No `[verify —
+DAW]` deferral was filed for this track's acceptance criterion ("the panel card shows the
+name") when it landed, unlike the sibling Ψ tracks.
+
+**Intended fix.** N/A — no code change. Daniel views the docked panel with real captures
+(quiet and loud material, long and short names) and confirms the name reads over the
+waveform at the shipping cell size.
+
+**The constraint the fix MUST handle.** N/A — verification only.
+
+**Priority / risk.** Not stated. The math clears its floor with real margin (see
+`testCardNameScrimClearsBodyFloorOnItsWorstBackground`), so this is a confirmation step,
+not a suspected defect.
+
+**Done looks like.** Daniel confirms the card name reads legibly over both quiet and
+loud waveform material at the shipping 140×84 cell size, or a follow-up adjusts the scrim
+alpha and this entry is re-filed against the new value.
+
 ## A realtime capture interrupted by a project switch leaves an untracked file behind
 
 **Context (found by the tracking-consolidation review, 2026-07-30).** `DriveRealtimeCapture` detects that the active project is no longer the one the in-flight capture belongs to, aborts the backend, and drops the handle. On a `Done` abort the backend has *already* moved the recorded WAV into the **original** project's bank folder (`capture_realtime_finalize`), so a file the tool created exists with no bank entry and no ledger record.