refactor(navigation): suppress the Space hotkey by prop

Replaces the view hotkey store with a suppressSpaceHotkey prop on
ViewNavigationMenu, alongside the suppressSettings prop which already exists
for exactly this purpose: a view opting out of a navigation chrome behaviour.

The store had one advantage, that it covered the preset route without the
router naming the view. That is a single expression in PresetView, and paying
for it with a global claim was the wrong trade: the claim was lifecycle state
that had to be released on unmount to avoid stranding Space for the whole
client, where a prop simply describes the route.

Verified both routes: /teleprompter and a locked preset targeting the
teleprompter leave Space to the view, while the timer and a preset targeting
the timer still open the navigation menu with it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Cb8RVPNQ2ETPJxdy4b8CHf

apps/client/src/common/components/navigation-menu/ViewNavigationMenu.tsx

@@ -3,7 +3,6 @@ import { memo } from 'react';
 import { useSearchParams } from 'react-router';
 
 import { hasCustomParams } from '../../stores/savedViewParams';
-import { useViewHotkeysStore } from '../../stores/viewHotkeys';
 import { useViewParamsEditorStore } from '../view-params-editor/viewParamsEditor.store';
 import FloatingNavigation from './floating-navigation/FloatingNavigation';
 import NavigationMenu from './NavigationMenu';
@@ -14,10 +13,12 @@ interface ViewNavigationMenuProps {
   isNavigationLocked?: boolean;
   /** prevent showing settings */
   suppressSettings?: boolean;
+  /** leave Space to the view, for views which need the key themselves */
+  suppressSpaceHotkey?: boolean;
 }
 
 export default memo(ViewNavigationMenu);
-function ViewNavigationMenu({ isNavigationLocked, suppressSettings }: ViewNavigationMenuProps) {
+function ViewNavigationMenu({ isNavigationLocked, suppressSettings, suppressSpaceHotkey }: ViewNavigationMenuProps) {
   const [isMenuOpen, menuHandler] = useDisclosure();
   const { open: showEditFormDrawer } = useViewParamsEditorStore();
   const [searchParams] = useSearchParams();
@@ -27,9 +28,7 @@ function ViewNavigationMenu({ isNavigationLocked, suppressSettings }: ViewNaviga
     [
       'Space',
       () => {
-        if (isNavigationLocked) return;
-        // a view can take over Space for itself, see viewHotkeys store
-        if (useViewHotkeysStore.getState().spaceClaimed) return;
+        if (isNavigationLocked || suppressSpaceHotkey) return;
         menuHandler.toggle();
       },
       { preventDefault: true },

apps/client/src/common/stores/viewHotkeys.ts

@@ -1,23 +0,0 @@
-import { create } from 'zustand';
-
-interface ViewHotkeysStore {
-  /** a view has taken over the Space key and the navigation menu must not react to it */
-  spaceClaimed: boolean;
-  claimSpace: () => void;
-  releaseSpace: () => void;
-}
-
-/**
- * Lets a view take ownership of a hotkey which the view chrome also binds.
- *
- * The navigation menu binds Space at document level, but the teleprompter needs
- * it for playback, which is the convention every prompter and every foot pedal
- * follows. Prop threading does not work here because AppRouter renders
- * ViewNavigationMenu generically for presets, so the claim lives in a store
- * which the view sets on mount and clears on unmount.
- */
-export const useViewHotkeysStore = create<ViewHotkeysStore>((set) => ({
-  spaceClaimed: false,
-  claimSpace: () => set({ spaceClaimed: true }),
-  releaseSpace: () => set({ spaceClaimed: false }),
-}));