fix(modes): resolve react-hooks/exhaustive-deps in window message listener

Use a stable ref to hold the latest switchMode and avoid capturing it in the window "message" listener closure:
Add a switchModeRef updated via useEffect; call switchModeRef.current in the importModeResult fallback instead of switchMode
Mirrors existing handleModeSwitchRef/customModesRef pattern to keep handler stable while accessing fresh values
Prevents re-registration churn and removes the ESLint warning with no runtime behavior change

File touched:
webview-ui/src/components/modes/ModesView.tsx

Why:
The effect that registers the window event listener intentionally has an empty dependency array; directly referencing switchMode violates react-hooks/exhaustive-deps. Using a ref decouples the effect from function identity changes while preserving up-to-date behavior.

Author: heyseth

webview-ui/src/components/modes/ModesView.tsx

@@ -197,6 +197,12 @@ const ModesView = ({ onDone }: ModesViewProps) => {
 		customModesRef.current = customModes
 	}, [customModes])
 
+	// Keep latest switchMode available inside window message handler
+	const switchModeRef = useRef(switchMode)
+	useEffect(() => {
+		switchModeRef.current = switchMode
+	}, [switchMode])
+
 	// Handler for popover open state change
 	const onOpenChange = useCallback((open: boolean) => {
 		setOpen(open)
@@ -482,7 +488,7 @@ const ModesView = ({ onDone }: ModesViewProps) => {
 						} else {
 							// Fallback: switch by slug to keep backend in sync and update visual selection
 							setVisualMode(slug)
-							switchMode(slug)
+							switchModeRef.current?.(slug)
 						}
 					}
 				} else {