fix(views): seed active view on init and state restore

Tools and rendering panels gate on currentImageID, which resolves
through activeView -> viewByID[activeView].dataID. The slice
manipulator's scroll-ref watcher used to set activeView as a side
effect on first paint, so a fresh app and pre-5.0.2 session loads
both relied on that. Removing the watcher (to stop cine playback
from fighting over the active view) left activeView undefined on
both paths, so the brush/ruler/etc. buttons stayed disabled and the
layer opacity slider never rendered.

Call ensureActiveViewIsVisible after pushing the initial layout
views and after deserializing a manifest. Fixes ~10 previously
failing e2e specs (full local wdio suite goes 23/23).

Author: PaulHax

src/store/views.ts

@@ -331,6 +331,11 @@ export const useViewStore = defineStore('view', () => {
         } as unknown as ViewInfo;
       });
     }
+
+    // Older manifests (pre-5.0.2) don't persist activeView, so the restored
+    // state can land with no active view and tools/panels gated on
+    // currentImageID never enable. Pick the first visible view as a fallback.
+    ensureActiveViewIsVisible();
   }
 
   function bindViewsToData(
@@ -353,6 +358,10 @@ export const useViewStore = defineStore('view', () => {
   firstLayout.views.forEach((viewInit) => {
     layoutSlots.value.push(addView(viewInit));
   });
+  // The slice manipulators used to set the active view as a side effect of
+  // their initial scroll-ref watcher firing. That watcher was removed so cine
+  // playback wouldn't fight over the active view, so seed it explicitly here.
+  ensureActiveViewIsVisible();
 
   watch(disabledViewTypes, () => {
     applyDisabledViewTypesFilter();