⚡ Bolt: Optimize weekly report aggregation loops

[seonghobae]

💡 What: Combined multiple array/object reduction loops into a single thisWeekRollups pass using Object.keys() instead of Object.values().reduce().
🎯 Why: Avoids unnecessary intermediate array allocations and array method overhead during data aggregation.
📊 Impact: Reduces memory usage and CPU cycles per report generation request.
🔬 Measurement: Observe memory and response time for large projects' weekly report generations.

---

PR created automatically by Jules for task 17012732691017088122 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 19 minutes and 44 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: 831b19e4-af8d-4753-a479-c7248c4ebe49

📥 Commits

Reviewing files that changed from the base of the PR and between 220b497 and 18ada08.

📒 Files selected for processing (2)

• .jules/bolt.md
• packages/web/src/lib/server/weekly-report.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bolt-optimize-weekly-report-loops-17012732691017088122

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch bolt-optimize-weekly-report-loops-17012732691017088122

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]

최신 upstream/main 기준으로 이 PR 브랜치(bolt-optimize-weekly-report-loops-17012732691017088122)는 95개 파일의 stale diff를 포함합니다. 특히 .claude agent/skill 파일 삭제와 오래된 lockfile/env/code 변경이 섞여 있어 그대로 유지하거나 upstream에 올리면 이미 반영된 변경을 되돌릴 위험이 큽니다.

현재 큐는 upstream #30 → upstream #21 순서로 정리 중입니다. 이 PR의 아이디어가 여전히 필요하면 최신 upstream/main에서 단일 목적 브랜치로 깨끗하게 다시 추출하겠습니다. stale PR로 닫습니다.