⚡ Bolt: [optimize gateway fetch concurrency]

[bobdivx]

💡 What: Eagerly initiates the external ZimaOS sessions fetch at the start of the dashboard health API route, instead of sequentially waiting for local DB and filesystem tasks.
🎯 Why: Resolves a bottleneck where the external network call blocked the response unnecessarily, maximizing concurrent execution in the handler.
📊 Impact: Reduces total API response time for the dashboard poll.
🔬 Measurement: Verify tests pass and visually inspect dashboard load latency.

---

PR created automatically by Jules for task 5440750099178278998 started by @bobdivx

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
forge	Ready	Preview, Comment	May 29, 2026 5:38pm

[gemini-code-assist]

Code Review

This pull request optimizes the response time of the dashboard projects health API route by initiating the external fetch fetchZimaOSSessionsPayload concurrently at the start of the handler. Feedback suggests improving the error handling of this promise by returning a fallback payload object in the .catch() block instead of using a dummy catch handler, which avoids throwing an exception during the subsequent await.

[gemini-code-assist]

Instead of attaching a dummy .catch(() => {}) handler that does nothing, it is cleaner and more robust to catch the rejection and return a fallback ZimaOSSessionsPayloadResult object. This prevents await zimaosSessionPromise from throwing an exception later in the handler, allowing the error to be handled gracefully through the existing oc.ok and oc.error checks rather than relying on the outer try/catch block.

  const zimaosSessionPromise = fetchZimaOSSessionsPayload(email).catch((err) => ({
    ok: false,
    status: 500,
    data: null,
    error: err instanceof Error ? err.message : String(err),
    attempts: [],
  }));