⚡ Bolt: 디렉토리 처리 루프에서 불필요한 상수 할당 및 해시 연산 제거

[seonghobae]

💡 What: process_dir 함수 내부에 있던 cssContent, css, index_bottom 문자열과 styleHash 해시 연산을 private object StaticAssets 내부로 분리하여 상수로 선언했습니다.
🎯 Why: 디렉토리를 순회하며 process_dir가 호출될 때마다 크기가 큰 문자열이 메모리에 반복 할당되고 무거운 SHA-256 연산이 불필요하게 반복되는 성능 병목이 발생했습니다.
📊 Impact: 디렉토리 처리 속도 향상, 메모리 할당 및 가비지 컬렉션 부담 감소, CPU 사용량 절약으로 크롤링(프로세싱) 속도가 크게 향상됩니다.
🔬 Measurement: ./gradlew clean test jacocoTestReport jacocoTestCoverageVerification 테스트 통과 및 프로파일러를 통한 메모리 할당 빈도 측정을 통해 확인할 수 있습니다.

---

PR created automatically by Jules for task 2894962710334745461 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: 5 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: 23149888-4a38-456c-a24a-2049199582f1

📥 Commits

Reviewing files that changed from the base of the PR and between a859a11 and 9eb11ed.

📒 Files selected for processing (2)

• .jules/bolt.md
• src/main/kotlin/html4tree/main.kt

---

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