fix: add max_clarification_rounds parameter passing from frontend to backend (#616)

Bug Fix
This PR fixes the issue where max_clarification_rounds parameter was not being passed from the frontend to the backend, causing a TypeError: '<' not supported between instances of 'int' and 'NoneType' error.

Technical Details
The issue was that the frontend was not passing the max_clarification_rounds parameter to the backend API, causing the backend to receive None values and fail during comparison operations. This fix ensures the parameter is properly typed and passed through the entire request chain.

web/src/core/api/chat.ts

@@ -19,6 +19,7 @@ export async function* chatStream(
     resources?: Array<Resource>;
     auto_accepted_plan: boolean;
     enable_clarification?: boolean;
+    max_clarification_rounds?: number;
     max_plan_iterations: number;
     max_step_num: number;
     max_search_results?: number;

web/src/core/store/store.ts

@@ -105,6 +105,7 @@ export async function sendMessage(
       resources,
       auto_accepted_plan: settings.autoAcceptedPlan,
       enable_clarification: settings.enableClarification ?? false,
+      max_clarification_rounds: settings.maxClarificationRounds ?? 3,
       enable_deep_thinking: settings.enableDeepThinking ?? false,
       enable_background_investigation:
         settings.enableBackgroundInvestigation ?? true,