fix: remove stopping_point from agent requests

The backend's ExplorerAutofixRequestSerializer overrides step to
'root_cause' when stopping_point is set, which would restart the
entire analysis instead of continuing from the current step.
Match the frontend's request format: just send step + run_id.

Author: MathurAditya724

src/lib/api/seer.ts

@@ -60,7 +60,6 @@ export async function triggerRootCauseAnalysis(
       params: EXPLORER_MODE_PARAMS,
       body: {
         step: "root_cause",
-        stopping_point: "root_cause",
       },
     }
   );
@@ -125,7 +124,6 @@ export async function triggerSolutionPlanning(
       params: EXPLORER_MODE_PARAMS,
       body: {
         step: "solution",
-        stopping_point: "solution",
         run_id: runId,
       },
     }

test/lib/api-client.seer.test.ts

@@ -71,7 +71,6 @@ describe("triggerRootCauseAnalysis", () => {
 
     expect(capturedBody).toEqual({
       step: "root_cause",
-      stopping_point: "root_cause",
     });
   });
 
@@ -228,7 +227,6 @@ describe("triggerSolutionPlanning", () => {
     expect(capturedRequest?.url).toContain("mode=explorer");
     expect(capturedBody).toEqual({
       step: "solution",
-      stopping_point: "solution",
       run_id: 12_345,
     });
   });