Ψ-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

src/core/view/CLAUDE.md

@@ -92,7 +92,7 @@ settled 2026-07-23):
 ## Modules
 
 - `view_mode_model` — Design View mode system: mode registry, GUID-keyed membership, folder-tree-aware visibility derivation, snapshot-based park/restore planner, the per-mode `SoloCache` it owns, JSON round-trip.
-- `solo_cache` — the per-mode solo surface: `SoloCache` (mode id → GUID → raw `I_SOLO`), the soloed-subset filter, and `planSoloRestore`, whose two drop rules (dead GUID, track parked in the incoming mode) and their reasoning live in its header.
+- `solo_cache` — the per-mode solo surface: `SoloCache` (mode id → GUID → raw `I_SOLO`), the soloed-subset filter, and `planSoloRestore`, whose two drop rules (dead GUID, not visible in the incoming mode) and their reasoning live in its header.
 - `view_tree` — pure `I_FOLDERDEPTH`→FolderTree helper for the Design View shell.
 - `mode_switch` — REAPER-free segment layout + hit-test for the bank_panel's Design View mode switch.
 - `guid_diff` — the pure, REAPER-free core of the D2 Wave-2 new-content detection: `newGuids(previous, current)` computes the GUIDs present in `current` but absent from `previous` (empty GUIDs ignored); `GuidBaseline` tracks the live GUID set across polls for one project, implementing the first-poll-after-open guard (the first `observe()` after construction/`reset()` records a baseline and reports nothing new, so pre-existing content is never mass-tagged) and re-arms via `reset()` on a detected project switch so detection never diffs across two unrelated projects.

src/core/view/solo_cache.cpp

@@ -53,11 +53,11 @@ std::size_t SoloCache::reconcile(const std::set<std::string>& liveGuids) {
 
 std::vector<SoloOp> planSoloRestore(const std::map<std::string, int>& cached,
                                     const std::set<std::string>& liveGuids,
-                                    const std::set<std::string>& parkedGuids) {
+                                    const std::set<std::string>& visibleGuids) {
     std::vector<SoloOp> ops;
     for (const auto& [guid, value] : cached) {
         if (liveGuids.count(guid) == 0) continue;
-        if (parkedGuids.count(guid) != 0) continue;
+        if (visibleGuids.count(guid) == 0) continue;
         ops.push_back(SoloOp{guid, value});
     }
     return ops;

src/core/view/solo_cache.h

@@ -73,14 +73,18 @@ private:
 // The incoming mode's restore writes, in GUID order. Two kinds of entry are dropped
 // rather than written:
 //   * a GUID absent from `liveGuids` — the track is gone (same prune rule as above);
-//   * a GUID parked in the incoming mode — a parked track is hidden and carries
-//     B_MAINSEND=0, so soloing it would silence the whole mix while contributing
-//     nothing audible, and the user would have no visible control to undo it.
+//   * a GUID absent from `visibleGuids` — not visible in the incoming mode, whether
+//     because the leaf is parked or because it is a folder parent that is itself
+//     derived-invisible there. Either way the track is hidden and (for a parked
+//     leaf) carries B_MAINSEND=0, so soloing it would silence the whole mix while
+//     contributing nothing audible, and the user would have no visible control to
+//     undo it. A show-both leaf is a member of every mode's visible set, so it is
+//     never dropped by this rule.
 // The caller consumes the whole mode entry regardless (clear-on-restore), so a
 // dropped entry does not linger as zombie state waiting on a track that may never
-// come back unparked.
+// become visible again.
 std::vector<SoloOp> planSoloRestore(const std::map<std::string, int>& cached,
                                     const std::set<std::string>& liveGuids,
-                                    const std::set<std::string>& parkedGuids);
+                                    const std::set<std::string>& visibleGuids);
 
 } // namespace reasampler::view