⚡ Bolt: [Performance] Cache decorated node data with WeakMap to prevent re-renders on drag

[seonghobae]

💡 What (어떤 작업을 했나요?)
React Flow의 nodes 배열이 갱신될 때 파생 데이터(검색 하이라이트 등)를 생성하는 visibleNodes 계산 로직에 WeakMap 캐시를 도입했습니다.

🎯 Why (왜 이 작업이 필요한가요?)
기존에는 노드를 드래그하여 위치만 변경되더라도, App.tsx 내의 visibleNodes가 useMemo를 통해 다시 계산되면서 모든 노드의 data 객체를 새로 생성했습니다.
새로 생성된 객체 참조로 인해 커스텀 노드 컴포넌트(TableNode.tsx)의 React.memo 얕은 비교(prev.data === next.data)가 깨지게 되어, 60fps로 발생하는 드래그 이벤트마다 전체 ERD 캔버스의 모든 테이블 노드가 심각한 불필요한 리렌더링을 겪는 병목 현상이 발생했습니다.

📊 Impact (어떤 효과가 있나요?)

• 리렌더링 최소화: 원본 node.data의 참조를 WeakMap의 키로 사용하여 이전과 동일한 파생 데이터를 반환하므로, React Flow가 노드 위치만 업데이트할 때 커스텀 노드의 리렌더링을 완벽히 건너뜁니다.
• 메모리 효율 및 가비지 컬렉션 부담 감소: 드래그할 때마다 수백/수천 개의 새로운 데이터 객체가 생성되는 것을 방지합니다.

🔬 Measurement (어떻게 확인할 수 있나요?)

• 개발자 도구의 React Profiler를 사용하여 노드를 드래그할 때 ERD 캔버스의 모든 테이블에 대해 "Rendered" 항목이 발생하는지 검사할 수 있습니다. 최적화 이후에는 위치만 변경되고 내부 노드는 렌더링되지 않습니다.
• 모든 테스트(pnpm run test --coverage)가 성공적으로 통과함을 확인했습니다 (100% 커버리지).

---

PR created automatically by Jules for task 13676382864250301798 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, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 27 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: 3e22377a-39ad-4b7b-b3c1-a6286fa34cdd

📥 Commits

Reviewing files that changed from the base of the PR and between 72afe6d and 82e68b4.

📒 Files selected for processing (15)

• .jules/bolt.md
• fix_plan10.txt
• fix_plan11.txt
• fix_plan12.txt
• fix_plan13.txt
• fix_plan14.txt
• fix_plan15.txt
• fix_plan3.txt
• fix_plan4.txt
• fix_plan5.txt
• fix_plan6.txt
• fix_plan7.txt
• fix_plan8.txt
• fix_plan9.txt
• frontend/src/App.tsx

---

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

[seonghobae]

This overlapping WeakMap optimization is consolidated into #693, which is the canonical reviewed branch for derived node-data identity and snapshot-polling behavior. Closing this duplicate avoids conflicting App.tsx implementations and prevents the temporary fix_plan*.txt artifacts from entering the protected branch.

[google-labs-jules]

This overlapping WeakMap optimization is consolidated into #693, which is the canonical reviewed branch for derived node-data identity and snapshot-polling behavior. Closing this duplicate avoids conflicting App.tsx implementations and prevents the temporary fix_plan*.txt artifacts from entering the protected branch.

Understood. Acknowledging that this work is consolidated into #693 and is now obsolete. I will stop work on this PR.