Integrate v2 task api

[wintonzheng]

Important

Integrate v2 task API by adding a new Axios client, updating API calls, and renaming types and fields to align with the new API structure.

• API Client:
  • Add v2Client in AxiosClient.ts with base URL apiV2BaseUrl.
  • Update getClient() to return v2Client for version "v2".
• Type Updates:
  • Rename ObserverCruise to ObserverTask in types.ts.
  • Rename observer_cruise to observer_task in WorkflowRunStatusApiResponse.
  • Rename observer_thought_id to thought_id in workflowRunTypes.ts.
• Component Updates:
  • Update PromptBox.tsx to use v2Client for task creation.
  • Update WorkflowRun.tsx, WorkflowRunOverview.tsx, and WorkflowRunTimeline.tsx to use thought_id.
  • Update WorkflowPostRunParameters.tsx and WorkflowRunOutput.tsx to use observer_task instead of observer_cruise.

^{This description was created by for ef58dbd. It will automatically update as commits are pushed.}

[ellipsis-dev]

👍 Looks good to me! Incremental review on ef58dbd in 1 minute and 21 seconds

More details

• Looked at 240 lines of code in 10 files
• Skipped 0 files when reviewing.
• Skipped posting 2 drafted comments based on config settings.

1. skyvern-frontend/src/api/AxiosClient.ts:32

• Draft comment:
  The removeAuthorizationHeader function only checks if the Authorization header is present in client before deleting it from both client and v2Client. Consider checking for the header in both clients separately to avoid unintended deletions.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable:
  The comment raises a valid point about potential unintended deletions, but is it actually a problem? Both clients are initialized the same way, and headers are always set on both clients simultaneously in setAuthorizationHeader(). There's no way for them to get out of sync. The check is just an optimization to avoid unnecessary deletions when no header exists.
  The comment identifies a theoretical edge case where the clients could have different header states. What if some other code modifies the headers directly?
  The entire file shows a consistent pattern of treating both clients' headers identically. The API design enforces this through the exported functions, making direct header modification unlikely and unsupported.
  The comment should be deleted as it suggests a defensive coding pattern that adds complexity without providing meaningful protection against realistic scenarios.

2. skyvern-frontend/src/api/AxiosClient.ts:44

• Draft comment:
  The removeApiKeyHeader function only checks if the X-API-Key header is present in client before deleting it from both client and v2Client. Consider checking for the header in both clients separately to avoid unintended deletions.
• Reason this comment was not posted:
  Marked as duplicate.

Workflow ID: wflow_zDSVZej4hmzQKSKr

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.