[Superseded] ⚡ Bolt: timeline chart rendering performance

[seonghobae]

Superseded

Closed without merge because current developmental already contains the durable O(N+M)-style timeline aggregation boundary. At base snapshot 4f8796ec8c3a8d130136029650705714724cb0ac, SessionTimelineChart uses a documented buildChartData() helper that sorts local usage/tool copies and consumes tool events through a single forward cursor rather than filtering the complete tool-event list for each usage point.

This PR is anchored to stale base 9ef092b9979d46b96063701e706521d21407d6a9, exact head 46a5e19eb872a8960b711f73d67fb79bc7f56b6e, is non-mergeable, and carries eleven changed files for the same primary objective. The broad stale diff would reintroduce competing implementation and unrelated-change risk. No checks, reviews, or approvals from this head transfer to current development.

Any residual Date-parsing or allocation improvement should be rebuilt as a focused diff on the live base with fresh exact-head verification.

[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, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 19 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

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.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 4fdd22b7-4da6-4d62-a3ae-312aa7087ee9

📥 Commits

Reviewing files that changed from the base of the PR and between e04e50e and 46a5e19.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (3)

• .jules/sentinel.md
• package.json
• pnpm-workspace.yaml

📝 Walkthrough

Walkthrough

도구 호출을 사전 정렬하고 two-pointer 방식으로 usage별 관련 도구를 수집하도록 변경했습니다. 또한 Semgrep 억제 주석과 패키지 버전 override 및 점검 기록을 갱신했습니다.

Changes

도구 요약 계산 최적화

Layer / File(s)	Summary
정렬 기반 도구 구간 수집 packages/web/src/components/dashboard/session-timeline-chart.tsx	요약 포맷팅과 도구 필터링을 분리하고, 정렬된 도구 호출을 usage 구간별로 순차 수집해 toolSummary를 생성합니다.

Semgrep 억제 주석

Layer / File(s)	Summary
정적 분석 억제 지점 추가 .claude/skills/.../probe_harness.py, packages/cli/src/**	HTTP probe, hook, 프로젝트 설정, transcript 테스트의 기존 코드에 nosemgrep 주석을 추가합니다.

의존성 override 갱신

Layer / File(s)	Summary
취약점 대응 버전 고정 package.json, pnpm-workspace.yaml, .jules/sentinel.md	minimatch 및 여러 패키지의 강제 버전을 갱신하고 관련 점검 기록을 추가합니다.

Estimated code review effort: 3 (Moderate) | ~25 minutes

Sequence Diagram(s)

sequenceDiagram
  participant UsageTimeline
  participant ChartData
  participant ToolFormatter
  UsageTimeline->>ChartData: usage timestamps
  ChartData->>ChartData: sort calls and collect relevantTools
  ChartData->>ToolFormatter: relevantTools
  ToolFormatter-->>ChartData: toolSummary

Loading

Possibly related PRs

• ContextualWisdomLab/argos#337: 동일 컴포넌트에서 두 포인터 방식으로 도구 요약을 구성합니다.
• ContextualWisdomLab/argos#338: 동일한 probe 코드와 점검 기록에 Semgrep 억제 변경을 적용합니다.
• ContextualWisdomLab/argos#350: 동일 컴포넌트에서 정렬 및 two-pointer 기반 toolSummary 계산을 변경합니다.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	제목이 타임라인 차트 렌더링 성능 개선이라는 핵심 변경 사항을 명확하고 간결하게 잘 요약합니다.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Fix failing CI checks

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bolt-performance-optim-timeline-1663549892591885913

---

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