Ψ-W1-T2 review remediation: solo restore drops on visible-in-target, not parked; N-mode segments read dead when unroutable

Fixes a hidden-parent solo replay that could silence the mix. Also closes the N-mode segment silent no-op, amends the invariant comment, trims view.cpp under 600 lines, hedges two SDK inferences, drops a dead null-check.

src/core/ui/CLAUDE.md

@@ -95,7 +95,7 @@ L7 sub-pass, 2026-07-27):
 - `theme` — pure palette module: role→color mapping, REAPER-grey neutral ladder + the pastel accent system, the keyboard strip's spectral ramp, WCAG contrast-floor helpers + `compositeOver` (the effective color of a translucent fill, so alpha overlays are testable). Only the ramp's MID stop is its own constant; lo/hi are still aliases of `accent/primary`/`accent/tertiary`, so a categorical accent move CAN still reorder the ramp — `testSpectralRampLuminanceIsMonotonic` is the build-time catch, not the structure.
 - `component_geometry` — pure button/slider/list-row geometry + hover hit-test helpers.
 - `action_bar` — pure task-grouped action-bar layout/hit-test: clusters (Capture / Placement / Maintenance / Tagging / Switching).
-- `footer_bar` — pure footer layout/hit-test: `[Arrange|Design]` mode-toggle geometry, Tail button, and Prune placement, plus `modeSegmentEnabled` — the mode segment's live/dead predicate under the playback gate (the transport bool is passed IN, so this stays REAPER-free).
+- `footer_bar` — pure footer layout/hit-test: `[Arrange|Design]` mode-toggle geometry, Tail button, and Prune placement, plus `modeSegmentEnabled` — the mode segment's live/dead predicate under the playback gate AND under whether the shell resolved a routable command id for it (both bools passed IN, so this stays REAPER-free).
 - `overflow_menu` — pure overflow-menu-button geometry/reserve/hit-test for the top-toolbar More (⋯) button.
 - `mode_enable` — pure opposite-mode enablement predicate: given the active mode, computes per-button live/disabled state for the four Item/Track × Arrange/Design tag buttons.
 - `tooltip` — pure tooltip placement + prefix-strip: strips the `ReaSampler:` display prefix from the registered action phrase; width clamped to the client rect.

src/core/ui/footer_bar.cpp

@@ -64,8 +64,8 @@ FooterHit hitTestFooterBar(int px, int py, const FooterBarLayout& layout) {
     return FooterHit::None;
 }
 
-bool modeSegmentEnabled(bool isActiveSegment, bool transportRunning) {
-    return isActiveSegment || !transportRunning;
+bool modeSegmentEnabled(bool isActiveSegment, bool transportRunning, bool routable) {
+    return isActiveSegment || (!transportRunning && routable);
 }
 
 } // namespace reasampler::ui

src/core/ui/footer_bar.h

@@ -65,7 +65,11 @@ FooterHit hitTestFooterBar(int px, int py, const FooterBarLayout& layout);
 // plays or records (shell/view::transportBlocksModeSwitch), so an unreachable segment must READ
 // dead before the click, not merely refuse on it. The ACTIVE segment stays live regardless: it
 // fires a reapply, which is never gated, and dimming the mode you are already in would read as
-// "this mode is unavailable" rather than "you cannot leave it right now".
-bool modeSegmentEnabled(bool isActiveSegment, bool transportRunning);
+// "this mode is unavailable" rather than "you cannot leave it right now". `routable` is whether
+// the shell resolved a live command id for this segment (the model is N-mode, the UI ships two
+// seeded ids — a third registered mode has no action to route through, so its segment must read
+// dead rather than paint live and silently no-op on click). Passed IN so this predicate — and
+// `core/ui` — stays REAPER-free, exactly as `transportRunning` is.
+bool modeSegmentEnabled(bool isActiveSegment, bool transportRunning, bool routable);
 
 } // namespace reasampler::ui