⚡ Bolt: [parallelize whoIsWorking queries]

[seonghobae]

💡 What: Refactored activeSessions, activeLocks, and openMergeRequests queries to execute concurrently via Promise.all.
🎯 Why: The original implementation awaited each asynchronous operation sequentially, creating an unnecessary performance bottleneck where total latency was the sum of all individual query latencies.
📊 Impact: Total fetch time for checking who is working is reduced from T_sessions + T_locks + T_merges to max(T_sessions, T_locks, T_merges).
🔬 Measurement: Verify by running pnpm exec vitest run apps/api/tests/unit/application/who-is-working.test.ts to ensure behavior remains identical. The execution time of whoIsWorking should visibly decrease under load or simulated DB latency.

---

PR created automatically by Jules for task 5429912811920169169 started by @seonghobae

[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.

[coderabbitai]

Warning

Review limit reached

@seonghobae, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 36 minutes and 55 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b46f2672-45d2-4958-8d2c-7f196591b936

📥 Commits

Reviewing files that changed from the base of the PR and between b2d68a0 and e2f8c34.

📒 Files selected for processing (2)

• .jules/bolt.md
• apps/api/src/application/who-is-working.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch perf/who-is-working-parallel-queries-5429912811920169169

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch perf/who-is-working-parallel-queries-5429912811920169169

Warning

Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption.

---

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

[seonghobae]

통합 PR에서 유효 변경만 선별해 다시 다루고 있어 이 중복/잔여 PR은 정리합니다. #39 및 vibemafiaclub/vooster#34를 기준으로 후속 검토를 진행합니다.