fix(frontend): Ensure agent version is fetched when active_version_id exists

[seer-by-sentry]

Changes 🏗️

Fixes BUILDER-4HJ. The issue was that: Server-side rendering failed to retrieve the Supabase access token, causing authenticated API calls to omit the Authorization header.

• Ensures that the agent version is fetched only when creator_agent.active_version_id exists and the status code is 200.
• Enables the prefetchGetV2GetAgentByStoreIdQuery query when creator_agent.active_version_id exists.

This fix was generated by Seer in Sentry, triggered by Craig Swift. 👁️ Run ID: 2234004

Not quite right? Click here to continue debugging with Seer.

Checklist 📋

For code changes:

• I have clearly listed my changes in the PR description
• I have made a test plan
• I have tested my changes according to the test plan:
  • N/A

Example test plan

• Create from scratch and execute an agent with at least 3 blocks
• Import an agent from file upload, and confirm it executes correctly
• Upload agent to marketplace
• Import an agent from marketplace and confirm it executes correctly
• Edit an agent from monitor, and confirm it executes correctly

For configuration changes:

• .env.default is updated or already compatible with my changes
• docker-compose.yml is updated or already compatible with my changes
• I have included a list of my configuration changes in the PR description (under Changes)

Examples of configuration changes

• Changing ports
• Adding new services that need to communicate with each other
• Secrets or environment variable changes
• New or infrastructure changes such as databases

[github-actions]

This PR targets the master branch but does not come from dev or a hotfix/* branch.

Automatically setting the base branch to dev.

[sentry]

🔍 Existing Issues For Review

Your pull request is modifying functions with the following pre-existing issues:

📄 File: autogpt_platform/frontend/src/app/(platform)/marketplace/agent/[creator]/[slug]/page.tsx

Function	Unhandled Issue
MarketplaceAgentPage	ApiError: An error occurred while retrieving the store agent details Page Server Component (/(platform)/marketplace/age... Event Count: 3 Affected Users: 0

[netlify]

✅ Deploy Preview for auto-gpt-docs canceled.

Name	Link
🔨 Latest commit	f4ea9f5
🔍 Latest deploy log	https://app.netlify.com/projects/auto-gpt-docs/deploys/69046b116d1ef50008dc2e23

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[deepsource-io]

Here's the code health analysis summary for commits e6fb649..f4ea9f5. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
JavaScript	✅ Success	🎯 2 occurences resolved	View Check ↗
Python	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[AutoGPT-Agent]

Thank you for submitting this PR to fix the issue with server-side rendering and token retrieval. The changes look reasonable and well-focused on the problem described.

However, before this can be approved for merging, please complete the checklist in the PR description by checking the appropriate boxes. Specifically:

• Check the box for "I have clearly listed my changes in the PR description"
• Either provide a test plan and check those boxes, or check the N/A box if no test plan is needed

The PR looks good otherwise, with a clear description of the issue being fixed and changes that appear to address the problem directly.

[AutoGPT-Agent]

Thank you for submitting this PR to fix the SSR issue with agent version fetching. The changes look straightforward and well-scoped.

However, I noticed that you haven't checked off the items in the checklist. Please mark the following items:

• I have clearly listed my changes in the PR description
• I have made a test plan

You can mark the test plan as N/A since you've indicated that, but the checkboxes themselves need to be checked for the PR to be compliant with our guidelines.

Otherwise, the code changes look good - ensuring the agent version is only fetched when necessary conditions are met should resolve the server-side rendering issue described in the Sentry report.