fix: only block server start for profile validation errors

The ServerStatusToggle was using rawConfigErrors.length > 0 which
included all config errors like genai-disabled. This caused the
Start button to be disabled even when the profile was valid.

Now filters to only profile validation errors:
- no-active-profile
- invalid-label-selector
- no-custom-rules

This fixes the e2e test failure where the Start button was disabled.

Signed-off-by: Ian Bolton <[email protected]>

Author: ibolton336

webview-ui/src/components/AnalysisPage/AnalysisPage.tsx

@@ -135,6 +135,15 @@ const AnalysisPage: React.FC = () => {
 
   const selectedProfile = profiles.find((p) => p.id === activeProfileId);
 
+  // Profile validation errors that should block server start
+  const profileValidationErrors = rawConfigErrors.filter(
+    (e) =>
+      e.type === "no-active-profile" ||
+      e.type === "invalid-label-selector" ||
+      e.type === "no-custom-rules",
+  );
+  const hasProfileValidationErrors = profileValidationErrors.length > 0;
+
   const [isExpanded, setIsExpanded] = useState(false);
 
   return (
@@ -160,7 +169,7 @@ const AnalysisPage: React.FC = () => {
                             isStarting={isStartingServer}
                             isInitializing={isInitializingServer}
                             onToggle={handleServerToggle}
-                            hasWarning={rawConfigErrors.length > 0}
+                            hasWarning={hasProfileValidationErrors}
                           />
                         </ToolbarItem>
                         {!isGenAIDisabled && (